Better support SARIF ruleId attribute #5025
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
damiencarol
force-pushed
the
fix_gitleaks_sarif
branch
from
c82d42c
to
e977fc8
Compare
|
@StefanFl addressed your comments and also implemented |
StefanFl
approved these changes
Sep 7, 2021
valentijnscholten
approved these changes
Sep 8, 2021
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.
According to specification, attribute
ruleIdcould be missing from reports. (cf https://docs.oasis-open.org/sarif/sarif/v2.1.0/os/sarif-v2.1.0-os.html#_Toc34317643 )This PR allow to import reports for tools that don't emit
ruleIdproperly (like Gitleaks7.5.0which we use for a new unit tests)Work done
ruleIdwhen tools doesn't set it cleanly (missing, reference but no data, etc...)mitigationattribute