danger (npm) has 1 known vulnerability, the worst rated MODERATE. Upgrade to 13.0.8 or later to clear it. No malicious-package signal is recorded.
55 direct dependencies
15 carry known advisories, worst CRITICAL
0 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, 66th percentile of all CVEs
CyberXYZ composite out of 10
fig. 01 — GHSA-3x93-p86w-5jvh, the advisory selected below
A vulnerability was identified in danger danger-js up to 13.0.7.
Full advisory text at GitHub advisory or NVD.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
CyberXYZ does not call a package safe in absolute terms. It records 1 known vulnerability for danger (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 danger (npm), the worst rated MODERATE. They are GHSA-3x93-p86w-5jvh.
13.0.8 or later clears every advisory recorded for danger (npm). Check the release you pick before installing it.
Search danger in CyberXYZ Check at https://cyberxyz.io/check?q=danger. The xyz Scanner checks a project's dependencies, and CyberXYZ Proxy checks each package as it is installed.
Checked 2026-11-14 at 06:19 UTC. The most recent advisory here was published 2026-07-23. Updated continuously from NVD, GHSA, OSV and CNA feeds.