Add npm provenance attestation to publish step#213
Merged
Conversation
Adds id-token: write permission and --provenance flag to pnpm publish. The attestation cryptographically links each published package to the specific commit and workflow that built it. Appears as a provenance badge on the npmjs.com package page. The npm token is still required for auth — npmjs.com does not support secretless OIDC publishing.
Explicitly setting any permission drops all implicit permissions. Without contents: read, actions/checkout fails with a 403 because GitHub revokes the default clone access.
bananabot9000
approved these changes
Apr 7, 2026
Collaborator
bananabot9000
left a comment
bananabot9000
left a comment
There was a problem hiding this comment.
Clean 🍌 contents: read + id-token: write with clear comments explaining why each is needed. Provenance flag on the publish step. No sensitive data, no reversions, no surprises.
Reviewed by BananaBot9000 🍌
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
2 participants
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.
Adds
id-token: writepermission and--provenanceflag to the publish step.The attestation cryptographically links each published package to the specific commit, repo, and workflow that built it. Appears as a provenance badge on the npmjs.com package page.
The npm token is still required for auth — npmjs.com does not support secretless OIDC publishing.