ci(scorecard): signed releases (Sigstore provenance) + pin fuzz-build deps#62
Merged
Conversation
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
1 participant
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.
Ports redstamp's Scorecard hardening (askalf/redstamp#65 + askalf/redstamp#66) to this repo.
Signed-Releases (currently N/A — releases carry no assets, so the check doesn't run): auto-release now attaches the
npm packtarball and its keyless Sigstore provenance bundle (<tarball>.sigstore.json, signed via GitHub OIDC by hash-pinnedactions/attest-build-provenancev4.1.1) to every release. Verify withgh attestation verify <tarball> --owner askalf. Takes effect on the next version bump. The slsa-github-generator route was deliberately skipped: it can only be referenced by tag, which would hand Pinned-Dependencies a permanent unpinned-action warn.Pinned-Dependencies (clears both open warns):
.clusterfuzzlite/Dockerfile— base image pinned by digest (the digest Scorecard itself recommends; same pin redstamp uses)..clusterfuzzlite/build.sh—npm install→npm ci, so the fuzz build verifies every integrity hash in the committed lockfile. Jazzer is already a locked devDependency here; installed set is unchanged.New job permissions:
id-token: write+attestations: write; top-level stayscontents: read.