The ConfigCommentParser#parseJSONLikeConfig API is vulnerable to a Regular Expression Denial of Service (ReDoS) attack in its only argument.
Full advisory text at GitHub advisory.
npm package report
Is @eslint/plugin-kit safe?
@eslint/plugin-kit (npm) has 2 known vulnerabilities, the worst rated LOW. Upgrade to 0.3.4 or later to clear all of them. No malicious-package signal is recorded.
// reach
0 direct dependencies
none carry a known advisory
Create a free accountfor every dependency path, dependent and what to upgrade
// ai model usage
Tracked for PyPI packages. HuggingFace models declare Python dependencies, so npm packages are not covered.
cvss
2.5
low
severity band, no base score published
epss
not scored
chance of exploitation in 30 days
xyz score
2.0
low
CyberXYZ composite out of 10
fig. 01 — GHSA-xffm-g5w8-qvg7, the advisory selected below
// 2 advisories
Is @eslint/plugin-kit safe to install?
CyberXYZ does not call a package safe in absolute terms. It records 2 known vulnerabilities for @eslint/plugin-kit (npm), the worst rated LOW, and no malicious-package signal. Whether it is acceptable depends on the version you run.
Does @eslint/plugin-kit have known vulnerabilities?
Yes. CyberXYZ records 2 known vulnerabilities for @eslint/plugin-kit (npm), the worst rated LOW. They are GHSA-xffm-g5w8-qvg7, GHSA-7q7g-4xm8-89cq.
Which version of @eslint/plugin-kit should I use?
0.3.4 or later clears every advisory recorded for @eslint/plugin-kit (npm). Check the release you pick before installing it.
How do I check @eslint/plugin-kit before installing?
Search @eslint/plugin-kit in CyberXYZ Check at https://cyberxyz.io/check?q=%40eslint%2Fplugin-kit. The xyz Scanner checks a project's dependencies, and CyberXYZ Proxy checks each package as it is installed.
Checked 2026-11-14 at 07:00 UTC. The most recent advisory here was published 2025-07-18. Updated continuously from NVD, GHSA, OSV and CNA feeds.