jest-message-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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): New deps (@jest/types, graceful-fs, @types/stack-utils) are all legitimate, well-known packages consistent with Jest v26 refactoring. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change from cpojer to simenb reflects a legitimate Jest team transition at Facebook; simenb is a well-known Jest core contributor with a strong track record. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers are known Jest/Facebook contributors; this reflects the documented Jest team evolution, not a takeover. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removed maintainers are consistent with team changes within the Jest project at Facebook; no compromise indicators. | ai | |
| dependencies | unvetted-dep:@jest/types | AI (dependencies): @jest/types is a core Jest monorepo package; always co-released with jest-message-util at the same version. Stable false positive for this package. | ai | |
| dependencies | unvetted-dep:stack-utils | AI (dependencies): stack-utils is a well-known, stable utility used by Jest for stack trace parsing. No security concerns. | ai | |
| dependencies | unvetted-dep:@types/stack-utils | AI (dependencies): Type definitions package for stack-utils; no runtime risk. Stable false positive for this package. | ai | |
| npm-metadata | suspicious-initial-version | AI (npm-metadata): [email protected] is a well-known Jest monorepo placeholder version published by the core Jest maintainer; 0.0.0 is a standard stub pattern in this ecosystem. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Jest monorepo internal utility; missing description is standard for such packages and not a risk signal. | ai | |
| phantom-deps | phantom-dep:@types/stack-utils | AI (phantom-deps): @types/stack-utils is a TypeScript type declaration used at compile time, not imported at runtime. Phantom-dep detection is a stable false positive for @types/* packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo-published package; empty description and inflated semver are expected patterns in Jest's versioning scheme, not malware indicators. | ai |
Versions (showing 100 of 108)
| Version | Deps | Published |
|---|---|---|
| 30.4.1 | 10 / 4 | |
| 30.4.0 | 10 / 4 | |
| 30.3.0 | 9 / 4 | |
| 30.2.0 | 9 / 4 | |
| 30.1.0 | 9 / 4 | |
| 30.0.5 | 9 / 4 | |
| 30.0.2 | 9 / 4 | |
| 30.0.1 | 9 / 4 | |
| 30.0.0 | 9 / 4 | |
| 29.7.0 | 9 / 4 | |
| 29.6.3 | 9 / 4 | |
| 29.6.2 | 9 / 4 | |
| 29.6.1 | 9 / 4 | |
| 29.6.0 | 9 / 4 | |
| 29.5.0 | 9 / 4 | |
| 29.4.3 | 9 / 4 | |
| 29.4.2 | 9 / 4 | |
| 29.4.1 | 9 / 3 | |
| 29.4.0 | 9 / 3 | |
| 29.3.1 | 9 / 3 | |
| 29.2.1 | 9 / 3 | |
| 29.2.0 | 9 / 3 | |
| 29.1.2 | 9 / 3 | |
| 29.1.0 | 9 / 3 | |
| 29.0.3 | 9 / 3 | |
| 29.0.2 | 9 / 3 | |
| 29.0.1 | 9 / 3 | |
| 29.0.0 | 9 / 3 | |
| 28.1.3 | 9 / 3 | |
| 28.1.1 | 9 / 3 | |
| 28.1.0 | 9 / 3 | |
| 28.0.2 | 9 / 3 | |
| 28.0.1 | 9 / 3 | |
| 28.0.0 | 9 / 3 | |
| 27.5.1 | 9 / 3 | |
| 27.5.0 | 9 / 3 | |
| 27.4.6 | 9 / 3 | |
| 27.4.2 | 9 / 3 | |
| 27.4.1 | 9 / 3 | |
| 27.4.0 | 9 / 3 | |
| 27.3.1 | 9 / 3 | |
| 27.3.0 | 9 / 3 | |
| 27.2.5 | 9 / 3 | |
| 27.2.4 | 9 / 3 | |
| 27.2.3 | 9 / 3 | |
| 27.2.2 | 9 / 3 | |
| 27.2.0 | 9 / 3 | |
| 27.1.1 | 9 / 3 | |
| 27.1.0 | 9 / 3 | |
| 27.0.6 | 9 / 3 | |
| 27.0.2 | 9 / 3 | |
| 27.0.1 | 9 / 3 | |
| 27.0.0 | 9 / 3 | |
| 26.6.2 | 9 / 3 | |
| 26.6.1 | 8 / 3 | |
| 26.6.0 | 8 / 3 | |
| 26.5.2 | 8 / 3 | |
| 26.5.0 | 8 / 3 | |
| 26.3.0 | 8 / 3 | |
| 26.2.0 | 8 / 3 | |
| 26.1.0 | 8 / 3 | |
| 26.0.1 | 8 / 3 | |
| 26.0.0 | 8 / 3 | |
| 25.5.0 | 8 / 3 | |
| 25.4.0 | 7 / 2 | |
| 25.3.0 | 7 / 2 | |
| 25.2.6 | 7 / 2 | |
| 25.2.5 | 7 / 2 | |
| 25.2.4 | 8 / 2 | |
| 25.2.3 | 8 / 2 | |
| 25.2.1 | 8 / 2 | |
| 25.2.0 | 8 / 2 | |
| 25.1.0 | 8 / 2 | |
| 25.0.0 | 8 / 2 | |
| 24.9.0 | 8 / 3 | |
| 24.8.0 | 8 / 3 | |
| 24.7.1 | 8 / 3 | |
| 24.7.0 | 8 / 3 | |
| 24.6.0 | 8 / 3 | |
| 24.5.0 | 8 / 3 | |
| 24.3.0 | 8 / 3 | |
| 24.0.0 | 5 / 0 | |
| 23.4.0 | 5 / 0 | |
| 23.3.0 | 5 / 0 | |
| 23.2.0 | 5 / 0 | |
| 23.1.0 | 5 / 0 | |
| 23.0.2 | 5 / 0 | |
| 23.0.0 | 5 / 0 | |
| 22.4.3 | 5 / 0 | |
| 22.4.0 | 5 / 0 | |
| 22.2.0 | 5 / 0 | |
| 22.1.0 | 5 / 0 | |
| 22.0.6 | 5 / 0 | |
| 22.0.3 | 5 / 0 | |
| 22.0.2 | 5 / 0 | |
| 22.0.1 | 5 / 0 | |
| 22.0.0 | 5 / 0 | |
| 21.2.1 | 3 / 0 | |
| 21.2.0 | 3 / 0 | |
| 21.1.0 | 3 / 0 |
v30.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v30.4.0
2 findingsPackage 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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v30.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v30.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v30.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v30.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v30.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v29.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v28.1.3
2 findingsThis 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
2 findingsThis 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
2 findingsThis 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
2 findingsThis 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
2 findingsThis 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
2 findingsThis 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
2 findingsThis 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
2 findingsThis 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.6
2 findingsThis version was published by a different npm account than previous versions on 2022-01-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.
v27.4.2
2 findingsThis 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
2 findingsThis 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
2 findingsThis 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
2 findingsThis 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
2 findingsThis 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
2 findingsThis 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
2 findingsThis 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
2 findingsThis 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.2
2 findingsThis version was published by a different npm account than previous versions on 2021-09-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.2.0
2 findingsThis 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
2 findingsThis 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
2 findingsThis 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
2 findingsThis 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
2 findingsThis 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
2 findingsThis 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.
v27.0.0
2 findingsThis 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
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.2.5
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.2.4
2 findingsThis version was published by a different npm account than previous versions on 2020-03-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.
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.
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.
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.
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.
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.
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.
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.7.1
2 findingsThis version was published by a different npm account than previous versions on 2019-04-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.
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.
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.
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.
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.
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.4.0
2 findingsThis version was published by a different npm account than previous versions on 2018-07-10. 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.
v23.3.0
2 findingsThis version was published by a different npm account than previous versions on 2018-07-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.
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.1.0
2 findingsThis version was published by a different npm account than previous versions on 2018-05-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.
v23.0.2
2 findingsThis version was published by a different npm account than previous versions on 2018-05-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.
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.
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.
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.
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.1
1 findingPackage 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.