ng-packagr (npm) has 1 known vulnerability, the worst rated MODERATE. Upgrade to 10.1.1 or later to clear it. No malicious-package signal is recorded.
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, 84th percentile of all CVEs
CyberXYZ composite out of 10
fig. 01 â GHSA-qm28-7hqv-wg5j, the advisory selected below
The package ng-packagr before 10.1.1 are vulnerable to Command Injection via the styleIncludePaths option.
Full advisory text at GitHub advisory or NVD.
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H
CyberXYZ does not call a package safe in absolute terms. It records 1 known vulnerability for ng-packagr (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 ng-packagr (npm), the worst rated MODERATE. They are GHSA-qm28-7hqv-wg5j.
10.1.1 or later clears every advisory recorded for ng-packagr (npm). Check the release you pick before installing it.
Search ng-packagr in CyberXYZ Check at https://cyberxyz.io/check?q=ng-packagr. The xyz Scanner checks a project's dependencies, and CyberXYZ Proxy checks each package as it is installed.
Checked 2026-11-14 at 12:04 UTC. The most recent advisory here was published 2021-05-07. Updated continuously from NVD, GHSA, OSV and CNA feeds.