fix(ci): pin Go dev tool versions to prevent supply chain attacks#76
Merged
Conversation
Pin gofumpt, deadcode, mage, and govulncheck to specific versions instead of using @latest. This ensures CI builds are reproducible and prevents a compromised upstream from injecting malicious code. Pinned versions: - gofumpt v0.10.0 - deadcode v0.45.0 (golang.org/x/tools) - mage v1.17.2 - govulncheck v1.3.0 Closes #74 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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
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
Pin Go dev tool versions in CI workflow to specific releases instead of using @latest.
Why
Using @latest resolves to whatever version the Go module proxy returns at build time. If an attacker publishes a malicious version of any tool, all subsequent CI runs would execute it with full repository access (CWE-829).
Changes
Verification
Closes #74