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-2024-4068 braces: fails to limit the number of characters it can handleCVE-2024-4067 micromatch: vulnerable to Regular Expression Denial of ServiceCVE-2026-67213 nanoid (Nano ID) before 5.1.6 contains an infinite loop in the customA ...CVE-2026-67214 nanoid (Nano ID) before 5.1.16 contains an infinite loop in the custom ...CVE-2024-55565 nanoid: nanoid mishandles non-integer valuesCVE-2026-33671 picomatch: Picomatch: Regular Expression Denial of Service via crafted extglob patternsCVE-2026-33672 picomatch: Picomatch: Data integrity compromised via method injection with crafted POSIX bracket expressionsCVE-2026-45623 postcss: PostCSS: Information disclosure and denial of service via crafted CSS inputGHSA-r28c-9q8g-f849 PostCSS: Path Traversal in Previous Source Map Auto-Loading (sourceMappingURL) leads to Arbitrary .map File DisclosureCVE-2023-44270 PostCSS: Improper input validation in PostCSSCVE-2026-41305 postcss: PostCSS: Cross-Site Scripting (XSS) via improper escaping of style closing tagsCVE-2026-69153 postcss: PostCSS: Information disclosure via crafted sourceMappingURLCVE-2026-33532 yaml: yaml: Denial of Service via deeply nested YAML document parsingYour dependencies cross-checked against the OSV vulnerability database.
GHSA-67hx-6x53-jw92 Babel vulnerable to arbitrary code execution when compiling specifically crafted malicious codeGHSA-968p-4wvh-cqc8 Babel has inefficient RegExp complexity in generated code with .replace when transpiling named capturing groupsGHSA-67mh-4wv8-2f99 esbuild enables any website to send any requests to the development server and read the responseGHSA-9c47-m6qq-7p4h Prototype Pollution in JSON5 via Parse MethodGHSA-28wg-ghj8-5hjv nanoid: non-secure generators can loop indefinitely with negative sizeGHSA-2v37-7h3g-55p8 nanoid: custom generators can loop indefinitely when size is zeroGHSA-mwcw-c2x4-8c55 Predictable results in nanoid generation when given non-integer valuesGHSA-6g55-p6wh-862q PostCSS: Arbitrary file read and information disclosure via attacker-controlled sourceMappingURL in CSS commentsGHSA-7fh5-64p2-3v2j PostCSS line return parsing errorGHSA-fxqj-rqcc-2cmp PostCSS: incomplete fix of GHSA-6g55-p6wh-862q — attacker-controlled sourceMappingURL reads arbitrary .map files when `from` is unsetGHSA-qx2v-qp2m-jg93 PostCSS has XSS via Unescaped </style> in its CSS Stringify OutputGHSA-r28c-9q8g-f849 PostCSS: Path Traversal in Previous Source Map Auto-Loading (sourceMappingURL) leads to Arbitrary .map File DisclosureGHSA-gcx4-mw62-g8wm DOM Clobbering Gadget found in rollup bundled scripts that leads to XSSGHSA-mw96-cpmx-2vgc Rollup 4 has Arbitrary File Write via Path TraversalGHSA-c2qf-rxjj-qqgw semver vulnerable to Regular Expression Denial of ServiceGHSA-353f-5xf4-qw67 Vite Server Options (server.fs.deny) can be bypassed using double forward-slash (//)GHSA-356w-63v5-8wf4 Vite has an `server.fs.deny` bypass with an invalid `request-target`GHSA-4r4m-qw57-chr8 Vite has a `server.fs.deny` bypassed for `inline` and `raw` with `?import` queryGHSA-4w7w-66w2-5vf9 Vite Vulnerable to Path Traversal in Optimized Deps `.map` HandlingGHSA-64vr-g452-qvp3 Vite DOM Clobbering gadget found in vite bundled scripts that leads to XSSGHSA-859w-5945-r5v3 Vite's server.fs.deny bypassed with /. for files under project rootGHSA-8jhw-289h-jh2g Vite's `server.fs.deny` did not deny requests for patterns with directories.GHSA-93m4-6634-74q7 vite allows server.fs.deny bypass via backslash on WindowsGHSA-9cwx-2883-4wfx Vite's `server.fs.deny` is bypassed when using `?import&raw`GHSA-c24v-8rfc-w8vw Vite dev server option `server.fs.deny` can be bypassed when hosted on case-insensitive filesystemCode that can be exploited: injection, hardcoded credentials and similar.
Nothing found by this check. ✓
Packages that look intentionally malicious: typosquats, sneaky install scripts.
Nothing found by this check. ✓
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.