ci(security): add gitleaks scanning#84
Merged
nanaf6203-bit merged 1 commit intoJun 20, 2026
Merged
Conversation
Contributor
|
Gitleaks + the Husky pre-commit hook is a great catch — exactly what we want before this thing lives anywhere real. Merged. |
6 tasks
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.
Problem
Secrets such as JWT keys, API tokens, wallet private keys, and Stellar secret keys could be committed without an automated repository gate.
Solution
.gitleaks.tomlwith default rules plus a Stellar secret-key rule.Secret ScanCI job that runs the requestedzricethezav/gitleaks-action@v1full repository scan and a PR diff scan.gitleaks protect --staged --redact --config .gitleaks.tomlwhen the local binary is installed.Closes #63
Verification
.gitleaks.tomlwith Pythontomllibnpx.cmd --yes prettier --check .github/workflows/ci.yml docs/SECRET-SCANNING.mdgit diff --checkI could not execute Gitleaks locally because this Windows machine does not have the
gitleaksbinary or Docker installed. The new CI job should exercise the scanner on the branch.