Informational scan, not a security audit. How this is computed.
API keys, passwords or tokens committed into the repo.
Nothing found by this check. ✓
Packages you depend on that have known security holes (CVEs).
CVE-2023-45311 Code injection in fseventsCVE-2019-10747 nodejs-set-value: prototype pollution in function set-valueCVE-2019-10747 nodejs-set-value: prototype pollution in function set-valueCVE-2026-59873 tar: node-tar: Denial of Service via crafted gzip bombCVE-2024-4068 braces: fails to limit the number of characters it can handleCVE-2024-4068 braces: fails to limit the number of characters it can handleCVE-2022-38900 decode-uri-component: improper input validation resulting in DoSCVE-2020-7788 nodejs-ini: Prototype pollution via malicious INI fileCVE-2019-20149 nodejs-kind-of: ctorName in index.js allows external user input to overwrite certain internal attributesCVE-2024-4067 micromatch: vulnerable to Regular Expression Denial of ServiceCVE-2024-4067 micromatch: vulnerable to Regular Expression Denial of ServiceCVE-2021-23440 nodejs-set-value: type confusion allows bypass of CVE-2019-10747CVE-2021-23440 nodejs-set-value: type confusion allows bypass of CVE-2019-10747CVE-2021-32803 nodejs-tar: Insufficient symlink protection allowing arbitrary file creation and overwriteCVE-2021-32804 nodejs-tar: Insufficient absolute path sanitization allowing arbitrary file creation and overwriteCVE-2021-37701 nodejs-tar: Insufficient symlink protection due to directory cache poisoning using symbolic links allowing arbitrary file creation and overwriteCVE-2021-37712 nodejs-tar: Insufficient symlink protection due to directory cache poisoning using symbolic links allowing arbitrary file creation and overwriteCVE-2021-37713 nodejs-tar: Arbitrary File Creation/Overwrite on Windows via insufficient relative path sanitizationCVE-2026-23745 node-tar: tar: node-tar: Arbitrary file overwrite and symlink poisoning via unsanitized linkpaths in archivesCVE-2026-23950 node-tar: tar: node-tar: Arbitrary file overwrite via Unicode path collision race conditionCVE-2026-24842 node-tar: tar: node-tar: Arbitrary file creation via path traversal bypass in hardlink security checkCVE-2026-26960 node-tar: node-tar: Arbitrary file read/write via malicious archive hardlink creationCVE-2026-29786 node-tar: hardlink path traversal via drive-relative linkpathCVE-2026-31802 tar: tar: File overwrite via drive-relative symlink traversalCVE-2026-59874 tar: Node-tar: Denial of Service via malformed tar archive headerYour dependencies cross-checked against the OSV vulnerability database.
GHSA-67hx-6x53-jw92 Babel vulnerable to arbitrary code execution when compiling specifically crafted malicious codeMAL-2023-462 Malicious code in fsevents (npm)GHSA-8r6j-v8pm-fqw3 Code injection in fseventsGHSA-xvch-5gv4-984h Prototype Pollution in minimistGHSA-xvch-5gv4-984h Prototype Pollution in minimistGHSA-xvch-5gv4-984h Prototype Pollution in minimistGHSA-4g88-fppr-53pp Prototype Pollution in set-valueGHSA-4g88-fppr-53pp Prototype Pollution in set-valueGHSA-23hp-3jrh-7fpw node-tar: Decompression/parse DoS via unlimited inputGHSA-2g4f-4pwh-qvx6 ajv has ReDoS when using `$data` optionGHSA-v88g-cgmw-v5xw Prototype Pollution in AjvGHSA-93q8-gq69-wqmw Inefficient Regular Expression Complexity in chalk/ansi-regexGHSA-3jxr-9vmj-r5cp brace-expansion: DoS via exponential-time expansion of consecutive non-expanding {} groupsGHSA-f886-m6hf-6m8v brace-expansion: Zero-step sequence causes process hang and memory exhaustionGHSA-mh99-v99m-4gvg brace-expansion: DoS via unbounded expansion length causing an out-of-memory process crashGHSA-rgw5-rvv9-x895 brace-expansion: DoS via unbounded intermediate arrays, bypassing the CVE-2026-14257 mitigationGHSA-grv7-fg5c-xmjg Uncontrolled resource consumption in bracesGHSA-grv7-fg5c-xmjg Uncontrolled resource consumption in bracesGHSA-3xgq-45jj-v275 Regular Expression Denial of Service (ReDoS) in cross-spawnGHSA-w573-4hg7-7wgq decode-uri-component vulnerable to Denial of Service (DoS)GHSA-qqgx-2p2h-9c37 ini before 1.3.6 vulnerable to Prototype Pollution via ini.parseGHSA-52cp-r559-cp3m js-yaml: YAML merge-key chains can force quadratic CPU consumptionGHSA-5p4m-2wfm-xmqj JS-YAML: Quadratic CPU consumption in !!omap resolution (3.x and 4.x) — CVE-2026-59870 fix not backportedGHSA-h67p-54hq-rp68 JS-YAML: Quadratic-complexity DoS in merge key handling via repeated aliasesGHSA-mh29-5h37-fv8m js-yaml has prototype pollution in merge (<<)Code that can be exploited: injection, hardcoded credentials and similar.
Nothing found by this check. ✓
Packages that look intentionally malicious: typosquats, sneaky install scripts.
This check didn’t finish — that’s not the same as “clean.” Try Check again above.
A signal about how the project is maintained — not a vulnerability in your code. It doesn’t affect the verdict above.
Maintenance & supply-chain hygiene. A signal about the project, not a vulnerability in your code.
This check didn’t finish — that’s not the same as “clean.” Try Check again above.