static-eval (npm) has 3 known vulnerabilities, the worst rated CRITICAL. No single fixed version is recorded that clears every advisory, so check each one below. No malicious-package signal is recorded.
0 direct dependencies
none carry a known advisory
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
CyberXYZ composite out of 10
fig. 01 — GHSA-8v27-2fg9-7h62, the advisory selected below
All versions of package static-eval are vulnerable to Arbitrary Code Execution using FunctionExpressions and TemplateLiterals.
Full advisory text at GitHub advisory or NVD.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CyberXYZ does not call a package safe in absolute terms. It records 3 known vulnerabilities for static-eval (npm), the worst rated CRITICAL, and no malicious-package signal. Whether it is acceptable depends on the version you run.
Yes. CyberXYZ records 3 known vulnerabilities for static-eval (npm), the worst rated CRITICAL. They are GHSA-8v27-2fg9-7h62, GHSA-x9hc-rw35-f44h, GHSA-5mjw-6jrh-hvfq.
Search static-eval in CyberXYZ Check at https://cyberxyz.io/check?q=static-eval. The xyz Scanner checks a project's dependencies, and CyberXYZ Proxy checks each package as it is installed.
Checked 2026-11-14 at 12:01 UTC. The most recent advisory here was published 2021-05-06. Updated continuously from NVD, GHSA, OSV and CNA feeds.