You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What would you like to be added:
When I generate SBOMs from Syft (in either CycloneDX or SPDX), the resulting SBOM files don't show the dependency hierarchies (i.e. the tree relationships between libraries) that other generators do (like the open-sbom-generator).
I want/need to be able to see, for a given vulnerable library, how it was introduced into an asset.
Ex:
Dependency 1 (has a CVE)
introduced by dep 2
introduced by dep 3
introduced by dep 4, which is a top-level library / root node.
Why is this needed:
This allows me to tell developers what libraries they specifically need to upgrade/replace in order to remediate vulns or other issues introduced.
Additional context:
The text was updated successfully, but these errors were encountered:
What would you like to be added:
When I generate SBOMs from Syft (in either CycloneDX or SPDX), the resulting SBOM files don't show the dependency hierarchies (i.e. the tree relationships between libraries) that other generators do (like the open-sbom-generator).
I want/need to be able to see, for a given vulnerable library, how it was introduced into an asset.
Ex:
Why is this needed:
This allows me to tell developers what libraries they specifically need to upgrade/replace in order to remediate vulns or other issues introduced.
Additional context:
The text was updated successfully, but these errors were encountered: