feat: add basic VEX support for SBOM and other sources #2798
+168
−1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
551fc99 to
9f34a67
Compare
Populate a single ID, `pkg:generic/<lowercase name>@<version>`, as long as we have that data in the source like an SBOM. This enables VEX files to be used to describe fixed vulnerabilities in a product described with an SBOM. Signed-off-by: Dmitrii Sharshakov <d3dx12.xx@gmail.com>
9f34a67 to
2197792
Compare
wagoodman
approved these changes
Oct 6, 2025
|
Thank you for adding a test. Should I rebase this PR to resolve conflicts to facilitate merging? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Populate a single ID,
pkg:generic/<lowercase name>@<version>, as longas we have that data in the source like an SBOM.
This enables VEX files to be used to describe fixed vulnerabilities in
a product described with an SBOM.
Fixes #2471