21 commits since v0.2.0. Two things happened here.
Recall
Three slices moved the held-out baseline off zero:
- tool-registry extraction for the five registration idioms real MCP servers actually use
- un-gated
auth_posturefrom the Python AST - un-gated
secret_handling's name branch from the Python AST
Against the five pinned third-party targets, findings went from 0 to 88.
Honesty
The README had been claiming a 0/53 precision figure that described the pre-recall state, with no record of the recall wave at all. The CI count-gate was also RED on a drifted test count. Both corrected.
Read the 88 carefully. 2 were hand-audited as true positives, and the honest read is 1 -- only airtable src/main.ts:54 has real-world consequence, and even that is opt-in and already disclosed upstream. The other is a credential upstream deliberately committed as a read-only public-data test token.
2/88 is a low precision figure. A rising test count is not evidence of capability either, and the JS/TS precision layer still does not exist.
Tests
648 passed, 9 skipped. The 9 skips are the dogfood self-audit tests, which need MCP_SCANNER_FLEET_ROOT pointed at real repos and skip cleanly in a fresh clone.