Local evidence verification
Inspect the record.
Keep your files private.
Verify supported evidence-pack integrity against anchors you trust. No upload, account or execution of the assessed software.
Accountability depends on records that remain checkable outside the system that produced them. This check covers integrity; the problems a certificate reports and its current applicability require their own review.
Your files stay on this device.
Verification runs in an isolated browser worker. Nothing you select is uploaded.
No anchor is required to inspect a pack; without one, historical integrity is unverifiable. Archives and unknown formats are rejected. No evidence URLs are followed. The verifier is bounded to 5 seconds and 128 MiB of WebAssembly memory.
Open. Offline. Inspectable.
The browser uses the pinned Rust core from Geometer’s standalone verifier. It is the same implementation in a different interface, not an independent verifier.
geo-verify PACK.json --anchor ANCHOR.json --jsonKnow what it does not prove.
Supported: geometer.evidence-pack v1, existing Ed25519 checkpoint/key records, and retained anchors. Derived action/coverage views are not authenticated.
Certificates and unknown signature suites are unsupported. Valid integrity does not establish truth, complete observation, trusted issuer identity or current applicability.
Integrity and certificate accuracy →Try the reproducible synthetic vectors
These are public educational fixtures with publicly known test keys. Use their test anchor only for these synthetic files, never as an issuer trust root.