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-2021-44906 minimist: prototype pollutionCVE-2022-2421 Insufficient validation when decoding a Socket.IO packetCVE-2020-28502 nodejs-xmlhttprequest: Code injection through user input to xhr.sendCVE-2021-31597 xmlhttprequest-ssl: SSL certificate validation disabled by defaultCVE-2017-20165 A vulnerability classified as problematic has been found in debug-js d ...CVE-2020-36048 yarnpkg-socket.io/engine.io: allows attackers to cause a denial of service (resource consumption) via a POST request to the long polling transportCVE-2022-41940 engine.io: Specially crafted HTTP request can trigger an uncaught exceptionCVE-2020-7598 nodejs-minimist: prototype pollution allows adding or modifying properties of Object.prototype using a constructor or __proto__ payloadCVE-2017-20162 Vercel ms Inefficient Regular Expression Complexity vulnerabilityCVE-2024-36751 parse-uri Regular expression Denial of Service (ReDoS)CVE-2020-28481 CORS misconfiguration in socket.ioCVE-2024-38355 socket.io: Unhandled 'error' eventCVE-2020-36049 yarnpkg-socket.io-parser: a denial of service (memory consumption) via a large packet because a concatenation approach is usedCVE-2026-33151 socket.io: Socket.IO: Denial of Service due to excessive buffering of specially crafted packetsCVE-2026-69185 socket.io-parser: Socket.IO: Denial of Service via memory exhaustion from crafted packetsCVE-2023-32695 socket.io parser is a socket.io encoder and decoder written in JavaScr ...CVE-2026-41907 uuid: uuid: Out-of-bounds write vulnerability impacts data integrity and confidentialityCVE-2024-37890 nodejs-ws: denial of service when handling a request with many HTTP headersCVE-2026-48779 ws: ws: Denial of Service via memory exhaustion from small WebSocket fragmentsCVE-2024-47764 cookie: cookie accepts cookie name, path, and domain with out of bounds charactersCVE-2017-16137 nodejs-debug: Regular expression Denial of ServiceYour dependencies cross-checked against the OSV vulnerability database.
GHSA-xvch-5gv4-984h Prototype Pollution in minimistGHSA-qm95-pgcg-qqfq Insufficient validation when decoding a Socket.IO packetGHSA-72mh-269x-7mh5 Improper Certificate Validation in xmlhttprequest-sslGHSA-h4j5-c7cj-74xg xmlhttprequest and xmlhttprequest-ssl vulnerable to Arbitrary Code InjectionGHSA-9vvw-cc9w-f27h debug Inefficient Regular Expression Complexity vulnerabilityGHSA-j4f2-536g-r55m Resource exhaustion in engine.ioGHSA-r7qp-cfhv-p84w Uncaught exception in engine.ioGHSA-vh95-rmgr-6w4m Prototype Pollution in minimistGHSA-w9mr-4mfr-499f Vercel ms Inefficient Regular Expression Complexity vulnerabilityGHSA-6fx8-h7jm-663j parse-uri Regular expression Denial of Service (ReDoS)GHSA-25hc-qcg6-38wj socket.io has an unhandled 'error' eventGHSA-fxwf-4rqh-v8g3 CORS misconfiguration in socket.ioGHSA-2m8v-j782-fhvr Socket.IO: Zero-attachment Memory ExhaustionGHSA-677m-j7p3-52f9 socket.io allows an unbounded number of binary attachmentsGHSA-cqmj-92xf-r6r9 Insufficient validation when decoding a Socket.IO packetGHSA-xfhh-g9f5-x4m4 Resource exhaustion in socket.io-parserGHSA-w5hq-g745-h8pq uuid: Missing buffer bounds check in v3/v5/v6 when buf is providedGHSA-3h5v-q93c-6h6q ws affected by a DoS when handling a request with many HTTP headersGHSA-96hv-2xvq-fx4p ws: Memory exhaustion DoS from tiny fragments and data chunksGHSA-pxg6-pf52-xh8x cookie accepts cookie name, path, and domain with out of bounds charactersGHSA-gxpj-cx7g-858c Regular Expression Denial of Service in debugCode that can be exploited: injection, hardcoded credentials and similar.
Nothing found by this check. ✓
Packages that look intentionally malicious: typosquats, sneaky install scripts.
guarddog-npm-npm-install-script npm-install-script match in tldjs 2.3.2guarddog-npm-shady-links shady-links match in tldjs 2.3.2A 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.