Free
One person, one machine
Free
- 5 synced reports a day, 15 a week
- 21 days of report retention
- 5 share links per report
Authorized application security testing
Local application security testing for JavaScript, TypeScript and Python, run by the coding agent you already use. No separate model key, and nothing uploaded unless you say so.
npx myrqen@latestThen myrqen auto, or /myrqen auto inside Claude Code.
Recall is 0.250 on holdout-7, which nobody had tuned against; our own gate is 0.90. Burned-corpus figures are holdout-3, after the fixes it prompted. All are the static pass alone, scored one file at a time with no agent involved, so a clean report is not evidence that an application is secure.
One command, and the agent already in your terminal drives the assessment. It reads your project instead of guessing at it, and every step leaves a record you can check.
Your agent maps the project, starts it, and walks every route it can reach. The CLI owns the record of what happened, so the agent cannot promote its own guess.
A finding is settled against your running app: signed in as one user, it asks for another user's record and keeps the response as evidence.
src/server.js:94
- const order = orders.find((candidate) => candidate.id === id);
+ const order = orders.find((candidate) => candidate.id === id && candidate.userId === user.id);Retest replays the same two identities
Each finding carries the change your agent should make and the check that shows it worked. The same probe runs again before anything is marked fixed.
Scored against corpora committed to the repository, including one nobody had tuned the rules against. The method and the raw output are published.
Precision that high means what it reports is worth acting on. Recall that low means it misses more than half of what a thorough human would find, so it belongs next to a review rather than instead of one. Every corpus, the method, and the raw output.
The recorded assessment of vuln-shop, the deliberately vulnerable app committed beside the scanner, including the findings it could not settle.
broken object level authorization
src/server.js:95GET /api/orders/102
Signed in as user_a and requested /api/orders/102, a record listed for user_b. The response was HTTP 200 with a body of 93 bytes.
if (!user) return json(response, 401, { error: "sign in first" });const id = Number(url.pathname.split("/").pop());const order = orders.find((candidate) => candidate.id === id);if (!order) return json(response, 404, { error: "not found" });return json(response, 200, order);4 destructive actions refused. 0 secrets in output.
17 findings9 verified, 5 unsettled6 shown
Claude Code ships /security-review and Codex ships Codex Security. Both read your code well, and if reading it is enough, use them. This is for when you want the finding demonstrated, and a boundary on what the agent may touch while it does.
Reading the code
Reasoned about from the source. Useful, and not the same as proven.
Myrqen
Exercised against your running application under two identities and an admin.
Reading the code
Confidence expressed in prose.
Myrqen
A verification state the CLI owns, so an agent cannot promote its own finding.
Reading the code
Not needed. It touches nothing.
Myrqen
Exact-origin grants, a refusal list higher effort cannot relax, and quarantine for origins your project text proposed.
Reading the code
None published.
Myrqen
Recall 0.250 on a held-out corpus, and 0.500 on an earlier one after the fixes it prompted, against a 0.90 gate. Precision 1.000 on that earlier corpus. The static pass alone, scored one file at a time with no agent involved.
Reading the code
Tied to the agent that ships it.
Myrqen
One skill bundle, thirteen agents, identical behaviour where slash commands do not exist.
Where it loses, and should: language breadth, dependency analysis, compliance reporting, CI gating, and price against a free feature built into the agent. The comparison in full.
Scanning runs on your machine against your own project. Secrets, .env values and raw traffic stay local; what can sync is the report you generated, never your source tree.
There is no Myrqen model key, and no prompt of yours reaches a model we operate.
Per scan, never by default, and never the source tree.
Support cannot read a synced report without a time-boxed grant written to an audit trail.
Destructive actions are refused at every effort level. The recorded run refused 4 and allowed none.
Authorizing api.example.com never authorizes example.com or any sibling host.
The application and the retention worker run in europe-west4.
What is not independently verified about any of this is named on the security page.
One bundle, written in each vendor's own documented format. The invocation does not change: /myrqen auto where slash commands exist, myrqen auto everywhere else.
skillskillskillskillrules filerules filerules filerules filerules fileconventionsinstructionsGEMINI.mdshared fileThe Claude Code workflow · Codex and OpenCode · the exact file written for each
Every finding at every severity is free, local and unlimited. Plans add synced history, sharing and team workspaces.
One person, one machine
Free
Recommended
One engineer who ships often
€19/ month
A team sharing one security picture
€49/ month
Including the two answers that say this is the wrong tool.
One command in the agent you already have open. Free and unlimited to scan, with no account and no card.
npx myrqen@latest