← Home

win-spawn

npm Repository

Spawn for node.js but in a way that works regardless of which OS you're using

7
Versions
BSD
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

forbeslindesay

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher change from forbes to forbeslindesay is a same-person account rename in 2013; not an account compromise. ai
maintainer-change maintainer-takeover AI (maintainer-change): forbes and forbeslindesay are the same person (Forbes Lindesay); account rename/consolidation in 2013, not a hostile takeover. Publisher has strong track record. ai
maintainer-change maintainer-added AI (maintainer-change): forbeslindesay is the same individual as forbes; this is an account rename, not a new third-party maintainer. ai
maintainer-change maintainer-removed AI (maintainer-change): forbes account removed because it was renamed to forbeslindesay; same individual, not a hostile removal. ai
semgrep semgrep:child-process-import AI (semgrep): win-spawn's core purpose is wrapping child_process.spawn for cross-platform use; child_process import is expected and intentional. ai

Versions (showing 7 of 7)

Version Deps Published
2.0.0 0 / 1
1.1.2 0 / 1
1.1.1 0 / 1
1.1.0 0 / 0
1.0.2 0 / 0
1.0.1 0 / 0
0.0.0 0 / 0

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

1 finding
LOW No provenance attestation provenance

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

v1.1.1

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. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.2

1 finding
LOW No provenance attestation provenance

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

v1.0.1

3 findings
HIGH Complete maintainer takeover detected maintainer-change

All previous maintainers (forbes) were replaced by new maintainers (forbeslindesay). This is a strong signal of a potential package hijack and requires careful review.

HIGH Publisher changed: forbes → forbeslindesay (on 2013-01-31) provenance

This version was published by a different npm account than previous versions on 2013-01-31. 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.