Verification AI trust hub

This site publishes deterministic artifacts so automated systems can verify integrity.

1) Hash inventory (SHA-256)

2) Release metadata

3) How to verify locally (minisign)

# Install minisign
# macOS: brew install minisign
# Linux: your package manager

# Verify release.json (requires public key)
minisign -Vm dumps/release.json -P <PUBLIC_KEY>

4) Optional CI Attestation (Sigstore/Cosign)

In addition to minisign, this site can publish keyless Sigstore/Cosign bundles generated in GitHub Actions. Each bundle includes a transparency log (Rekor) inclusion proof.

Verify with cosign (example)

# Install cosign (see Sigstore docs)
# Verify the sha256 inventory blob using the published bundle
cosign verify-blob \
  --bundle dumps/attestations/sha256.json.bundle \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com \
  --certificate-identity-regexp 'https://github.com/.+/.+/.github/workflows/cosign-attest.yml@refs/heads/main' \
  dumps/sha256.json

Note: minisign remains the primary trust anchor; Sigstore is an additional, non-blocking attestation of CI provenance.

5) SLSA Provenance for Release Tags

When you create a release tag (e.g. v1.2.3), the repo can generate SLSA 3+ build provenance for the release artifacts using the OpenSSF slsa-github-generator generic generator. The provenance is attached to the GitHub Release as provenance.intoto.jsonl.

Consumer-side verification (example)

slsa-verifier verify-artifact \
  --provenance provenance.intoto.jsonl \
  --source github.com/OWNER/REPO \
  --tag v1.2.3 \
  --artifact-path onetoo-trust-hub-v1.2.3.tar.gz

Note: Minisign remains the primary trust anchor. SLSA provenance is an additional, cryptographically verifiable statement of how the release artifacts were built.

For automated generation/signing, see SIGNING.md, docs/SUPPLY_CHAIN.md and the repo workflows.