git-spawned-stream MIT 4 versions

git-spawned-stream

npm Repository Homepage

Create a readable stream from a spawned git process.

Versions

MIT

License

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

alessioalex

Keywords

spawnedgitstream

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 core purpose is spawning git processes as readable streams; child_process.spawn is fundamental to its design, not a malicious indicator.	ai	2026/04/24
provenance	no-provenance	AI (provenance): Package is 11+ years old, predating Sigstore provenance on npm. Absence is expected and not a risk signal for this established package.	ai	2026/04/24

Versions (showing 4 of 4)

Version	Deps	Published
1.0.1	2 / 3	2018-10-12
1.0.0	2 / 3	2017-05-02
0.1.1	2 / 3	2015-10-30
0.1.0	2 / 3	2014-05-25

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

1 finding

LOW No provenance attestation provenance

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

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