feat(ci): Add govulncheck as ci workflow #4623
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
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.
Ref #3753
Motivation
Adding the govulncheck tool to the project CI will provides more visibility on vulnerabilities of the golang code.
Description
The govulncheck looks into the dependencies but also how they are used in the code. As a result, it has been activated for any change on not only in go.mod/go.sum files but also on any golang file (*.go) changed.
It is active on PRs and main/release branches changes.
For now I decided not to use the recently created github action as I plan to see if other security tools like gosec could be added.
Release Note