jest-environment-node
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher change from cpojer to kentaromiura occurred in 2016 as part of documented Jest team transitions at Facebook. Historical event, not a current risk. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Added maintainers (dmitriiabramov, fb, kentaromiura) are known Jest core contributors from Facebook. This 2016 change reflects legitimate team expansion, not compromise. | ai | |
| dependencies | unvetted-dep:@jest/fake-timers | AI (dependencies): @jest/fake-timers is a first-party Jest monorepo package published in lockstep; not an unvetted third-party dependency. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): @types/node is a standard runtime type dependency for jest-environment-node; phantom-dep detection is a false positive here. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Spam signals are false positives: cpojer and fb are canonical Facebook/Jest maintainer accounts. Tiny payload and no description are normal for this utility sub-package. | ai |
Versions (showing 100 of 156)
| Version | Deps | Published |
|---|---|---|
| 30.4.1 | 7 / 2 | |
| 30.4.0 | 7 / 2 | |
| 30.2.0 | 7 / 2 | |
| 30.1.2 | 7 / 2 | |
| 30.1.1 | 7 / 2 | |
| 30.1.0 | 7 / 2 | |
| 30.0.5 | 7 / 2 | |
| 30.0.4 | 7 / 2 | |
| 30.0.2 | 7 / 2 | |
| 30.0.1 | 7 / 2 | |
| 30.0.0 | 7 / 2 | |
| 29.7.0 | 6 / 1 | |
| 29.6.4 | 6 / 1 | |
| 29.6.3 | 6 / 1 | |
| 29.6.2 | 6 / 1 | |
| 29.6.1 | 6 / 1 | |
| 29.6.0 | 6 / 1 | |
| 29.5.0 | 6 / 1 | |
| 29.4.3 | 6 / 1 | |
| 29.4.2 | 6 / 1 | |
| 29.4.1 | 6 / 1 | |
| 29.4.0 | 6 / 1 | |
| 29.3.1 | 6 / 1 | |
| 29.3.0 | 6 / 1 | |
| 29.2.2 | 6 / 1 | |
| 29.2.1 | 6 / 1 | |
| 29.2.0 | 6 / 1 | |
| 29.1.2 | 6 / 1 | |
| 29.1.1 | 6 / 1 | |
| 29.1.0 | 6 / 1 | |
| 29.0.3 | 6 / 1 | |
| 29.0.2 | 6 / 1 | |
| 29.0.1 | 6 / 1 | |
| 29.0.0 | 6 / 1 | |
| 28.1.3 | 6 / 1 | |
| 28.1.2 | 6 / 1 | |
| 28.1.1 | 6 / 1 | |
| 28.1.0 | 6 / 1 | |
| 28.0.2 | 6 / 1 | |
| 28.0.1 | 6 / 1 | |
| 28.0.0 | 6 / 1 | |
| 27.5.1 | 6 / 1 | |
| 27.5.0 | 6 / 1 | |
| 27.4.6 | 6 / 1 | |
| 27.4.4 | 6 / 1 | |
| 27.4.2 | 6 / 1 | |
| 27.4.1 | 6 / 1 | |
| 27.4.0 | 6 / 1 | |
| 27.3.1 | 6 / 1 | |
| 27.3.0 | 6 / 1 | |
| 27.2.5 | 6 / 1 | |
| 27.2.4 | 6 / 1 | |
| 27.2.3 | 6 / 1 | |
| 27.2.2 | 6 / 1 | |
| 27.2.0 | 6 / 1 | |
| 27.1.1 | 6 / 1 | |
| 27.1.0 | 6 / 1 | |
| 27.0.6 | 6 / 1 | |
| 27.0.5 | 6 / 1 | |
| 27.0.3 | 6 / 1 | |
| 27.0.2 | 6 / 1 | |
| 27.0.1 | 6 / 1 | |
| 27.0.0 | 6 / 1 | |
| 26.6.2 | 6 / 1 | |
| 26.6.1 | 6 / 0 | |
| 26.6.0 | 6 / 0 | |
| 26.5.2 | 6 / 0 | |
| 26.5.0 | 6 / 0 | |
| 26.3.0 | 6 / 0 | |
| 26.2.0 | 6 / 0 | |
| 26.1.0 | 5 / 0 | |
| 26.0.1 | 5 / 0 | |
| 26.0.0 | 5 / 0 | |
| 25.5.0 | 6 / 1 | |
| 25.4.0 | 6 / 1 | |
| 25.3.0 | 6 / 1 | |
| 25.2.6 | 6 / 1 | |
| 25.2.4 | 6 / 1 | |
| 25.2.3 | 6 / 1 | |
| 25.2.2 | 6 / 1 | |
| 25.2.1 | 5 / 0 | |
| 25.2.0 | 5 / 0 | |
| 25.1.0 | 5 / 0 | |
| 25.0.0 | 5 / 0 | |
| 24.9.0 | 5 / 0 | |
| 24.8.0 | 5 / 0 | |
| 24.7.1 | 5 / 0 | |
| 24.7.0 | 5 / 0 | |
| 24.6.0 | 5 / 0 | |
| 24.5.0 | 5 / 0 | |
| 24.4.0 | 5 / 0 | |
| 24.3.1 | 5 / 0 | |
| 24.3.0 | 5 / 0 | |
| 24.0.0 | 2 / 0 | |
| 23.4.0 | 2 / 0 | |
| 23.3.0 | 2 / 0 | |
| 23.2.0 | 2 / 0 | |
| 23.1.0 | 2 / 0 | |
| 23.0.1 | 2 / 0 | |
| 23.0.0 | 2 / 0 |
v30.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v30.4.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2026-05-07. This could indicate a legitimate maintainer transition or an account compromise.
v30.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v30.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v30.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v30.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v30.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v30.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v30.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v30.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v30.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v28.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.2.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-03-26. This could indicate a legitimate maintainer transition or an account compromise.
v25.2.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-03-25. This could indicate a legitimate maintainer transition or an account compromise.
v25.1.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-01-22. This could indicate a legitimate maintainer transition or an account compromise.
v25.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.8.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2019-05-05. This could indicate a legitimate maintainer transition or an account compromise.
v24.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.7.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2019-04-03. This could indicate a legitimate maintainer transition or an account compromise.
v24.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.3.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2019-03-07. This could indicate a legitimate maintainer transition or an account compromise.
v24.0.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2019-01-25. This could indicate a legitimate maintainer transition or an account compromise.
v23.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.