@npmcli/promise-spawn
spawn processes the way the npm cli likes to do
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): npm-cli-ops and saquibkhan are known npm CLI team members; normal team roster change. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): darcyclarke and nlf departures reflect known npm CLI team changes; not indicative of takeover. | ai | |
| provenance | publisher-changed | AI (provenance): Both lukekarrys and nlf are known npm CLI team members at GitHub; routine team rotation within @npmcli scope. | ai | |
| provenance | no-provenance | AI (provenance): Published in 2022 before Sigstore provenance was standard for npm CLI packages; low-risk informational finding. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): This package's entire purpose is to wrap child_process.spawn; the import is the core functionality, not a malicious indicator. Stable false positive for all versions. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 10.0.0 | 1 / 4 | |
| 9.0.1 | 1 / 4 | |
| 9.0.0 | 1 / 4 | |
| 8.0.3 | 1 / 4 | |
| 8.0.2 | 1 / 4 | |
| 8.0.1 | 1 / 4 | |
| 8.0.0 | 1 / 4 | |
| 7.0.2 | 1 / 4 | |
| 7.0.1 | 1 / 4 | |
| 7.0.0 | 1 / 4 | |
| 6.0.2 | 1 / 5 | |
| 6.0.1 | 1 / 5 | |
| 6.0.0 | 1 / 5 | |
| 5.0.0 | 0 / 4 | |
| 4.0.0 | 1 / 4 | |
| 3.0.0 | 1 / 4 | |
| 2.0.1 | 0 / 4 | |
| 2.0.0 | 0 / 4 | |
| 1.3.2 | 1 / 3 | |
| 1.3.1 | 1 / 3 | |
| 1.3.0 | 1 / 3 | |
| 1.2.0 | 1 / 3 | |
| 1.1.0 | 1 / 3 | |
| 1.0.0 | 1 / 3 |
v10.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.0.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.1
2 findingsThis version was published by a different npm account than previous versions on 2024-01-04. 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.
v7.0.0
2 findingsThis version was published by a different npm account than previous versions on 2023-08-30. 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.
v6.0.2
2 findingsThis version was published by a different npm account than previous versions on 2022-12-12. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.1
2 findingsThis version was published by a different npm account than previous versions on 2022-11-01. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
2 findingsThis version was published by a different npm account than previous versions on 2022-11-01. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
2 findingsThis version was published by a different npm account than previous versions on 2022-10-26. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
2 findingsThis version was published by a different npm account than previous versions on 2022-04-05. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
2 findingsThis version was published by a different npm account than previous versions on 2022-03-03. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
2 findingsThis version was published by a different npm account than previous versions on 2021-06-09. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
2 findingsThis version was published by a different npm account than previous versions on 2020-10-30. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
2 findingsThis version was published by a different npm account than previous versions on 2020-10-26. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
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.