Skip to content
MLReps

Setup

Set up MLReps

Two ways in, and the same dashboard at the end of both: your architecture, what a change would touch, what is slow, and what is exposed. Pick one — you can add the other later.

What you get· an example repository, not yours
acme/storefrontapp/checkout/page.tsxapp/cart/page.tsxapp/api/checkout/route.tsapp/api/orders/route.tslib/orders/OrderService.tslib/pricing/PriceRules.tslib/invoice.tsprisma/schema.prismaREADSSCREENSAPISERVER CODEDATAcheckoutcart/api/checkout/api/ordersOrderService.tsPriceRules.tsinvoice.tsordersusersOrderService.ts · a query in a loop
  1. 1 Connect a repository
  2. 2 MLReps reads the code
  3. 3 See how it fits together, and what to fix

Step 1 · your first repository

How do you want to connect?

Compare the ways in — and whether your code leaves your machine
 From your terminal or CIGitHub AppRun it yourself
Does your code leave your machine?No — only the result travelsYes, a read-only copyWhat that copy is, and where it goes
  • We copy the repository to our server and analyse it in a container with no network access.
  • Our copy is deleted from our server when the scan ends. Nothing is removed on your side.
  • Read-only: your repository is never written to or changed.
  • What stays in our database is the result — nodes, edges, findings, counts and the commit.
No — Your source never leaves your machine; the report is uploaded so you can open and share it.
What we end up storingThe same thing either way: nodes, edges, findings, counts and the commit they came from. Never your source, and never trained on.Nothing — there is no account and no key on this one
Who has to approve itYou, for this one repositoryWhoever may install an App on the organisationYou, plus whoever reviews a workflow file
Checks on pull requestsPosted by your CI, with your own tokenPosted by the App, on every pull requestPosted by your CI — and that is the whole path
Time to the first mapAbout two minutes, from your own machineOne push after installingThere is no map on this one
Runtime, measuredA separate, optional step in either. Until it is set, Runtime reads not measured — and shows no numbers rather than zeros.Not possible: there is nothing of yours here to attach it to

Not sure? Take the first. It is the only one where you can see exactly what was sent, in your own scrollback, before anything reaches us.

Not sure yet?

Check a public repository first

No account needed. Paste a public repository and it says, before you install anything, how much of your code each way reads — then opens a demo of its Optimize, Architecture and Findings, scanned for real.

Public repositories only. The check reads GitHub’s language counts and file names; the demo that opens after it scans the public code in our sandbox, and keeps the result for a day.