npm-registry-fetch (npm) has 1 known vulnerability, the worst rated MODERATE. Upgrade to 4.0.5 or later to clear it. No malicious-package signal is recorded.
0 direct dependencies
none carry a known advisory
6 packages depend on it
an advisory here reaches each of them
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
CyberXYZ composite out of 10
fig. 01 — GHSA-jmqm-f2gx-4fjv, the advisory selected below
Affected versions of npm-registry-fetch are vulnerable to an information exposure vulnerability through log files.
Full advisory text at GitHub advisory.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
CyberXYZ does not call a package safe in absolute terms. It records 1 known vulnerability for npm-registry-fetch (npm), the worst rated MODERATE, and no malicious-package signal. Whether it is acceptable depends on the version you run.
Yes. CyberXYZ records 1 known vulnerability for npm-registry-fetch (npm), the worst rated MODERATE. They are GHSA-jmqm-f2gx-4fjv.
4.0.5 or later clears every advisory recorded for npm-registry-fetch (npm). Check the release you pick before installing it.
Search npm-registry-fetch in CyberXYZ Check at https://cyberxyz.io/check?q=npm-registry-fetch. The xyz Scanner checks a project's dependencies, and CyberXYZ Proxy checks each package as it is installed.
Checked 2026-11-14 at 11:50 UTC. The most recent advisory here was published 2020-07-07. Updated continuously from NVD, GHSA, OSV and CNA feeds.