Reviewers approve diffs. Bundles aren’t diffs.

PR review sees source lines, never substitutions. The dangerous transformation happens later, alone. Verify outputs free.

2026-08-234 min read

What Human code review does well

context-rich judgment catches hardcoded literals and wrong-env reads directly in diffs.

Understands intent behind changes.
Flags suspicious patterns inline.

What Deployed-output verification adds

inspects what substitution produced regardless of how plausible the diff looked.

Two-line renames pass review precisely because review sees variable names. Substitution converts names to literals afterwards — alone, unreviewed, invisible to everyone who approved anything.

Intent-level judgment.,Free with existing process.

Ground truth about artifacts.
Immune to plausibility bias.
K
e
e
p
r
e
v
i
e
w
f
o
r
i
n
t
e
n
t
;
a
d
d
a
r
t
i
f
a
c
t
c
h
e
c
k
s
f
o
r
a
r
i
t
h
m
e
t
i
c
.
N
e
i
t
h
e
r
a
r
g
u
e
s
t
h
e
o
t
h
e
r
a
w
a
y
.

Using them together

Diff looks odd? Reviewer catches it.,Diff looks innocent but bundles leak? Only output checks see it.

Decision rule

Keep what already works for its stated strength.
Add KeyDrift when the deployed artifact itself needs watching.

Neither answer replaces the other; they watch different files at different moments. The mistake is believing one report covers both.

Why this keeps happening industry-wide

Zoom out and the pattern is bigger than one repo. AI-assisted output has outgrown review capacity everywhere at once, which means thousands of teams are making the same reasonable-looking tradeoffs in the same week. Nobody using modern tooling is uniquely exposed. The failure mode documented above is the modal outcome of velocity without verification, not evidence of carelessness.

How KeyDrift reports this exact finding

Report anatomy matters during incidents, so it is worth reading once calmly: masked string (never the live value — it ceases to exist outside the detection engine), salted fingerprint (trackable within your workspace, useless to strangers), chunk path (your starting point for a "git log -S" hunt), disposition (secret versus public-by-design), confidence (matches below 0.5 never reach the page at all).

Manual check, step by step

The full manual drill, for readers who want zero dependence on any tool: open the deployed site in a private window; launch DevTools → Sources; use Search-all-files (Ctrl/Cmd+Shift+F) for eyJ; then repeat for the other marker families — eyJ, sk_live_, sk-proj-, AKIA, postgres, BEGIN PRIVATE KEY. Decode anything JWT-shaped before reacting, and classify public-by-design formats as expected guests rather than intruders.

Close the loop with monitoring

If you take one operational step from this page, make it this: put the URL under continuous monitoring (free tier covers one project daily). The first scan tells you whether you have a problem today; the schedule tells you whether the problem comes back next month after someone re-adds the convenient line.

What the plans change

Free $0 — 1 project · daily scans · email alerts · findings always visible.
Indie $29/mo — 3 projects · hourly · Slack added · 80 chunks per scan.
Team $89/mo — 15 projects · every 15 minutes · Discord + webhooks · 150 chunks.
Growth — from $249/mo, quoted display-only until checkout ships.

The constant across every tier: plans limit how much is watched, never what a scan found. Visibility is structural, not promotional — asserted by tests over the entitlements model itself.

Common questions

Is Human code review bad practice then?

No — the page credits exactly where it wins. Blind spots are structural, not sloppy.

Bottom line?

Add KeyDrift when the deployed artifact itself needs watching.

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.