spawn-default-shell
Spawn shell command with platform default shell
3
Versions
MIT
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
kimmobrunfeldt
Keywords
shellexecbashshcommandcross-platformwindowslinuxmac
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): This package's entire purpose is to spawn shell commands via child_process; the import is expected and benign for all versions. | ai | |
| semgrep | semgrep:child-process-spawn | AI (semgrep): child_process.spawn() is the core functionality of this package; not a risk signal for any version. | ai | |
| provenance | no-provenance | AI (provenance): Established package from a trusted publisher; lack of Sigstore provenance is not a meaningful risk here. | ai |
v2.0.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.