xss
Sanitize untrusted HTML (to prevent XSS) with a configuration specified by a Whitelist
2
Versions
MIT
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
leizongmin
Keywords
sanitizationxsssanitizesanitisationinputsecurityescapeencodefiltervalidatorhtmlinjectionwhitelist
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:qs | AI (typosquat): xss is a legitimate, well-known HTML sanitization library; its name describes its purpose and is not a typosquat of qs. Edit distance match is purely coincidental. | ai | |
| typosquat | typosquat.levenshtein:rxjs | AI (typosquat): xss is a legitimate, well-known HTML sanitization library; its name describes its purpose and is not a typosquat of rxjs. Edit distance match is purely coincidental. | ai | |
| phantom-deps | phantom-dep:commander | AI (phantom-deps): commander is used by the xss CLI binary (bin/xss); it is a legitimate runtime dependency even if not imported in the library source files. | ai |
v1.0.13
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.