happy-dom-without-node
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.
Keywords
jsdomdombrowsercustomelementswebcomponentshtmlwhatwgw3c
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): Used in SyncFetch for synchronous HTTP via subprocess — standard happy-dom pattern, not malicious. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Decodes HTTP response body data from base64; legitimate transport encoding handling. | ai | |
| phantom-deps | phantom-dep:webidl-conversions | AI (phantom-deps): webidl-conversions is a declared dependency used transitively; phantom-dep false positive for this package. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 14.12.3 | 4 / 0 |
v14.12.3
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.