Skip to content
MLReps

Welcome back

Pick up where your
system left off.

Nothing has been running in the background and nothing has been watching your code. Your last scan is exactly where you left it, with the date it was taken printed on it.

  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.

Sign in

We will take you back to the last repository you were reading.

Next: connect GitHub

Sign in to MLReps here — or create an account. Right after, we take you to GitHub, where you sign in with your GitHub account and choose the repositories. Your GitHub password is only ever typed on GitHub.

Forgotten your password?

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.