@jest/globals
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@jest/expect | AI (dependencies): @jest/expect is a sibling package in the jestjs/jest monorepo, always published in lockstep with @jest/globals. This dependency is expected and legitimate. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Jest monorepo packages omit descriptions/keywords by convention, and inflated semver reflects lockstep versioning with the broader Jest project, not a spam/malware pattern. | ai |
Versions (showing 51 of 81)
| Version | Deps | Published |
|---|---|---|
| 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.3 | 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 | 3 / 0 | |
| 28.1.2 | 3 / 0 | |
| 28.1.1 | 3 / 0 | |
| 28.1.0 | 3 / 0 | |
| 28.0.3 | 3 / 0 | |
| 28.0.2 | 3 / 0 | |
| 28.0.1 | 3 / 0 | |
| 28.0.0 | 3 / 0 | |
| 27.5.1 | 3 / 0 | |
| 27.5.0 | 3 / 0 | |
| 27.4.6 | 3 / 0 | |
| 27.4.4 | 3 / 0 | |
| 27.4.2 | 3 / 0 | |
| 27.4.1 | 3 / 0 | |
| 27.4.0 | 3 / 0 | |
| 27.3.1 | 3 / 0 | |
| 27.3.0 | 3 / 0 |
v30.2.0
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.3
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. 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.1
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. 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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.