nuget package report

Is npm-registry-fetch safe?

1 known vulnerability.

cvss
not scored

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

UNKNOWN

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
>=0, <4.0.5, >=5.0.0, <8.1.1
Fixed in
not stated
Weakness
CWE-352
Published
2020-07-07
Source
osv

OSV


// ai model usage

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


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

Think a verdict here is wrong? Tell us — we respond within 2 business days.
Is npm-registry-fetch safe? nuget package security report | CyberXYZ