fix(security): resolve gitleaks tag-history secrets (closes #63) - #69
Merged
Conversation
CI's actions/checkout@v4 (fetch-depth: 0) force-updates tags, so gitleaks git mode permanently rescans the abandoned pre-history-rewrite v0.2.0/v0.2.0-beta tag tips instead of main (0 leaks in 389 commits). Each of the 7 tag-only findings individually verified dead/rotated (GitHub PAT, RAGBIO_API_KEY, 2x JWT secret, Grafana/Prometheus creds) and added to .gitleaksignore with per-entry justification -- no blanket suppression. scripts/secret-scan.sh now passes clean (450 commits scanned, no leaks found). Adds SECRET_SCAN_CI_INVESTIGATION.md (root-cause diagnosis) and SECRET_SCAN_RESOLUTION.md (credential verification + fix trail) as the permanent record. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UtrDnVmNutDYsKAXnZrvWy
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.
Summary
Closes #63.
CI's
actions/checkout@v4(fetch-depth: 0) force-updates every tag, sogitleaks git(which walks all refs) permanently rescans the abandonedpre-history-rewrite
v0.2.0/v0.2.0-betatag tips instead ofmain.mainitself has 0 leaks in 389 commits — this was never amaincompromise.
Each of the 7 tag-only findings was individually investigated and
verified live/dead by the repo owner (no blanket suppression):
.env).env)docker-compose*.yml)expclaim, already pastDEPLOYMENT.mdx3).gitleaksignorenow has a per-entry justification for each. Verifiedscripts/secret-scan.sh(CI's actual step) passes clean:450 commits scanned,no leaks found, after re-fetching with CI's exact refspec torule out local-tag drift as a confound.
See
SECRET_SCAN_CI_INVESTIGATION.md(root-cause diagnosis) andSECRET_SCAN_RESOLUTION.md(credential verification + fix trail) for thefull record.
Test plan
bash scripts/secret-scan.shexits 0, no leaks found🤖 Generated with Claude Code