Free pull request risk analyzer
Paste a public GitHub pull request and estimate how much review effort it deserves from its size, spread, sensitive paths, and test signals. No GitHub login required.
Public repositories only. This page requests data from GitHub's public API; no GitHub login is required.
How the pull request risk estimate works
Paste a public GitHub pull request URL to inspect additions, deletions, changed files, repository areas, test-file signals, and sensitive paths such as authentication, migrations, or CI.
The analyzer combines those signals in a transparent planning heuristic. Use the result to split large changes, choose reviewers, and decide what to test before review. It does not tell you whether the code is correct or secure.
For the reasoning behind these signals, read why diff-only code review misses bugs.
Frequently asked questions
- What makes a pull request hard to review?
- Size and spread are the strongest signals. Many changed lines across many repository areas make it harder to keep the whole change in mind. Authentication, migrations, and CI raise the cost of a mistake, while no test-file change removes a useful signal. The analyzer scores those factors.
- Does a high score mean the code has bugs?
- No. The score estimates review effort, not correctness. A clean but wide change can deserve a careful review, while a small change can still hide a serious bug.
- Does the analyzer access my repository?
- It only reads public pull requests through GitHub's unauthenticated API, directly from your browser. No token, no repository access, no storage.
Try Scopy AI on your next pull request
Accurate, open-source AI code reviewer that understands your project. Self-host it or start in the cloud.