Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Support for the SARIF (Static Analysis Results Interchange Format)
See original GitHub issueIs your feature request related to a problem? Please describe. I think integration is the name of the game today and the SARIF format (https://github.com/oasis-tcs/sarif-spec) is a standard that most static analysis tools have embraced. It would be great if Bandit could have that as well. Simply because this integrates with Github, Vulnerability Management Tools and makes results consistent
Describe the solution you’d like
Support for the sarif-spec based on the JSON spec listed here and --output and --format flags that support SARIF as an option in addition to JSON, XML, etc.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:8
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@ericwb Hi Eric. My team is planning to modify either bandit or the converter provided above so that the SARIF output includes suppression information. I see you’ve added this enhancement for 2.0.0 - is someone already working on this? How could we contribute? Thanks.
For reference, it looks like Microsoft wrote a converter here: https://github.com/microsoft/bandit-sarif-formatter