Your agent writes it. MLReps checks it.
MLReps reads your whole repository, draws every route from the open internet to your data, and checks every pull request against main before you merge.
An example, not a measurement — this repository is made up.
See a real report. No account needed.
Six open-source projects, read at a pinned commit on 8 November 2026. These are the engine’s own recorded answers — the figures npm run golden holds it to on every release.
No report has been published on this deployment yet, so the numbers above are the measurement and not a page you can open. They are the same figures a published report would carry.
One command on your machine. Or three clicks on GitHub.
npm install -g mlrepsnpx mlreps@latest scan .pnpm add -g mlrepsyarn global add mlrepsMerge like you read every line.
MLReps posts a check on every pull request, compared against main. Only what this pull request changes counts.
An example, not a measurement — this repository is made up.
An example, not a measurement — this repository is made up.
A report, not a dashboard.
One page per audit, in plain words first and file:line second. Send the link to your team or a client.
Find the slow parts before your users do.
For the code that works but costs you: queries inside loops, N+1 queries and heavy files — each with the line to change.
An example, not a measurement — this repository is made up.
An example, not a measurement — this repository is made up.
Every way in, in order.
The loopholes someone could use: an upload route that writes anywhere, credentials left in code, calls to functions that are gone.
One map behind every check, report and finding.
You see it the first time, and again when something breaks and you go looking.
An example, not a measurement — this repository is made up.
Run on 6 open-source repositories.
Pinned commits, recorded 8 November 2026. These are the engine’s recorded answers, held on every release by npm run golden.
Why one of them reads 44%. Fastify wires itself up at runtime through plugins and decorators, which a reader that follows code rather than running it cannot trace. That is a limit of ours, not a verdict on their code — and it is on this page because a repository we read badly is the one you most need to see before you trust the others.
Per repository. Never per developer.
Add the eleventh developer and the bill is the same.
CodeRabbit’s published plans, billed annually — their pricing page, read 17 November 2026. How we compare.
- Audits the default branch of the repositories you pick
- A check on every pull request, against main
- Audit report, optimization report, findings and the map — no separate report fee
- Runs on our worker inside a sandbox with no network, and the checkout is deleted when the analysis ends
- Your source never leaves your machine; the report is uploaded so you can open and share it.
- The scan and its findings in your terminal are free, every time, on every repository
- Publishing a report is what costs — the same commit published again costs nothing
- Unchanged code
- The local scan
- An audit we could not do
- A repository already audited today
- Anything that failed on our side
We read your code. We don’t keep it.
Your source code is never stored.
No column exists that can hold source, a diff, a patch or a token — retaining one would take a database migration, and a build gate fails any log call that could receive source. On the command-line path your code never leaves your machine at all. On the GitHub App path it is unpacked onto an analysis worker, read inside a sandbox with no network, and deleted when that one analysis ends.
Nothing about your code is sent to an AI model — not your source, and not metadata about it.
No file path, no line number, no operation name, no count and no finding of ours leaves for a model, and no model writes a word you read. Three things make that so rather than one: the one screen that sent a model anything no longer does, no model key is configured in the service at all, and a build gate counts every place in the code that could reach one. If we ever turn on the assistant that would send a question and its evidence to be worded, /security says what that sends and this page will say it before it happens.
- Repository names — Until you uninstall, which removes them at once.
- Findings and the architecture map — Until you ask us to delete it. Uninstalling the App does not erase it — see below.
- Your account — Until the account is deleted.
- A payment reference, if you pay — For as long as the balance exists. The ledger is append-only, so a credit is never edited or removed — a correction is another entry beside it.
One organisation can never read another's data.
The one write is for posting the check on your pull request, and nothing else.
There are things that are not true yet — uninstalling does not erase your history, there is no self-serve delete or export, and operator access is not yet mechanically blocked. /security says all of it, including what we have not built.
The reason to believe the numbers is the ones it will not print.
A score it did not measure.
No index, no score and no debt figure is printed anywhere — not a number on a scale, not a ranking, not an estimate in hours. What you get is counts, what was read, and what a change reaches.
A map of a codebase it could not read.
Below 70% resolution no picture is drawn at all; between 70 and 90 it is drawn with its gaps named.
That a change is safe.
An empty blast radius means we found nothing, never that nothing is affected.
Anything about a person.
No per-developer score, no leaderboard, and no column anywhere for who dismissed a finding.