Repository navigation
Add a leak check to CI - #1
Merged
Merged
Conversation
Every public repo should run a leak check. In CI it fails on email addresses that aren't noreply or placeholders and on committed binaries or build output. Run locally, it also checks for private terms read from a file outside the repo (LEAK_PRIVATE_TERMS, default ~/.leak-private-terms), and reports only file and line, never the term. It passes on the current tree without a terms file. The private-terms path was exercised with a stand-in file only; no terms file at the default path exists yet. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.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.
Adds
scripts/leak-check.shand runs it in CI right after checkout..example/.testdomains, and on committed binaries or build output (jars, zips,dist/,build/,node_modules/and so on).LEAK_PRIVATE_TERMS(default~/.leak-private-terms). It reports file and line only, never the term. No terms are in the repo or in CI.scripts/leak-allow.txt, if added later, skips lines containing a listed public phrase.Tested: passes on the current tree without a terms file. The terms path was exercised with a stand-in file only.
🤖 Generated with Claude Code