jest-validate
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): cpojer is a known Jest core maintainer; publisher rotation is expected for Jest 30. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): OpenJS Foundation transition; all added maintainers are known Jest contributors. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Old Meta/FB-era maintainers removed as part of OpenJS transition. | ai | |
| bogus-package | bogus-package | AI (bogus-package): False positive; spam-publisher signal is wrong — these are established Jest maintainers. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Jest monorepo sub-package; missing description is a stable metadata quirk, not a malware signal. | ai |
Versions (showing 100 of 121)
| Version | Deps | Published |
|---|---|---|
| 30.4.1 | 6 / 1 | |
| 30.4.0 | 6 / 1 | |
| 30.3.0 | 6 / 1 | |
| 30.2.0 | 6 / 1 | |
| 30.1.0 | 6 / 1 | |
| 30.0.5 | 6 / 1 | |
| 30.0.2 | 6 / 1 | |
| 30.0.1 | 6 / 1 | |
| 30.0.0 | 6 / 1 | |
| 29.7.0 | 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.2.2 | 6 / 1 | |
| 29.2.1 | 6 / 1 | |
| 29.2.0 | 6 / 1 | |
| 29.1.2 | 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.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.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.2 | 6 / 1 | |
| 27.0.1 | 6 / 1 | |
| 27.0.0 | 6 / 1 | |
| 26.6.2 | 6 / 1 | |
| 26.6.1 | 6 / 1 | |
| 26.6.0 | 6 / 1 | |
| 26.5.3 | 6 / 1 | |
| 26.5.2 | 6 / 1 | |
| 26.5.0 | 6 / 1 | |
| 26.4.2 | 6 / 1 | |
| 26.4.0 | 6 / 1 | |
| 26.3.0 | 6 / 1 | |
| 26.2.0 | 6 / 1 | |
| 26.1.0 | 6 / 1 | |
| 26.0.1 | 6 / 1 | |
| 26.0.0 | 6 / 1 | |
| 25.5.0 | 6 / 1 | |
| 25.4.0 | 6 / 1 | |
| 25.3.0 | 6 / 1 | |
| 25.2.6 | 6 / 1 | |
| 25.2.3 | 6 / 1 | |
| 25.2.1 | 6 / 1 | |
| 25.2.0 | 6 / 1 | |
| 25.1.0 | 6 / 0 | |
| 25.0.0 | 6 / 0 | |
| 24.9.0 | 6 / 0 | |
| 24.8.0 | 6 / 2 | |
| 24.7.0 | 6 / 2 | |
| 24.6.0 | 6 / 2 | |
| 24.5.0 | 6 / 2 | |
| 24.4.0 | 6 / 2 | |
| 24.3.1 | 6 / 2 | |
| 24.3.0 | 6 / 2 | |
| 24.0.0 | 5 / 0 | |
| 23.6.0 | 4 / 0 | |
| 23.5.0 | 4 / 0 | |
| 23.4.0 | 4 / 0 | |
| 23.3.0 | 4 / 0 | |
| 23.2.0 | 4 / 0 | |
| 23.0.1 | 4 / 0 | |
| 23.0.0 | 4 / 0 | |
| 22.4.4 | 5 / 0 | |
| 22.4.3 | 5 / 0 | |
| 22.4.2 | 5 / 0 | |
| 22.4.1 | 5 / 0 | |
| 22.4.0 | 5 / 0 | |
| 22.2.2 | 4 / 0 | |
| 22.2.0 | 4 / 0 | |
| 22.1.2 | 4 / 0 |
v30.4.1
2 findingsThis version was published by a different npm account than previous versions on 2026-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.
v30.4.0
2 findingsThis 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.
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. 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.2
2 findingsThis version was published by a different npm account than previous versions on 2025-06-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.
v30.0.1
2 findingsThis version was published by a different npm account than previous versions on 2025-06-18. 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.
v30.0.0
2 findingsThis version was published by a different npm account than previous versions on 2025-06-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.
v29.7.0
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.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.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. Consider requesting the maintainer enable provenance via CI/CD.
v29.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.