feat(report): add PURLs in sarif report#10722
Open
axidex wants to merge 1 commit into
Open
Conversation
Contributor
|
Hello @axidex Please first create a discussion so that we can assess how much this functionality is needed by the community.Please first create a discussion so that we can assess how much this functionality is needed by the community. Regards, Dmitriy |
Contributor
Author
|
Looks like flaky. |
Contributor
Author
|
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.
Description
Adding PURLs to Rule.Properties in SARIF output.
This brings Trivy SARIF reports to parity with Grype, which already exposes PURLs in rules[].properties.purls, so downstream tooling can correlate SARIF findings back to components in an SBOM.
PURLs are only added to vulnerability rules -- misconfiguration, secret, and license rules are unchanged.
Output
Before
After
Checklist