@jest/types
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): simenb is a well-known Jest core contributor at Facebook/Meta; the publisher transition is a documented, legitimate team change, not a compromise. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): simenb and davidzilburg are established Jest team members; addition reflects legitimate team evolution at Facebook/Meta. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): jeanlauliac's removal is consistent with documented Jest team changes; no evidence of hostile takeover. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): chalk is a highly trusted, widely-used npm package; its addition to @jest/types poses no supply chain risk. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): @types/* packages are TypeScript type declarations consumed by the TS compiler, not runtime imports. Phantom-dep detection is a stable false positive for all @types/* deps in this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Inflated semver is a false positive for Jest monorepo packages which use synchronized versioning. Missing description/keywords are cosmetic issues common in monorepo sub-packages. | ai | |
| phantom-deps | phantom-dep:@types/yargs | AI (phantom-deps): @types/yargs is a TypeScript type declaration package; not directly imported at runtime by design. | ai | |
| phantom-deps | phantom-dep:@types/istanbul-reports | AI (phantom-deps): @types/istanbul-reports is a TypeScript type declaration package; not directly imported at runtime by design. | ai | |
| phantom-deps | phantom-dep:@types/istanbul-lib-coverage | AI (phantom-deps): @types/istanbul-lib-coverage is a TypeScript type declaration package; not directly imported at runtime by design. | ai |
Versions (showing 51 of 69)
| Version | Deps | Published |
|---|---|---|
| 30.4.1 | 7 / 0 | |
| 30.4.0 | 7 / 0 | |
| 30.3.0 | 7 / 0 | |
| 30.2.0 | 7 / 0 | |
| 30.0.5 | 7 / 0 | |
| 30.0.1 | 7 / 0 | |
| 30.0.0 | 7 / 0 | |
| 29.6.3 | 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 | 5 / 2 | |
| 27.5.0 | 5 / 2 | |
| 27.4.2 | 5 / 1 | |
| 27.4.1 | 5 / 1 | |
| 27.4.0 | 5 / 0 | |
| 27.2.5 | 5 / 0 | |
| 27.2.4 | 5 / 0 | |
| 27.2.3 | 5 / 0 | |
| 27.1.1 | 5 / 0 | |
| 27.1.0 | 5 / 0 | |
| 27.0.6 | 5 / 0 | |
| 27.0.2 | 5 / 0 | |
| 27.0.1 | 5 / 0 | |
| 26.6.2 | 5 / 0 | |
| 26.6.1 | 5 / 0 | |
| 26.6.0 | 5 / 0 | |
| 26.5.2 | 5 / 0 | |
| 26.5.0 | 5 / 0 | |
| 26.3.0 | 5 / 0 | |
| 26.2.0 | 5 / 0 | |
| 26.1.0 | 4 / 1 |
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.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.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.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.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.
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.