chore: gitleaks config — allowlist the consent test fixture#108
Merged
Conversation
A history secret-scan (gitleaks) flagged `SECRET = 'test-consent-signing-key-…'` in packages/limner-mcp/test/consent.test.ts as a generic-api-key. It is a dummy HMAC key used only by the consent OAuth unit test, never a real credential. This config extends the default ruleset and allowlists exactly that value in that file, so `gitleaks git .` reports clean — useful on a flagship repo someone may scan. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Signed-off-by: Jim Vinson <jim@vinson.org>
vinsonconsulting
force-pushed
the
chore/gitleaks-allowlist-testkey
branch
from
2b607bb to
76459aa
Compare
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.
Part of the punch-list secret-scan (S3). A
gitleakshistory scan across all six public repos is clean except for one false positive here: the dummy signing key inpackages/limner-mcp/test/consent.test.ts(test-consent-signing-key-0123456789) trips the generic-api-key rule. It is a unit-test fixture, not a real credential.This adds a minimal
.gitleaks.tomlthat extends the default ruleset and allowlists exactly that value in that file, sogitleaks git .reports clean for anyone scanning the flagship repo. The repo's committed history carries no real secrets; the only on-diskgitleaks dirhits are in gitignored.envandnode_modules, neither tracked.🤖 Generated with Claude Code