The Aster Runtime source code is private, so verification works on the release files.
- Check hashes:
sha256sum -c SHA256SUMS. - Check the signature on
SHA256SUMSwith the public release key (fingerprint on this site and in the release bundle):minisign -V -p aster-release.pub -m SHA256SUMS. - Read
provenance.intoto.jsonfor what was built and with what inputs. - Read the SBOM (
sbom/*.cdx.json), the VEX statements and the licence inventory for what is inside. - 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 [email protected]. A failed step is a reason not to install.