File Explorer

1.TH "NPM-DENY-SCRIPTS" "1" "June 2026" "NPM@11.17.0" ""2.SH "NAME"3\fBnpm-deny-scripts\fR - Deny install scripts for specific dependencies4.SS "Synopsis"5.P6.RS 27.nf8npm deny-scripts <pkg> \[lB]<pkg> ...\[rB]9npm deny-scripts --all10.fi11.RE12.P13Note: This command is unaware of workspaces.14.SS "Description"15.P16The companion command to npm help approve-scripts. Writes \fBfalse\fR entries into the \fBallowScripts\fR field of your project's \fBpackage.json\fR, recording that a dependency must not run install scripts even if a future version would otherwise be eligible.17.P18In the current release, install scripts still run by default, so \fBdeny-scripts\fR only affects how installs of denied packages are reported. A future release will block unreviewed install scripts and respect deny entries at install time.19.P20.RS 221.nf22npm deny-scripts <pkg> \[lB]<pkg> ...\[rB]23npm deny-scripts --all24.fi25.RE26.P27\fB<pkg>\fR matches every installed version of that package. Denies are always written name-only (\fB"pkg": false\fR), regardless of \fB--allow-scripts-pin\fR. Pinning a deny to a specific version would silently re-allow scripts for any other version of the same package, which defeats the purpose; the command picks the safer default for you.28.P29\fB--all\fR denies every package with unreviewed install scripts.30.P31If a \fBtrue\fR (pinned or name-only) entry exists for a package and you then deny it, the existing allow entries are removed so the name-only deny is unambiguous.32.SS "Examples"33.P34.RS 235.nf36# Deny a specific package outright37npm deny-scripts telemetry-pkg38 39# Deny everything that has install scripts and isn't already approved40npm deny-scripts --all41.fi42.RE43.SS "Configuration"44.SS "\fBall\fR"45.RS 046.IP \(bu 447Default: false48.IP \(bu 449Type: Boolean50.RE 051 52.P53Show or act on all packages, not just the ones your project directly depends on. For \fBnpm outdated\fR and \fBnpm ls\fR this lists every outdated or installed package. For \fBnpm approve-scripts\fR and \fBnpm deny-scripts\fR it selects every package with pending install scripts.54.SS "\fBallow-scripts-pending\fR"55.RS 056.IP \(bu 457Default: false58.IP \(bu 459Type: Boolean60.RE 061 62.P63List packages with install scripts that are not yet covered by the \fBallowScripts\fR policy, without modifying \fBpackage.json\fR. Only meaningful for \fBnpm approve-scripts\fR.64.SS "\fBallow-scripts-pin\fR"65.RS 066.IP \(bu 467Default: true68.IP \(bu 469Type: Boolean70.RE 071 72.P73Write pinned (\fBpkg@version\fR) entries when approving install scripts. Set to \fBfalse\fR to write name-only entries that allow any version. Has no effect on \fBnpm deny-scripts\fR, which always writes name-only entries regardless of this setting.74.SS "\fBjson\fR"75.RS 076.IP \(bu 477Default: false78.IP \(bu 479Type: Boolean80.RE 081 82.P83Whether or not to output JSON data, rather than the normal output.84.RS 085.IP \(bu 486In \fBnpm pkg set\fR it enables parsing set values with JSON.parse() before saving them to your \fBpackage.json\fR.87.RE 088 89.P90Not supported by all npm commands.91.SS "See Also"92.RS 093.IP \(bu 494npm help approve-scripts95.IP \(bu 496npm help install97.IP \(bu 498\fBpackage.json\fR \fI\(la/configuring-npm/package-json\(ra\fR99.RE 0100