← Home

xss

npm Repository Homepage

Sanitize untrusted HTML (to prevent XSS) with a configuration specified by a Whitelist

16
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

leizongmin

Keywords

sanitizationxsssanitizesanitisationinputsecurityescapeencodefiltervalidatorhtmlinjectionwhitelist

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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

Versions (showing 16 of 16)

Version Deps Published
1.0.15 2 / 7
1.0.14 2 / 7
1.0.13 2 / 7
1.0.12 2 / 7
1.0.11 2 / 6
1.0.10 2 / 6
1.0.9 2 / 6
1.0.8 2 / 6
1.0.7 2 / 6
1.0.6 2 / 6
1.0.5 2 / 6
1.0.4 2 / 6
1.0.3 2 / 6
1.0.2 2 / 6
1.0.1 2 / 6
1.0.0 2 / 6

v1.0.14

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.12

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.11

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.10

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.9

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.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.