Browse documentation
Docs target stable release v0.15.0; v0.16.2 on main is unreleased.Stable vs main checked 2026-10-30

Verifiable run evidence

v0.15 exports an in-toto Statement v1 in a signed DSSE envelope. Its subject is the run's SHA-256 content address. The predicate records status, models, providers, lineage, usage and cost totals, agent ref, and opentine version. Prompts, completions, and tool payloads are omitted; all included strings are redacted.

Terminal
tine keygen --out agent.key --pub agent.key.pub
tine export result.tine --format intoto --ed25519-key-file agent.key --output result.intoto.jsonl
tine verify result.tine --attestation result.intoto.jsonl --pubkey agent.key.pub --json

An unsigned statement is never written. DSSE uses Ed25519, not HMAC. Verification checks both the envelope signature and the run's recomputed subject digest, and exits 1 on failure. A did:key identifies a key, not its owner; pin the key before relying on its identity. Embedded-key trust reports verified-tofu.

Transparency receipts

Terminal
# Explicit network publication to Rekor
tine export result.tine --format intoto --ed25519-key-file agent.key --rekor --output result.sigstore.json

# Use independently obtained trusted Rekor key material
tine verify result.tine --attestation result.sigstore.json --pubkey agent.key.pub --rekor-key rekor.pub --require-receipt --json

--rekor [URL] logs the envelope and writes a Sigstore bundle v0.3. The default log is Rekor's public service. Offline receipt verification checks the signed entry timestamp, inclusion proof, signed checkpoint, and envelope binding. --require-receipt fails when the receipt or trusted log key is missing or invalid.

Keyless signing

--keyless obtains a short-lived Fulcio certificate for an OIDC identity and always logs to Rekor. Supply the token through --identity-token, SIGSTORE_ID_TOKEN, or the GitHub Actions ambient identity. Tokens are never printed or persisted.

Verification requires --cert-identity, --cert-oidc-issuer, --fulcio-root FILE, and --rekor-key FILE. Successful keyless verification reports verified-keyless. Trust roots must come from the operator's trusted configuration.

Portable artifact signatures, repository attestations, action manifests, and DSSE evidence cover different signed views. See repository claim verification and signed actions.