babel-jest
Jest plugin to use babel for transformation.
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:babel-core | AI (dependencies): babel-core is the canonical Babel 6 core package; its use is expected and appropriate for a Babel-Jest integration package. | ai | |
| provenance | no-provenance | AI (provenance): babel-jest is a long-established, high-download package from the official Jest monorepo; lack of Sigstore provenance is not a meaningful risk signal here. | ai | |
| dependencies | unvetted-dep:@jest/transform | AI (dependencies): @jest/transform is a core Jest monorepo package, always a legitimate dependency of babel-jest. | ai | |
| dependencies | unvetted-dep:slash | AI (dependencies): slash is a well-known, widely used utility package; a stable legitimate dependency of babel-jest across versions. | ai | |
| dependencies | unvetted-dep:babel-preset-jest | AI (dependencies): babel-preset-jest is a core Jest monorepo package, always a legitimate dependency of babel-jest. | ai | |
| dependencies | unvetted-dep:@types/babel__core | AI (dependencies): @types/babel__core is a standard DefinitelyTyped package; legitimate type dependency for babel-jest. | ai | |
| dependencies | unvetted-dep:babel-plugin-istanbul | AI (dependencies): babel-plugin-istanbul is a well-established coverage instrumentation plugin; a stable legitimate dependency of babel-jest. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removed maintainers reflect normal team evolution during Jest's OpenJS Foundation transition. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): rickhanlonii and openjs-operations reflect Jest's OpenJS Foundation governance; legitimate additions. | ai | |
| provenance | publisher-changed | AI (provenance): cpojer is the original Jest creator and long-standing maintainer; publisher change from simenb is a legitimate team rotation. | ai | |
| phantom-deps | phantom-dep:@types/babel__core | AI (phantom-deps): @types/babel__core is intentionally listed as a runtime dep in the Jest monorepo to provide TypeScript types; this is a stable, known pattern for this package. | ai |
Versions (showing 51 of 159)
| Version | Deps | Published |
|---|---|---|
| 30.4.1 | 7 / 4 | |
| 30.4.0 | 7 / 4 | |
| 30.2.0 | 7 / 4 | |
| 30.1.2 | 7 / 3 | |
| 30.1.1 | 7 / 3 | |
| 30.1.0 | 7 / 3 | |
| 30.0.5 | 7 / 3 | |
| 30.0.4 | 7 / 3 | |
| 30.0.2 | 7 / 3 | |
| 30.0.1 | 7 / 3 | |
| 30.0.0 | 7 / 3 | |
| 29.7.0 | 7 / 3 | |
| 29.6.4 | 7 / 3 | |
| 29.6.3 | 7 / 3 | |
| 29.6.2 | 7 / 3 | |
| 29.6.1 | 7 / 3 | |
| 29.6.0 | 7 / 3 | |
| 29.5.0 | 7 / 3 | |
| 29.4.3 | 7 / 3 | |
| 29.4.2 | 7 / 3 | |
| 29.4.1 | 7 / 3 | |
| 29.4.0 | 7 / 3 | |
| 29.3.1 | 7 / 3 | |
| 29.3.0 | 7 / 3 | |
| 29.2.2 | 7 / 3 | |
| 29.2.1 | 7 / 3 | |
| 29.2.0 | 7 / 3 | |
| 29.1.2 | 7 / 3 | |
| 29.1.0 | 7 / 3 | |
| 29.0.3 | 7 / 3 | |
| 29.0.2 | 7 / 3 | |
| 29.0.1 | 7 / 3 | |
| 29.0.0 | 7 / 3 | |
| 28.1.3 | 7 / 3 | |
| 28.1.2 | 7 / 3 | |
| 28.1.1 | 7 / 3 | |
| 28.1.0 | 7 / 3 | |
| 28.0.3 | 7 / 3 | |
| 28.0.2 | 7 / 3 | |
| 28.0.1 | 7 / 3 | |
| 28.0.0 | 7 / 3 | |
| 27.5.1 | 8 / 3 | |
| 27.5.0 | 8 / 3 | |
| 27.4.6 | 8 / 3 | |
| 27.4.5 | 8 / 3 | |
| 27.4.4 | 8 / 3 | |
| 27.4.2 | 8 / 3 | |
| 27.4.1 | 8 / 3 | |
| 27.4.0 | 8 / 3 | |
| 27.3.1 | 8 / 3 | |
| 27.3.0 | 8 / 3 |
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.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.2
1 findingPackage 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 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.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.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.
v28.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.1.2
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.3
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.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.4.4
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.