govulncheck to report known vulnerabilities #5199
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: CrazyMax <1951866+crazy-max@users.noreply.github.com>
github-actions
bot
added
area/hack
thompson-shaun
approved these changes
Jul 30, 2024
AkihiroSuda
approved these changes
Jul 30, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
similar to docker/buildx#2631
Runs govulncheck tool in our workflow to report known vulnerabilities that affect Go code using the Go vulnerability database at https://vuln.go.dev/ and output a SARIF report that will be uploaded to GitHub Code scanning so we have these issues reported in the Security tab like done with Docker Scout in #5184.
Atm dependabot will open a pull request when such vulnerabilities are found similar to #4786 but we often close them because it needs coordination with upstream repositories.
I suggest to disable security updates for Dependabot under https://github.com/moby/buildkit/settings/security_analysis and check issues reported in the Security tab instead with this workflow if we are ok with it:
SARIF output: https://github.com/moby/buildkit/actions/runs/10161094819/job/28098853183?pr=5199#step:4:332