Repository navigation
ci: block committed secrets and private keys - #14
Merged
Merged
Conversation
Pull requests are scanned with the pinned Betterleaks and the private-key guard, and the full history is scanned weekly. Matches already in the history are verified placeholders or fixtures and are listed in .gitleaksignore. Env files, key files and data/ are now ignored.
0xmanhnv
added a commit
that referenced
this pull request
Oct 19, 2026
Pull requests are scanned with the pinned Betterleaks and the private-key guard, and the full history is scanned weekly. Matches already in the history are verified placeholders or fixtures and are listed in .gitleaksignore. Env files, key files and data/ are now ignored. Co-authored-by: Nguyen Manh <18032641+0xmanhnv@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.
Adds a blocking secret scan to this repository. It changes CI only; no code or history is touched.
.github/workflows/secret-scan.yml:.key .p12 .pfx .jks), or anything underdata/. Throwaway keys undertestdata/are allowed. The guard is the same scriptopenctemio/openctemuses.main, a manual run and a weekly run scan the full history..betterleaks.toml: the default rules, minus test fixtures, lock files and obvious placeholders (your-…,<…>,${…},example…,changeme)..gitleaksignore(only where the history has matches): fingerprints of the matches already in the history. Each one was checked by hand: they are documentation placeholders and test fixtures, not credentials..gitignore: ignores.envfiles, key files and/data/, so they are not committed by accident.Verified locally: a full-history scan with this config exits 0, actionlint passes, and a planted token makes the scan fail.