fabro/docs/reference/verifying-releases.mdx
Bryan Helmkamp b5e17ba082
ci(release): attest SLSA build provenance for binaries and image
Tarballs in each compile matrix and the multi-arch ghcr image now get
Sigstore-signed provenance attestations via GitHub's attest-build-provenance
action. Users can verify with `gh attestation verify` — covered in a new
docs/reference/verifying-releases.mdx.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-18 15:05:32 -04:00

42 lines
1.9 KiB
Text

---
title: "Verifying Releases"
description: "Verify Fabro binaries and images were built by our release workflow"
---
Fabro publishes [SLSA Build Provenance](https://slsa.dev/) attestations for every release tarball and the multi-arch Docker image. Attestations are signed via [Sigstore](https://www.sigstore.dev/) and recorded in the public transparency log, so you can verify that an artifact was built by our GitHub Actions workflow from a specific commit in [`fabro-sh/fabro`](https://github.com/fabro-sh/fabro) before you run it.
<Note>
Provenance proves **where and how** an artifact was built. It does not vouch for the correctness or security of the source code itself — only that what you downloaded was built by our workflow from the commit it claims.
</Note>
## Prerequisites
Install the [GitHub CLI](https://cli.github.com/) and authenticate:
```bash
gh auth login
```
## Verify a binary tarball
Download the tarball for your platform from the [releases page](https://github.com/fabro-sh/fabro/releases), then:
```bash
gh attestation verify fabro-aarch64-apple-darwin.tar.gz --repo fabro-sh/fabro
```
A successful verification prints `Loaded digest …` followed by `✓ Verification succeeded!` and details of the matched attestation.
## Verify the Docker image
The attestation is attached to the image in GHCR, so no separate download is needed:
```bash
gh attestation verify oci://ghcr.io/fabro-sh/fabro:<version> --repo fabro-sh/fabro
```
Replace `<version>` with the release version (e.g. `0.207.0`) or use `latest` / `nightly`.
## Homebrew installs
The `fabro-sh/tap` Homebrew formula verifies a SHA-256 checksum against each tarball Homebrew downloads, so there is no separate attestation step to run at install time. If you want provenance verification for a Homebrew-installed release, download the matching tarball from the [releases page](https://github.com/fabro-sh/fabro/releases) and run `gh attestation verify` against it.