npm-lifecycle
JavaScript package lifecycle hook runner
Supply chain provenance
Status for the latest visible version.
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
Keywords
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): Core function of npm-lifecycle is spawning child processes for lifecycle hooks; this import is fundamental and expected. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): npm org consolidation; published by trusted isaacs account with strong track record. | ai | |
| provenance | publisher-changed | AI (provenance): Both iarna and zkat are known npm CLI team members; legitimate maintainer transition within the npm org. | ai | |
| semgrep | semgrep:env-bulk-read | AI (semgrep): Iterates env keys only to find case-insensitive PATH on Windows; core to lifecycle runner functionality. | ai | |
| phantom-deps | phantom-dep:node-gyp | AI (phantom-deps): node-gyp is a declared dep used as a runtime binary by the lifecycle runner; not a direct import. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 3.1.5 | 8 / 5 | |
| 3.1.4 | 8 / 7 | |
| 3.1.3 | 8 / 7 | |
| 3.1.2 | 8 / 7 | |
| 3.1.1 | 8 / 7 | |
| 3.1.0 | 8 / 7 | |
| 3.0.0 | 8 / 7 | |
| 2.1.1 | 8 / 7 | |
| 2.1.0 | 8 / 7 | |
| 2.0.3 | 8 / 7 | |
| 2.0.2 | 8 / 7 | |
| 2.0.1 | 8 / 7 | |
| 2.0.0 | 8 / 7 | |
| 1.0.3 | 5 / 6 | |
| 1.0.2 | 5 / 6 | |
| 1.0.1 | 5 / 6 | |
| 1.0.0 | 5 / 6 |
v3.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
2 findingsThis version was published by a different npm account than previous versions on 2019-05-08. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
2 findingsThis version was published by a different npm account than previous versions on 2018-03-08. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
2 findingsThis version was published by a different npm account than previous versions on 2017-11-17. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.