-
Notifications
You must be signed in to change notification settings - Fork 601
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failure on SBOM from cdxgen 11.0.0 #2263
Comments
@metametadata thanks for the issue here. I've tracked down the changes in the cds schema to: If you search this page for Grype and Syft have not been updated to this latest schema. I've added this work to our backlog so we can update the schemas to the latest changes and get new versions of the tooling out. Dev note: who ever picks this up might want to look at how we do these schema updates going forward. Currently it's a manual process that has not been run in 5 months. We might want more automation to cover if something changes in the specifications. |
Not reproducible with Grype |
We're still working out some process so that grype can automatically consume updates from syft regarding any changes in how it processes/recognizes changes in the cdx specification. I'm going to leave this open for now and follow up with a comment summarizing the current state of that conflict between the tooling. |
What happened:
What you expected to happen:
No error.
How to reproduce it (as minimally and precisely as possible):
Use
cdxgen
11.0.0 to generate an SBOM frompom.xml
:Then run Grype 0.84.0:
sbom.json
:Click me
Notes
Differences between 10.10.7 (works with Grype) and 11.0.0
cdxgen
output:sbom.json
fromcdxgen
10.10.7:Click me
The text was updated successfully, but these errors were encountered: