Skip to main content
FOSSA Logo
Skip to package details

xmldom

npm469 GitHub stars

v0.6.0 · Apr 2021 · MIT (top-level declared license)

npm install xmldom
  • 16 known CVEs (16 in v0.6.0)
  • 6.6M downloads/mo
  • 36 versions

Description

A pure JavaScript W3C standard-based (XML DOM Level 2 Core) `DOMParser` and `XMLSerializer` module.

Licenses

Declared license

MIT (top-level declared license of xmldom)

Transitive dependency licenses

xmldom declares no runtime dependencies, so its license exposure is limited to its own MIT license.

This view is derived from declared package metadata, and a full FOSSA scan detects licenses that declared metadata misses. Scan free.

License and vulnerability information on this page is derived from public package metadata and public advisory databases. It is not legal advice, and it reflects the top-level declared license only. Verify the license and terms of any software for your own needs.

Need xmldom approved? Get the full license and vulnerability report for your codebase. Scan free.

Scan free

Vulnerabilities

CVE-linked advisories
Affected rangeCVECWECVSSEPSS
<=0.6.0CVE-2022-39353CWE-1288, CWE-209.8 Critical severity advisories0.01272
<=0.6.0CVE-2026-34601CWE-917.5 High severity advisories0.00536
<=0.6.0CVE-2021-32796CWE-1166.5 Medium severity advisories0.01358
<=0.6.0CVE-2026-41673CWE-6740.00882
<=0.6.0CVE-2026-41674CWE-910.00650
<=0.6.0CVE-2026-41672CWE-910.00650
<=0.6.0CVE-2026-41675CWE-910.00633
<=0.6.0CVE-2026-83611CWE-12860.00619
<=0.6.0CVE-2026-83608CWE-910.00612
<=0.6.0CVE-2026-83605CWE-910.00612
<=0.6.0CVE-2026-83616CWE-910.00612
<=0.6.0CVE-2026-83607CWE-910.00612
<=0.6.0CVE-2026-83613CWE-4070.00604
<=0.6.0CVE-2026-83610CWE-1160.00590
>=0.3.0 <=0.6.0CVE-2026-83614CWE-400, CWE-4070.00590
>=0.1.5 <=0.6.0CVE-2026-83615CWE-7700.00590

Version history

Published versions
VersionPublishedLicense
0.6.0Apr 2021MIT
0.5.0Mar 2021
0.4.0YankedOct 2020
0.3.0YankedMar 2020
0.2.1YankedDec 2019
0.2.0YankedDec 2019
0.1.31YankedDec 2019
0.1.30YankedDec 2019
0.1.29YankedDec 2019
0.1.27YankedNov 2016
0.1.26YankedNov 2016
0.1.25YankedNov 2016
0.1.24YankedNov 2016
0.1.22YankedJan 2016
0.1.21YankedJan 2016
0.1.20YankedJan 2016
0.1.19YankedJan 2014
0.1.18YankedJan 2014
0.1.17YankedDec 2013
0.1.16YankedMay 2013
0.1.15YankedApr 2013
0.1.14YankedMar 2013
0.1.13YankedOct 2012
0.1.12YankedSep 2012
0.1.11YankedJun 2012
11 older releases
Older published versions
VersionPublishedLicense
0.1.10YankedJun 2012
0.1.9YankedJun 2012
0.1.8YankedMay 2012
0.1.7YankedMay 2012
0.1.6YankedMay 2012
0.1.5YankedMay 2012
0.1.4YankedMay 2012
0.1.3YankedMay 2012
0.1.2YankedFeb 2012
0.1.1YankedJan 2012
0.1.0YankedJan 2012

npm install xmldom resolves to the 0.x line today. Older major lines may still receive fixes.

Popularity

Downloads last month
6.6M
Known dependents in this corpus
2,004
GitHub stars
469
OpenSSF score
7.6 / 10

FAQ

What is the latest version of xmldom?
The latest version of xmldom is 0.6.0, published April 2021.
What license is xmldom under?
xmldom declares MIT as its top-level declared license.
Does xmldom have known vulnerabilities?
xmldom has 16 known CVE-linked advisories across its published versions; 16 affect the latest version, v0.6.0.
How do I install xmldom?
Install xmldom with npm install xmldom.
How do I generate an SBOM that includes xmldom?
FOSSA's SBOM generator produces SPDX or CycloneDX output for a codebase that includes xmldom. Generate an SPDX or CycloneDX SBOM free.

Dependency graph and package metadata from deps.dev (Google Open Source Insights), used under CC BY 4.0.

Vulnerability data from the Open Source Vulnerability (OSV) database, including the GitHub Advisory Database and the PyPI Advisory Database, used under CC BY 4.0. Only CVE-linked advisories are shown.

EPSS scores from the Exploit Prediction Scoring System, maintained by the EPSS Special Interest Group at FIRST.

Download counts from the npm public registry API.

Repository stars from the GitHub API.

OpenSSF Scorecard results from deps.dev.

License and vulnerability information on this page is derived from public package metadata and public advisory databases. It is not legal advice, and it reflects the top-level declared license only. Verify the license and terms of any software for your own needs.