npm package report

Is npm-registry-fetch safe?

1 known vulnerability, worst severity MODERATE.

cvss

5.0

how bad it is if exploited, out of 10

epss

not scored

chance of exploitation in the next 30 days

xyz score

not scored

CyberXYZ composite, out of 10

fig. 01 — GHSA-jmqm-f2gx-4fjv, the advisory selected below

// advisories

GHSA-jmqm-f2gx-4fjv

MODERATE

Affected versions of npm-registry-fetch are vulnerable to an information exposure vulnerability through log files. The cli supports URLs like <protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>. The password value is not redacted and is printed to stdout and also to any generated log files.

Affected: >= 5.0.0, < 8.1.1, < 4.0.5
Fixed in: 8.1.1
Weakness: CWE-352
Published: 2020-07-07
Source: github

GHSA reference reference reference reference

// dependencies

0 direct

// ai model usage

Tracked for PyPI packages. HuggingFace models declare Python dependencies, so npm packages are not covered.

Checked 2026-09-22 at 00:51 UTC. The most recent advisory here was published 2020-07-07. Updated continuously from NVD, GHSA, OSV and CNA feeds.

Is npm-registry-fetch safe? npm package security report | CyberXYZ