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-2019-10744 nodejs-lodash: prototype pollution in defaultsDeep function leading to modifying propertiesCVE-2021-3807 nodejs-ansi-regex: Regular expression denial of service (ReDoS) matching ANSI escape codesCVE-2018-16487 lodash: Prototype pollution in utilities functionCVE-2020-8203 nodejs-lodash: prototype pollution in zipObjectDeep functionCVE-2021-23337 nodejs-lodash: command injection via templateCVE-2026-4800 lodash: lodash: Arbitrary code execution via untrusted input in template importsCVE-2019-1010266 lodash: uncontrolled resource consumption in Data handler causing denial of serviceCVE-2020-28500 nodejs-lodash: ReDoS via the toNumber, trim and trimEnd functionsCVE-2025-13465 lodash: prototype pollution in _.unset and _.omit functionsCVE-2026-2950 lodash: Lodash: Prototype pollution allows deletion of built-in prototype properties via array path bypassCVE-2026-44705 tmp is a temporary file and directory creator for node.js. Prior to 0. ...CVE-2021-27516 nodejs-urijs: mishandling certain uses of backslash may lead to confidentiality compromiseCVE-2022-1243 Incorrect protocol extraction via \r, \n and \t charactersCVE-2020-26291 urijs: Hostname spoofing via backslashes in URLCVE-2021-3647 URIjs Vulnerable to Hostname spoofing via backslashes in URL CVE-2022-0613 urijs: Authorization Bypass Through User-Controlled KeyCVE-2022-0868 Open Redirect in urijsCVE-2022-1233 URL Confusion When Scheme Not Supplied in medialize/uri.jsCVE-2022-24723 urijs: Leading white space bypasses protocol validationCVE-2018-3721 lodash: Prototype pollution in utilities functionCVE-2025-54798 tmp: tmp Symbolic Link Write VulnerabilityYour dependencies cross-checked against the OSV vulnerability database.
GHSA-jf85-cpcp-j695 Prototype Pollution in lodashGHSA-xvch-5gv4-984h Prototype Pollution in minimistGHSA-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-3xgq-45jj-v275 Regular Expression Denial of Service (ReDoS) in cross-spawnGHSA-43f8-2h32-f4cj Regular Expression Denial of Service in hosted-git-infoGHSA-2pr6-76vf-7546 Denial of Service in js-yamlGHSA-52cp-r559-cp3m js-yaml: YAML merge-key chains can force quadratic CPU consumptionGHSA-8j8c-7jfh-h6hx Code Injection in js-yamlGHSA-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 (<<)GHSA-29mw-wpgm-hmr9 Regular Expression Denial of Service (ReDoS) in lodashGHSA-35jh-r3h4-6jhm Command Injection in lodashGHSA-4xc9-xhrj-v574 Prototype Pollution in lodashGHSA-f23m-r3pf-42rh lodash vulnerable to Prototype Pollution via array path bypass in `_.unset` and `_.omit`GHSA-fvqr-27wr-82fm Prototype Pollution in lodashGHSA-p6mc-m468-83gw Prototype Pollution in lodashGHSA-x5rq-j2xg-h7qm Regular Expression Denial of Service (ReDoS) in lodashGHSA-23c5-xmqv-rm74 minimatch ReDoS: nested *() extglobs generate catastrophically backtracking regular expressionsGHSA-3ppc-4f35-3m26 minimatch has a ReDoS via repeated wildcards with non-matching literal in patternCode 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.