@jest/console
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): cpojer (Christoph Pojer) is a well-known Jest core contributor; addition reflects the jestjs org transition, not a suspicious takeover. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removals are consistent with the Jest project's transition to the jestjs GitHub org; no indication of malicious takeover. | ai | |
| provenance | no-provenance | AI (provenance): Jest monorepo packages consistently publish without Sigstore provenance; stable pattern across all versions. | ai | |
| phantom-deps | phantom-dep:slash | AI (phantom-deps): slash is a legitimate runtime dep used in Jest build output; phantom detection is a false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): @types/node is a framework-scoped type package conventionally included as a runtime dep in Jest packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): @jest/console is a legitimate Jest core package; no description/keywords are expected for internal monorepo packages. The spam-publisher signal is the real concern, not the package structure. | ai |
Versions (showing 51 of 78)
| Version | Deps | Published |
|---|---|---|
| 30.3.0 | 6 / 1 | |
| 30.2.0 | 6 / 1 | |
| 30.1.2 | 6 / 1 | |
| 30.1.1 | 6 / 1 | |
| 30.1.0 | 6 / 1 | |
| 30.0.5 | 6 / 1 | |
| 30.0.4 | 6 / 1 | |
| 30.0.2 | 6 / 1 | |
| 30.0.1 | 6 / 1 | |
| 29.7.0 | 6 / 1 | |
| 29.6.4 | 6 / 1 | |
| 29.6.3 | 6 / 1 | |
| 29.6.2 | 6 / 1 | |
| 29.6.1 | 6 / 1 | |
| 29.6.0 | 6 / 1 | |
| 29.5.0 | 6 / 1 | |
| 29.4.3 | 6 / 1 | |
| 29.4.2 | 6 / 1 | |
| 29.4.1 | 6 / 1 | |
| 29.4.0 | 6 / 1 | |
| 29.3.1 | 6 / 1 | |
| 29.2.1 | 6 / 1 | |
| 29.2.0 | 6 / 1 | |
| 29.1.2 | 6 / 1 | |
| 29.1.0 | 6 / 1 | |
| 29.0.3 | 6 / 1 | |
| 29.0.2 | 6 / 1 | |
| 29.0.1 | 6 / 1 | |
| 29.0.0 | 6 / 1 | |
| 28.1.3 | 6 / 1 | |
| 28.1.1 | 6 / 1 | |
| 28.1.0 | 6 / 1 | |
| 28.0.2 | 6 / 1 | |
| 28.0.1 | 6 / 1 | |
| 28.0.0 | 6 / 1 | |
| 27.5.1 | 6 / 2 | |
| 27.5.0 | 6 / 2 | |
| 27.4.6 | 6 / 2 | |
| 27.4.2 | 6 / 2 | |
| 27.4.1 | 6 / 2 | |
| 27.4.0 | 6 / 2 | |
| 27.3.1 | 6 / 2 | |
| 27.3.0 | 6 / 2 | |
| 27.2.5 | 6 / 2 | |
| 27.2.4 | 6 / 2 | |
| 27.2.3 | 6 / 2 | |
| 27.2.2 | 6 / 2 | |
| 27.2.0 | 6 / 2 | |
| 27.1.1 | 6 / 2 | |
| 27.1.0 | 6 / 2 | |
| 27.0.6 | 6 / 2 |
v30.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v30.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v30.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v30.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v30.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v30.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v30.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v30.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v30.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.