Skip to content

Require approval for dependency install scripts #49

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.

Sign up for GitHub

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

Merged
jstayton merged 1 commit into from
Oct 6, 2026
Merged

Require approval for dependency install scripts #49

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions .npmrc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
strict-allow-scripts=true
9 changes: 9 additions & 0 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,6 +25,15 @@ code in this repository.
CommonJS module (`"main": "./src/main.js"`, no build step). Node `>=22` is
required.

`.npmrc` sets `strict-allow-scripts`, so an install fails on any dependency with
an install script that hasn't been reviewed. None has one today, so
`package.json` has no `allowScripts` field yet. If a new dependency needs one,
read what the script does, then add it with `npm approve-scripts <pkg>` (pinned
to the reviewed version), or `npm deny-scripts <pkg>` when it isn't needed —
never `npm approve-scripts --all` or `--dangerously-allow-all-scripts`. It's
enforced by npm 11.19+ (Node 24 and later); Node 22's npm 10 ignores it with an
"Unknown project config" warning.

## Architecture

This is a small published library (`@truepic/webhook-verifier`) that verifies
Expand Down
Loading