@jest/test-result
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 rubennorte to scotthovestadt reflects a legitimate Jest core team maintainer transition within the facebook/jest monorepo; both are known Meta engineers. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): scotthovestadt is a known Jest core team member with a strong track record (2767 approved packages); addition is consistent with legitimate team transition. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Jest monorepo sub-packages consistently lack descriptions; this is a structural pattern, not a malware indicator. | ai | |
| provenance | no-provenance | AI (provenance): Package was published in 2019, before Sigstore provenance was available; absence is expected for this era. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Jest monorepo packages routinely omit descriptions/keywords and publish at high semver matching the Jest release version. Not indicative of spam or malice. | ai | |
| phantom-deps | phantom-dep:@types/istanbul-lib-coverage | AI (phantom-deps): Type-only dependency used for TypeScript declarations, not runtime imports. Expected pattern for Jest packages. | ai |
Versions (showing 51 of 85)
| Version | Deps | Published |
|---|---|---|
| 30.4.1 | 4 / 2 | |
| 30.4.0 | 4 / 2 | |
| 30.3.0 | 4 / 2 | |
| 30.2.0 | 4 / 2 | |
| 30.1.3 | 4 / 2 | |
| 30.1.2 | 4 / 2 | |
| 30.1.1 | 4 / 2 | |
| 30.1.0 | 4 / 2 | |
| 30.0.5 | 4 / 2 | |
| 30.0.4 | 4 / 2 | |
| 30.0.2 | 4 / 2 | |
| 30.0.1 | 4 / 2 | |
| 30.0.0 | 4 / 2 | |
| 29.7.0 | 4 / 2 | |
| 29.6.4 | 4 / 2 | |
| 29.6.3 | 4 / 2 | |
| 29.6.2 | 4 / 2 | |
| 29.6.1 | 4 / 2 | |
| 29.6.0 | 4 / 2 | |
| 29.5.0 | 4 / 2 | |
| 29.4.3 | 4 / 2 | |
| 29.4.2 | 4 / 2 | |
| 29.4.1 | 4 / 2 | |
| 29.4.0 | 4 / 2 | |
| 29.3.1 | 4 / 0 | |
| 29.2.1 | 4 / 0 | |
| 29.2.0 | 4 / 0 | |
| 29.1.2 | 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.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.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 |
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. Consider requesting the maintainer enable provenance via CI/CD.
v30.1.3
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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.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.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.