go: use govulncheck to detect security issues#2274
Merged
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Uses
govulncheckto check each build for known Go vulnerabilities in the source.Inspired by opentofu/opentofu#2600, this attempts to cut through the steady drip of noisy automated reports. Where most automated reports detect inclusion of a vulnerable dependency version via package manifests (
go.mod,go.sum),govulncheckanalyzes the source code for use of vulnerable symbols. This has a dramatically higher signal to noise ratio. Reports fromgovulncheckshould often be actionable and require an advisory. Anything not reported is most likely noise and does not merit an advisory.Uses the new
go toolfeatures in Go 1.24 to invoke the command.