Add native SARIF output support #2062
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
Fix lint and test issue fix lint issue Fix type issue address feedbacks set explicity type Add "/" to path use snake case
…h/ansible-lint into users/yongyan-gh/sarif
ssbarnea
approved these changes
Apr 6, 2022
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
We are looking for the ability of ansible-lint tool to produce SARIF reports so the uses can upload the reports to GitHub in a custom workflow uses ansible-lint action and generate code scanning alert in the GitHub security tab for the issues it found.
The SARIF spec can be found at https://docs.oasis-open.org/sarif/sarif/v2.1.0/sarif-v2.1.0.html
Attached an example SARIF file generated with this change.
ansible-lint-results.zip
Screenshot of an example GitHub code scanning alert generated from the SARIF result:
Please review and let's know if any comment.