@jest/schemas
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 |
|---|---|---|---|---|
| — | publisher-changed | — | sean | |
| dependencies | unvetted-dep:@sinclair/typebox | AI (dependencies): @sinclair/typebox is a well-known TypeScript schema library; its use here is legitimate and expected for Jest's schema validation utilities. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Internal Jest monorepo package; missing description is expected for utility packages not marketed to end users. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Signals reflect internal monorepo package nature (minimal README, no keywords), not malicious intent. Jest is legitimate. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 30.4.1 | 1 / 0 | |
| 30.4.0 | 1 / 0 | |
| 30.0.5 | 1 / 0 | |
| 30.0.1 | 1 / 0 | |
| 30.0.0 | 1 / 0 | |
| 29.6.3 | 1 / 0 | |
| 29.6.0 | 1 / 0 | |
| 29.4.3 | 1 / 0 | |
| 29.4.2 | 1 / 0 | |
| 29.4.0 | 1 / 0 | |
| 29.0.0 | 1 / 0 | |
| 28.1.3 | 1 / 0 | |
| 28.0.2 | 1 / 0 | |
| 28.0.0 | 1 / 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 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.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.