Skip to content

Topic

Secret Scanning

Practice of detecting exposed credentials and tokens in source code or repositories, using pattern matching, entropy analysis, and verification checks.

Current stories

buildOne report1 publisher

GitHub's Anthropic key detectors block pushes only in repositories with secret scanning on

GitHub added Anthropic service and user API keys to push protection defaults on October 13, but a push is blocked only where secret scanning is enabled. Teams whose agents push config need to check coverage per repository, private ones included.

Publishers:dev.to

Reality

Evidence55
Adoption
Not scored
Hype gap−10
Incentives
Not scored
Confidence55
securityOne report1 publisher

GitHub's ModernBERT classifier replaces an LLM in secret scanning at over 98% lower serving cost

GitHub says a fine-tuned ModernBERT classifier cut median post-push secret-scan time by 86% and model serving costs by over 98% against its LLM pipeline. The speed also let it extend generic secret detection to push protection.

Reality

Evidence55
Adoption50
Hype gap+10
Incentives60
Confidence60
buildOne report1 publisher

GitHub adds Anthropic user and service API keys to its default push-protection block list

GitHub's Oct. 13 changelog adds two Anthropic key types, user and service, to the secrets push protection blocks by default. A private repository on default settings still gets no block, according to a dev.to analysis of the entry.

Publishers:dev.to

Reality

Evidence65
Adoption
Not scored
Hype gap−10
Incentives20
Confidence62
securityOne report1 publisher

GitHub's push protection gets an AI classifier for passwords that pattern matching misses

GitHub says adding an AI classifier to push protection could more than double the secrets it can stop, by spotting passwords that have no fixed format. Push protection now stops about 30% of newly detected secrets before they reach repository history.

Reality

Evidence42
Adoption30
Hype gap+25
Incentives62
Confidence48
buildOne report1 publisher

A key in a test widget moved GoodBarber's secrecy decision into deterministic code

On July 22 a model wrote a forty-character API key into a page's JavaScript and declared the API not secret. GoodBarber now has the model state only how a key is sent and lets code default every key to secret.

Publishers:dev.to

Reality

Evidence57
Adoption20
Hype gap+10
Incentives55
Confidence52
buildOne report1 publisher

A dependency-free Node gate classifies a context bundle against eleven regexes before it ships

The policy lives in a JSON file a reviewer can read without reading the code, and the gate resolves overlapping matches by severity, so a JWT found inside a log line is denied instead of merely warned on.

Publishers:dev.to

Reality

Evidence58
Adoption
Not scored
Hype gap+30
Incentives78
Confidence45
buildOne report1 publisher

One matching prefix aborts all four writes in a Claude Code audit-memo sync

The gate between Claude Code's self-written audit memos and one developer's Obsidian wiki scans only the four files it intends to copy, tests them against two credential prefixes, and exits 2 on the first match.

Publishers:dev.to

Reality

Evidence58
Adoption8
Hype gap+12
Incentives20
Confidence40
securityOne report1 publisher

Draft ORKS spec hands revocation of a leaked API key to whoever finds it

Plain API keys leak more than any other credential and still have no standard kill switch, so a draft called ORKS copies OAuth's discoverable revocation endpoint and lets the person who found the key pull it.

Publishers:securityweek.com

Reality

Evidence45
Adoption5
Hype gap+20
Incentives60
Confidence50
buildOne report1 publisher

A 41% Throughput Win That Was Algebra, Not Assembly

A Go secret scanner sped up its Shannon entropy stage by rewriting the formula and precomputing a 4 KiB table, with no CGo, no unsafe, and no heap allocations.

Publishers:dev.to

Reality

Evidence64
Adoption14
Hype gap+14
Incentives62
Confidence57