Kingfisher (MongoDB’s secret scanner) vs KeyDrift
MongoDB open-sourced Kingfisher for high-performance secret detection in code. Code remains a different artifact than bundles.
A modern Rust entrant backed by a major platform company signals continued investment in source-side tooling.
This page compares the two honestly: strengths credited specifically, differences traced to structure rather than quality, and a decision rule at the end. Verified August 2026.
What Kingfisher does well
Public materials position it as fast, extensible secret detection for codebases and histories.
- Modern implementation with performance focus.
- Major-company stewardship implies longevity.
- Open-source accessibility.
The gap KeyDrift fills: the deployed bundle
Where the two diverge is timing and target. Kingfisher evaluates work as it moves through your pipeline; KeyDrift evaluates what has already shipped, from the outside, the way an attacker or a researcher would fetch it. The gap between those two views is not theoretical — it is exactly where NEXT_PUBLIC_ substitutions and copied-in demo keys live.
- Fetched-and-diffed scanning of live URLs, including chunks reachable only through route manifests.
- Streamed server data (
self.__next_f.push,window.__NUXT__) read as carefully as chunk files. - Calibrated dispositions: Supabase anon keys, publishable keys and Firebase web keys recognised as public-by-design instead of reported as leaks.
- Drift transitions — created, regressed, resolved — so a reintroduced key alerts as a regression, not as news.
Feature-by-feature
- Surfaces scanned. Code repositories and related stores. versus KeyDrift: deployed web artifacts fetched live, or pasted bundle source for anything behind a login.
- Detection approach. Rule-based detection optimized for speed. versus KeyDrift: 21 secret detectors across 13 providers with placeholder rejection, alphabet-normalised entropy, payload decoding and a confidence floor below which matches are dropped rather than caveated.
- Change over time. CLI reporting oriented to repo workflows. versus KeyDrift: scheduled scans diffed into created/regressed/resolved with alert routing to email, Slack, Discord and webhooks.
- Getting started. Standard open-source install paths. versus KeyDrift: paste a URL at /scan — free, no account — or paste source for private surfaces.
Side-by-side
Every cell below states a specific capability. Where Kingfisher documents more detail than fits here, follow their docs; where KeyDrift claims something, it is verifiable in a two-minute free scan.
| Capability | Kingfisher | KeyDrift |
| --- | --- | --- |
| Primary surfaces | Code repositories and related stores. | Deployed web artifacts fetched live: HTML, all chunks (incl. route-manifest-only), streamed payloads |
| Build-time substitution (NEXT_PUBLIC_/VITE_) | Source-side only — substitution happens after these scans complete | Detected in served output — exactly where it lands |
| Hydration payloads (self.__next_f.push, window.__NUXT__) | Outside source-scan scope | Read as carefully as chunk files |
| Public-vs-secret calibration | Varies by engine; anon-key false positives remain the classic complaint | Dispositions built-in: anon/publishable/Firebase-web reported informational, sample keys rejected by name |
| Change over time | CLI reporting oriented to repo workflows. | Scheduled scans diffed into created/regressed/resolved; regression alerts name comebacks |
| Alert routing | CLI reporting oriented to repo workflows. | Email · Slack · Discord · raw webhooks with per-destination severity thresholds |
| Getting started | Standard open-source install paths. | Paste any URL at keydrift.dev/scan — free, no account; paste-source mode for behind-login surfaces |
| Privacy of findings | Varies by vendor | Masks + salted fingerprints only; no column anywhere can hold a live secret |_Cells describing Kingfisher summarize their public documentation as of the verified date above._
Where each one wins
- Kingfisher wins when organizations standardizing fast source scanning across many teams.
- KeyDrift wins when the question is “what credentials can strangers retrieve from this deployment right now?” — live fetching, calibrated dispositions, and regression alerting without agents installed.
Switching from Kingfisher
Nobody rip-and-replaces Kingfisher, and this page never asks for that. The realistic switch is additive: keep Kingfisher as the system of record for its domain, give KeyDrift the URLs you serve to strangers, and let drift alerting catch the reintroductions that neither tooling nor memory catches today.
Adopt freely for source; pair with deployment-side verification for what builds produce.
Decision rule
- Keeping Kingfisher for its documented strengths makes sense — it earns them.
- Add KeyDrift when deployment truth matters: post-build artifacts, preview URLs, and reintroduction watch on a schedule.
_Compared against Kingfisher documentation and pricing as verified August 2026. Capabilities change; check their site._ MongoDB and associated marks are trademarks of MongoDB, referenced for identification and descriptive comparison.
Bottom line: if your question is “is our source clean?”, Kingfisher may already answer it well. If your question is “what can a stranger pull from our live JavaScript right now?” — only a scanner that fetches deployments can answer, and that is the entire product on this side of the table.
How teams actually run Kingfisher and KeyDrift together
In practice the pairing is boring in the best way: Kingfisher stays authoritative for whatever it was built to do, KeyDrift runs on a schedule against every public deployment, and alerts route into the same channels your team already reads. Nothing is migrated; nothing is turned off. The only new habit is reading one more alert type — and that one arrives masked, classified, and linked to a fix guide.
What to verify on their site before deciding
- Their current scanned-surface list (Code repositories and related stores.) — confirm against your stack.
- Whether drift/change-detection over time is part of their product or a roadmap item.
- Free-tier shape: what you can prove about YOUR deployment before any purchase conversation.
Common questions
Is Kingfisher bad at security?
No — the page credits specific strengths above. The difference is which artifact gets inspected, not effort or care.
Pricing comparison?
Their list pricing lives on their site and changes; ours sits on the plans page with findings visible free at every tier. Numbers go stale; philosophy does not.
Run a free scan at keydrift.dev/scan — paste a URL or the bundle source itself, no account. Findings arrive masked, with the exact chunk they live in.