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.
- 1 Connect a repository
- 2 MLReps reads the code
- 3 See how it fits together, and what to fix
Step 1 · your first repository
How do you want to connect?
Choose one to get started. You can add the other later, per repository.
Compare the ways in — and whether your code leaves your machine
| From your terminal or CI | GitHub App | Run it yourself | |
|---|---|---|---|
| Does your code leave your machine? | No — only the result travels | Yes, a read-only copyiWhat that copy is, and where it goes
| No — Your source never leaves your machine; the report is uploaded so you can open and share it. |
| What we end up storing | The 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 it | You, for this one repository | Whoever may install an App on the organisation | You, plus whoever reviews a workflow file |
| Checks on pull requests | Posted by your CI, with your own token | Posted by the App, on every pull request | Posted by your CI — and that is the whole path |
| Time to the first map | About two minutes, from your own machine | One push after installing | There is no map on this one |
| Runtime, measured | A 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.