Connect GitHub
Choose the repositories. Not the account.
Nothing to add to your repository. Install it on the repositories you choose. Every push is scanned for you, and each pull request shows what the change affects.
Step 1 of 2
Sign in to MLReps first
GitHub connects to your MLReps account, so sign in — or create an account, on the same page — and you go straight on to GitHub to install it.
Sign in to continueNothing to add to your repository: no CI changes, no files, no key. MLReps reads your default branch in a sandbox with no network, deletes it afterwards, and re-reads it on every push and pull request. After this, nothing here needs a terminal.
Install it on GitHub
Opens in a new tab. GitHub asks which repositories — start with one; you can add the rest afterwards, and a first scan you can check is worth more than ten you cannot.
Use the button in the box above.What it can access, and what we keepCome back to this tab
Once it is installed, GitHub takes the other tab to your dashboard and the first scan starts on its own — this page notices it too. If GitHub says the App is already installed and sends you nowhere, it has dropped the proof of which account this was for: uninstall it on GitHub, then use the button above again.
What happens to your code in this mode
- On each push, we take a read-only copy of the repository into a container on our server. Your repository is not changed.
- The analysis runs there, with no network access out of it.
- When the scan ends, our copy goes with the container it ran in. Nothing is removed on your side — this never touches your repository.
- No copy of your code reaches our database. What is kept is the result: nodes, edges, findings, counts, and the commit it came from.
If that trade is not one you want to make, the terminal path never moves your code — and gives you the same map.
What the App can write
A check and a comment on pull requests, when you turn that on. It does not push commits, create branches, or change settings.