lockfile-lint-api (npm) has 1 known vulnerability, the worst rated MODERATE. Upgrade to 5.9.2 or later to clear it. No malicious-package signal is recorded.
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; GitHub rates it MODERATE
chance of exploitation in 30 days, 39th percentile of all CVEs
CyberXYZ composite out of 10
fig. 01 — GHSA-7cfr-5cjf-32p4, the advisory selected below
Versions of the package lockfile-lint-api before 5.9.2 are vulnerable to Incorrect Behavior Order: Early Validation via the resolved attribute of the package…
Full advisory text at GitHub advisory or NVD.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L
CyberXYZ does not call a package safe in absolute terms. It records 1 known vulnerability for lockfile-lint-api (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 lockfile-lint-api (npm), the worst rated MODERATE. They are GHSA-7cfr-5cjf-32p4.
5.9.2 or later clears every advisory recorded for lockfile-lint-api (npm). Check the release you pick before installing it.
Search lockfile-lint-api in CyberXYZ Check at https://cyberxyz.io/check?q=lockfile-lint-api. The xyz Scanner checks a project's dependencies, and CyberXYZ Proxy checks each package as it is installed.
Checked 2026-11-14 at 10:45 UTC. The most recent advisory here was published 2025-05-16. Updated continuously from NVD, GHSA, OSV and CNA feeds.