jsdom-no-contextify
A JavaScript implementation of the DOM and HTML standards
1
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
davidagraf
Keywords
domhtmlwhatwgw3c
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Package is a legitimate ~11-year-old jsdom fork. Inflated semver reflects upstream jsdom version at fork time; README link dump is inherited from upstream project documentation. | ai | |
| phantom-deps | phantom-dep:browser-request | AI (phantom-deps): browser-request is declared as a Browserify browser-field alias for the request package — standard pattern, not a phantom dependency in the malicious sense. | ai | |
| provenance | no-provenance | AI (provenance): Package was published ~11 years ago, long before Sigstore provenance was available on npm. No provenance is expected and not a risk signal here. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 3.1.0 | 9 / 12 |
v3.1.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.