[K9VULN-2227] Add artifacts to SARIF output #568
Merged
Conversation
This file contains 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
amaanq
approved these changes
Dec 10, 2024
jasonforal
force-pushed
the
jf/K9VULN-2227
branch
from
8ea61aa to
193812b
Compare
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.
What problem are you trying to solve?
In order to add test file detection to the analyzer, we will be generating metadata about individual artifacts (in our case, only files). A way to do this within the SARIF spec is by adding the
artifactsproperty to a SARIFrunand then attaching a property bag to each artifact.What is your solution?
artifactsto the SARIF output (associating tags via a property bag will come in a future PR).Alternatives considered
What the reviewer should know