Semgrep (Secrets) vs KeyDrift
Semgrep’s engine credibility is real; Secrets extends crossfile analysis toward credential findings in code.
The OSS scanner engineers love, productized with rules-as-code philosophy intact.
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 Semgrep Secrets does well
Secrets documentation highlights cross-file taint/dataflow reducing noise versus pure regex.
- Rules-as-code flexibility teams can extend.
- Crossfile analysis cuts false positives meaningfully.
- Huge OSS community trust.
The gap KeyDrift fills: the deployed bundle
The structural difference is the artifact under inspection. Semgrep Secrets watches inputs to the build — commits, branches, configuration. KeyDrift watches the output: the HTML and JavaScript a browser downloads from the live URL. Build-time substitution, agent-written client calls and streamed payloads live in that output and in none of the inputs, which is why a green Semgrep Secrets report and a leaking deployment can coexist without anyone being wrong.
- 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. Source code at PR/CI time. versus KeyDrift: deployed web artifacts fetched live, or pasted bundle source for anything behind a login.
- Detection approach. Dataflow-aware rules plus curated secret rulesets. 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. CI-findings workflows. versus KeyDrift: scheduled scans diffed into created/regressed/resolved with alert routing to email, Slack, Discord and webhooks.
- Getting started. App/platform signup for managed rules. 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 Semgrep Secrets documents more detail than fits here, follow their docs; where KeyDrift claims something, it is verifiable in a two-minute free scan.
| Capability | Semgrep Secrets | KeyDrift |
| --- | --- | --- |
| Primary surfaces | Source code at PR/CI time. | 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 | CI-findings workflows. | Scheduled scans diffed into created/regressed/resolved; regression alerts name comebacks |
| Alert routing | CI-findings workflows. | Email · Slack · Discord · raw webhooks with per-destination severity thresholds |
| Getting started | App/platform signup for managed rules. | 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 Semgrep Secrets summarize their public documentation as of the verified date above._
Where each one wins
- Semgrep Secrets wins when developer-first AppSec programs extending rules themselves.
- 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 Semgrep Secrets
Teams arriving from Semgrep Secrets usually keep their existing setup and add one job: point KeyDrift at production, staging, and preview URLs. First week looks like this — day one, run the free scan on every deployment and triage findings by severity; day two, fix or schedule fixes using the linked guides; day three onward, monitoring watches for regressions while Semgrep Secrets continues doing what it does best.
Write rules about source forever; verify artifacts once built — different loops, compatible tools.
Decision rule
- Keeping Semgrep Secrets 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 Semgrep Secrets documentation and pricing as verified August 2026. Capabilities change; check their site._ Semgrep, Inc. and associated marks are trademarks of Semgrep, Inc., referenced for identification and descriptive comparison.
Bottom line: choose Semgrep Secrets for its category strengths without hesitation. Choose KeyDrift the moment someone asks what your bundles expose — then keep both, because they were never competing for the same job.
How teams actually run Semgrep Secrets and KeyDrift together
In practice the pairing is boring in the best way: Semgrep Secrets 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 (Source code at PR/CI time.) — 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 Semgrep Secrets 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.