jest-util
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-mock | AI (phantom-deps): jest-mock is declared and used transitively in Jest monorepo; phantom-dep pattern is expected for internal utilities. | ai | |
| provenance | no-provenance | AI (provenance): Provenance attestation is a best practice but not a blocker for established packages from trusted publishers. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are all legitimate Jest @jest/* scoped packages and well-known utilities added during the Jest v24 monorepo restructuring. No suspicious packages. | ai | |
| phantom-deps | phantom-dep:source-map | AI (phantom-deps): source-map is a legitimate dependency used in build/config context; phantom detection is a false positive for this package. | ai | |
| phantom-deps | phantom-dep:slash | AI (phantom-deps): slash is a legitimate utility used in build/config context; phantom detection is a false positive for this package. | ai | |
| source-diff | large-new-source-files | AI (source-diff): 36 new source files reflect the Jest v24 TypeScript migration and monorepo restructuring from the official facebook/jest repo. | ai | |
| phantom-deps | phantom-dep:graceful-fs | AI (phantom-deps): graceful-fs is declared and used in config/build; phantom-dep pattern is stable for this package. | ai | |
| dependencies | unvetted-dep:jest-file-exists | AI (dependencies): jest-file-exists is a sibling Jest monorepo package published by the same Facebook/Jest team; no malicious signal expected across versions. | ai | |
| npm-metadata | no-description | AI (npm-metadata): jest-util is an internal monorepo utility package; missing description is a stable characteristic, not a malware indicator. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change from alexjuarez to cpojer reflects the known transfer to Facebook/Jest core team in 2017. cpojer is a highly trusted publisher with 747 approved packages. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of alexjuarez is part of the documented 2017 transfer to the Facebook/Jest core team. Consistent with legitimate project handoff. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers (cpojer, aaronabramov, jeanlauliac, fb) are the official Facebook/Jest core team. Legitimate transition, not a compromise. | ai | |
| maintainer-change | maintainer-takeover | AI (maintainer-change): This reflects the well-documented 2017 transfer of jest-util to the official Facebook/Jest core team (cpojer, aaronabramov, fb). Not a hijack — a legitimate ownership transition. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase from v0.0.2 to v21.1.0 is a major version jump representing a complete rewrite as part of Jest monorepo restructuring. Expected and legitimate. | ai | |
| typosquat | typosquat.pattern:jest | AI (typosquat): jest-util is an official package in the Jest monorepo (jestjs/jest). The name similarity to 'jest' is intentional — it IS part of the Jest project. Stable false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Inflated semver and missing description are expected for a monorepo package tracking Jest's release cycle (v30.x). Not indicative of spam or malicious intent. | ai |
Versions (showing 49 of 149)
| Version | Deps | Published |
|---|---|---|
| 21.2.0 | 7 / 0 | |
| 21.1.0 | 7 / 0 | |
| 21.0.2 | 7 / 0 | |
| 21.0.0 | 7 / 0 | |
| 20.0.3 | 7 / 0 | |
| 20.0.2 | 7 / 0 | |
| 20.0.1 | 7 / 0 | |
| 20.0.0 | 7 / 0 | |
| 19.0.2 | 8 / 0 | |
| 19.0.1 | 8 / 0 | |
| 19.0.0 | 8 / 0 | |
| 18.1.0 | 6 / 0 | |
| 18.0.0 | 6 / 0 | |
| 17.0.2 | 6 / 0 | |
| 17.0.0 | 6 / 0 | |
| 16.0.2 | 6 / 0 | |
| 16.0.0 | 6 / 0 | |
| 15.1.1 | 6 / 1 | |
| 15.1.0 | 6 / 1 | |
| 15.0.1 | 6 / 1 | |
| 15.0.0 | 6 / 1 | |
| 14.0.0 | 5 / 1 | |
| 13.2.2 | 5 / 1 | |
| 13.2.1 | 5 / 1 | |
| 13.1.2 | 5 / 1 | |
| 13.1.1 | 5 / 1 | |
| 13.1.0 | 5 / 1 | |
| 13.0.0 | 5 / 1 | |
| 12.1.0 | 5 / 1 | |
| 12.0.2 | 3 / 1 | |
| 12.0.1 | 3 / 1 | |
| 12.0.0 | 3 / 1 | |
| 11.0.2 | 3 / 1 | |
| 11.0.1 | 3 / 0 | |
| 11.0.0 | 3 / 0 | |
| 10.0.3 | 3 / 0 | |
| 10.0.2 | 3 / 0 | |
| 10.0.1 | 2 / 0 | |
| 10.0.0 | 2 / 0 | |
| 9.0.3 | 2 / 0 | |
| 1.0.0 | 2 / 0 | |
| 0.0.3 | 2 / 0 | |
| 0.0.2 | 3 / 0 | |
| 0.0.1 | 1 / 0 | |
| 30.0.0-rc.1 | 6 / 3 | |
| 30.0.0-beta.8 | 6 / 3 | |
| 30.0.0-beta.7 | 6 / 3 | |
| 30.0.0-beta.6 | 6 / 3 | |
| 30.0.0-beta.3 | 6 / 2 |
v21.2.0
3 findingsAll previous maintainers (alexjuarez) were replaced by new maintainers (mjesun, aaronabramov, jeanlauliac, cpojer, fb). This is a strong signal of a potential package hijack and requires careful review.
This version was published by a different npm account than previous versions on 2017-09-26. 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.
v21.1.0
3 findingsAll previous maintainers (alexjuarez) were replaced by new maintainers (mjesun, aaronabramov, jeanlauliac, cpojer, fb). This is a strong signal of a potential package hijack and requires careful review.
This version was published by a different npm account than previous versions on 2017-09-14. 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.
v21.0.2
3 findingsAll previous maintainers (alexjuarez) were replaced by new maintainers (mjesun, aaronabramov, jeanlauliac, cpojer, fb). This is a strong signal of a potential package hijack and requires careful review.
This version was published by a different npm account than previous versions on 2017-09-08. 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.
v21.0.0
3 findingsAll previous maintainers (alexjuarez) were replaced by new maintainers (mjesun, aaronabramov, jeanlauliac, cpojer, fb). This is a strong signal of a potential package hijack and requires careful review.
This version was published by a different npm account than previous versions on 2017-09-04. 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.
v20.0.3
3 findingsAll previous maintainers (alexjuarez) were replaced by new maintainers (cpojer, dmitriiabramov, fb). This is a strong signal of a potential package hijack and requires careful review.
This version was published by a different npm account than previous versions on 2017-05-17. 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.
v20.0.2
3 findingsAll previous maintainers (alexjuarez) were replaced by new maintainers (cpojer, dmitriiabramov, fb). This is a strong signal of a potential package hijack and requires careful review.
This version was published by a different npm account than previous versions on 2017-05-17. 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.
v20.0.1
3 findingsAll previous maintainers (alexjuarez) were replaced by new maintainers (cpojer, dmitriiabramov, fb). This is a strong signal of a potential package hijack and requires careful review.
This version was published by a different npm account than previous versions on 2017-05-11. 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.
v20.0.0
3 findingsAll previous maintainers (alexjuarez) were replaced by new maintainers (cpojer, dmitriiabramov, fb). This is a strong signal of a potential package hijack and requires careful review.
This version was published by a different npm account than previous versions on 2017-05-06. 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.
v19.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.0.0
2 findingsThis version was published by a different npm account than previous versions on 2016-08-31. 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.
v14.0.0
2 findingsThis version was published by a different npm account than previous versions on 2016-07-27. 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.
v13.2.2
2 findingsThis version was published by a different npm account than previous versions on 2016-07-07. 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.
v13.2.1
2 findingsThis version was published by a different npm account than previous versions on 2016-07-07. 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.
v13.1.2
2 findingsThis version was published by a different npm account than previous versions on 2016-07-07. 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.
v13.1.1
2 findingsThis version was published by a different npm account than previous versions on 2016-07-06. 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.
v13.1.0
2 findingsThis version was published by a different npm account than previous versions on 2016-07-05. 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.
v13.0.0
2 findingsThis version was published by a different npm account than previous versions on 2016-06-22. 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.
v12.1.0
2 findingsThis version was published by a different npm account than previous versions on 2016-05-20. 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.
v12.0.2
2 findingsThis version was published by a different npm account than previous versions on 2016-04-28. 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.
v12.0.1
2 findingsThis version was published by a different npm account than previous versions on 2016-04-27. 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.
v12.0.0
2 findingsThis version was published by a different npm account than previous versions on 2016-04-27. 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.
v11.0.2
2 findingsThis version was published by a different npm account than previous versions on 2016-04-18. 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.
v11.0.1
2 findingsThis version was published by a different npm account than previous versions on 2016-04-15. 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.
v11.0.0
2 findingsThis version was published by a different npm account than previous versions on 2016-04-12. 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.
v10.0.3
2 findingsThis version was published by a different npm account than previous versions on 2016-04-12. 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.
v10.0.2
2 findingsThis version was published by a different npm account than previous versions on 2016-04-11. 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.
v10.0.1
2 findingsThis version was published by a different npm account than previous versions on 2016-03-30. 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.
v10.0.0
2 findingsThis version was published by a different npm account than previous versions on 2016-03-30. 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.
v9.0.3
2 findingsThis version was published by a different npm account than previous versions on 2016-03-23. 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.
v1.0.0
2 findingsThis version was published by a different npm account than previous versions on 2016-03-17. 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.
v0.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v30.0.0-rc.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 2025-06-09. This could indicate a legitimate maintainer transition or an account compromise.
v30.0.0-beta.8
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 2025-06-04. This could indicate a legitimate maintainer transition or an account compromise.
v30.0.0-beta.7
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 2025-06-04. This could indicate a legitimate maintainer transition or an account compromise.
v30.0.0-beta.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 2025-06-03. This could indicate a legitimate maintainer transition or an account compromise.
v30.0.0-beta.3
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 2025-05-27. This could indicate a legitimate maintainer transition or an account compromise.