detect-secrets
v1.5.0 open-sourceThe section your link pointed to isn't on detect-secrets's page any more, so we've brought you to the top.
An enterprise friendly way of detecting and preventing secrets in code. - Yelp/detect-secrets
detect-secrets-hook --json detect-secrets scan --multiprocessing . detect-secrets audit --report . > secrets_report.json detect-secrets scan ./src/config/ detect-secrets scan --slim > .secrets.baseline detect-secrets scan --exclude-secrets 'TEST-KEY-[0-9]+' ./src detect-secrets scan --exclude-files '.*\.min\.js' --exclude-lines '10-20' . > .secrets.baseline detect-secrets scan --use-all-plugins . > .secrets.baseline detect-secrets audit --diff detect-secrets > Is this a valid secret? > password123 > no > (b)ack echo "my_secret_token" | detect-secrets scan --stdin detect-secrets scan --all-files detect-secrets scan --update baseline.yaml detect-secrets migrate secrets.baseline detect-secrets audit secrets.baseline
Summary
detect-secrets is an open-source command-line tool that scans a codebase for secrets accidentally committed to source control, using regex, entropy, and keyword heuristics rather than full history scans. It is free to use. Rather than treating every scan as pass/fail, it generates a baseline file that records secrets already present, then checks future diffs against that baseline so new secrets are caught while existing ones are tracked for later cleanup, an approach its README pitches at enterprise codebases rather than small side projects; this makes it a fit for application security and platform teams enforcing pre-commit checks across large, pre-existing repositories rather than greenfield ones. Maintained by Yelp since 2017 with 96 contributors, it has seen only one commit in the past year and its last release was over two years ago, suggesting development has slowed considerably.
An enterprise friendly way of detecting and preventing secrets in code. - Yelp/detect-secrets
How detect-secrets helps
Which of my files already contain secrets that predate any scanning I'm about to enforce?
scans the repository once and writes every match it finds into a baseline file, separating what already exists from what shows up afterward
Does a new commit introduce a secret that wasn't there before?
diffs the incoming changes against the stored baseline and flags only matches that are not already recorded, rather than re-flagging everything
Which of the flagged strings in my repo are real secrets versus false positives?
walks through each baseline entry interactively so someone can label it as real or false, updating the baseline with that verdict
Which kinds of credentials is my codebase even being checked for right now?
lists every detector plugin currently enabled, so gaps in coverage (a token type nobody turned on) are visible before they matter
Has my baseline gone stale as the repository changed?
re-scans and rewrites the baseline against the current file set, dropping entries for secrets that no longer exist and adding new matches to be triaged
Which flagged secrets still need to be rolled and migrated to safer storage?
produces a report that splits confirmed real secrets from confirmed false positives, giving a working list of what still needs remediation
Languages
Command line
No command matches.
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
Responsiveness median time to a maintainer’s first reply
Nine scores for detect-secrets, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail detect-secrets puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Releases
24 entries
No entries match these filters.
- May 20242
- October 20222
- July 20222
- February 20222
- April 20212
- February 20211
- August 20201
- July 20201
- March 20201
- October 20191
- September 20192
- July 20191
- May 20191
- February 20191
- November 20181
- September 20181
- August 20181
- June 20181
Project health
Issue, contributor and maintainer activity in Yelp/detect-secrets, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 1 −3 vs prior 12 months
- Maintainers 0 +0 joined · −0 left, last 12 months
- Bus factor 0 committers behind half the commits
- Community-filed 100% of issues opened, last 12 months
- Median time to close < 1 day first maintainer reply 32 days
- Open backlog 99 of 346 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 99
- Contributors / month 0
- Commits / month 0
- Stars 4,635
- other 100%
Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.