Conversation
|
For viz: zizmorcore/zizmor#57 will make the SARIF output slightly friendlier for GitHub's SARIF support once fixed. Right now the SARIF results are well-formed and uploaded correctly, but don't rebase correctly on top of the repo root. |
|
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. |
woodruffw
left a comment
There was a problem hiding this comment.
LGTM behaviorally. I leave it up to you whether you'd prefer I fix zizmorcore/zizmor#57 before merging here or not -- the results will show up as is, but won't be as easy to relate to existing files until that's fixed 🙂
This seems like it would be useful.
|
Dropped
May also just wait until this is fixed. |
|
I've released v0.1.3, which contains the SARIF fix. Example render: https://github.com/woodruffw/zizmor/security/code-scanning/2 |
|
Can't see, but we can re-run |
|
Cool. Let's give this a try. There are a lot of warnings though -- many of them would be difficult to address. |
|
Something that would be nice to fix is that the output on GitHub isn't quite as nice as on the command-line. For example: https://github.com/Homebrew/homebrew-core/security/code-scanning/34 Compare this with: On GitHub you don't see the recommendation to set |
Yep, this is tracked with zizmorcore/zizmor#66. I'll try and fix that with the next release. |

This tool, written by a certain @woodruffw, seems like it would be useful.
See https://github.com/woodruffw/zizmor.
Needs #195936.