jest-resolve
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 rotation on the official Facebook/Jest project by a trusted core maintainer (cpojer); consistent with normal team evolution, not a takeover signal. | ai | |
| dependencies | unvetted-dep:jest-pnp-resolver | AI (dependencies): jest-pnp-resolver is a well-known PnP resolver adapter for Jest; stable legitimate dependency. | ai | |
| dependencies | unvetted-dep:jest-util | AI (dependencies): jest-util is a core Jest monorepo package; always a legitimate dependency of jest-resolve. | ai | |
| dependencies | unvetted-dep:jest-validate | AI (dependencies): jest-validate is a core Jest monorepo package; always a legitimate dependency of jest-resolve. | ai | |
| dependencies | unvetted-dep:jest-haste-map | AI (dependencies): jest-haste-map is a core Jest monorepo package; always a legitimate dependency of jest-resolve. | ai | |
| dependencies | unvetted-dep:slash | AI (dependencies): slash is a widely-used path separator utility; no security concern for this package. | ai | |
| dependencies | unvetted-dep:unrs-resolver | AI (dependencies): unrs-resolver is a Rust-based module resolver used by Jest; legitimate dependency for this package. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): browser-resolve is a legitimate, established package for browser module resolution — a natural dependency for jest-resolve which handles both Node and browser environments. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): dmitriiabramov and fb are recognized Jest/Facebook contributors; additions are consistent with the official Jest project's maintainer evolution, not a suspicious takeover. | ai | |
| provenance | publisher-changed | AI (provenance): Both cpojer and mjesun are known Jest core contributors at Facebook/Meta. Publisher transitions within the Jest team are expected and this pattern is stable for this package. | ai | |
| npm-metadata | suspicious-initial-version | AI (npm-metadata): [email protected] is a namespace reservation by trusted Jest maintainer cpojer; 0.0.0 is intentional for placeholder packages in this ecosystem. | ai | |
| dependencies | unvetted-dep:resolve.exports | AI (dependencies): resolve.exports is a legitimate, purpose-built package for resolving package.json exports fields; its use in jest-resolve is appropriate and expected across all versions. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Monorepo sub-packages from the Jest project commonly omit descriptions; not a malicious signal for this package. | ai | |
| provenance | no-provenance | AI (provenance): Publisher cpojer is a long-standing Jest maintainer; lack of provenance is not unusual for this ecosystem and does not indicate risk here. | ai | |
| bogus-package | bogus-package | AI (bogus-package): jest-resolve is a monorepo sub-package of the official Jest project; inflated semver, no description, and no keywords are expected for monorepo packages and not spam indicators. | ai |
Versions (showing 51 of 151)
| Version | Deps | Published |
|---|---|---|
| 23.4.0 | 3 / 1 | |
| 23.2.0 | 3 / 1 | |
| 23.1.0 | 3 / 1 | |
| 23.0.2 | 3 / 1 | |
| 23.0.1 | 3 / 1 | |
| 23.0.0 | 3 / 1 | |
| 22.4.3 | 2 / 1 | |
| 22.4.2 | 2 / 1 | |
| 22.4.1 | 2 / 1 | |
| 22.4.0 | 2 / 1 | |
| 22.3.0 | 2 / 1 | |
| 22.2.2 | 2 / 1 | |
| 22.2.0 | 2 / 1 | |
| 22.1.4 | 2 / 1 | |
| 22.1.0 | 2 / 1 | |
| 22.0.6 | 2 / 1 | |
| 22.0.4 | 2 / 1 | |
| 22.0.3 | 2 / 1 | |
| 22.0.2 | 2 / 1 | |
| 22.0.1 | 2 / 1 | |
| 22.0.0 | 2 / 1 | |
| 21.2.0 | 3 / 1 | |
| 21.1.0 | 3 / 1 | |
| 21.0.2 | 3 / 1 | |
| 21.0.0 | 3 / 1 | |
| 20.0.4 | 3 / 1 | |
| 20.0.3 | 3 / 1 | |
| 20.0.2 | 3 / 1 | |
| 20.0.1 | 3 / 1 | |
| 20.0.0 | 3 / 1 | |
| 19.0.2 | 3 / 0 | |
| 19.0.0 | 3 / 0 | |
| 18.1.0 | 4 / 0 | |
| 18.0.0 | 4 / 0 | |
| 17.0.3 | 4 / 0 | |
| 17.0.2 | 4 / 0 | |
| 17.0.1 | 4 / 0 | |
| 17.0.0 | 4 / 0 | |
| 16.0.2 | 4 / 0 | |
| 16.0.0 | 4 / 0 | |
| 15.0.1 | 4 / 0 | |
| 15.0.0 | 4 / 0 | |
| 14.1.0 | 4 / 0 | |
| 14.0.0 | 4 / 0 | |
| 13.2.2 | 3 / 0 | |
| 13.2.1 | 3 / 0 | |
| 13.1.1 | 3 / 0 | |
| 13.0.0 | 3 / 0 | |
| 12.1.1 | 2 / 0 | |
| 12.1.0 | 2 / 0 | |
| 0.0.0 | 0 / 0 |
v23.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.1.4
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 2018-01-19. This could indicate a legitimate maintainer transition or an account compromise.
v22.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.6
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 2018-01-11. This could indicate a legitimate maintainer transition or an account compromise.
v22.0.4
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 2017-12-22. This could indicate a legitimate maintainer transition or an account compromise.
v22.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.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.
v0.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.