# dompurify@3.4.16 security report (npm)

- Verdict: **No issues** (risk level: safe)
- Scanned: 2026-10-06T14:15:51.000Z
- Files reviewed: 9
- Findings: no findings
- Report: https://security.togoder.click/npm/dompurify
- Source: Togoder Security (https://security.togoder.click), AI source-code review

## Summary

Togoder Security scanned the npm package dompurify@3.4.16 on Oct 6, 2026. An AI review of 9 source files produced no findings. No malicious behavior, install-time payloads, credential theft or exfiltration were identified.

## Findings

No findings.

## Files reviewed

- `dist/purify.cjs.js` (safe): This is the legitimate DOMPurify HTML sanitization library (v3.4.16), containing only standard Babel-transpiled helpers and DOMPurify's documented sanitization logic with no malicious patterns such as exfiltration, credential harvesting, dynamic code execution, or install-time hooks.
- `dist/purify.es.mjs` (safe): This is the legitimate DOMPurify 3.4.16 XSS sanitization library with no malicious patterns detected.
- `dist/purify.js` (safe): No malicious patterns detected; this is a legitimate, unmodified build of DOMPurify 3.4.16 whose code performs HTML sanitization without any exfiltration, credential harvesting, obfuscated payloads, dynamic code execution, network calls, or process spawning.
- `src/attrs.ts` (safe): Cleared by Jev triage; no further analysis needed
- `src/config.ts` (safe): Cleared by Jev triage; no further analysis needed
- `src/regexp.ts` (safe): Cleared by Jev triage; no further analysis needed
- `src/tags.ts` (safe): Cleared by Jev triage; no further analysis needed
- `src/types.ts` (safe): Cleared by Jev triage; no further analysis needed
- `src/utils.ts` (safe): No malicious patterns detected; the code is a defensive utility library (DOMPurify-style) that hardens against prototype pollution and implements safe string/object operations.

AI analysis is guidance, not a guarantee. Methodology: https://security.togoder.click/methodology