chrono-node (npm) has 1 known vulnerability, the worst rated HIGH. Upgrade to 2.2.4 or later to clear it. No malicious-package signal is recorded.
0 direct dependencies
none carry a known advisory
13 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, 81st percentile of all CVEs
CyberXYZ composite out of 10
fig. 01 — GHSA-hpmr-g4pq-jhgp, the advisory selected below
This affects the package chrono-node before 2.2.4.
Full advisory text at GitHub advisory or NVD.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CyberXYZ does not call a package safe in absolute terms. It records 1 known vulnerability for chrono-node (npm), the worst rated HIGH, and no malicious-package signal. Whether it is acceptable depends on the version you run.
Yes. CyberXYZ records 1 known vulnerability for chrono-node (npm), the worst rated HIGH. They are GHSA-hpmr-g4pq-jhgp.
2.2.4 or later clears every advisory recorded for chrono-node (npm). Check the release you pick before installing it.
Search chrono-node in CyberXYZ Check at https://cyberxyz.io/check?q=chrono-node. The xyz Scanner checks a project's dependencies, and CyberXYZ Proxy checks each package as it is installed.
Checked 2026-11-14 at 07:04 UTC. The most recent advisory here was published 2021-05-06. Updated continuously from NVD, GHSA, OSV and CNA feeds.