chore: harden npm install defaults#5
Merged
fielding merged 1 commit intoMay 29, 2026
Conversation
✅ Deploy Preview for fielding ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Contributor
Author
|
Sedge re-verification 2026-05-22 06:30 CDT:\n\n- GitHub still reports OPEN / MERGEABLE / CLEAN at b195b75.\n- Local temp worktree verification passed: npm ci --ignore-scripts --audit=false --fund=false, npm run build, git diff --check origin/main..HEAD, and .npmrc marker smoke for ignore-scripts=true/save-exact=true/audit=true/fund=false.\n- npm run check still fails only on the known pre-existing site baseline outside this one-file .npmrc PR (Experience.svelte, Now.svelte, +layout.svelte, plus Projects.svelte a11y warning), same cleanup lane tracked separately by PR #4/site-68ed47.\n\nNo new blocker found for this npm hardening PR. |
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.
Summary
.npmrcdefaults that reduce npm supply-chain blast radius.ignore-scripts=true).save-exact=true).Why
Recent npm worm/supply-chain campaigns abuse install/publish lifecycle hooks and ambient tokens. This makes the safe path the default; projects that truly need lifecycle scripts can still run reviewed scripts explicitly.
Verification
git diff --checkGenerated by Sedge for Fielding's npm supply-chain hardening sweep.