Informational scan, not a security audit. How this is computed.
API keys, passwords or tokens committed into the repo.
This check didn’t finish — that’s not the same as “clean.” Try Check again above.
Packages you depend on that have known security holes (CVEs).
CVE-2025-7783 form-data: Unsafe random function in form-dataCVE-2025-55182 next: React Server Components: Pre-authentication remote code execution via unsafe deserializationCVE-2026-41242 protobufjs: protobufjs: Arbitrary code execution via injected protobuf definition type fieldsCVE-2026-44288 protobufjs: protobufjs: Security control bypass due to improper handling of overlong UTF-8 sequencesCVE-2026-12143 form-data: form-data: Form field override via CRLF injectionCVE-2026-4800 lodash: lodash: Arbitrary code execution via untrusted input in template importsCVE-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-2025-66400 mdast-util-to-hast: mdast-util-to-hast: Markdown code elements can appear as regular page contentCVE-2026-44573 next.js: Next.js: Information disclosure due to middleware bypass in Pages Router with i18nCVE-2026-44575 next.js: Next.js: Unauthorized access to protected content via middleware bypassCVE-2026-44578 Next.js: Next.js: Server-Side Request Forgery via crafted WebSocket upgrade requestsCVE-2026-44579 next.js: Next.js: Denial of Service via crafted POST requests to server actionsCVE-2026-45109 next.js: Next.js: Information disclosure via security fix bypass in middleware with TurbopackCVE-2026-64641 next: Next.js: Denial of Service via crafted requests to App Router with Server ActionsCVE-2026-64645 next: Next.js: Server-Side Request Forgery vulnerabilityCVE-2026-64649 next: Next.js: Server-Side Request Forgery via malicious host redirection in Server ActionsGHSA-8h8q-6873-q5fj Next.js Vulnerable to Denial of Service with Server ComponentsGHSA-h25m-26qc-wcjf Next.js HTTP request deserialization can lead to DoS when using insecure React Server ComponentsGHSA-mwv6-3258-q52c Next Vulnerable to Denial of Service with Server ComponentsGHSA-q4gf-8mx6-v5v3 Next.js has a Denial of Service with Server ComponentsCVE-2025-55173 nextjs: Next.js Content Injection Vulnerability for Image OptimizationCVE-2025-57752 nextjs: Next.js Affected by Cache Key Confusion for Image Optimization API RoutesCVE-2025-57822 Next.js Improper Middleware Redirect Handling Leads to SSRFCVE-2025-59471 next: NextJS Denial of Service in Image OptimizerYour dependencies cross-checked against the OSV vulnerability database.
GHSA-fjxv-7rqg-78g4 form-data uses unsafe random function in form-data for choosing boundaryGHSA-9qr9-h5gf-34mp Next.js is vulnerable to RCE in React flight protocolGHSA-xq3m-2v4x-88gg Arbitrary code execution in protobufjsGHSA-q6x5-8v7m-xcrf protobufjs has overlong UTF-8 decodingGHSA-2g4f-4pwh-qvx6 ajv has ReDoS when using `$data` optionGHSA-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-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-25h7-pfq9-p65f flatted vulnerable to unbounded recursion DoS in parse() revive phaseGHSA-rf6f-7fwh-wjgh Prototype Pollution via parse() in NodeJS flattedGHSA-hmw2-7cc7-3qxx form-data: CRLF injection in form-data via unescaped multipart field names and filenamesGHSA-52cp-r559-cp3m js-yaml: YAML merge-key chains can force quadratic CPU consumptionGHSA-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-f23m-r3pf-42rh lodash vulnerable to Prototype Pollution via array path bypass in `_.unset` and `_.omit`GHSA-r5fr-rjxr-66jc lodash vulnerable to Code Injection via `_.template` imports key namesGHSA-4fh9-h7wg-q85m mdast-util-to-hast has unsanitized class attributeGHSA-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 patternGHSA-7r86-cg39-jmmj minimatch has ReDoS: matchOne() combinatorial backtracking via multiple non-adjacent GLOBSTAR segmentsCode 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.