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 happened:
When scanning docker:cgr.dev/chainguard/curl:latest with the sbom cataloger we are seeing the upstream package from an SBOM showing up "flat" in the SBOM. For example curl 8.12.0 and 8.12.0-r1 are both in the SPDX SBOM with 8.12.0-r1 being "Generated_from" 8.12.0.
What you expected to happen:
I would expect the "Generated_from" pacakge (8.12.0) to no be in the returned b/c the SPDX/SBOM isn't saying its in the image but that its generated from the package.
Another option (maybe better id) would be to preserve that relationship and show it in the results so its clear that 8.12.0 isnt in the SBOM but that 8.12.0-r1 was generated from it.
One other weird situation in the Wolfi spdx files - it leads to discovery of many components that are named *.yaml, for example:
git.yaml version d5b8192e47958e7c3f8173ef26701ae84a796f50
Not sure what is going on here as git with the correct version of 2.48.1-r1 is also discovered.
What happened:
When scanning
docker:cgr.dev/chainguard/curl:latest
with the sbom cataloger we are seeing the upstream package from an SBOM showing up "flat" in the SBOM. For example curl8.12.0
and8.12.0-r1
are both in the SPDX SBOM with 8.12.0-r1 being "Generated_from" 8.12.0.What you expected to happen:
I would expect the "Generated_from" pacakge (8.12.0) to no be in the returned b/c the SPDX/SBOM isn't saying its in the image but that its generated from the package.
Another option (maybe better id) would be to preserve that relationship and show it in the results so its clear that 8.12.0 isnt in the SBOM but that 8.12.0-r1 was generated from it.
Steps to reproduce the issue:
config.yaml
Environment:
The text was updated successfully, but these errors were encountered: