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 100 of 151)
| Version | Deps | Published |
|---|---|---|
| 30.4.1 | 8 / 2 | |
| 30.4.0 | 8 / 2 | |
| 30.3.0 | 8 / 2 | |
| 30.2.0 | 8 / 2 | |
| 30.1.3 | 8 / 2 | |
| 30.1.0 | 8 / 2 | |
| 30.0.5 | 8 / 2 | |
| 30.0.2 | 8 / 2 | |
| 30.0.1 | 8 / 2 | |
| 30.0.0 | 8 / 1 | |
| 29.7.0 | 9 / 5 | |
| 29.6.4 | 9 / 5 | |
| 29.6.3 | 9 / 5 | |
| 29.6.2 | 9 / 5 | |
| 29.6.1 | 9 / 5 | |
| 29.6.0 | 9 / 5 | |
| 29.5.0 | 9 / 5 | |
| 29.4.3 | 9 / 5 | |
| 29.4.2 | 9 / 5 | |
| 29.4.1 | 9 / 5 | |
| 29.4.0 | 9 / 5 | |
| 29.3.1 | 9 / 5 | |
| 29.3.0 | 9 / 5 | |
| 29.2.2 | 9 / 5 | |
| 29.2.1 | 9 / 5 | |
| 29.2.0 | 9 / 5 | |
| 29.1.2 | 9 / 5 | |
| 29.1.0 | 9 / 5 | |
| 29.0.3 | 9 / 5 | |
| 29.0.2 | 9 / 5 | |
| 29.0.1 | 9 / 5 | |
| 29.0.0 | 9 / 5 | |
| 28.1.3 | 9 / 5 | |
| 28.1.1 | 9 / 5 | |
| 28.1.0 | 9 / 5 | |
| 28.0.3 | 9 / 4 | |
| 28.0.2 | 9 / 4 | |
| 28.0.1 | 9 / 4 | |
| 28.0.0 | 9 / 4 | |
| 27.5.1 | 10 / 2 | |
| 27.5.0 | 10 / 2 | |
| 27.4.6 | 10 / 2 | |
| 27.4.5 | 10 / 2 | |
| 27.4.4 | 10 / 2 | |
| 27.4.2 | 10 / 2 | |
| 27.4.1 | 10 / 2 | |
| 27.4.0 | 10 / 2 | |
| 27.3.1 | 10 / 2 | |
| 27.3.0 | 10 / 2 | |
| 27.2.5 | 10 / 2 | |
| 27.2.4 | 10 / 2 | |
| 27.2.3 | 10 / 2 | |
| 27.2.2 | 10 / 2 | |
| 27.2.0 | 10 / 2 | |
| 27.1.1 | 10 / 2 | |
| 27.1.0 | 10 / 2 | |
| 27.0.6 | 9 / 3 | |
| 27.0.5 | 9 / 3 | |
| 27.0.4 | 9 / 3 | |
| 27.0.2 | 9 / 3 | |
| 27.0.1 | 8 / 3 | |
| 27.0.0 | 8 / 3 | |
| 26.6.2 | 8 / 3 | |
| 26.6.1 | 8 / 3 | |
| 26.6.0 | 8 / 3 | |
| 26.5.2 | 8 / 3 | |
| 26.5.0 | 8 / 3 | |
| 26.4.0 | 8 / 3 | |
| 26.3.0 | 8 / 3 | |
| 26.2.2 | 8 / 3 | |
| 26.2.1 | 8 / 3 | |
| 26.2.0 | 8 / 3 | |
| 26.1.0 | 8 / 3 | |
| 26.0.1 | 8 / 3 | |
| 26.0.0 | 8 / 3 | |
| 25.5.1 | 9 / 4 | |
| 25.5.0 | 9 / 4 | |
| 25.4.0 | 8 / 3 | |
| 25.3.0 | 6 / 3 | |
| 25.2.6 | 6 / 3 | |
| 25.2.5 | 6 / 3 | |
| 25.2.3 | 6 / 3 | |
| 25.2.1 | 6 / 3 | |
| 25.2.0 | 6 / 3 | |
| 25.1.0 | 5 / 2 | |
| 25.0.0 | 5 / 2 | |
| 24.9.0 | 5 / 2 | |
| 24.8.0 | 5 / 2 | |
| 24.7.1 | 5 / 2 | |
| 24.7.0 | 5 / 2 | |
| 24.6.0 | 5 / 2 | |
| 24.5.0 | 5 / 2 | |
| 24.4.0 | 5 / 2 | |
| 24.3.1 | 4 / 2 | |
| 24.3.0 | 4 / 2 | |
| 24.1.0 | 3 / 1 | |
| 24.0.0 | 3 / 1 | |
| 23.6.0 | 3 / 1 | |
| 23.5.0 | 3 / 1 | |
| 23.4.1 | 3 / 1 |
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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v30.1.3
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.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.
v30.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.
v30.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.
v29.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.6.4
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.3
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.4.0
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.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.2.2
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.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.
v29.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.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.
v29.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.
v29.0.0
1 finding[Accepted risk] Package 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.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.
v27.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.2.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-03-25. This could indicate a legitimate maintainer transition or an account compromise.
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. Consider requesting the maintainer enable provenance via CI/CD.
v24.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.7.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-04-03. This could indicate a legitimate maintainer transition or an account compromise.
v24.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.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 2019-02-05. This could indicate a legitimate maintainer transition or an account compromise.
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. Consider requesting the maintainer enable provenance via CI/CD.
v23.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.