Fix #9972 (Add support for SARIF output format)#6863
Conversation
|
There is no testing yet. I will see if I can integrate it into github. |
Sorry, something went wrong.
|
@mario-campos would you be interested to test/review this Cppcheck SARIF output? |
Sorry, something went wrong.
Sorry, something went wrong.
4651: very related but this is a simpler approach. 3365: I don't think this is related to the uniq/append output. |
Sorry, something went wrong.
|
I believe that we can output findings directly btw. We don't have to construct the complete report at the end. However I am not sure if that will be very useful anyway, the report is so verbose I don't think anybody would like to read the sarif output "live". I believe a minimal SARIF header would be: |
Sorry, something went wrong.
a9065ff to
a798d28
Compare
October 6, 2024 14:36
|
This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation. |
Sorry, something went wrong.
There was a problem hiding this comment.
Looks great!! Can't wait to see this merged!
I left a few comments about some missing SARIF properties, which GitHub requires. I think it would be a good idea to implement them, because I think someone will eventually try to upload the SARIF file to GitHub expecting it to work.
Sorry, something went wrong.
|
@mario-campos thanks for the comments. Can you please check again? Example output: |
Sorry, something went wrong.
|
@mario-campos please take an extra careful look on the |
Sorry, something went wrong.
mario-campos
left a comment
There was a problem hiding this comment.
Nice job! A few more finishing touches.
Also, you can validate the SARIF file at https://sarifweb.azurewebsites.net/. I've already submitted it and there's a few "issues" but I wouldn't worry about them. According to the docs, they're not required.
Sorry, something went wrong.
Co-authored-by: Mario Campos <mario-campos@github.com>
Co-authored-by: Mario Campos <mario-campos@github.com>
Co-authored-by: Mario Campos <mario-campos@github.com>
|
@mario-campos I merged it now. but please feel free to provide additional advice if there is something we can fix.. |
Sorry, something went wrong.
…6863) Co-authored-by: Mario Campos <mario-campos@github.com>
No description provided.