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 51 of 149)
| Version | Deps | Published |
|---|---|---|
| 30.4.1 | 6 / 5 | |
| 30.4.0 | 6 / 5 | |
| 30.3.0 | 6 / 5 | |
| 30.2.0 | 6 / 3 | |
| 30.0.5 | 6 / 3 | |
| 30.0.2 | 6 / 3 | |
| 30.0.1 | 6 / 3 | |
| 30.0.0 | 6 / 3 | |
| 29.7.0 | 6 / 2 | |
| 29.6.3 | 6 / 2 | |
| 29.6.2 | 6 / 2 | |
| 29.6.1 | 6 / 2 | |
| 29.6.0 | 6 / 2 | |
| 29.5.0 | 6 / 2 | |
| 29.4.3 | 6 / 2 | |
| 29.4.2 | 6 / 2 | |
| 29.4.1 | 6 / 2 | |
| 29.4.0 | 6 / 2 | |
| 29.3.1 | 6 / 2 | |
| 29.2.1 | 6 / 2 | |
| 29.2.0 | 6 / 2 | |
| 29.1.2 | 6 / 2 | |
| 29.1.0 | 6 / 2 | |
| 29.0.3 | 6 / 2 | |
| 29.0.2 | 6 / 2 | |
| 29.0.1 | 6 / 2 | |
| 29.0.0 | 6 / 2 | |
| 28.1.3 | 6 / 2 | |
| 28.1.1 | 6 / 2 | |
| 28.1.0 | 6 / 2 | |
| 28.0.2 | 6 / 2 | |
| 28.0.1 | 6 / 2 | |
| 28.0.0 | 6 / 2 | |
| 27.5.1 | 6 / 3 | |
| 27.5.0 | 6 / 3 | |
| 27.4.2 | 6 / 3 | |
| 27.4.1 | 6 / 3 | |
| 27.4.0 | 6 / 3 | |
| 27.3.1 | 6 / 3 | |
| 27.3.0 | 6 / 4 | |
| 27.2.5 | 6 / 4 | |
| 27.2.4 | 6 / 4 | |
| 27.2.3 | 6 / 4 | |
| 27.2.0 | 6 / 4 | |
| 27.1.1 | 6 / 4 | |
| 27.1.0 | 6 / 4 | |
| 27.0.6 | 6 / 4 | |
| 27.0.2 | 6 / 4 | |
| 27.0.1 | 6 / 4 | |
| 26.6.2 | 6 / 3 | |
| 26.6.1 | 6 / 3 |
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.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.1.3
3 findingsAll previous maintainers (alexjuarez) were replaced by new maintainers (scotthovestadt, rubennorte, simenb, fb, aaronabramov, davidzilburg). 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 2022-07-13. 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.
v28.1.1
3 findingsAll previous maintainers (alexjuarez) were replaced by new maintainers (scotthovestadt, rubennorte, simenb, fb, aaronabramov, davidzilburg). 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 2022-06-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.
v28.1.0
3 findingsAll previous maintainers (alexjuarez) were replaced by new maintainers (scotthovestadt, rubennorte, simenb, fb, aaronabramov, davidzilburg). 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 2022-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.
v28.0.2
3 findingsAll previous maintainers (alexjuarez) were replaced by new maintainers (scotthovestadt, rubennorte, simenb, fb, aaronabramov, davidzilburg). 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 2022-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.
v28.0.1
3 findingsAll previous maintainers (alexjuarez) were replaced by new maintainers (scotthovestadt, rubennorte, simenb, fb, aaronabramov, davidzilburg). 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 2022-04-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.
v28.0.0
3 findingsAll previous maintainers (alexjuarez) were replaced by new maintainers (scotthovestadt, rubennorte, simenb, fb, aaronabramov, davidzilburg). 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 2022-04-25. 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.
v27.5.1
3 findingsAll previous maintainers (alexjuarez) were replaced by new maintainers (scotthovestadt, rubennorte, simenb, fb, aaronabramov, davidzilburg). 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 2022-02-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.
v27.5.0
3 findingsAll previous maintainers (alexjuarez) were replaced by new maintainers (scotthovestadt, rubennorte, simenb, fb, aaronabramov, davidzilburg). 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 2022-02-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.
v27.4.2
3 findingsAll previous maintainers (alexjuarez) were replaced by new maintainers (scotthovestadt, rubennorte, simenb, fb, aaronabramov, davidzilburg). 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 2021-11-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.
v27.4.1
3 findingsAll previous maintainers (alexjuarez) were replaced by new maintainers (scotthovestadt, rubennorte, simenb, fb, aaronabramov, davidzilburg). 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 2021-11-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.
v27.4.0
3 findingsAll previous maintainers (alexjuarez) were replaced by new maintainers (scotthovestadt, rubennorte, simenb, fb, aaronabramov, davidzilburg). 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 2021-11-29. 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.
v27.3.1
3 findingsAll previous maintainers (alexjuarez) were replaced by new maintainers (scotthovestadt, rubennorte, simenb, fb, aaronabramov, davidzilburg). 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 2021-10-19. 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.
v27.3.0
3 findingsAll previous maintainers (alexjuarez) were replaced by new maintainers (scotthovestadt, rubennorte, simenb, fb, aaronabramov, davidzilburg). 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 2021-10-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.
v27.2.5
3 findingsAll previous maintainers (alexjuarez) were replaced by new maintainers (scotthovestadt, rubennorte, simenb, fb, aaronabramov, davidzilburg). 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 2021-10-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.
v27.2.4
3 findingsAll previous maintainers (alexjuarez) were replaced by new maintainers (scotthovestadt, rubennorte, simenb, fb, aaronabramov, davidzilburg). 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 2021-09-29. 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.
v27.2.3
3 findingsAll previous maintainers (alexjuarez) were replaced by new maintainers (scotthovestadt, rubennorte, simenb, fb, aaronabramov, davidzilburg). 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 2021-09-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.
v27.2.0
3 findingsAll previous maintainers (alexjuarez) were replaced by new maintainers (scotthovestadt, rubennorte, simenb, fb, aaronabramov, davidzilburg). 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 2021-09-13. 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.
v27.1.1
3 findingsAll previous maintainers (alexjuarez) were replaced by new maintainers (scotthovestadt, rubennorte, simenb, fb, aaronabramov, davidzilburg). 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 2021-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.
v27.1.0
3 findingsAll previous maintainers (alexjuarez) were replaced by new maintainers (scotthovestadt, rubennorte, simenb, fb, aaronabramov, davidzilburg). 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 2021-08-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.
v27.0.6
3 findingsAll previous maintainers (alexjuarez) were replaced by new maintainers (scotthovestadt, rubennorte, simenb, fb, aaronabramov, davidzilburg). 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 2021-06-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.
v27.0.2
3 findingsAll previous maintainers (alexjuarez) were replaced by new maintainers (scotthovestadt, rubennorte, simenb, fb, aaronabramov, davidzilburg). 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 2021-05-29. 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.
v27.0.1
3 findingsAll previous maintainers (alexjuarez) were replaced by new maintainers (scotthovestadt, rubennorte, simenb, fb, aaronabramov, davidzilburg). 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 2021-05-25. 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.
v26.6.2
3 findingsAll previous maintainers (alexjuarez) were replaced by new maintainers (scotthovestadt, rubennorte, simenb, cpojer, fb, aaronabramov, davidzilburg). 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 2020-11-02. 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.
v26.6.1
3 findingsAll previous maintainers (alexjuarez) were replaced by new maintainers (scotthovestadt, rubennorte, simenb, cpojer, fb, aaronabramov, davidzilburg). 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 2020-10-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.