npm-run-all-next
A CLI tool to run multiple npm-scripts in parallel or sequentially, with support for retrying failed tasks.
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@mysticatea/eslint-plugin | AI (phantom-deps): Confirmed phantom: it's a lint-only dep incorrectly placed in dependencies; not imported at runtime. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Loads help submodule by CLI command name; not user-controlled arbitrary input. | ai | |
| semgrep | semgrep:env-bulk-read | AI (semgrep): Standard npm package config pattern; reads env keys to find npm_package_config_* variables only. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 1.4.2 | 9 / 15 | |
| 1.4.1 | 9 / 15 | |
| 1.4.0 | 9 / 15 | |
| 1.3.0 | 9 / 15 | |
| 1.1.1 | 10 / 15 | |
| 1.0.1 | 11 / 15 | |
| 1.0.0 | 11 / 15 |
v1.4.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.