Focused work. Faster feedback.
Verdict analyzes bounded diff chunks and filters generated files and trivial edits before scoring. Review the change, not the whole repository.
Less unnecessary model work keeps reviews focused and affordable.
Verdict Reviews finds the changed files that deserve your attention and explains why, right in GitHub. Get fast feedback, clear risk scores, and verified explanations without a heavyweight review bill.
Paid plans from $4/month. GitHub sign-in. Your team decides what merges.
Start with these two. The other three files look safe to merge.
demo/pr-review/migrations/0020_drop_user_index.sqlrisk 97high risk of a regression; looks unsafe to merge as it stands.
demo/pr-review/src/config/secrets.tsrisk 90a secret or credential appears to be written into the code; high risk of a regression.
| File | Risk | Readiness | Quality |
|---|---|---|---|
0020_drop_user_index.sql | 97 | 2 | 21 |
secrets.ts | 90 | 40 | 38 |
Header.tsx | 10 | 62 | 42 |
Footer.tsx | 9 | 63 | 42 |
README.md | 6 | 97 | 92 |
Speed is useful when the feedback is worth reading. Verdict combines focused scoring, code-side checks, and verified explanations.
Verdict analyzes bounded diff chunks and filters generated files and trivial edits before scoring. Review the change, not the whole repository.
Less unnecessary model work keeps reviews focused and affordable.
JEV scores the change; code combines signals and checks risky patterns. An optional explanation is kept only when JEV confirms the changed lines support it.
Get a reason to look closer, with human judgment still at the center.
Checks, changed-line annotations, and one updated PR comment bring attention to the files that matter. Push a new commit to review the updated change.
No new review ritual. No automatic merge approval.
Plans
Same review engine on every plan. Upgrade for more reviewed lines and API capacity.
Billed monthly per GitHub installation.
For maintainers who want dependable review coverage as their projects grow.
Checking checkout availability…
For busy teams reviewing more code and needing extra monthly headroom.
Checking checkout availability…
Start with your account. Connect repositories when you’re ready.
Continue with GitHub. If you already have a Verdict Reviews account, you’ll return to your existing workspace.
Sign up with GitHubInstall the GitHub app on your account or organization. Choose which repositories it can access.
Install the appActivate your plan in Billing and enable the repository in your dashboard. Open or update a PR to get your first Verdict review.
View your billing optionsSee your recent reviews and choose which repositories to connect. Keep your GitHub connections, review history, and plan details together.
Open your dashboardFrom your first PR to privacy, usage, and the feedback you can expect.
Sign in with GitHub, install Verdict, and choose its repositories. Activate a plan in Billing, enable automatic reviews for a repository in the dashboard, then open or update a PR. Installing the app alone does not enable reviews. Use the GitHub account that installed Verdict to manage the installation; no separate password is needed.
Yes. Install the GitHub App on a personal account or organization and select public or private repositories. Sign-in alone does not grant repository access. An organization owner may need to approve the installation. Each installation has its own plan and allowance, and you can change its repository selection in GitHub.
Verdict analyzes changed code for merge readiness, regression risk, and diff quality. A GitHub Check and updated PR comment show findings and scores: lower risk is safer; higher readiness and quality are better. Automatic reviews skip drafts; an authorized `/verdict` command can review an open draft. PRs over 8,000 changed lines are skipped without charges. Generated or unavailable patches may be unreviewed. Verdict is advisory and does not approve merges or replace tests and human judgment.
Small changes can be reviewed in seconds. In a local six-file demo, scoring, explanations, and the summary took about 4.2 seconds. That excludes GitHub delivery, queue wait, and publication time. Larger diffs, busy queues, provider limits, and retries can take longer; there is no fixed turnaround guarantee.
JEV answers narrow review questions, code combines the scores and applies static rules, and optional AI explanations are checked by JEV against the changed lines before they are kept. Ambiguous findings ask for a human look. These checks reduce unsupported feedback, but automated reviews can still miss issues or be wrong.
Yes. Toggle automatic reviews per repository in the dashboard. You can still comment /verdict on a PR to request a manual review while automation is off. Repository settings choose who can use that command. A new command comment can request a fresh review of the same commit.
Starter is $4/month and Pro is $20/month, billed per GitHub App installation. Both use the same review engine with different allowances. Manage cancellation and invoices in Billing’s customer portal; uninstalling the app does not cancel payment. Plan changes currently charge the full new monthly price immediately without unused-time credit.
Usage counts additions plus deletions, with no minimum charge. Updates normally count only changes since the last reviewed commit; unreliable comparisons can count the full diff. Usage shows the percentage used and reset date. Reviews that exceed the remaining allowance are skipped until it resets or you upgrade. Failed or superseded reviews are refunded; filtering files from model scoring does not exclude their lines from usage.
Diff chunks go to TypeSafe JEV; optional explanations send a selected changed block to the configured AI provider. Verdict does not copy or execute your whole repository. Diffs and responses are temporarily checkpointed for recovery, with terminal-job checkpoints eligible for cleanup after 14 days. Provider policies and review-history retention are separate. Secrets in changed code are not automatically redacted; see our Privacy Policy.
Check the app’s repository access, automatic-review toggle, active plan, and remaining allowance, then open or update a PR after setup. GitHub Checks and dashboard history show limits or failures. Temporary outages retry and larger reviews can take longer. A newer commit supersedes the old review with its usage refunded. If installation is pending, check the installer account and organization approval; try /verdict again after recovery.
Fast, affordable feedback where you already review code. Start with GitHub and let Verdict take a closer look.