chore(security): harden npm publish pipeline against supply-chain attacks#516
Open
arzafran wants to merge 1 commit into
Open
chore(security): harden npm publish pipeline against supply-chain attacks#516arzafran wants to merge 1 commit into
arzafran wants to merge 1 commit into
Conversation
arzafran
force-pushed
the
security/trusted-publishing
branch
2 times, most recently
from
12fa0a0 to
6feedb5
Compare
- Tag-triggered release workflow with build provenance - GitHub Actions pinned by commit SHA, hardened runner - Tag-version match guard before publish - Removes manual publish scripts - Adds SECURITY.md, npm Dependabot tracking, CODEOWNERS for release paths
arzafran
force-pushed
the
security/trusted-publishing
branch
from
6feedb5 to
fc36fbc
Compare
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.
Summary
Moves npm releases onto a GitHub Actions workflow using OIDC-based Trusted Publishing with build provenance.
Files
.github/workflows/release.yml— tag-triggered (v*) release workflow. SHA-pinned actions, hardened runner, OIDC publish,--provenance, tag-version match check.package.json— addspublishConfig.provenance,packageManager,prepublishOnly; drops the manual publish scripts./.npmrc+.gitignore—provenance=true; allowlists root/.npmrc, nested files still ignored..github/dependabot.yml— adds thenpmecosystem with grouped weekly updates..github/CODEOWNERS— explicit ownership of release-critical paths.SECURITY.md— disclosure policy, maintainer setup checklist, consumer verification.Setup before the next release
A one-time configuration on npmjs.com and github.com is required. Steps are in
SECURITY.md.Verifying a published version