jest-runner
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-removed | AI (maintainer-change): Maintainer changes are consistent with Facebook/Jest project team transitions; this is a well-established, high-download official package with no signs of takeover. | ai | |
| phantom-deps | phantom-dep:jest-jasmine2 | AI (phantom-deps): jest-jasmine2 is a test framework adapter referenced in config; phantom dependency is expected and benign. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): simenb is the established maintainer of jest-runner since 2020; this is a stable, legitimate maintainer for the package. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New deps (exit, jest-worker, jest-leak-detector) are established packages / Jest monorepo siblings replacing worker-farm and pify. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher transition from davidzilburg to simenb in 2020 reflects Jest project governance; stable for this package. | ai | |
| dependencies | unvetted-dep:exit-x | AI (dependencies): exit-x is a maintained replacement for the deprecated 'exit' package, used by Jest for process exit handling. Its use in jest-runner is intentional and documented in the Jest ecosystem. | ai | |
| provenance | no-provenance | AI (provenance): Package predates Sigstore provenance adoption; 43.7M weekly downloads and official Facebook authorship make this a stable false positive for this package. | ai | |
| dependencies | unvetted-dep:jest-jasmine2 | AI (dependencies): jest-jasmine2 is a sibling package in the official Facebook/Meta Jest monorepo, published by the same trusted team. This dependency relationship is stable and expected across all jest-runner versions. | ai | |
| dependencies | unvetted-dep:jest-runtime | AI (dependencies): jest-runtime is a Jest monorepo sibling package; always published together with jest-runner at the same version. Not an independent supply chain risk. | ai | |
| dependencies | unvetted-dep:jest-watcher | AI (dependencies): jest-watcher is a Jest monorepo sibling package; always published together with jest-runner at the same version. Not an independent supply chain risk. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Stub/placeholder version of a well-known package; absence of description is expected for this namespace reservation release. | ai | |
| npm-metadata | suspicious-initial-version | AI (npm-metadata): jest-runner 0.0.0 is a legitimate namespace placeholder by the Jest team (cpojer); the 0.0.0 version is a known monorepo stub pattern, not a malicious indicator for this package. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): Framework-scoped type package loaded by convention in Jest's architecture; not a real phantom dependency concern. | ai | |
| bogus-package | bogus-package | AI (bogus-package): jest-runner is a Jest monorepo package; inflated semver tracks the Jest release version, missing description/keywords are normal for monorepo sub-packages. | ai | |
| phantom-deps | phantom-dep:jest-environment-node | AI (phantom-deps): Referenced in config files as the default environment; expected phantom dep pattern for jest-runner. | ai | |
| phantom-deps | phantom-dep:@jest/environment | AI (phantom-deps): Jest environment interface loaded by convention; expected in jest-runner's architecture. | ai |
Versions (showing 54 of 154)
| Version | Deps | Published |
|---|---|---|
| 25.2.3 | 19 / 5 | |
| 25.2.2 | 19 / 5 | |
| 25.2.1 | 19 / 5 | |
| 25.2.0 | 19 / 5 | |
| 25.1.0 | 19 / 3 | |
| 25.0.0 | 19 / 3 | |
| 24.9.0 | 19 / 3 | |
| 24.8.0 | 19 / 3 | |
| 24.7.1 | 19 / 3 | |
| 24.7.0 | 19 / 3 | |
| 24.6.0 | 19 / 3 | |
| 24.5.0 | 19 / 3 | |
| 24.4.0 | 19 / 3 | |
| 24.3.1 | 19 / 3 | |
| 24.3.0 | 19 / 3 | |
| 24.1.0 | 14 / 0 | |
| 24.0.0 | 13 / 0 | |
| 23.6.0 | 13 / 0 | |
| 23.5.0 | 13 / 0 | |
| 23.4.2 | 13 / 0 | |
| 23.4.1 | 13 / 0 | |
| 23.4.0 | 13 / 0 | |
| 23.3.0 | 13 / 0 | |
| 23.2.0 | 13 / 0 | |
| 23.1.0 | 13 / 0 | |
| 23.0.1 | 13 / 0 | |
| 23.0.0 | 13 / 0 | |
| 22.4.4 | 11 / 0 | |
| 22.4.3 | 11 / 0 | |
| 22.4.2 | 11 / 0 | |
| 22.4.1 | 11 / 0 | |
| 22.4.0 | 11 / 0 | |
| 22.3.0 | 11 / 0 | |
| 22.2.2 | 11 / 0 | |
| 22.2.1 | 11 / 0 | |
| 22.2.0 | 11 / 0 | |
| 22.1.4 | 11 / 0 | |
| 22.1.3 | 11 / 0 | |
| 22.1.2 | 11 / 0 | |
| 22.1.1 | 11 / 0 | |
| 22.1.0 | 10 / 0 | |
| 22.0.6 | 10 / 0 | |
| 22.0.5 | 10 / 0 | |
| 22.0.4 | 10 / 0 | |
| 22.0.3 | 10 / 0 | |
| 22.0.2 | 10 / 0 | |
| 22.0.1 | 10 / 0 | |
| 22.0.0 | 10 / 0 | |
| 21.2.1 | 10 / 0 | |
| 21.2.0 | 10 / 0 | |
| 21.1.0 | 10 / 0 | |
| 21.0.2 | 10 / 0 | |
| 21.0.0 | 10 / 0 | |
| 0.0.0 | 0 / 0 |
v25.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v25.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v25.2.1
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 2020-03-26. This could indicate a legitimate maintainer transition or an account compromise.
v25.2.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.
v25.1.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 2020-01-22. This could indicate a legitimate maintainer transition or an account compromise.
v25.0.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.
v24.9.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.
v24.8.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.
v24.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.7.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.
v24.6.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.
v24.5.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.
v24.4.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.
v24.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.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.
v24.1.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.
v24.0.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 2019-01-25. This could indicate a legitimate maintainer transition or an account compromise.
v23.6.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.
v23.5.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.
v23.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.4.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.
v23.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.
v23.2.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.
v23.1.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.
v23.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.0.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.
v22.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.4.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.
v22.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.
v22.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.2.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.
v22.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.1.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.
v22.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.0.0
2 findingsThis version was published by a different npm account than previous versions on 2017-12-18. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.2.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.
v21.1.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.
v21.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v21.0.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.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.