JavaScript · TypeScript
A security scanner that tells you what it did not check.
49 rules over your JavaScript and TypeScript source, entry points recognised by 18 framework adapters, and every candidate exercised against your running application before it is called a finding. It runs locally. The coverage it did not reach is printed in the report, not left for you to assume.
npx myrqen@latestWhat makes this different from the other twelve.
Most scanners in this category match patterns and hand you a list. Three things here are not that.
- A candidate is not a finding until something exercised it. The static pass produces candidates. Your coding agent settles each one against the running application, under two identities and an admin. The result is
verified,strong_evidenceorneeds_review, and severity is a separate axis: "how bad if real" and "how sure it is real" are different questions. - The report states its own coverage. Every report ends with what was not assessed, in the engine's own words. Silence from a scanner is not a clean bill of health, and this one says so in writing.
- The miss rate is published. Not the flattering number: the one from the corpus nobody had tuned against. Method, corpora, per-class results, raw output.
Every figure above is the static pass alone, scored one file at a time with no agent involved.
What it can see.
A rule is only useful if the engine can find the entry point it applies to. Without an adapter for a framework's route shape there is no handler to follow anything into, which is why the previous release detected far less. These are the shapes recognised today.
| Surface | Recognised |
|---|---|
| Node | Express, Fastify, Koa-style handlers, raw http servers, tRPC procedures, GraphQL resolvers |
| Full-stack frameworks | Next.js route handlers and server actions, Nest controllers, Nitro, SvelteKit, Astro, Remix, TanStack/Solid |
| Alternative runtimes | Bun.serve, Deno and Deno Fresh, Cloudflare Workers |
| Serverless | Handler-shaped exports across the common providers |
| Other surfaces | Editor-extension commands and message handlers, desktop CLI entry points, realtime and WebSocket handlers |
| Data access recognised as a sink | Raw SQL, prepared statements, Drizzle and Kysely fluent builders, Prisma, key-value and document stores |
Not recognised: any language other than JavaScript, TypeScript and Python (FastAPI and Flask), template languages, configuration files, and infrastructure definitions. Data flow is followed across functions and modules only where a call resolves, up to four calls deep from a recognised handler; a value that travels through an event emitter, a queue or dynamic dispatch is not connected by the engine, and is handed to your agent instead.
What it found, and what it missed.
Per class, on holdout-3, a 68-case corpus scored blind once and since tuned against: 17 of 34 vulnerable cases detected after the fixes it prompted. The misses stay in the table because they are the useful half.
| Class | Detected | Cases, filled when detected |
|---|---|---|
| missing authentication | 0 of 2 | |
| broken function level authorization | 0 of 2 | |
| business logic price manipulation | 0 of 1 | |
| timing unsafe comparison | 0 of 1 | |
| secret exposed to client bundle | 0 of 1 | |
| stored cross site scripting | 0 of 1 | |
| nosql injection | 0 of 1 | |
| mass assignment | 0 of 1 | |
| broken object level authorization | 1 of 5 | |
| race condition double spend | 2 of 3 | |
| path traversal | 2 of 3 | |
| sql injection | 4 of 5 | |
| server side request forgery | 4 of 4 | |
| command injection | 2 of 2 | |
| prototype pollution | 1 of 1 | |
| insecure cors configuration | 1 of 1 |
A class at zero is one this corpus exercised and the engine did not catch. That is fixable work, and until it is done it is a class Myrqen will not find in your code either. The development corpus exercises 38 classes and reports 1.000, which is what a regression gate looks like and says nothing about unseen code.
How you use it.
Reports land in .myrqen/reports/ in the project you scanned, in four formats: self-contained HTML that opens with the network off, JSON, Markdown, and SARIF. They have no expiry, and nothing on our side can remove them.
your terminal
npx myrqen@latest # detects your coding agents, sets them up
npm run dev # start the application you are assessing
/myrqen auto # in Claude Code
myrqen auto # from Codex, OpenCode, or a plain terminalWithout a coding agent the static pass still runs and still writes all four reports. Every candidate simply stays needs_review, because nobody exercised it. The Claude Code workflow · Codex and OpenCode
When to use something else.
Stated here rather than discovered later.
- A codebase written mostly in anything other than JavaScript, TypeScript, or a FastAPI or Flask app. Use a mature SAST product.
- Dependency, licence, or supply-chain inventory. This is not composition analysis.
- A CI gate that must catch everything. At 0.250 recall it would pass code it should not, and a passing gate reads as a guarantee.
- A compliance artefact or an audit report. No third party has audited Myrqen.
- Scanning a deployed production system, or one you do not own. Myrqen exercises the application on your machine and refuses destructive actions, by design.