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-2018-3750 nodejs-deep-extend: Prototype pollution can allow attackers to modify object propertiesCVE-2017-16151 Chromium Remote Code Execution in electronCVE-2019-5786 chromium-browser: Use-after-free in FileReaderCVE-2025-7783 form-data: Unsafe random function in form-dataCVE-2023-45311 Code injection in fseventsCVE-2021-3918 nodejs-json-schema: Prototype pollution vulnerabilityCVE-2019-10744 nodejs-lodash: prototype pollution in defaultsDeep function leading to modifying propertiesCVE-2019-10744 nodejs-lodash: prototype pollution in defaultsDeep function leading to modifying propertiesCVE-2021-44906 minimist: prototype pollutionCVE-2021-44906 minimist: prototype pollutionCVE-2026-59873 tar: node-tar: Denial of Service via crafted gzip bombCVE-2020-15366 nodejs-ajv: prototype pollution via crafted JSON schema in ajv.validate functionCVE-2025-69873 ajv: ReDoS via $data referenceCVE-2017-18077 nodejs-brace-expansion: Regular expression denial of serviceCVE-2026-13149 brace-expansion: Brace-expansion: Denial of Service due to exponential-time complexityCVE-2026-14257 brace-expansion: Brace-expansion: Denial of Service via memory exhaustion in expand() functionCVE-2026-69152 brace-expansion: brace-expansion: Denial of Service via unbounded intermediate arraysCVE-2026-33750 brace-expansion: brace-expansion: Denial of Service via zero step value in brace patternNSWG-ECO-338 ReDoSGHSA-g74r-ffvr-5q9f Memory Exposure in concat-streamNSWG-ECO-392 Memory ExposureCVE-2017-20165 A vulnerability classified as problematic has been found in debug-js d ...CVE-2017-20165 A vulnerability classified as problematic has been found in debug-js d ...CVE-2017-12581 Electron vulnerable to remote command executionCVE-2018-1000006 Remote Code Execution in electronYour dependencies cross-checked against the OSV vulnerability database.
GHSA-67hx-6x53-jw92 Babel vulnerable to arbitrary code execution when compiling specifically crafted malicious codeGHSA-cpq7-6gpm-g9rc cipher-base is missing type checks, leading to hash rewind and passing on crafted dataGHSA-hr2v-3952-633q Prototype Pollution in deep-extendGHSA-4w88-rjj3-x7wp Chromium Remote Code Execution in electronGHSA-vjh7-7g9h-fjfh Elliptic's private key extraction in ECDSA upon signing a malformed input (e.g. a string)GHSA-6h5x-7c5m-7cr7 Exposure of Sensitive Information in eventsourceGHSA-fjxv-7rqg-78g4 form-data uses unsafe random function in form-data for choosing boundaryMAL-2025-21003 Malicious code in fs (npm)MAL-2023-462 Malicious code in fsevents (npm)GHSA-8r6j-v8pm-fqw3 Code injection in fseventsGHSA-896r-f27r-55mw json-schema is vulnerable to Prototype PollutionGHSA-76p3-8jx3-jpfq Prototype pollution in webpack loader-utilsGHSA-jf85-cpcp-j695 Prototype Pollution in lodashGHSA-jf85-cpcp-j695 Prototype Pollution in lodashGHSA-jf85-cpcp-j695 Prototype Pollution in lodashGHSA-jf85-cpcp-j695 Prototype Pollution in lodashGHSA-jf85-cpcp-j695 Prototype Pollution in lodashGHSA-xvch-5gv4-984h Prototype Pollution in minimistGHSA-xvch-5gv4-984h Prototype Pollution in minimistGHSA-v62p-rq8g-8h59 pbkdf2 silently disregards Uint8Array input, returning static keysGHSA-4cpg-3vgw-4877 Prototype pollution in Plist before 3.0.5 can cause denial of serviceGHSA-95m3-7q98-8xr5 sha.js is missing type checks leading to hash rewind and passing on crafted dataGHSA-23hp-3jrh-7fpw node-tar: Decompression/parse DoS via unlimited inputGHSA-hgjh-723h-mx2j Authorization Bypass Through User-Controlled Key in url-parseGHSA-pv4c-p2j5-38j4 Open Redirect in url-parseCode 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.