jest-each
Parameterised tests for Jest
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): cpojer is a well-known Jest core maintainer; publisher change reflects legitimate Jest project governance transition to OpenJS Foundation. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers (cpojer, rickhanlonii, aaronabramov, openjs-operations) are known Jest core contributors and OpenJS Foundation accounts — legitimate governance transition. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removed maintainers reflect Jest project governance reorganization under OpenJS Foundation; consistent with documented transition. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @jest/get-type is an internal Jest monorepo package replacing jest-get-type; a known v30 scope reorganization, not a suspicious external dependency. | ai |
Versions (showing 98 of 98)
| Version | Deps | Published |
|---|---|---|
| 30.4.1 | 5 / 0 | |
| 30.4.0 | 5 / 0 | |
| 30.3.0 | 5 / 0 | |
| 30.2.0 | 5 / 0 | |
| 30.1.0 | 5 / 0 | |
| 30.0.5 | 5 / 0 | |
| 30.0.2 | 5 / 0 | |
| 30.0.1 | 5 / 0 | |
| 30.0.0 | 5 / 0 | |
| 29.7.0 | 5 / 0 | |
| 29.6.3 | 5 / 0 | |
| 29.6.2 | 5 / 0 | |
| 29.6.1 | 5 / 0 | |
| 29.6.0 | 5 / 0 | |
| 29.5.0 | 5 / 0 | |
| 29.4.3 | 5 / 0 | |
| 29.4.2 | 5 / 0 | |
| 29.4.1 | 5 / 0 | |
| 29.4.0 | 5 / 0 | |
| 29.3.1 | 5 / 0 | |
| 29.2.1 | 5 / 0 | |
| 29.2.0 | 5 / 0 | |
| 29.1.2 | 5 / 0 | |
| 29.1.0 | 5 / 0 | |
| 29.0.3 | 5 / 0 | |
| 29.0.2 | 5 / 0 | |
| 29.0.1 | 5 / 0 | |
| 29.0.0 | 5 / 0 | |
| 28.1.3 | 5 / 0 | |
| 28.1.1 | 5 / 0 | |
| 28.1.0 | 5 / 0 | |
| 28.0.2 | 5 / 0 | |
| 28.0.1 | 5 / 0 | |
| 28.0.0 | 5 / 0 | |
| 27.5.1 | 5 / 0 | |
| 27.5.0 | 5 / 0 | |
| 27.4.6 | 5 / 0 | |
| 27.4.2 | 5 / 0 | |
| 27.4.1 | 5 / 0 | |
| 27.4.0 | 5 / 0 | |
| 27.3.1 | 5 / 0 | |
| 27.3.0 | 5 / 0 | |
| 27.2.5 | 5 / 0 | |
| 27.2.4 | 5 / 0 | |
| 27.2.3 | 5 / 0 | |
| 27.2.2 | 5 / 0 | |
| 27.2.0 | 5 / 0 | |
| 27.1.1 | 5 / 0 | |
| 27.1.0 | 5 / 0 | |
| 27.0.6 | 5 / 0 | |
| 27.0.2 | 5 / 0 | |
| 27.0.1 | 5 / 0 | |
| 27.0.0 | 5 / 0 | |
| 26.6.2 | 5 / 0 | |
| 26.6.1 | 5 / 0 | |
| 26.6.0 | 5 / 0 | |
| 26.5.2 | 5 / 0 | |
| 26.5.0 | 5 / 0 | |
| 26.4.2 | 5 / 0 | |
| 26.4.0 | 5 / 0 | |
| 26.3.0 | 5 / 0 | |
| 26.2.0 | 5 / 0 | |
| 26.1.0 | 5 / 0 | |
| 26.0.1 | 5 / 0 | |
| 26.0.0 | 5 / 0 | |
| 25.5.0 | 5 / 0 | |
| 25.4.0 | 5 / 0 | |
| 25.3.0 | 5 / 0 | |
| 25.2.6 | 5 / 0 | |
| 25.2.3 | 5 / 0 | |
| 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 | 4 / 0 | |
| 23.6.0 | 2 / 0 | |
| 23.5.0 | 2 / 0 | |
| 23.4.0 | 2 / 0 | |
| 23.2.0 | 2 / 0 | |
| 23.1.0 | 2 / 0 | |
| 23.0.2 | 2 / 0 | |
| 23.0.1 | 2 / 0 | |
| 0.5.0 | 1 / 10 | |
| 0.4.0 | 1 / 10 | |
| 0.3.1 | 1 / 9 | |
| 0.3.0 | 1 / 9 | |
| 0.2.0 | 1 / 9 | |
| 0.1.0 | 1 / 9 | |
| 0.0.1 | 1 / 9 |
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.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 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 2025-06-18. This could indicate a legitimate maintainer transition or an account compromise.
v30.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 2025-06-10. This could indicate a legitimate maintainer transition or an account compromise.
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.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.