← Home

spawn-wrap

Wrap all spawned Node.js child processes by adding environs and arguments ahead of the main JavaScript file argument.

37
Versions
BlueOak-1.0.0
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

isaacsbcoecoreyfarrell

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): bcoe → coreyfarrell is a known maintainer transition within the istanbuljs org; both are established npm publishers. ai
provenance no-provenance AI (provenance): Published in 2019 before Sigstore provenance existed; not a meaningful signal for this package. ai
semgrep semgrep:child-process-import AI (semgrep): spawn-wrap's core purpose is wrapping child process spawning; child_process import is fundamental to its functionality. ai
semgrep semgrep:dynamic-require AI (semgrep): Dynamic require is part of spawn-wrap's shim mechanism loading settings-driven modules; expected pattern for this package. ai
bogus-package bogus-package AI (bogus-package): isaacs (Isaac Z. Schlueter, npm creator) flagged as spam publisher is a clear false positive. No keywords is trivial. ai

Versions (showing 37 of 37)

Version Deps Published
3.0.0 7 / 1
2.0.0 6 / 2
1.4.3 6 / 1
1.4.2 6 / 1
1.4.1 6 / 1
1.4.0 6 / 1
1.3.8 6 / 1
1.3.7 6 / 1
1.3.6 6 / 1
1.3.5 6 / 1
1.3.4 6 / 1
1.3.3 6 / 1
1.3.2 6 / 1
1.3.1 6 / 1
1.3.0 6 / 1
1.2.4 6 / 1
1.2.3 6 / 1
1.2.2 6 / 1
1.2.1 6 / 1
1.2.0 6 / 1
1.1.1 5 / 1
1.1.0 5 / 1
1.0.2 5 / 1
1.0.1 4 / 1
0.1.2 3 / 0
0.1.1 3 / 0
0.1.0 3 / 0
0.0.9 2 / 0
0.0.8 2 / 0
0.0.7 2 / 0
0.0.6 2 / 0
0.0.5 2 / 0
0.0.4 2 / 0
0.0.3 2 / 0
0.0.2 2 / 0
0.0.1 2 / 0
0.0.0 1 / 0

v3.0.0

2 findings
HIGH Publisher changed: coreyfarrell → bcoe (on 2026-02-22) provenance

This version was published by a different npm account than previous versions on 2026-02-22. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v2.0.0

2 findings
HIGH Publisher changed: bcoe → coreyfarrell (on 2019-12-20) provenance

This version was published by a different npm account than previous versions on 2019-12-20. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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