@types/jsdom
TypeScript definitions for 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 |
|---|---|---|---|---|
| source-diff | net-exec-file:jsdom/base.d.ts | AI (source-diff): jsdom/base.d.ts is a TypeScript declaration file (.d.ts). References to network APIs and vm.Context are type signatures, not executable code. This is a stable false positive for DefinitelyTyped packages. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): undici-types is the official TypeScript types for Node.js's undici HTTP client. Adding it is expected as jsdom adopted undici for fetch; legitimate dependency for this package. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): @types/node is used via triple-slash references in .d.ts files, standard DefinitelyTyped practice. Not a phantom dependency. | ai | |
| phantom-deps | phantom-dep:@types/tough-cookie | AI (phantom-deps): @types/tough-cookie is used via triple-slash references in .d.ts files, standard DefinitelyTyped practice. Not a phantom dependency. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 28.0.3 | 4 / 0 | |
| 28.0.2 | 4 / 0 | |
| 28.0.1 | 4 / 0 | |
| 28.0.0 | 4 / 0 | |
| 27.0.0 | 3 / 0 | |
| 21.1.7 | 3 / 0 | |
| 12.2.3 | 3 / 0 |
v28.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.0.0
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.