Nosey Parker (Praetorian) vs KeyDrift
Nosey Parker hunts secrets at scale in repos/filesystems with strong performance engineering. Different target than your CDN.
Nosey Parker brings serious performance craft to secret scanning — Rust speed with structured rule management.
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 Nosey Parker does well
Its documentation emphasizes high-throughput scanning of large corpus sets with low false-positive rule design.
- Throughput on very large repositories/archives.
- Structured rules with curated quality.
- Actively maintained by a respected security firm.
The gap KeyDrift fills: the deployed bundle
Where the two diverge is timing and target. Nosey Parker 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. Filesystems, git data, and bulk corpora. versus KeyDrift: deployed web artifacts fetched live, or pasted bundle source for anything behind a login.
- Detection approach. Compiled rule engine emphasizing precision. 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-centric reporting for analyst workflows. versus KeyDrift: scheduled scans diffed into created/regressed/resolved with alert routing to email, Slack, Discord and webhooks.
- Getting started. Binary release aimed at practitioners. 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 Nosey Parker documents more detail than fits here, follow their docs; where KeyDrift claims something, it is verifiable in a two-minute free scan.
| Capability | Nosey Parker | KeyDrift |
| --- | --- | --- |
| Primary surfaces | Filesystems, git data, and bulk corpora. | 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-centric reporting for analyst workflows. | Scheduled scans diffed into created/regressed/resolved; regression alerts name comebacks |
| Alert routing | CLI-centric reporting for analyst workflows. | Email · Slack · Discord · raw webhooks with per-destination severity thresholds |
| Getting started | Binary release aimed at practitioners. | 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 Nosey Parker summarize their public documentation as of the verified date above._
Where each one wins
- Nosey Parker wins when red-team style engagements sweeping massive datasets.
- 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 Nosey Parker
Nobody rip-and-replaces Nosey Parker, and this page never asks for that. The realistic switch is additive: keep Nosey Parker 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.
Practitioner sweeps vs always-on product monitoring remain different jobs; both can coexist in one program.
Decision rule
- Keeping Nosey Parker 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 Nosey Parker documentation and pricing as verified August 2026. Capabilities change; check their site._ Praetorian and associated marks are trademarks of Praetorian, referenced for identification and descriptive comparison.
Bottom line: if your question is “is our source clean?”, Nosey Parker 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 Nosey Parker and KeyDrift together
In practice the pairing is boring in the best way: Nosey Parker 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 (Filesystems, git data, and bulk corpora.) — 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 Nosey Parker 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.