Graph
A structural pass over every source file maps modules, classes, functions and calls. No model involved.
Architecture and security review, checked against the code
Repo Review reads a GitHub repository and tells you how healthy it is: a verdict, seven ratings out of ten, the findings that matter and what to fix first. Every claim is checked against the source, and by default an architect reviews the report before you see it.
Get a free Snapshot How private repositories stay privateRead-only GitHub AppHosted in SydneyReviewed by a person
github.com/acme/booking-api · main
payments/stripe.pyVerdicts, not descriptions, and every one of them traceable to the code
Health Adequate
Each rating carries its weakest point and the reason, with the source lines behind it one click away.
Written from a structural graph of your repository built by real parsers, so every module, function and link a report names is one that exists in your source.
Sound, Adequate, At risk or Critical, and engineering standards, security, configuration, data, resilience, availability and performance, each out of ten with its reasons.
A risk register rated High, Medium and Low, each finding tied to the file and function it is about, and a remediation roadmap in the order to do it.
An architecture document with diagrams generated from the code, an inventory of every outbound call the code makes, and a searchable index of every function and class with its exact source.
Parsers decide what the code contains. Checks hold the writing to it. By default, a person signs it off.
A structural pass over every source file maps modules, classes, functions and calls. No model involved.
Every function gets its start and end line from the language's own parser, never a guess. Anything it cannot range is labelled approximate.
The report is written against the graph, then 20 to 50 automated checks: every named function must exist, every rating must carry its reasons, every link must resolve.
By default, a person reads every report before it is released. You get an email with links when it is.
Start with a free Snapshot. Go to the Full Audit when you want the whole story.
How healthy is it? A quick read with the verdict, the seven ratings and the three findings that matter most. About five minutes, then review.
What is wrong, why, and what do we do about it? The complete assessment and architecture documentation. About an hour, then review.
Prices in Australian dollars, including GST. Very large repositories are quoted before anything runs. Private repositories: see how access works.
Real reports on public open-source projects, released as they were delivered. Open the Snapshot, or the Full Audit's architecture document and symbol index
The Python web framework.
pallets/flask · main · 49943b5
Snapshot and Full Audit
Snapshot (opens in a new tab) · Architecture document (opens in a new tab)
Lets AI agents drive a web browser.
browser-use/browser-use · main · 4b5b1b0
Snapshot and Full Audit
Snapshot (opens in a new tab) · Architecture document (opens in a new tab)
The open-source virtual whiteboard.
excalidraw/excalidraw · master · 82d5847
Snapshot and Full Audit
Snapshot (opens in a new tab) · Architecture document (opens in a new tab)
A framework for teams of AI agents.
crewAIInc/crewAI · main · 2817a95
Snapshot and Full Audit
Snapshot (opens in a new tab) · Architecture document (opens in a new tab)
HTTP networking for Swift.
Alamofire/Alamofire · master · b3e74e8
Snapshot
Read through a GitHub App you control, one repository at a time, never with your password or a long-lived token
On GitHub, choose "Only select repositories" and pick the one to review. It asks for two permissions, both read-only: contents and metadata.
Email support@reporeview.com.au. The key works for that one repository and branch and nothing else, and expires.
Paste the key into the portal and press Start. The report comes back to you by email once it is released, after an architect has reviewed it unless you have agreed otherwise with us.
The app cannot push, open issues, read your organisation or act as any person. It sees only the repositories you selected.
When your run starts, GitHub issues a token for that single repository, valid for at most an hour. It is used for one shallow clone of one branch and deleted straight after.
Uninstall the app, or remove the repository from it, and the next request is refused. You never have to ask us.
It has its own encryption key, only the parts of the service that start runs can use it, never the containers that handle your code, and any other use alerts us at once.
Free sign-up takes public repositories only. A private repository is only ever set up with you directly, so naming it gets a stranger nothing.
Everything runs in our own AWS account in Sydney. Your code is copied once, analysed in a container that is destroyed afterwards, and the copy is deleted the next day, whatever happens to the run.
No production systems, no credentials, no secrets of yours. Nothing is ever committed or pushed to your repository.
The copy of your code after one day, the reports after thirty, or both at once whenever you ask. Retention is enforced by configuration, not by memory.
The analysis can reach only the model and the AWS services that run it, through a filter that logs every connection. During the alpha, your code is read and parsed, never run.
Each key is bound to one repository and branch, stored only as a hash, handed to you once, and expires. Rotate it from the portal whenever you like.
Reports are reached through links that expire after seven days, and the pages are sandboxed so nothing in them can reach your account.
The parts of your code the analysis needs are sent to Anthropic's Claude. Nothing is sent anywhere else.
Every key issued or revoked, every run started, released or deleted, and every link handed out is logged and kept for a year.
Before you ask
Anyone who has to decide about a codebase they did not write: buying a software business, investing in one, inheriting a system, or signing off an agency's or vendor's work. It answers in an hour what otherwise takes weeks of reading or a due-diligence engagement.
Open the portal, enter your email and a public GitHub repository, and we email you a key for one Snapshot of it. Paste the key back into the portal and press Start. One free Snapshot per repository, and three per email address.
Only that you install the read-only Architecture Automation GitHub App on that repository and email support@reporeview.com.au. No password, no personal access token, no deploy key. See how access works. GitLab and Bitbucket are possible too: ask us.
The structure comes from parsers, not the model, and every report has to pass 20 to 50 automated checks against it: every function it names must exist, every rating must carry its reasons, every link must resolve. Then an architect reads it before it is released. And the same code always gets the same scores, so a score that moves means the code changed.
Exact source ranges for JavaScript and TypeScript, Python, PHP, Go, Rust, Java, C#, Ruby, Swift, Terraform and CloudFormation, and Kotlin for most functions. Other languages get the full report with every symbol labelled approximate, never given a guessed body.
A Snapshot runs in about five minutes and a Full Audit in about an hour. Then an architect reviews it, and you get an email with links as soon as it is released.
The copy of your code for one day, the reports for thirty, and a few numbers (your scores, never code) so a rerun of unchanged code scores the same. You can delete a run and everything it left from the portal at any time.