Add Dependency-Track VEX reporting - #103
Merged
mmacata merged 15 commits intoSep 23, 2026
Merged
Conversation
mmacata
approved these changes
Sep 23, 2026
mmacata
left a comment
Member
There was a problem hiding this comment.
Thank you a lot for this improvement!! (:
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR extends the reusable SBOM vulnerability workflow with Dependency-Track integration.
Instead of generating OpenVEX directly from the Grype results, the workflow now uses the findings identified by Dependency-Track to generate a CycloneDX VEX document. This allows the VEX analysis to be matched directly to the components and vulnerabilities known by Dependency-Track.
The workflow now:
in_triageThe existing Grype/SARIF scan and GitHub Security reporting remain unchanged.