Skip to content
MLReps

Getting started

Two minutes from here
to a map of your system.

You make an account, run one command inside one project, and come back to the real architecture of that project — drawn from your own code, not from a diagram somebody has to maintain.

  1. Create your account

    No card, no sales call. One repository to begin with — you add more when you want to.

  2. Run one command in that project

    It asks your permission for that repository by name, and nothing else. The scan runs on your machine.

    $npm i -D mlreps && npx mlreps setup

  3. Come back and read it

    Architecture, request paths, slow queries, risks — and an explicit list of what the scan could not see.

Checkout screenROUTE/api/checkoutFILEOrderService.tsFILEpayments.tsTABLEorders
An example of one request path, traced from code. The dashed box is a screen MLReps has not measured yet — it says so rather than guessing.
  • Your code is read on your machine. With the CLI, what travels to us is the result — nodes, edges, findings, counts — not your source.
  • Never used to train anything. Not ours, not anybody else's model.
  • One repository per approval. Every machine and every repository you approve is on one screen, with a Revoke next to it.

Create your account

An account is where your published scans live, so the dashboard has a codebase to show.

No password needed: we send a link to the email above. It works once and expires in 15 minutes.

Creating an account means accepting our Terms and Privacy — both written to be read, and both saying what is not built yet as well as what is.