docs(readme,stats): sync stale FP-rate + pytest claims to live truth#58
Merged
Conversation
…t count README + stats/current.json still presented the FP rate as "~8.3% (known, actively tuning)" — but that was earlier builds (through v0.2.63); it was root-caused and fixed in v0.2.64 (zero-FP gate in CI, 86→0 on the real-code corpus). The live site already frames it correctly; GitHub now matches. Also fixed the README pytest count (7 → real 221 passing, +7 xfailed). current.json false_positive_rate_pct 8.3 → 0 with a historical note field. No detection/runtime change.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Stale public claims on the scanner repo, now synced to the truth the live site already shows:
stats/current.jsonpresented~8.3% (known, actively tuning)as current. That was earlier builds (≤v0.2.63); root-caused + fixed in v0.2.64 (zero-FP gate in CI, 86→0 on the real-code corpus). README reframed;current.jsonfalse_positive_rate_pct8.3 → 0 + historical note.7 passing; real is 221 passing (+7 xfailed).Verified
test_false_positives+test_real_corpus_fp→ 76 passed (0 FP)current.jsonvalid JSONNot changed (flagged for AZ, not guessed)
reports_published: 3in current.json vs site FAQ "4" — ambiguous what counts as a report.sunglasses/data/attacks/is a 136-file vestigial JSON db (engine uses patterns.py=1046; not shipped to pip per MANIFEST). Candidate for removal/regeneration — structural, left alone.internal_recall 64/64kept — it's the current figure the live site uses.