Verifying Release Artifacts

All release artifacts are cryptographically signed and have build provenance attestations. This document describes how to verify them before deployment.

Docker images

Docker images are signed with cosign (keyless via GitHub OIDC) and have build provenance attestations generated by actions/attest@v4.

Verify an image signature

cosign verify ghcr.io/yorch/ai-agents-observability/web:v2.1.0 \
  --certificate-identity-regexp 'https://github.com/yorch/ai-agents-observability/' \
  --certificate-oidc-issuer 'https://token.actions.githubusercontent.com'

Repeat for ingest, github-app, and migrations-runner.

Verify build provenance

gh attestation verify ghcr.io/yorch/ai-agents-observability/web:v2.1.0 \
  --repo yorch/ai-agents-observability

Server binaries and web tarball

The SHA256SUMS-binaries file (attached to each GitHub Release) is signed with cosign keyless via OIDC. The signature is in SHA256SUMS-binaries.sig.

Verify the checksums signature

# Download SHA256SUMS-binaries, SHA256SUMS-binaries.sig, and
# SHA256SUMS-binaries.crt from the GitHub Release page.
cosign verify-blob SHA256SUMS-binaries \
  --signature SHA256SUMS-binaries.sig \
  --certificate SHA256SUMS-binaries.crt \
  --certificate-identity-regexp 'https://github.com/yorch/ai-agents-observability/' \
  --certificate-oidc-issuer 'https://token.actions.githubusercontent.com'

Verify build provenance

gh attestation verify SHA256SUMS-binaries \
  --repo yorch/ai-agents-observability

Verify individual artifacts

sha256sum -c SHA256SUMS-binaries

This verifies every server binary and the web tarball against the signed checksums file.

Hook binaries

The SHA256SUMS-hook file (attached to each GitHub Release) contains checksums for the hook CLI binaries. Verify with:

sha256sum -c SHA256SUMS-hook

SBOMs

Each release includes CycloneDX SBOMs for all components: sbom-<component>-vX.Y.Z.json. Use these to scan for known vulnerabilities before deployment.

Air-gapped verification

For air-gapped environments, see air-gapped.md for the offline verification path using OCI archives and pre-downloaded signatures.