-
Notifications
You must be signed in to change notification settings - Fork 602
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
Add support for cyclonedx 1.4 and VEX #591
Labels
Comments
Syft ticket here: anchore/syft#744 |
Now that syft support for cyclonedx 1.4 is out, I believe this is unblocked. I might be able to get around to a draft PR this week. |
That would be amazing! I'm very excited about this one. |
@luhring Are there any plans to support CycloneDX 1.4 in the incoming releases ? Do you have an idea when that could happen ? Thanks :). |
@hectorj2f Just released! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
What would you like to be added: CycloneDX 1.4 was released with added support for a common vulnerability exchange format.
It would be great if grype could output its vulnerability reports in this format. This could also be helpful down the road as a standardized format to attach vulnerability data as intoto attestations.
Why is this needed: This provides a well defined standard to output and parse vulnerability information. syft already supports Cyclonedx SBOMs and this could be a great counterpart for grype.
Additional context:
More details athttps://cyclonedx.org/capabilities/vex/
https://github.com/CycloneDX/sbom-examples/blob/master/VEX/vex.json
The text was updated successfully, but these errors were encountered: