@pnpm/exec.commands
Commands for running scripts
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): pnpmuser is the established pnpm org publisher with 688 approved packages; transition from zkochan is a known org-level maintainer handoff. | ai | |
| dependencies | unvetted-dep:@pnpm/log.group | AI (dependencies): Internal pnpm monorepo package; consistent with established publisher pattern. | ai | |
| dependencies | unvetted-dep:@pnpm/shell.path | AI (dependencies): Internal pnpm monorepo package; consistent with established publisher pattern. | ai | |
| dependencies | unvetted-dep:@pnpm/exec.pnpm-cli-runner | AI (dependencies): Internal pnpm monorepo package; consistent with established publisher pattern. | ai | |
| dependencies | unvetted-dep:@pnpm/workspace.injected-deps-syncer | AI (dependencies): Internal pnpm monorepo package; consistent with established publisher pattern. | ai | |
| phantom-deps | phantom-dep:@pnpm/store.path | AI (phantom-deps): Same-org pnpm monorepo dep; phantom-dep heuristic is a false positive here. | ai | |
| phantom-deps | phantom-dep:@pnpm/engine.runtime.commands | AI (phantom-deps): Same-org pnpm monorepo dep; phantom-dep heuristic is a false positive here. | ai | |
| phantom-deps | phantom-dep:@zkochan/rimraf | AI (phantom-deps): Declared in package.json dependencies; phantom-dep heuristic fires on config-only reference, stable false positive. | ai | |
| semgrep | semgrep:env-spread | AI (semgrep): Script-runner package intentionally passes process.env to child processes; this is expected behavior for exec/lifecycle tooling. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 1100.2.2 | 38 / 13 | |
| 1100.2.1 | 38 / 13 | |
| 1100.2.0 | 38 / 13 | |
| 1100.1.13 | 38 / 14 | |
| 1100.1.12 | 38 / 14 | |
| 1100.1.11 | 38 / 14 | |
| 1100.1.10 | 38 / 14 | |
| 1100.1.9 | 38 / 14 | |
| 1100.1.8 | 38 / 14 | |
| 1100.1.7 | 38 / 14 | |
| 1100.1.6 | 38 / 14 | |
| 1100.1.5 | 38 / 14 | |
| 1100.1.4 | 38 / 14 | |
| 1100.1.3 | 38 / 14 | |
| 1100.1.2 | 38 / 14 | |
| 1100.1.1 | 38 / 14 | |
| 1100.1.0 | 38 / 14 | |
| 1100.0.9 | 37 / 14 | |
| 1100.0.8 | 37 / 14 | |
| 1100.0.7 | 37 / 14 | |
| 1100.0.6 | 37 / 14 | |
| 1100.0.5 | 37 / 14 | |
| 1100.0.4 | 37 / 14 | |
| 1100.0.3 | 37 / 14 | |
| 1100.0.2 | 37 / 14 | |
| 1100.0.1 | 37 / 14 | |
| 1100.0.0 | 37 / 14 | |
| 1001.0.15 | 37 / 13 |
v1100.2.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1100.2.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1100.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1100.1.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1100.1.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1100.1.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1100.1.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1100.1.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1100.1.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1100.1.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1100.1.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1100.1.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1100.1.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1100.1.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1100.1.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1100.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1100.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1100.0.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1100.0.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1100.0.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1100.0.6
2 findingsSpreading entire process.env into an object — may capture all secrets 11 | } 12 | const pathEnv = prependDirsToPath(opts.prependPaths); > 13 | return { 14 | ...process.env, 15 | ...opts.extraEnv,
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1100.0.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1100.0.4
2 findingsThis version was published by a different npm account than previous versions on 2026-04-21. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1100.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1100.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1100.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1100.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1001.0.15
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.