@locker/html-sanitizer
Lightning Web Security HTML and SVG sanitization utilities
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@types/dompurify | AI (phantom-deps): @types/dompurify is a TypeScript type package used at build time; not imported at runtime by convention. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established Salesforce @locker scoped package with 259 versions; sparse metadata is a team convention, not spam. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 0.28.1 | 5 / 0 | |
| 0.27.5 | 5 / 0 | |
| 0.27.4 | 5 / 0 | |
| 0.27.3 | 5 / 0 | |
| 0.27.2 | 5 / 0 | |
| 0.27.1 | 5 / 0 | |
| 0.26.4 | 5 / 0 | |
| 0.26.3 | 5 / 0 | |
| 0.26.2 | 5 / 0 | |
| 0.26.1 | 6 / 0 | |
| 0.26.0 | 6 / 0 | |
| 0.25.7 | 6 / 0 | |
| 0.25.6 | 6 / 0 | |
| 0.25.5 | 6 / 0 | |
| 0.25.4 | 6 / 0 | |
| 0.25.3 | 6 / 0 | |
| 0.25.2 | 6 / 0 |
v0.28.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.27.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.26.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.26.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.0
2 findingsThis version was published by a different npm account than previous versions on 2025-10-15. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.25.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.