Setting the file. One moment.
Subchapter 6.16
references/features-supply-chain-security.mdMarkdown5 KBView on GitHub
pnpm blocks several attack vectors by default. Agents installing dependencies must understand these, since installs can fail or prompt on them.
By default pnpm does not run dependency lifecycle scripts (preinstall/install/postinstall). Packages must be explicitly approved. Approval lives in one allowBuilds map in pnpm-workspace.yaml.
allowBuilds:
esbuild: true
core-js: false
# version selectors are supported
nx@21.6.4 || 21.6.5: truestrictDepBuilds: true (default) ⇒ unreviewed builds make install exit non-zero (ERR_PNPM_IGNORED_BUILDS). Set false to warn instead.pnpm-workspace.yaml with a placeholder so you can set true/false.
allowBuildsreplaces the removedonlyBuiltDependencies,neverBuiltDependencies,ignoredBuiltDependencies,onlyBuiltDependenciesFile, andignoreDepScripts.
pnpm approve-builds # interactive prompt
pnpm approve-builds --all # approve all pending
pnpm approve-builds esbuild fsevents !core-js # ! = deny
pnpm add --allow-build=esbuild my-bundler # approve while adding
pnpm add -g --allow-build=esbuild esbuild # global (replaces approve-builds -g)dangerouslyAllowAllBuilds: true # runs ALL build scripts now and in the future — avoidDelay installing freshly published versions so malicious releases (usually pulled within an hour) are avoided. Applies to all deps, including transitive.
minimumReleaseAge: 1440 # minutes; default 1440 (1 day) since v11
minimumReleaseAgeExclude: # always install newest of these immediately
- webpack
- '@myorg/*'
- nx@21.6.5 # exempt a specific versionminimumReleaseAgeStrict — when no in-range version satisfies the age, fail (default when you set minimumReleaseAge yourself) vs. fall back.minimumReleaseAgeIgnoreMissingTime — skip the check for registries that omit the time field (default true).Fail if a package’s trust level decreased vs earlier releases (e.g. was published by a trusted publisher, now only has provenance or nothing).
trustPolicy: no-downgrade # off (default) | no-downgrade
trustPolicyExclude:
- 'chokidar@4.0.3'
trustPolicyIgnoreAfter: 525600 # ignore the check for pkgs published > N minutes agoblockExoticSubdeps: true # defaultWhen true, only direct dependencies may use exotic sources (git repos, direct tarball URLs); all transitive deps must come from a trusted source (registry, local path, workspace link, or trusted GitHub repos).
Since v11, a downloaded tarball whose hash doesn’t match pnpm-lock.yaml is a hard error (ERR_PNPM_TARBALL_INTEGRITY) — protecting committed lockfiles from a compromised registry/proxy. --force and pnpm update do not bypass it.
pnpm install --update-checksums # narrow opt-in after verifying the new bytesThe content-addressable store, global virtual store, and metadata cache are part of pnpm’s trust domain. Share them only between mutually trusting users/jobs and protect with filesystem permissions. verifyStoreIntegrity (default true) detects accidental corruption but does not make a writable-by-untrusted store safe.
allowBuilds / pnpm approve-builds; unreviewed builds fail by default (strictDepBuilds).minimumReleaseAge (default 1 day in v11) delays new releases; trustPolicy: no-downgrade blocks trust regressions; blockExoticSubdeps limits transitive git/tarball sources.--update-checksums only after verification.