purify-edge
github.com/anzal1/purify-edge- Category
- Developer Tools
- Rank
- No. 3012Tools index
Previous survey · No. 2295 ·
- Pricing
- Open Source
- Type
- TOOL
- Use case
- Security & Identity
- GitHub
- 1 stars
- Latest release
- v0.1.2
- Date
About
purify-edge runs the unmodified DOMPurify sanitizer on a small parse5-based DOM instead of jsdom, so HTML sanitization works on Cloudflare Workers and other edge runtimes. Its output is byte-identical to DOMPurify on jsdom, at about 65 KB gzipped. It is verified against DOMPurify 3.4.16 only.
At a glance
purify-edge runs DOMPurify against a small DOM implementation that can fit edge environments. It is worth evaluating if your runtime cannot use jsdom and you need HTML sanitization in that runtime.
Good fit
Developers handling HTML on a supported edge runtime who can verify the sanitizer against their own inputs.
Consider something else when
Keep your existing sanitizer if it already works in your environment and you have a tested configuration.
Start here
Read the supported version and runtime matrix. Compare a small corpus of malicious and legitimate HTML against your expected output in the target runtime.
Cost and requirements
The project documents an npm package for Node.js 20 or later and tested edge runtimes. Check the repository license and pinned dependency versions before use.
Limits to know
The project’s parity claim applies to one DOMPurify version and its test corpus. Review supported options and treat version or runtime changes as reasons to recheck behavior.
Sources checked 2026-11-05. Source-based assessment.
Tags
Tech Stack
Comments (0)
No comments yet
Editorially curated, with community endorsements as a secondary signal. Corrections welcome.