ci: add govulncheck workflow#241
Merged
Merged
Conversation
Run govulncheck on pushes, pull requests and weekly to continuously scan the module set for known vulnerabilities. The tree currently reports no vulnerabilities. Signed-off-by: Gaál György <gb12335@gmail.com>
aa1ex
approved these changes
Jul 6, 2026
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.
What
Add a
Vulnerability Checkworkflow that runsgovulncheckagainst the module set.Triggers:
push/pull_requesttomain/master— catch vulnerabilities introduced by dependency or code changes.schedule(weekly) — catch newly disclosed vulnerabilities in unchanged dependencies.workflow_dispatch— manual runs.govulncheckreports only vulnerabilities that are actually reachable from the code, so it stays low-noise. The tree currently reports no vulnerabilities.New workflow file only; no code impact.