Skip to content

ci(security): add gitleaks scanning#84

Merged
nanaf6203-bit merged 1 commit into
StellarTips:mainfrom
singhvishalkr:ci/gitleaks-secret-scan-63
Jun 20, 2026
Merged

ci(security): add gitleaks scanning#84
nanaf6203-bit merged 1 commit into
StellarTips:mainfrom
singhvishalkr:ci/gitleaks-secret-scan-63

Conversation

@singhvishalkr

Copy link
Copy Markdown
Contributor

Problem

Secrets such as JWT keys, API tokens, wallet private keys, and Stellar secret keys could be committed without an automated repository gate.

Solution

  • Added .gitleaks.toml with default rules plus a Stellar secret-key rule.
  • Added a Secret Scan CI job that runs the requested zricethezav/gitleaks-action@v1 full repository scan and a PR diff scan.
  • Added a Husky pre-commit staged scan through gitleaks protect --staged --redact --config .gitleaks.toml when the local binary is installed.
  • Documented local setup, CI behavior, and the narrow placeholder allowlist.

Closes #63

Verification

  • Parsed .gitleaks.toml with Python tomllib
  • npx.cmd --yes prettier --check .github/workflows/ci.yml docs/SECRET-SCANNING.md
  • git diff --check

I could not execute Gitleaks locally because this Windows machine does not have the gitleaks binary or Docker installed. The new CI job should exercise the scanner on the branch.

Copy link
Copy Markdown
Contributor

Gitleaks + the Husky pre-commit hook is a great catch — exactly what we want before this thing lives anywhere real. Merged.

@nanaf6203-bit nanaf6203-bit merged commit bdf837a into StellarTips:main Jun 20, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add secret scanning with gitleaks pre-commit and CI

2 participants