← Home

execspawn

npm Repository Homepage

spawn stream for child_process.exec

4
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

andreasmadsen

Keywords

execstreamspawn

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:child-process-import AI (semgrep): execspawn is explicitly a child_process.spawn wrapper; importing child_process is the core functionality, not a risk signal. ai
provenance no-provenance AI (provenance): Package is 4634 days old, predating Sigstore provenance on npm; absence is expected and not a risk indicator. ai

Versions (showing 4 of 4)

Version Deps Published
1.0.1 1 / 2
1.0.0 1 / 2
0.2.1 1 / 2
0.2.0 1 / 2

v1.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.1

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.

v0.2.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.