chore(security): pin gitleaks 8.30.1 with sha256 verification#23
Merged
Conversation
Replace 'curl latest release' with a version- and checksum-pinned download. Removes the implicit trust in whatever 'latest' resolved to at CI time and makes the checksum bump-block visible in PR review when the version moves. Checksum from: https://github.com/gitleaks/gitleaks/releases/download/v8.30.1/gitleaks_8.30.1_checksums.txt
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
1 participant
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.
From the 2026-05-01 audit (P0.3).
Every CI run was downloading whatever the GitHub releases API resolved as
gitleaks/releases/latestat request time, no integrity check. A registry compromise or a tag-rewrite attack ongitleaks/gitleakswould silently swap the binary executed against our source tree.Change
Replace the floating
curl + grep + tarblock with a version- and SHA256-pinned download. Bumping the version forces an explicit checksum update (visible in PR review).Test plan