jest-environment-jsdom
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 |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): jest-environment-jsdom is a well-known Jest monorepo sub-package; missing description is a cosmetic issue, not a malware indicator. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): jest-mock is a core Jest monorepo package from the same publisher (cpojer/facebook); adding internal Jest dependencies is expected and benign for this package. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change from cpojer to mjesun reflects a documented Jest team transition in 2017; mjesun is a known Jest core contributor with strong track record. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers (mjesun, aaronabramov, jeanlauliac) are recognized Jest ecosystem contributors; addition is consistent with legitimate team expansion. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of dmitriiabramov is consistent with the same 2017 Jest team transition; no evidence of malicious takeover. | ai | |
| phantom-deps | phantom-dep:@types/jsdom | AI (phantom-deps): @types/jsdom is framework-scoped and loaded by convention in Jest packages; not a real dependency issue. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): @types/node is framework-scoped and loaded by convention in Jest packages; not a real dependency issue. | ai | |
| bogus-package | bogus-package | AI (bogus-package): jest-environment-jsdom is an official Jest monorepo package; inflated semver matches Jest's release train, and missing description/keywords are cosmetic gaps common in monorepo packages. | ai |
Versions (showing 51 of 157)
| Version | Deps | Published |
|---|---|---|
| 30.4.1 | 3 / 1 | |
| 30.4.0 | 3 / 1 | |
| 30.3.0 | 3 / 1 | |
| 30.2.0 | 5 / 1 | |
| 30.1.2 | 5 / 1 | |
| 30.1.1 | 5 / 1 | |
| 30.1.0 | 5 / 1 | |
| 30.0.5 | 5 / 1 | |
| 30.0.4 | 5 / 1 | |
| 30.0.2 | 5 / 1 | |
| 30.0.1 | 5 / 1 | |
| 30.0.0 | 5 / 1 | |
| 29.7.0 | 8 / 1 | |
| 29.6.4 | 8 / 1 | |
| 29.6.3 | 8 / 1 | |
| 29.6.2 | 8 / 1 | |
| 29.6.1 | 8 / 1 | |
| 29.6.0 | 8 / 1 | |
| 29.5.0 | 8 / 1 | |
| 29.4.3 | 8 / 1 | |
| 29.4.2 | 8 / 1 | |
| 29.4.1 | 8 / 1 | |
| 29.4.0 | 8 / 1 | |
| 29.3.1 | 8 / 1 | |
| 29.3.0 | 8 / 1 | |
| 29.2.2 | 8 / 1 | |
| 29.2.1 | 8 / 1 | |
| 29.2.0 | 8 / 1 | |
| 29.1.2 | 8 / 1 | |
| 29.1.1 | 8 / 1 | |
| 29.1.0 | 8 / 1 | |
| 29.0.3 | 8 / 1 | |
| 29.0.2 | 8 / 1 | |
| 29.0.1 | 8 / 1 | |
| 29.0.0 | 8 / 1 | |
| 28.1.3 | 8 / 1 | |
| 28.1.2 | 8 / 1 | |
| 28.1.1 | 8 / 1 | |
| 28.1.0 | 8 / 1 | |
| 28.0.2 | 8 / 1 | |
| 28.0.1 | 8 / 1 | |
| 28.0.0 | 8 / 1 | |
| 27.5.1 | 7 / 2 | |
| 27.5.0 | 7 / 2 | |
| 27.4.6 | 7 / 2 | |
| 27.4.4 | 7 / 2 | |
| 27.4.3 | 7 / 2 | |
| 27.4.2 | 8 / 1 | |
| 27.4.1 | 8 / 1 | |
| 27.4.0 | 8 / 1 | |
| 27.3.1 | 7 / 2 |
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.
v30.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v30.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v30.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v30.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v30.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v30.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v30.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v30.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
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.2.2
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v29.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.2
2 findingsThis version was published by a different npm account than previous versions on 2022-06-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.
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.4
2 findingsThis version was published by a different npm account than previous versions on 2021-12-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.
v27.4.3
2 findingsThis version was published by a different npm account than previous versions on 2021-12-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.
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.