Use case
Security review on every pull request
Catch issues in a change before it merges — scoped to the files the PR touches, with AI triage and a one-click summary comment.
$ openrouting review --pr ✓ scope ✓ triage ✓ comment never alters the repo's tracked findings $
In short: OpenRouting reviews only the files a GitHub pull request changes, has Claude triage each new finding, and, when you click, posts one summary comment to the PR. PR findings are kept apart from the tracked findings of the repository.
Review what's changing, not the whole repo
OpenRouting lists your repository's open pull requests. Open one to see its changed files, then run a review that scans only those files. You see the security findings introduced by the change, with likely false positives filtered out.
Post the review where the discussion is
When you're ready, post a single summary comment back to the pull request on GitHub. It lists the real findings with severity, file, and a short explanation — and it only happens when you click, as the connected user.
Keeps PR review honest
PR findings live on the review itself, separate from the repository's tracked findings, so a review never alters your main-branch state or trend. It's a focused check on the change in front of you.
Questions
Does OpenRouting comment on my PRs automatically?
No. You open a PR in OpenRouting, see its changed files, and run a review. Posting a summary comment back to GitHub is an explicit action you take — it never happens automatically.
Does it scan the whole repo or just the PR?
Just the files the pull request changes, so the review is fast and focused on what's new.
Who does the comment appear as?
As the connected GitHub user, with a note that it was generated by OpenRouting.