merge (npm) has 2 known vulnerabilities, the worst rated HIGH. Upgrade to 2.1.1 or later to clear all of them. No malicious-package signal is recorded.
0 direct dependencies
none carry a known advisory
Tracked for PyPI packages. HuggingFace models declare Python dependencies, so npm packages are not covered.
CVSS v3.1 base score out of 10
chance of exploitation in 30 days, 74th percentile of all CVEs
CyberXYZ composite out of 10
fig. 01 — GHSA-7wpw-2hjm-89gp, the advisory selected below
All versions of package merge <2.1.1 are vulnerable to Prototype Pollution via recursiveMerge .
Full advisory text at GitHub advisory or NVD.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
CyberXYZ does not call a package safe in absolute terms. It records 2 known vulnerabilities for merge (npm), the worst rated HIGH, and no malicious-package signal. Whether it is acceptable depends on the version you run.
Yes. CyberXYZ records 2 known vulnerabilities for merge (npm), the worst rated HIGH. They are GHSA-7wpw-2hjm-89gp, GHSA-f9cm-qmx5-m98h.
2.1.1 or later clears every advisory recorded for merge (npm). Check the release you pick before installing it.
Search merge in CyberXYZ Check at https://cyberxyz.io/check?q=merge. The xyz Scanner checks a project's dependencies, and CyberXYZ Proxy checks each package as it is installed.
Checked 2026-11-14 at 09:17 UTC. The most recent advisory here was published 2021-05-04. Updated continuously from NVD, GHSA, OSV and CNA feeds.