PII Redaction Auditor -- Measures What Was MISSED

Audits a redaction pass by hunting for residue, rather than asserting success.

THE SILENT FAILURE. Redaction tools report what they removed. Nobody can see what they missed, because the output looks clean -- that is what redaction means. A regex catching 123-45-6789 misses 123 45 6789 and 123.45.6789. An email pattern misses subaddressing and unicode domains. Teams ship a redactor, see redacted output, and believe the job is done. It surfaces years later in a breach report.

THE CONSISTENCY CHECK IS THE POINT: a value scrubbed on page one and left intact on page nine is the failure teams actually hit, and a per-field redactor cannot see it. It also detects over-redaction, which destroys a document's usefulness.

IT DOES NOT CLAIM COMPLETENESS. A pattern-based auditor cannot prove the absence of PII, and the README says so plainly rather than implying a guarantee -- overclaiming is worse than the bug, because it is what makes someone stop looking. It reports which classes it did NOT check.

A REAL BUG FOUND BEFORE RELEASE: an ordinary 11-digit order number was reported as a HIGH-severity phone number, because the optional country-code group consumed the leading digit and most 10-to-11 digit numbers satisfy the rest. A tool that asserts what it cannot know is the opposite of this product's thesis, and high-severity false positives are how an auditor gets switched off. Heuristic matches without corroborating context are now reported at a confidence the message actually earns, while a genuinely formatted phone number is still caught at high severity.

VERIFIED: 101 tests. Every mutation was observed FAILING before the source was restored -- a test never seen to fail is a decoration. Independently reviewed by a verifier whose job was to find what is wrong, not to agree.

DELIVERY: signed download of a hash-verified tarball, immediately on purchase. Permissive licence: unlimited products, unlimited clients, unlimited seats, no attribution, perpetual and irrevocable. One restriction, do not republish the source as source.

This is an engineering tool, not legal, tax or accounting advice. It computes and reports; a human decides.

Interface

What you call, and what comes back. Types and signatures only — the implementation ships with the source.

  export function scanResidue(redacted: string): Finding[];
  export function verifyClaimedRedactions(original: string, redacted: string, claims: string[]): ClaimVerificationResult;
  export function crossDocumentConsistency(original: string, redacted: string, minGroup: number): Finding[];
  export function detectOverRedaction( original: string, redacted: string, opts: Required<Pick<AuditOptions, "overRedactionWordRatio" | "blockRedactionRunLength">> ): Finding[];
  export function auditRedaction(input: AuditInput): AuditReport;
  export function luhnValid(digits: string): boolean;
  export function scanAllPatterns(text: string): PatternMatch[];
  export function buildLooseRegex(value: string): RegExp;
  export function maskForEvidence(raw: string): string;

  export type Severity = "critical" | "high" | "medium" | "low" | "info";