@git-lazy/spawn No license 17 versions

@git-lazy/spawn

npm Repository Homepage

17

Versions

—

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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

bluelovers

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:bluebird	AI (phantom-deps): bluebird is a declared runtime dep; phantom-dep heuristic false positive for this package.	ai	2026/04/29
phantom-deps	phantom-dep:debug-color2	AI (phantom-deps): debug-color2 is a declared runtime dep; phantom-dep heuristic false positive for this package.	ai	2026/04/29
phantom-deps	phantom-dep:crlf-normalize	AI (phantom-deps): crlf-normalize is a declared runtime dep; phantom-dep heuristic false positive for this package.	ai	2026/04/29

Versions (showing 17 of 17)

Version	Deps	Published
1.0.41	11 / 0	2024-03-09
1.0.40	11 / 0	2024-03-09
1.0.39	11 / 0	2024-02-03
1.0.38	11 / 0	2022-10-28
1.0.37	11 / 0	2022-10-01
1.0.36	11 / 0	2022-09-30
1.0.35	11 / 0	2022-08-27
1.0.34	11 / 0	2022-07-27
1.0.33	11 / 0	2022-07-26
1.0.32	11 / 0	2022-07-14
1.0.31	9 / 0	2022-03-29
1.0.30	9 / 0	2022-02-21
1.0.29	9 / 0	2022-02-15
1.0.28	8 / 0	2021-12-15
1.0.27	8 / 0	2021-08-29
1.0.26	8 / 0	2021-07-20
1.0.25	7 / 1	2021-05-30

v1.0.40

1 finding

LOW No provenance attestation provenance

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

v1.0.39

1 finding

LOW No provenance attestation provenance

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

v1.0.38

1 finding

LOW No provenance attestation provenance

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

v1.0.37

1 finding

LOW No provenance attestation provenance

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

v1.0.36

1 finding

LOW No provenance attestation provenance

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

v1.0.35

1 finding

LOW No provenance attestation provenance

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

v1.0.34

1 finding

LOW No provenance attestation provenance

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

v1.0.33

1 finding

LOW No provenance attestation provenance

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

v1.0.32

1 finding

LOW No provenance attestation provenance

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

v1.0.31

1 finding

LOW No provenance attestation provenance

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

v1.0.30

1 finding

LOW No provenance attestation provenance

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

v1.0.29

1 finding

LOW No provenance attestation provenance

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

v1.0.28

1 finding

LOW No provenance attestation provenance

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

v1.0.27

1 finding

LOW No provenance attestation provenance

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

v1.0.26

1 finding

LOW No provenance attestation provenance

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

v1.0.25

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.