Skip to content
MLReps
Sign in
Sign in

Public reports

The same analysis, run on code you can already read.

Every report on this page was produced by pointing MLReps at a public repository and publishing what it found — including what it could not read. They are here so you can judge the output on a project you already know, rather than on a demo we chose ourselves.

What a report shows, and what it deliberately does not

  • The architecture read out of the code: the lanes, what is in them, and the edges between them — each marked as read or inferred.
  • Performance and architecture findings in full, with the file, the line and why it matters.
  • Security findings as counts only — no file, no line, no detail, no fix. A page naming a weakness in somebody else’s project helps the wrong reader first.
  • How much of the repository could not be read, and which rules did not run at all.
  • None of their code. Not a line of it is stored, quoted or committed here — a report holds paths, line numbers and our own sentences.

Nothing is published yet

No report has been published on this site yet. That is a statement about this page and not about the projects: nothing has been scanned and withheld. When a report is published it appears here with the commit it was produced from.

If you maintain one of these projects

This report was produced by scanning the public repository. Security findings are shown as counts only — no file, no line, no detail. If you maintain this project you can ask us for the detail, or ask for this page to be taken down, and we will do either. Ask us for the detail or ask for a page to be taken down.

How these were produced

Cloned at one commit, scanned with the same engine a customer runs, and published through a narrower projection that has no field for a security detail to travel in.

The whole method, step by step

Read next