@jest/environment
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): @types/node is a types-only package with no executable code; its addition to @jest/environment is expected for Node.js type augmentation in Jest's environment interface. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Jest is a Facebook/Meta OSS project with routine maintainer rotation among core team members; removal of mjesun reflects normal team changes, not a takeover. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change from rubennorte to scotthovestadt reflects a legitimate Jest team maintainer transition in 2019; scotthovestadt is a known Jest contributor with a strong track record. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): scotthovestadt is a well-established Jest/Facebook team member; this maintainer addition is a legitimate transition, not a takeover. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Missing description is a known characteristic of this Jest monorepo sub-package; not indicative of malicious intent. | ai | |
| provenance | no-provenance | AI (provenance): Package predates Sigstore provenance attestation; absence is expected for this era of Jest releases. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): @types/node is a type-only dependency used for TypeScript declarations, not directly imported at runtime. Standard pattern for Jest packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Inflated semver and missing metadata are expected for a Jest monorepo package versioned in lockstep with the broader Jest release line. Not indicative of spam or malice. | ai | |
| dependencies | unvetted-dep:@jest/fake-timers | AI (dependencies): @jest/fake-timers is a sibling package in the Jest monorepo, always versioned in lockstep. Stable and expected dependency for this package. | ai |
Versions (showing 93 of 93)
| Version | Deps | Published |
|---|---|---|
| 30.4.1 | 4 / 0 | |
| 30.4.0 | 4 / 0 | |
| 30.3.0 | 4 / 0 | |
| 30.2.0 | 4 / 0 | |
| 30.1.2 | 4 / 0 | |
| 30.1.1 | 4 / 0 | |
| 30.1.0 | 4 / 0 | |
| 30.0.5 | 4 / 0 | |
| 30.0.4 | 4 / 0 | |
| 30.0.2 | 4 / 0 | |
| 30.0.1 | 4 / 0 | |
| 30.0.0 | 4 / 0 | |
| 29.7.0 | 4 / 0 | |
| 29.6.4 | 4 / 0 | |
| 29.6.3 | 4 / 0 | |
| 29.6.2 | 4 / 0 | |
| 29.6.1 | 4 / 0 | |
| 29.6.0 | 4 / 0 | |
| 29.5.0 | 4 / 0 | |
| 29.4.3 | 4 / 0 | |
| 29.4.2 | 4 / 0 | |
| 29.4.1 | 4 / 0 | |
| 29.4.0 | 4 / 0 | |
| 29.3.1 | 4 / 0 | |
| 29.3.0 | 4 / 0 | |
| 29.2.2 | 4 / 0 | |
| 29.2.1 | 4 / 0 | |
| 29.2.0 | 4 / 0 | |
| 29.1.2 | 4 / 0 | |
| 29.1.1 | 4 / 0 | |
| 29.1.0 | 4 / 0 | |
| 29.0.3 | 4 / 0 | |
| 29.0.2 | 4 / 0 | |
| 29.0.1 | 4 / 0 | |
| 29.0.0 | 4 / 0 | |
| 28.1.3 | 4 / 0 | |
| 28.1.2 | 4 / 0 | |
| 28.1.1 | 4 / 0 | |
| 28.1.0 | 4 / 0 | |
| 28.0.2 | 4 / 0 | |
| 28.0.1 | 4 / 0 | |
| 28.0.0 | 4 / 0 | |
| 27.5.1 | 4 / 0 | |
| 27.5.0 | 4 / 0 | |
| 27.4.6 | 4 / 0 | |
| 27.4.4 | 4 / 0 | |
| 27.4.2 | 4 / 0 | |
| 27.4.1 | 4 / 0 | |
| 27.4.0 | 4 / 0 | |
| 27.3.1 | 4 / 0 | |
| 27.3.0 | 4 / 0 | |
| 27.2.5 | 4 / 0 | |
| 27.2.4 | 4 / 0 | |
| 27.2.3 | 4 / 0 | |
| 27.2.2 | 4 / 0 | |
| 27.2.0 | 4 / 0 | |
| 27.1.1 | 4 / 0 | |
| 27.1.0 | 4 / 0 | |
| 27.0.6 | 4 / 0 | |
| 27.0.5 | 4 / 0 | |
| 27.0.3 | 4 / 0 | |
| 27.0.2 | 4 / 0 | |
| 27.0.1 | 4 / 0 | |
| 27.0.0 | 4 / 0 | |
| 26.6.2 | 4 / 0 | |
| 26.6.1 | 4 / 0 | |
| 26.6.0 | 4 / 0 | |
| 26.5.2 | 4 / 0 | |
| 26.5.0 | 4 / 0 | |
| 26.3.0 | 4 / 0 | |
| 26.2.0 | 4 / 0 | |
| 26.1.0 | 3 / 1 | |
| 26.0.1 | 3 / 1 | |
| 26.0.0 | 3 / 1 | |
| 25.5.0 | 3 / 1 | |
| 25.4.0 | 3 / 1 | |
| 25.3.0 | 3 / 1 | |
| 25.2.6 | 3 / 1 | |
| 25.2.4 | 3 / 1 | |
| 25.2.3 | 3 / 1 | |
| 25.2.1 | 3 / 1 | |
| 25.2.0 | 3 / 1 | |
| 25.1.0 | 3 / 1 | |
| 25.0.0 | 4 / 0 | |
| 24.9.0 | 4 / 0 | |
| 24.8.0 | 4 / 0 | |
| 24.7.1 | 4 / 0 | |
| 24.7.0 | 4 / 0 | |
| 24.6.0 | 4 / 0 | |
| 24.5.0 | 5 / 0 | |
| 24.4.0 | 5 / 0 | |
| 24.3.1 | 5 / 0 | |
| 24.3.0 | 5 / 0 |
v30.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v30.4.0
2 findings[Accepted risk] Package 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.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v30.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Consider requesting the maintainer enable provenance via CI/CD.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.4.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.2.0
2 findingsThis version was published by a different npm account than previous versions on 2021-09-13. 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.
v27.1.1
2 findings[Accepted risk] Package 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 2021-09-08. This could indicate a legitimate maintainer transition or an account compromise.
v27.1.0
2 findingsThis version was published by a different npm account than previous versions on 2021-08-27. 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.
v27.0.6
2 findingsThis version was published by a different npm account than previous versions on 2021-06-28. 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.
v27.0.5
2 findingsThis version was published by a different npm account than previous versions on 2021-06-22. 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.
v27.0.3
2 findingsThis version was published by a different npm account than previous versions on 2021-05-29. 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.
v27.0.2
2 findingsThis version was published by a different npm account than previous versions on 2021-05-29. 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.
v27.0.1
2 findingsThis version was published by a different npm account than previous versions on 2021-05-25. 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.
v27.0.0
2 findingsThis version was published by a different npm account than previous versions on 2021-05-25. 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.
v26.6.2
2 findingsThis version was published by a different npm account than previous versions on 2020-11-02. 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.
v26.6.1
2 findingsThis version was published by a different npm account than previous versions on 2020-10-23. 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.
v26.6.0
2 findingsThis version was published by a different npm account than previous versions on 2020-10-19. 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.
v26.5.2
2 findingsThis version was published by a different npm account than previous versions on 2020-10-06. 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.
v26.5.0
2 findingsThis version was published by a different npm account than previous versions on 2020-10-05. 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.
v26.3.0
2 findingsThis version was published by a different npm account than previous versions on 2020-08-10. 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.
v26.2.0
2 findingsThis version was published by a different npm account than previous versions on 2020-07-30. 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.
v26.1.0
2 findingsThis version was published by a different npm account than previous versions on 2020-06-23. 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.
v26.0.1
2 findingsThis version was published by a different npm account than previous versions on 2020-05-05. 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.
v26.0.0
2 findingsThis version was published by a different npm account than previous versions on 2020-05-04. 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.
v25.5.0
2 findingsThis version was published by a different npm account than previous versions on 2020-04-28. 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.
v25.4.0
2 findingsThis version was published by a different npm account than previous versions on 2020-04-19. 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.
v25.3.0
2 findingsThis version was published by a different npm account than previous versions on 2020-04-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.
v25.2.6
2 findingsThis version was published by a different npm account than previous versions on 2020-04-02. 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.
v25.2.4
2 findingsThis version was published by a different npm account than previous versions on 2020-03-29. 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.
v25.2.3
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.2.1
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.2.0
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.1.0
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.9.0
2 findingsThis version was published by a different npm account than previous versions on 2019-08-16. 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.
v24.8.0
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.