@xmldom/xmldom
npmIs @xmldom/xmldom safe to use?
The latest brin safety scan flagged @xmldom/xmldom v0.8.11 with risk indicators that warrant review. 2 known CVE vulnerabilities. Trust score: 65/100. Review the findings below before use. This is an automated assessment and may contain errors.
Install (safety-checked)
@xmldom/xmldom Has Warnings
Warnings detected due to potential concerns
2
0
0
Risk Indicators
- •Can spawn child processes
@xmldom/xmldom CVE Vulnerabilities (2)
Misinterpretation of malicious XML input
Fixed in: 0.7.0
xmldom allows multiple root nodes in a DOM
Fixed in: 0.9.0-beta.4
brin Recommendations
- →This package has warnings detected. Evaluate the specific concerns before proceeding.
Install with brin add @xmldom/xmldom to automatically apply these checks before installation.
This is an automated, point-in-time assessment and may contain errors. Findings are risk indicators, not confirmed threats. Security posture may change over time. Maintainers can dispute findings via the brin review process.
@xmldom/xmldom Capabilities & Permissions
What @xmldom/xmldom can access when installed. Review these capabilities before using with AI agents like Cursor, Claude Code, or Codex.
Process Spawning
This package can spawn child processes.
AGENTS.md for @xmldom/xmldom
Good instructions lead to good results. brin adds @xmldom/xmldom documentation to your AGENTS.md so your agent knows how to use it properly—improving both safety and performance.
brin initVercel's research: 100% accuracy with AGENTS.md vs 53% without →
@xmldom/xmldom Documentation & Source Code
For the full @xmldom/xmldom README, API documentation, and source code, visit the official package registry.
Frequently asked questions about @xmldom/xmldom safety
Install (safety-checked)
Weekly Downloads
Version
0.8.11License
MITLast Scanned
Trust Score
CVEs (2)
Capabilities
Spawns child processes