Verify a sample bundle.
Run the offline verifier yourself. Download our sample evidence bundle and verify it locally, no network required.
Sample Evidence Bundle
A complete, verifiable evidence bundle demonstrating the AGA format.
How to verify
Download the Sample Bundle
Get sample-bundle.zip. It contains three files: evidence-bundle.json, verify.mjs, and README.txt.
Extract the ZIP
Unzip to any directory. You get the evidence bundle, the verifier script, and a README that explains the contents.
Run Offline Verification
Open a terminal in the extracted folder and run node verify.mjs evidence-bundle.json. It needs Node 18 or later, has zero dependencies, and makes no network calls. To also prove provenance, add --pubkey with the gateway key printed in README.txt.
Review the Results
The verifier checks every Ed25519 signature, the hash chain, and the Merkle inclusion proofs, then prints an overall PASS or FAIL.
$ node verify.mjs evidence-bundle.jsonOr verify it here, live
A sample SEP bundle, checked in your browser by the real verifier. No download, no server. Flip the tamper toggle and watch a genuine PASS become a genuine FAIL.
The verifier is published. Check us with it.
The same Ed25519-SHA256-JCS construction the gateway signs with is published as an independent command-line verifier on npm. Install it and re-check any evidence bundle on your own machine, or run the VerifyBundle offline verifier in your browser. The package ships with SLSA build provenance.
What you get depends on the key. Without a pinned key the verifier confirms integrity only: that the bundle is internally consistent under its own key. Pin the gateway key to also prove who issued it and to rule out whole-bundle re-signing.
The demo gateway key is a published fixture, and a live deployment uses a persisted key (the server’s default key is ephemeral).
What this demonstrates
Offline Verification
All verification happens locally. No API calls, no network dependency.
Tamper Detection
Edit any field in the evidence bundle and verification fails. Try it.
Chain Integrity
Each receipt links to the previous via hash. No gaps, no reordering.
Try the Tamper Test
Edit any field in evidence-bundle.json, save it, and re-run verification. The verdict flips to FAIL, with an error indicating which field was modified.
This demonstrates why evidence bundles are tamper-evident. Any modification breaks the cryptographic chain.
This is a sample bundle for demonstration purposes.
Evidence bundles provide cryptographic, offline-verifiable integrity checks. This is not legal advice. Admissibility varies by jurisdiction.