Source, provenance and support

Verifying a release

In reviewUpdated 2026-11-15Trust Center

In review. This record, and the tools and files it cites, are on a review branch. They are not in the main source tree yet, so you cannot check them in a copy of the main source today.

The Aster Runtime source code is private, so verification works on the release files.

  1. Check hashes: sha256sum -c SHA256SUMS.
  2. Check the signature on SHA256SUMS with the public release key (fingerprint on this site and in the release bundle): minisign -V -p aster-release.pub -m SHA256SUMS.
  3. Read provenance.intoto.json for what was built and with what inputs.
  4. Read the SBOM (sbom/*.cdx.json), the VEX statements and the licence inventory for what is inside.
  5. Watch it run: see No data: what Aster does and does not do.

We have not had a third-party security audit. Report a problem to me@barnyak.com. A failed step is a reason not to install.

Source docs/trust/VERIFYING-A-RELEASE.mdlast changed 2026-11-15

More records

Every record in the Trust Center is public.