jest-matcher-utils
A set of utility functions for expect and related packages
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): rubennorte is a known Facebook/Jest core maintainer; the cpojer→rubennorte transition is a legitimate team handoff within the Jest monorepo, not a compromise. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): gaearon (Dan Abramov) is a well-known Facebook/Meta engineer; his addition as maintainer on a Facebook Jest package is expected and not a compromise signal. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): pretty-format is a first-party Jest ecosystem package from the same Facebook/Jest monorepo; its addition as a dependency is entirely expected for jest-matcher-utils. | ai | |
| dependencies | unvetted-dep:jest-diff | AI (dependencies): jest-diff is a core Jest monorepo package published by the same trusted publisher (cpojer/jestjs) in lockstep with jest-matcher-utils; not a third-party risk. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Stub 0.0.0 release of a well-known Jest package; missing description is expected for this placeholder version. | ai | |
| npm-metadata | suspicious-initial-version | AI (npm-metadata): jest-matcher-utils is a long-established Jest core package (3571 days, 252 versions). The 0.0.0 is a historical placeholder stub, not a malicious throwaway. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Signals reflect a historical stub release of a legitimate Jest ecosystem package by trusted publisher cpojer. Not a spam or bogus package. | ai | |
| provenance | no-provenance | AI (provenance): Jest packages historically do not publish Sigstore provenance; this is consistent across the monorepo and not a risk signal for this well-established project. | ai |
Versions (showing 100 of 127)
| Version | Deps | Published |
|---|---|---|
| 30.4.1 | 4 / 2 | |
| 30.4.0 | 4 / 2 | |
| 30.3.0 | 4 / 2 | |
| 30.2.0 | 4 / 2 | |
| 30.1.2 | 4 / 2 | |
| 30.1.1 | 4 / 2 | |
| 30.1.0 | 4 / 2 | |
| 30.0.5 | 4 / 2 | |
| 30.0.4 | 4 / 2 | |
| 30.0.3 | 4 / 2 | |
| 30.0.2 | 4 / 2 | |
| 30.0.1 | 4 / 2 | |
| 30.0.0 | 4 / 2 | |
| 29.7.0 | 4 / 2 | |
| 29.6.4 | 4 / 2 | |
| 29.6.3 | 4 / 2 | |
| 29.6.2 | 4 / 2 | |
| 29.6.1 | 4 / 2 | |
| 29.6.0 | 4 / 2 | |
| 29.5.0 | 4 / 2 | |
| 29.4.3 | 4 / 2 | |
| 29.4.2 | 4 / 2 | |
| 29.4.1 | 4 / 2 | |
| 29.4.0 | 4 / 2 | |
| 29.3.1 | 4 / 2 | |
| 29.2.2 | 4 / 2 | |
| 29.2.1 | 4 / 2 | |
| 29.2.0 | 4 / 2 | |
| 29.1.2 | 4 / 2 | |
| 29.1.0 | 4 / 2 | |
| 29.0.3 | 4 / 2 | |
| 29.0.2 | 4 / 2 | |
| 29.0.1 | 4 / 2 | |
| 29.0.0 | 4 / 2 | |
| 28.1.3 | 4 / 2 | |
| 28.1.1 | 4 / 2 | |
| 28.1.0 | 4 / 2 | |
| 28.0.2 | 4 / 2 | |
| 28.0.1 | 4 / 2 | |
| 28.0.0 | 4 / 2 | |
| 27.5.1 | 4 / 2 | |
| 27.5.0 | 4 / 2 | |
| 27.4.6 | 4 / 2 | |
| 27.4.2 | 4 / 2 | |
| 27.4.1 | 4 / 2 | |
| 27.4.0 | 4 / 2 | |
| 27.3.1 | 4 / 2 | |
| 27.3.0 | 4 / 2 | |
| 27.2.5 | 4 / 2 | |
| 27.2.4 | 4 / 2 | |
| 27.2.3 | 4 / 2 | |
| 27.2.2 | 4 / 2 | |
| 27.2.0 | 4 / 2 | |
| 27.1.1 | 4 / 2 | |
| 27.1.0 | 4 / 2 | |
| 27.0.6 | 4 / 2 | |
| 27.0.2 | 4 / 2 | |
| 27.0.1 | 4 / 2 | |
| 27.0.0 | 4 / 2 | |
| 26.6.2 | 4 / 2 | |
| 26.6.1 | 4 / 2 | |
| 26.6.0 | 4 / 2 | |
| 26.5.2 | 4 / 2 | |
| 26.5.0 | 4 / 2 | |
| 26.4.2 | 4 / 2 | |
| 26.4.1 | 4 / 2 | |
| 26.4.0 | 4 / 2 | |
| 26.3.0 | 4 / 2 | |
| 26.2.0 | 4 / 2 | |
| 26.1.0 | 4 / 2 | |
| 26.0.1 | 4 / 2 | |
| 26.0.0 | 4 / 2 | |
| 25.5.0 | 4 / 2 | |
| 25.4.0 | 4 / 2 | |
| 25.3.0 | 4 / 2 | |
| 25.2.7 | 4 / 2 | |
| 25.2.6 | 4 / 2 | |
| 25.2.3 | 4 / 2 | |
| 25.2.1 | 4 / 2 | |
| 25.2.0 | 4 / 2 | |
| 25.1.0 | 4 / 0 | |
| 25.0.0 | 4 / 0 | |
| 24.9.0 | 4 / 0 | |
| 24.8.0 | 4 / 0 | |
| 24.7.0 | 4 / 0 | |
| 24.6.0 | 4 / 0 | |
| 24.5.0 | 4 / 0 | |
| 24.4.0 | 4 / 0 | |
| 24.3.1 | 4 / 0 | |
| 24.3.0 | 4 / 0 | |
| 24.0.0 | 4 / 0 | |
| 23.6.0 | 3 / 0 | |
| 23.5.0 | 3 / 0 | |
| 23.2.0 | 3 / 0 | |
| 23.0.1 | 3 / 0 | |
| 23.0.0 | 3 / 0 | |
| 22.4.3 | 3 / 0 | |
| 22.4.0 | 3 / 0 | |
| 22.2.0 | 3 / 0 | |
| 22.1.0 | 3 / 0 |
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.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v30.1.1
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.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.
v30.0.3
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. Consider requesting the maintainer enable provenance via CI/CD.
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.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. Consider requesting the maintainer enable provenance via CI/CD.
v29.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.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.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.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
2 findingsThis 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.6.1
2 findingsThis 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v26.6.0
2 findingsThis version was published by a different npm account than previous versions on 2020-10-19. 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.
v26.5.2
2 findingsThis version was published by a different npm account than previous versions on 2020-10-06. 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.
v26.5.0
2 findingsThis version was published by a different npm account than previous versions on 2020-10-05. 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.
v26.4.2
2 findingsThis version was published by a different npm account than previous versions on 2020-08-22. 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.
v26.4.1
2 findingsThis version was published by a different npm account than previous versions on 2020-08-20. 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.
v26.4.0
2 findingsThis version was published by a different npm account than previous versions on 2020-08-12. 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.
v26.3.0
2 findingsThis version was published by a different npm account than previous versions on 2020-08-10. 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.
v26.2.0
2 findingsThis version was published by a different npm account than previous versions on 2020-07-30. 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.
v26.1.0
2 findingsThis version was published by a different npm account than previous versions on 2020-06-23. 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.
v26.0.1
2 findingsThis version was published by a different npm account than previous versions on 2020-05-05. 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.
v26.0.0
2 findingsThis version was published by a different npm account than previous versions on 2020-05-04. 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.
v25.5.0
2 findingsThis version was published by a different npm account than previous versions on 2020-04-28. 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.
v25.4.0
2 findingsThis version was published by a different npm account than previous versions on 2020-04-19. 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.
v25.3.0
2 findingsThis version was published by a different npm account than previous versions on 2020-04-08. 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.
v25.2.7
2 findingsThis version was published by a different npm account than previous versions on 2020-04-03. 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.
v25.2.6
2 findingsThis version was published by a different npm account than previous versions on 2020-04-02. 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.
v25.2.3
2 findingsThis 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.2.1
2 findingsThis 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.2.0
2 findingsThis 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.1.0
2 findingsThis 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.0.0
2 findingsThis version was published by a different npm account than previous versions on 2019-08-22. 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.
v24.9.0
2 findingsThis version was published by a different npm account than previous versions on 2019-08-16. 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.
v24.8.0
2 findingsThis version was published by a different npm account than previous versions on 2019-05-05. 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.
v24.7.0
2 findingsThis 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.6.0
2 findingsThis version was published by a different npm account than previous versions on 2019-04-01. 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.
v24.5.0
2 findingsThis version was published by a different npm account than previous versions on 2019-03-12. 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.
v24.4.0
2 findingsThis version was published by a different npm account than previous versions on 2019-03-11. 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.
v24.3.1
2 findingsThis version was published by a different npm account than previous versions on 2019-03-07. 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.
v24.3.0
2 findingsThis version was published by a different npm account than previous versions on 2019-03-07. 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.
v24.0.0
2 findingsThis 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.6.0
2 findingsThis version was published by a different npm account than previous versions on 2018-09-10. 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.
v23.5.0
2 findingsThis version was published by a different npm account than previous versions on 2018-08-10. 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.
v23.2.0
2 findingsThis version was published by a different npm account than previous versions on 2018-06-25. 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.
v23.0.1
2 findingsThis version was published by a different npm account than previous versions on 2018-05-27. 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.
v23.0.0
2 findingsThis version was published by a different npm account than previous versions on 2018-05-24. 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.
v22.4.3
2 findingsThis version was published by a different npm account than previous versions on 2018-03-21. 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.
v22.4.0
2 findingsThis version was published by a different npm account than previous versions on 2018-02-20. 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.
v22.2.0
2 findingsThis version was published by a different npm account than previous versions on 2018-02-07. 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.
v22.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.