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 57 of 157)
| Version | Deps | Published |
|---|---|---|
| 23.0.0 | 3 / 0 | |
| 22.4.3 | 3 / 0 | |
| 22.4.1 | 3 / 0 | |
| 22.4.0 | 3 / 0 | |
| 22.3.0 | 3 / 0 | |
| 22.2.2 | 3 / 0 | |
| 22.2.0 | 3 / 0 | |
| 22.1.4 | 3 / 0 | |
| 22.1.2 | 3 / 0 | |
| 22.1.0 | 3 / 0 | |
| 22.0.6 | 3 / 0 | |
| 22.0.5 | 3 / 0 | |
| 22.0.4 | 3 / 0 | |
| 22.0.3 | 3 / 0 | |
| 22.0.2 | 3 / 0 | |
| 22.0.1 | 3 / 0 | |
| 22.0.0 | 3 / 0 | |
| 21.2.1 | 3 / 0 | |
| 21.2.0 | 3 / 0 | |
| 21.1.0 | 3 / 0 | |
| 21.0.2 | 3 / 0 | |
| 21.0.0 | 3 / 0 | |
| 20.0.3 | 3 / 0 | |
| 20.0.2 | 3 / 0 | |
| 20.0.1 | 3 / 0 | |
| 20.0.0 | 3 / 0 | |
| 19.0.2 | 3 / 0 | |
| 19.0.1 | 3 / 0 | |
| 19.0.0 | 3 / 0 | |
| 18.1.0 | 3 / 0 | |
| 18.0.0 | 3 / 0 | |
| 17.0.2 | 3 / 0 | |
| 17.0.0 | 3 / 0 | |
| 16.0.2 | 3 / 0 | |
| 16.0.0 | 3 / 0 | |
| 15.1.1 | 2 / 0 | |
| 15.1.0 | 2 / 0 | |
| 15.0.1 | 2 / 0 | |
| 15.0.0 | 2 / 0 | |
| 14.0.0 | 2 / 0 | |
| 13.2.2 | 2 / 0 | |
| 13.2.1 | 2 / 0 | |
| 13.2.0 | 2 / 0 | |
| 13.1.3 | 2 / 0 | |
| 13.1.2 | 2 / 0 | |
| 13.1.1 | 2 / 0 | |
| 13.1.0 | 2 / 0 | |
| 13.0.0 | 2 / 0 | |
| 12.1.0 | 2 / 0 | |
| 12.0.2 | 2 / 0 | |
| 12.0.1 | 2 / 0 | |
| 12.0.0 | 2 / 0 | |
| 11.0.2 | 2 / 0 | |
| 11.0.1 | 2 / 0 | |
| 11.0.0 | 2 / 0 | |
| 10.0.2 | 2 / 0 | |
| 1.0.0 | 0 / 0 |
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.1
2 findingsThis version was published by a different npm account than previous versions on 2018-02-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.
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.3.0
2 findingsThis version was published by a different npm account than previous versions on 2018-02-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.
v22.2.2
2 findingsThis version was published by a different npm account than previous versions on 2018-02-09. 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.4
2 findingsThis version was published by a different npm account than previous versions on 2018-01-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.
v22.1.2
2 findingsThis version was published by a different npm account than previous versions on 2018-01-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.
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.5
2 findingsThis version was published by a different npm account than previous versions on 2018-01-09. 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.0.4
2 findingsThis version was published by a different npm account than previous versions on 2017-12-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.
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.
v21.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.