-
Notifications
You must be signed in to change notification settings - Fork 3
chore(pnpm): add security settings for supply chain attack prevention #307
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1 @@ | ||
| ../../.claude/rules/nix-workflow.md |
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -57,6 +57,20 @@ onlyBuiltDependencies: | |||||
|
|
||||||
| shellEmulator: true | ||||||
|
|
||||||
| # Security settings (supply chain attack prevention) | ||||||
| # See: https://pnpm.io/settings | ||||||
|
|
||||||
| # Blocks lifecycle scripts (postinstall, etc.) from running in dependencies by default | ||||||
| # Only packages listed in onlyBuiltDependencies can run build scripts | ||||||
| # Prevents Shai-Hulud-style worm attacks that exploit automatic script execution | ||||||
| strictDepBuilds: true | ||||||
|
|
||||||
| # Blocks dependencies from non-registry sources (Git repos, tarball URLs) | ||||||
| # Prevents PhantomRaven-style attacks that bypass npm scanning | ||||||
|
||||||
| # Prevents PhantomRaven-style attacks that bypass npm scanning | |
| # Reduces supply-chain risk from unvetted or externally sourced subdependencies |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The comment "Prevents Shai-Hulud-style worm attacks" is an informal / unclear reference and also overstates what
strictDepBuildsguarantees. Consider replacing it with a neutral description (e.g., "mitigates supply-chain risk from dependency lifecycle scripts") and/or link to a concrete advisory if you want to reference a specific incident.