LinkFinder vs KeyDrift
LinkFinder extracts endpoints from JavaScript elegantly. Endpoint mapping is a different job than credential monitoring.
A staple of JS reconnaissance, focused and well-crafted.
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 LinkFinder does well
Documentation describes endpoint/path extraction from JS files using parsing plus regex hybrid approaches.
- Clean endpoint surface mapping.
- Lightweight and scriptable.
- Provided JavaScript assets.
The gap KeyDrift fills: the deployed bundle
The structural difference is the artifact under inspection. LinkFinder 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 LinkFinder 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. Parser-assisted regex for route strings. versus KeyDrift: deployed web artifacts fetched live, or pasted bundle source for anything behind a login.
- Detection approach. None. 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. Python CLI. versus KeyDrift: scheduled scans diffed into created/regressed/resolved with alert routing to email, Slack, Discord and webhooks.
- Getting started. attack-surface mapping exercises. 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 LinkFinder documents more detail than fits here, follow their docs; where KeyDrift claims something, it is verifiable in a two-minute free scan.
| Capability | LinkFinder | KeyDrift |
| --- | --- | --- |
| Primary surfaces | Parser-assisted regex for route strings. | 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 | Python CLI. | Scheduled scans diffed into created/regressed/resolved; regression alerts name comebacks |
| Alert routing | Python CLI. | Email · Slack · Discord · raw webhooks with per-destination severity thresholds |
| Getting started | attack-surface mapping exercises. | 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 LinkFinder summarize their public documentation as of the verified date above._
Where each one wins
- LinkFinder wins when Endpoint maps tell testers where to probe; credential scanners tell owners what already leaked. Different outputs, both useful.
- 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 LinkFinder
Nobody rip-and-replaces LinkFinder, and this page never asks for that. The realistic switch is additive: keep LinkFinder 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.
undefined
Decision rule
- Keeping LinkFinder 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 LinkFinder documentation and pricing as verified August 2026. Capabilities change; check their site._ OSS (GerbenJavado) and associated marks are trademarks of OSS (GerbenJavado), referenced for identification and descriptive comparison.
Bottom line: choose LinkFinder 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 LinkFinder and KeyDrift together
In practice the pairing is boring in the best way: LinkFinder 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 (Parser-assisted regex for route strings.) — 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 LinkFinder 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.