Informational scan, not a security audit. How this is computed.
API keys, passwords or tokens committed into the repo.
generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive operations.generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive operations.generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive operations.generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive operations.generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive operations.generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive operations.generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive operations.generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive operations.Packages you depend on that have known security holes (CVEs).
CVE-2024-21538 cross-spawn: regular expression denial of serviceCVE-2025-15599 DOMPurify: DOMPurify: Cross-site scriptingCVE-2025-26791 dompurify: Mutation XSS in DOMPurify Due to Improper Template Literal HandlingCVE-2026-0540 DOMPurify: DOMPurify: Cross-site scripting vulnerabilityCVE-2026-41238 DOMPurify: DOMPurify: Cross-Site Scripting bypass via prototype pollutionCVE-2026-41239 DOMPurify: Vue 2: DOMPurify: Cross-site scripting due to incomplete sanitization of template expressionsCVE-2026-41240 DOMPurify: DOMPurify: Cross-Site Scripting (XSS) via inconsistent tag sanitizationCVE-2026-49458 dompurify: DOMPurify: Cross-site scripting due to improper sanitization of DOM nodesCVE-2026-49459 dompurify: DOMPurify: Cross-site scripting bypass allows arbitrary script executionCVE-2026-49978 dompurify: DOMPurify: Cross-site scripting vulnerability allows code executionCVE-2026-65898 DOMPurify before 3.4.11 fails to clone the ALLOWED_ATTR allowlist when ...CVE-2026-65902 DOMPurify before 3.4.7 (affected versions <= 3.4.5) passes direct refe ...CVE-2026-65903 dompurify: DOMPurify: Security bypass allows injection of malicious contentCVE-2026-65912 DOMPurify before 3.3.2 contains a URI validation bypass vulnerability ...CVE-2026-65913 DOMPurify before 3.3.2 contains a prototype pollution vulnerability in ...CVE-2026-65914 DOMPurify before 3.3.2 contains a mutation-XSS vulnerability when sani ...GHSA-55q2-fjhq-7xh7 DOMPurify: IN_PLACE hook removal leaves a detached subtree executable, causing XSSCVE-2025-32014 estree-util-value-to-estree allows prototype pollution in generated ESTreeCVE-2025-32014 estree-util-value-to-estree allows prototype pollution in generated ESTreeCVE-2026-59869 js-yaml: js-yaml: Denial of Service via crafted YAML documentsGHSA-5p4m-2wfm-xmqj JS-YAML: Quadratic CPU consumption in !!omap resolution (3.x and 4.x) — CVE-2026-59870 fix not backportedCVE-2025-64718 js-yaml: js-yaml prototype pollution in mergeCVE-2026-53550 js-yaml: js-yaml: Denial of Service via crafted YAML merge keysCVE-2025-23207 katex: \htmlData does not validate attribute names in KaTeXCVE-2026-4800 lodash: lodash: Arbitrary code execution via untrusted input in template importsYour dependencies cross-checked against the OSV vulnerability database.
GHSA-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-3xgq-45jj-v275 Regular Expression Denial of Service (ReDoS) in cross-spawnGHSA-39q2-94rc-95cp DOMPurify's ADD_TAGS function form bypasses FORBID_TAGS due to short-circuit evaluationGHSA-55q2-fjhq-7xh7 DOMPurify: IN_PLACE hook removal leaves a detached subtree executable, causing XSSGHSA-76mc-f452-cxcm DOMPurify: Hook mutation of `data.allowedTags` / `data.allowedAttributes` permanently pollutes `DEFAULT_ALLOWED_TAGS` / `DEFAULT_ALLOWED_ATTR`GHSA-cj63-jhhr-wcxv DOMPurify USE_PROFILES prototype pollution allows event handlersGHSA-cjmm-f4jc-qw8r DOMPurify ADD_ATTR predicate skips URI validationGHSA-cmwh-pvxp-8882 DOMPurify: Permanent `ALLOWED_ATTR` pollution via `setConfig()` bypassing the hook clone-guard (incomplete fix of the 3.4.7 hook-pollution patch)GHSA-crv5-9vww-q3g8 DOMPurify has a SAFE_FOR_TEMPLATES bypass in RETURN_DOM modeGHSA-h7mw-gpvr-xq4m DOMPurify: FORBID_TAGS bypassed by function-based ADD_TAGS predicate (asymmetry with FORBID_ATTR fix)GHSA-h8r8-wccr-v5f2 DOMPurify is vulnerable to mutation-XSS via Re-Contextualization GHSA-hpcv-96wg-7vj8 DOMPurify: Cross-realm IN_PLACE sanitization leaves executable markup intact via realm-bound `instanceof` checksGHSA-r47g-fvhr-h676 DOMPurify: IN_PLACE mode preserves attributes of a clobbered root element, allowing XSS via attacker-controlled root DOMGHSA-rp9w-3fw7-7cwq DOMPurify IN_PLACE Sanitization Bypass via Attached Shadow Root Inside <template>.contentGHSA-v2wj-7wpq-c8vv DOMPurify contains a Cross-site Scripting vulnerabilityGHSA-v8jm-5vwx-cfxm DOMPurify contains a Cross-site Scripting vulnerabilityGHSA-v9jr-rg53-9pgp DOMPurify: Prototype Pollution to XSS Bypass via CUSTOM_ELEMENT_HANDLING FallbackGHSA-vhxf-7vqr-mrjg DOMPurify allows Cross-site Scripting (XSS)GHSA-f7f6-9jq7-3rqj estree-util-value-to-estree allows prototype pollution in generated ESTreeGHSA-f7f6-9jq7-3rqj estree-util-value-to-estree allows prototype pollution in generated ESTreeGHSA-5j98-mcp5-4vw2 glob CLI: Command injection via -c/--cmd executes matches with shell:trueGHSA-52cp-r559-cp3m js-yaml: YAML merge-key chains can force quadratic CPU consumptionCode 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.