OpenPRoT release firmware is built with signed SLSA build provenance. This page describes what is attested, how to verify it, and what is not yet covered.
SLSA Build Level 2 for the release artifacts built by .github/workflows/release.yml:
actions/attest-build-provenance and signed with a short-lived Sigstore certificate bound to the workflow identity. The build steps cannot forge the signing identity, but they run in the same job as the attestation step, so this is not Build L3.bazel build --config=release, which sets --lockfile_mode=error: a stale MODULE.bazel.lock fails the build rather than re-resolving dependencies. Build caches are disabled. A lockfile freshness check also runs in ./pw presubmit, and therefore on every pull request: it regenerates the lockfile and fails if the result differs from the committed file, so drift is caught before release time.gh attestation verify passes for every artifact, so a failed verification never leaves a published release.Each release publishes, together with its provenance:
SHA256SUMS.txt listing the digest of each image.The default release target is the AST10x0 eRoT image, //target/ast10x0/erot:erot, built for the //target/ast10x0 platform. The workflow accepts other targets and platforms through workflow_dispatch inputs. Earlgrey and VeeR have no production images yet, only test images.
Install the GitHub CLI and run:
gh attestation verify <artifact> \ --repo OpenPRoT/openprot \ --signer-workflow OpenPRoT/openprot/.github/workflows/release.yml
A successful run proves the artifact's digest matches an attestation signed by the release workflow of this repository. The attestation records the source commit and the workflow run that produced the artifact. Check the digest of the file you flash against SHA256SUMS.txt as well.
All workflows follow these rules:
github-actions ecosystem keeps them current.permissions:. Only the release job gets id-token: write and attestations: write.target/earlgrey/tooling/signing/nonhermetic.bzl reads $HOME, the pip configuration passes --trusted-host, and some git_override dependencies are pinned by commit rather than by content hash. The default release target does not use the Earlgrey signing rules, but this has not been verified to be reproducible bit-for-bit.CODEOWNERS are not covered here. No SBOM is generated yet.