One extension, two threat models
A .ts file may render in the browser or run with database credentials. Scanners that treat both the same flood you with irrelevant findings.
For JavaScript & TypeScript teams
Corgea classifies every JS and TS file as browser or server code before scanning, so React components get DOM XSS rules and Express routes get injection and authorization analysis, with review-ready fixes in the PR.
+0K scans every month - Trusted by thousands of devs
Pain points
The challenges teams hit before they bring Corgea into their workflow.
A .ts file may render in the browser or run with database credentials. Scanners that treat both the same flood you with irrelevant findings.
IDOR, mass assignment, and skipped authorization are absent lines, not dangerous ones, so grep-style rules never see them.
Next.js server actions, route handlers, and middleware sit next to client components, and secrets slip into bundles through NEXT_PUBLIC_ prefixes.
Hundreds of transitive packages generate advisories that are never reachable, while typosquats and malicious install scripts slip through.
How Corgea helps
Context-aware static analysis for the browser, Node.js, and everything in between.
Framework signatures, imports, and code patterns route each file to the right ruleset: DOM XSS, open redirects, and postMessage abuse for the browser; SQL and command injection, path traversal, SSRF, and auth bypass for the server.
Corgea understands what a route is supposed to do, so it flags the missing ownership check and the unsafe merge, not just the dangerous innerHTML.
Every finding ships with a review-ready fix and a plain-English explanation, delivered in the pull request, the IDE, or through MCP to your coding agent.
Start scanning free or book a demo to see how findings and fixes show up in your existing workflow.
Outcomes
FAQ
Short answers built for search visibility and faster evaluation.
Corgea scans JavaScript and TypeScript across React, Next.js, Angular, Vue, Express, Fastify, NestJS, and plain Node.js, and supports more than 20 languages and frameworks overall.
Corgea detects DOM, stored, and reflected XSS, SQL and NoSQL injection, command injection, code injection through eval and template engines, prototype pollution, insecure deserialization, SSRF, path traversal, open redirects, insecure storage, and authorization and business logic flaws such as IDOR and mass assignment.
Yes. Before scanning, Corgea classifies each file as frontend or backend using framework signatures, import statements, and code patterns, then applies the matching ruleset so browser findings do not show up in server code and vice versa.
Run the Corgea CLI or integration on every pull request to scan the diff, use blocking rules by severity and CWE to gate merges, and schedule full-repository scans for complete coverage. Findings and fixes appear as pull request comments.
More solutions
Every solution page runs on the same shared template so teams get a consistent evaluation experience.
Ready to move
Free, no credit card | First findings in minutes