-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add grype vulnerability scanner to CI #155
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
bb02c3b
to
73be8e0
Compare
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. |
I wanted a summary as a PR comment but the https://github.com/crypto-bug-hunters/bug-buster/security/code-scanning may be enough for now. |
* ci: add grype vulnerability scanner * chore: bump go version to 1.23.1 * fix: go-ethereum CVE-2024-32972 (#158)
This PR will add a scan step into the CI that will upload the SARIF output to GitHub, and it will show security alerts like the ones in this link https://github.com/crypto-bug-hunters/bug-buster/security/code-scanning?query=pr%3A155+is%3Aopen
We should define some policy on where to enforce CI to fail at a certain level of vulnerability or not.
Currently, it's configured not to fail.