Verifying a release
Every file a polylint release publishes is listed in its sha256sums.txt, and every one of them, sha256sums.txt
included, carries a GitHub artifact attestation
signed with the identity of the release workflow (.github/workflows/publish.yaml) on the tagged commit. Each
poly archive and each engine component archive built for the release also ships a CycloneDX SBOM next to it, as
<archive>.cdx.json, attested against the archive it describes. The release binaries embed their dependency list
as well (cargo auditable).
Verify an archive by hand
Section titled “Verify an archive by hand”You need the GitHub CLI (gh). Replace X.Y.Z and the triple with the release and
platform you install.
-
Download the archive, its SBOM and the checksums:
Terminal window gh release download vX.Y.Z --repo polylint/polylint \--pattern 'poly-X.Y.Z-x86_64-unknown-linux-gnu.tar.gz*' --pattern sha256sums.txt -
Check the bytes against the release’s checksums:
Terminal window sha256sum -c --ignore-missing sha256sums.txtOn macOS use
shasum -a 256 -c --ignore-missing sha256sums.txt. -
Check that the release workflow built the archive:
Terminal window gh attestation verify poly-X.Y.Z-x86_64-unknown-linux-gnu.tar.gz --repo polylint/polylint \--signer-workflow polylint/polylint/.github/workflows/publish.yamlThe output names the workflow run, the commit and the tag. The same command verifies
sha256sums.txt,poly-components.lock.jsonand anypoly-component-*.tar.gz.Releases up to and including v0.35.0 were published before the repository moved to the
polylintorganization, and their attestations keep the identity they were signed under. For those, name the old repository in both places:Terminal window gh attestation verify poly-X.Y.Z-x86_64-unknown-linux-gnu.tar.gz --repo Goldziher/polylint \--signer-workflow Goldziher/polylint/.github/workflows/publish.yaml -
Check the SBOM attestation, which binds
poly-X.Y.Z-x86_64-unknown-linux-gnu.tar.gz.cdx.jsonto the archive:Terminal window gh attestation verify poly-X.Y.Z-x86_64-unknown-linux-gnu.tar.gz --repo polylint/polylint \--predicate-type https://cyclonedx.org/bom
The SBOM is plain CycloneDX 1.5 JSON, so any SBOM tool reads it. The installed binary describes itself too:
cargo audit bin "$(command -v poly)" reads the embedded dependency list and checks it against the RustSec database.
The npm platform packages carry the same SBOM as bin/poly.cdx.json, and the PyPI wheels as
polylint/sbom/poly.cdx.json.
Require the attestation when installing
Section titled “Require the attestation when installing”The installer scripts always check the archive against sha256sums.txt. With POLY_VERIFY_ATTESTATION=1 they also
run gh attestation verify and refuse to install when it fails or when gh is missing. They accept either
signing identity, polylint/polylint or the pre-transfer Goldziher/polylint:
curl -fsSL https://raw.githubusercontent.com/polylint/polylint/main/install.sh | POLY_VERIFY_ATTESTATION=1 sh$env:POLY_VERIFY_ATTESTATION = "1"irm https://raw.githubusercontent.com/polylint/polylint/main/install.ps1 | iexIn GitHub Actions, the setup action takes the same switch. The job’s token is enough for gh:
- uses: polylint/polylint@v0 with: verify-attestation: trueThe action caches the release archive, not the installed binary, and re-checks a restored archive against
sha256sums.txt on every run, so a tampered cache entry is downloaded again rather than run.
Components
Section titled “Components”A core build downloads engine components on demand and checks each against the archive digest and Ed25519 signature
in the component lock compiled into the binary, so no extra step is needed. To audit one by hand, download the
poly-component-*.tar.gz from the release that built it (the lock’s url) and run step 3 on it. How the signing key
is kept apart from the build and rotated is recorded in
ADR 0060.