4 ms·
I wonder if this uses the Static Analysis Results Interchange Format (SARIF) standard internally. https://docs.oasis-open.org/sarif/sarif/v2.0/csprd01/sarif-v2
by pabs3 7y ago
I wonder if this uses the Static Analysis Results Interchange Format (SARIF) standard internally.
https://docs.oasis-open.org/sarif/sarif/v2.0/csprd01/sarif-v2.0-csprd01.html https://docs.oasis-open.org/sarif/sarif/v2.0/csprd01/sarif-v...
- greysteil 7y agoPM for GitHub Advanced Security here. We use SARIF as the input format so third party code analysis engines can easily integrate with code scanning. Their results can then be shown in the same way that scans using our own CodeQL analysis engine are displayed. Docs on how we translate each SARIF property into the code scanning display are below: https://help.github.com/en/github/finding-security-vulnerabilities-and-errors-in-your-code/about-sarif-support-for-code-scanning https://help.github.com/en/github/finding-security-vulnerabi... (The beta notice on that page is very relevant here - we wanted to build extensibility options into code scanning from its inception, but whilst it is in beta the API won't be 100% stable. We'll do our best to avoid any unnecessary churn.)