Sanitize untrusted HTML (to prevent XSS) with a configuration specified by a Whitelist
68%
Total Score
50
100
95
80
50
No build attestation or trusted publisher identity is present, reducing publication transparency, though this is a provenance gap rather than evidence that the package is unsafe.
A prepublish lifecycle script adds some build-time supply-chain complexity, although the signal does not show a postinstall script that would run for consumers installing the package.
Only one registry account has publishing access, creating a modest publishing continuity risk; the linked repository and long release history provide some compensating project evidence.
The repository is owned by an individual rather than an organization, so there is no visible organizational backing to offset the single-publisher structure.
The package has a long history with 73 releases, but its latest registry release was over two years ago and it had no releases in the last 12 months, indicating slowed publishing.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
commander Version ^2.20.3 | — | — |
cssfilter Version 0.0.10 | — | — |
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.