Summary
Togoder Security scanned the npm package parse5@8.0.1 on Oct 6, 2026. An AI review of 14 source files produced no findings. No malicious behavior, install-time payloads, credential theft or exfiltration were identified.
Findings
No findings. The reviewer saw nothing malicious or risky in this version.
Files reviewed
| File | Verdict | What the reviewer saw |
|---|---|---|
| dist/common/doctype.js | safe | Cleared by Jev triage; no further analysis needed |
| dist/common/error-codes.js | safe | No malicious patterns detected |
| dist/common/foreign-content.js | safe | Cleared by Jev triage; no further analysis needed |
| dist/common/html.js | safe | No malicious patterns detected; the file only defines HTML namespace, tag name, and tag ID constants with no I/O, network, or dynamic code execution. |
| dist/common/token.js | safe | No malicious patterns detected |
| dist/common/unicode.js | safe | No malicious patterns detected; the file contains only standard Unicode code point constants and helper functions. |
| dist/index.js | safe | Cleared by Jev triage; no further analysis needed |
| dist/parser/formatting-element-list.js | safe | Cleared by Jev triage; no further analysis needed |
| dist/parser/open-element-stack.js | safe | Cleared by Jev triage; no further analysis needed |
| dist/serializer/index.js | safe | Cleared by Jev triage; no further analysis needed |
| dist/tokenizer/index.js | safe | This is a legitimate HTML tokenizer implementation (parse5) with no malicious patterns, network calls, process execution, or obfuscated code. |
| dist/tokenizer/preprocessor.js | safe | Cleared by Jev triage; no further analysis needed |
| dist/tree-adapters/default.js | safe | Cleared by Jev triage; no further analysis needed |
| dist/tree-adapters/interface.js | safe | Cleared by Jev triage; no further analysis needed |
Affected version ranges
None of the 3 scanned versions of parse5 are flagged high or critical. The latest scanned version, 8.0.1, is clean. Only versions we have scanned are listed; unscanned versions between them are not covered.
| Versions | Verdict | Count | Range | Top findings |
|---|---|---|---|---|
| 8.0.1 | No issues | 1 | 8.0.1 | |
| 7.3.0 | Not scanned | 1 | 7.3.0 | |
| 5.1.1 – 6.0.1 | No issues | 2 | >=5.1.1 <=6.0.1 |
Full list, including published versions not scanned yet: version ranges API.
Scanned versions of parse5
Frequently asked questions
Is parse5 safe to use?
Our AI source review of parse5@8.0.1 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does parse5 contain malware?
No malware was identified in parse5@8.0.1 when Togoder Security scanned it on Oct 6, 2026. A new version can still introduce malicious code, so scan the exact versions in your lockfile.
How was parse5 checked?
Togoder Security downloaded the published npm package and had an AI model read its 14 source files, looking for install scripts, credential access, network exfiltration, obfuscation, backdoors and crypto-wallet theft. The results are cached by file hash and shown here.
How do I scan parse5 together with the rest of my dependencies?
Upload your lockfile at https://security.togoder.click/scan or call the API documented at https://security.togoder.click/api-docs. Files that have already been scanned, like the ones in parse5@8.0.1, cost nothing.