jest-repl
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@jest/environment | AI (phantom-deps): @jest/environment is explicitly listed as a direct dependency in package.json; phantom-dep detection is a false positive for this package. | ai | |
| provenance | publisher-changed | AI (provenance): cpojer is a well-known Jest core maintainer; publisher change from simenb to cpojer is a legitimate transition within the Jest project. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers (cpojer, rickhanlonii, openjs-operations) are all known Jest/OpenJS Foundation contributors; legitimate organizational transition. | ai | |
| bogus-package | bogus-package | AI (bogus-package): jest-repl is a legitimate Facebook/Meta Jest monorepo sub-package. Spam-flagged maintainers (fb, cpojer) are known Facebook OSS accounts; missing description/keywords is typical for monorepo sub-packages. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Monorepo sub-package of Jest; missing description is a metadata quality issue, not a malicious indicator for this well-established package. | ai |
Versions (showing 51 of 172)
| Version | Deps | Published |
|---|---|---|
| 30.0.0 | 11 / 2 | |
| 29.7.0 | 11 / 2 | |
| 29.6.4 | 11 / 2 | |
| 29.6.3 | 11 / 2 | |
| 29.6.2 | 11 / 2 | |
| 29.6.1 | 11 / 2 | |
| 29.6.0 | 11 / 2 | |
| 29.5.0 | 11 / 2 | |
| 29.4.3 | 11 / 2 | |
| 29.4.2 | 11 / 2 | |
| 29.4.1 | 11 / 2 | |
| 29.4.0 | 11 / 2 | |
| 29.3.1 | 11 / 2 | |
| 29.3.0 | 11 / 2 | |
| 29.2.2 | 11 / 2 | |
| 29.2.1 | 11 / 2 | |
| 29.2.0 | 11 / 2 | |
| 29.1.2 | 11 / 2 | |
| 29.1.1 | 11 / 2 | |
| 29.1.0 | 11 / 2 | |
| 29.0.3 | 11 / 2 | |
| 29.0.2 | 11 / 2 | |
| 29.0.1 | 11 / 2 | |
| 29.0.0 | 11 / 2 | |
| 28.1.3 | 11 / 2 | |
| 28.1.2 | 11 / 2 | |
| 28.1.1 | 11 / 2 | |
| 28.1.0 | 11 / 2 | |
| 28.0.3 | 11 / 2 | |
| 28.0.2 | 11 / 2 | |
| 28.0.1 | 11 / 2 | |
| 28.0.0 | 11 / 2 | |
| 27.5.1 | 11 / 2 | |
| 27.5.0 | 11 / 2 | |
| 27.4.7 | 11 / 2 | |
| 27.4.6 | 11 / 2 | |
| 27.4.5 | 11 / 3 | |
| 27.4.4 | 11 / 3 | |
| 27.4.3 | 11 / 3 | |
| 27.4.2 | 11 / 3 | |
| 27.4.1 | 11 / 3 | |
| 27.4.0 | 11 / 3 | |
| 27.3.1 | 11 / 3 | |
| 27.3.0 | 11 / 3 | |
| 27.2.5 | 11 / 3 | |
| 27.2.4 | 11 / 3 | |
| 27.2.3 | 11 / 3 | |
| 27.2.2 | 11 / 3 | |
| 27.2.1 | 11 / 3 | |
| 27.2.0 | 11 / 3 | |
| 27.1.1 | 11 / 3 |
v30.0.0
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. 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.