Schema reference
Implemented in this page as a JSON Schema subset: type, required, properties, additionalProperties, pattern, minLength, maxLength, enum, minItems, maxItems, uniqueItems, items. Anything outside that subset is not enforced; the scope card below lists exactly what is checked.
What is proven here
Every result on this page is computed from the input you supply, in this tab:
1. The refusal scanner runs deterministic pattern matching (regex plus a word-run heuristic) over the manifest and every attached file, and reports the field, the rule and the exact offset of each finding. Because it matches patterns rather than meaning, a disguised secret can pass it and harmless text can be flagged — twelve ordinary lowercase words in a row read as a recovery phrase. The evidence line lets you judge each finding yourself.
2. Evidence lines never echo the matched secret; only its length and offset are shown, so a scan can be run on real material without the finding becoming the leak.
3. Schema validation enforces the subset listed above: type, required, properties, additionalProperties, pattern, minLength, maxLength, enum, minItems, maxItems, uniqueItems and items. A manifest that expresses a rule with oneOf, $ref, format or minimum sits outside that subset and is not evaluated, so the reference table is the complete list of what is checked.
4. The zip is built byte by byte here with real CRC32 values and a real central directory, then re-read from the generated bytes so the entry table, the local offsets and every CRC check can be inspected directly. It writes the STORE method: no deflate, no zip64, no encryption and no signing.
5. Nothing is uploaded or sent anywhere, and no field content leaves the browser tab. The archive is generated in memory and handed to you as a download.