npm-run-all2
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): Transition from personal account to GitHub Actions CI/CD publishing, confirmed by SLSA provenance. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Major version bump after period of stability; established package with provenance attestation. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Fires on CLI help-loader with controlled tool name variable, not arbitrary user input. Stable pattern for this package. | ai | |
| semgrep | semgrep:env-bulk-read | AI (semgrep): npm config parsing via process.env enumeration is core documented functionality of npm-run-all2. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 9.0.1 | 8 / 14 | |
| 9.0.0 | 8 / 14 | |
| 8.0.4 | 8 / 10 | |
| 8.0.3 | 8 / 10 | |
| 8.0.2 | 8 / 10 | |
| 8.0.1 | 8 / 10 | |
| 8.0.0 | 8 / 10 |
v9.0.1
2 findingsThis version was published by a different npm account than previous versions on 2026-05-23. 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.
v9.0.0
2 findingsThis version was published by a different npm account than previous versions on 2026-05-19. 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.
v8.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.