How to Set Up Secret Scanning with GitGuardian in 30 Minutes
GitGuardian alerts you the moment an API key lands in a commit. Here is the GitHub App install, the pre-commit hook, and the correct order…
GitGuardian is a secrets-detection platform that scans Git repositories, CI pipelines and messaging apps for leaked API keys, tokens and passwords. It is free for up to 25 developers, and pricing moves to roughly $25 per developer per month on the Business tier.
GitGuardian watches for the moment someone commits an AWS secret key, a Stripe live key or a database URI into a repo. It parses commits (not just the current file state) so a secret deleted three commits later still gets flagged.
Detection runs against a pattern library of about 450 credential types plus entropy checks. Every alert carries a validity check: GitGuardian will actually call the provider to see whether the key still works.
Free for 25 developers, unlimited repositories, on public and private GitHub, GitLab and Bitbucket. Historical scan of up to 8,000 commits per repo on signup. You also get the honeytoken feature — a decoy key you plant and get alerted on when someone uses it.
The paid Business plan (about $25/dev/month at low volume) opens up unlimited commit history, alert auto-assignment, SSO and a longer audit trail. Enterprise adds on-prem and air-gapped scanning.
ggshield secret scan pre-commit blocks a commit locally before it leaves the laptop.Fit: any team with a public repo or contractors. One leaked key can cost more than a year of the license, so the math is easy.
Less of a fit: solo developers who keep everything in a private monorepo and already use GitHub’s built-in secret scanning. GitHub’s version is free and now catches around 100 provider patterns, so the overlap is real.
Two honest complaints. First, custom internal patterns require the CLI config, not a dashboard toggle. Second, on the free plan you cannot bulk-close history alerts, and the 8,000-commit backfill will not cover an old monorepo.