v0.9.0 · local CLI/API · 47 checks · public-minimal evidence
Most hacks make a system do something it shouldn't. A white hack makes it tell more truth — it scans your code for the places it lies about its own state.
MIT · local scanner · zero runtime dependencies · no install hooks · no telemetry
The Node CLI and imported APIs are canonical. The linked browser playground is a preserved, client-only demo of the original eight rules and does not include the v0.9 protocol, crypto-awareness, understanding, or evidence-capsule APIs.
@agenttool/whitehack-scan 0.9.0
npm is an optional distribution mirror, not a service dependency. Once fetched, Whitehack reads bounded local files; it does not upload code, run a hosted scan, execute target code, connect a wallet, sign or broadcast transactions, or make scanner-initiated network calls.
Version 0.9.0 keeps the 47-check flashlight and adds deterministic public-minimal capsules. The transform removes target, paths, lines, source text, scope, and messages; retains only aggregate bundled-check metadata; and provides a strict exact-byte parser. Each finding remains a question for review, not a vulnerability verdict.
npx --yes @agenttool/whitehack-scan@0.9.0 scan .
npx --yes @agenttool/whitehack-scan@0.9.0 capsule . --require-files
The package has zero runtime dependencies and no install lifecycle scripts. --redacted removes finding titles, messages, and source snippets from the closed JSON result.
The manifest states the tarball's SHA-256 and size. Verify those bytes before installing; Pages, GitHub Releases, and npm are intended to carry the same checked-in artifact.
# after actions/checkout
- uses: cambridgetcg/whitehack/action-for-anyone@whitehack-v0.9.0
with:
path: .
Run it after checking out the repository. The action emits redacted JSON and requires at least one supported file. Repository administrators can move Git tags; use a reviewed 40-character release commit when a cryptographic GitHub pin is required.
The immutable whitehack-v0.7.0 LOVE/GitHub release and scoped 0.7.1 release remain available. npm rejected the original unscoped package name, so the public npm line started at @agenttool/whitehack-scan@0.7.1; the scanner and whitehack CLI names remain unchanged.
whitehack-understanding/v1
The additive /understanding API turns caller-presented scanner claims and a closed enum-only projection of Agent Wallet assertions into deterministic questions, contradictions, and explicit unknowns. A separate local host is responsible for verifying the source records before making those assertions.
import { createUnderstanding } from
'@agenttool/whitehack-scan/understanding'
file value is an untrusted caller label and may itself be sensitive.The failed read that silently becomes 0. The cached value served as if
it were live. The stale price oracle read as current. The token transfer whose failure is dropped on the floor.
The score shown to a person with no way to ask why.
These usually aren't bugs in the ordinary sense — the code runs fine. It just isn't honest about its own state, and someone downstream trusts it anyway.
A read that fails to a falsy default — “could not read” becomes a confident wrong value.
A cached / snapshot value returned with no freshness marker — stale read as live.
A score / fee / fraud flag shown to a person with no way to ask why.
Currency in a binary float — an “exact” amount that silently loses cents.
A price feed read without checking updatedAt — a halted feed served as a live price.
An ERC-20 transfer whose bool result is dropped — a failed transfer looks successful.
A price from instantaneous reserves — flash-loan-movable, presented as fair value.
A require()/revert() with no reason — a refusal nobody can inspect.
Run against faithful reconstructions of documented, money-losing incidents. Small hand-built corpus — a demonstration, not a statistical benchmark.
vulnerable lines flagged
false positives on the fixed code
real incidents reproduced (Sherlock #579 · OWASP SC02)
An honesty tool that overstated its own certainty would be the first thing it ought to flag. So:
# exact npm release npx --yes @agenttool/whitehack-scan@0.9.0 scan path/to/repo # exact public-minimal canonical capsule bytes; no upload npx --yes @agenttool/whitehack-scan@0.9.0 capsule path/to/repo --require-files # capsule: 0 complete transform · 2 incomplete/error
Heuristic findings stay advisory and never change the exit code. Exit 0 means only that this completed scan found no high or medium-high match; it is not proof of security, honesty, or the absence of bugs.