Repository navigation
ci(release): attach each release's tarball and provenance - #38
Merged
Merged
Conversation
Every @hlang-org GitHub Release now carries the tarball it released (checked against the registry's integrity hash), the Sigstore bundle of the SLSA provenance npm recorded at publish time, and the in-toto attestation inside it. Nothing is signed by the script; every file comes from the registry. The step runs on every push to main and is idempotent, so it also completes past releases; versions published before trusted publishing have no provenance and are left as they are. SECURITY.md explains how to verify a release, and its supported-versions table now says runtime 2.x and interpreter 2.x. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
OpenSSF Scorecard reports Signed-Releases: no releases found. We have 36 GitHub Releases, but Scorecard only counts releases that carry files, and ours had none.
scripts/release/attach-assets.mjsattaches three files to every@hlang-org/*release:<pkg>-<ver>.tgz: the registry tarball, verified againstdist.integrity(SHA-512).<pkg>-<ver>.sigstore.json: the Sigstore bundle of the SLSA v1 provenance that npm recorded through trusted publishing.<pkg>-<ver>.intoto.jsonl: the DSSE in-toto envelope from that bundle.Nothing is signed by us; every file comes from the registry. The script runs as its own release.yml step on every push to main and is idempotent, so it also backfills past releases. Versions published before trusted publishing have no provenance; they are reported and left untouched (15 of 36).
Verification
--dry-runagainst the live registry: 21 releases verified (integrity matches), 15 skipped.hlang-tech/hlang/.github/workflows/release.yml@refs/heads/main.npm audit signaturesverifies the installed packages.lint:docsreports 0 issues.Docs
🤖 Generated with Claude Code