Explainer

Offline verification

Offline verification means a reviewer can replay verification locally with pinned artifacts — no uploads, no tracking, and no dependency on a live service.

Open verifier Download verifier kit Site release integrity
Why offlineReproducible

What it prevents

  • Supply‑chain “moving target” audits (unstable versions).
  • Privacy or policy concerns about uploading artifacts.
  • Reviewer dependence on a vendor service to re‑run checks.
  • Silent changes: verification is replayed under pinned artifacts.
What you getTicket-ready

Expected outputs

The verifier outputs deterministic results and reason codes:

  • PASS: all checks verify.
  • FAIL: a check deterministically fails.
  • HOLD: evidence is missing or uncertain (fail‑closed).

Procurement can attach one DSSE pointer; reviewers can replay the full chain.

NextOne URL

Start from the DSSE pointer

DSSE connects the packet, proofs, and expected outputs. It is the cleanest attachable.

Open DSSE viewer DSSE in 60 seconds What HOLD means

FAQ

Why verify offline?
Offline verification removes network trust and makes reviews reproducible: anyone can replay the same artifacts and get the same outputs.
What outputs should I expect?
Deterministic PASS / FAIL / HOLD, plus reason codes that explain exactly what succeeded or what is missing/invalid.
What do auditors typically want in a ticket?
A DSSE URL, the packet URL, the proof URL, and the expected outputs (GO/HOLD) — all copy‑pasteable from Trust Center.