FAQ

Which VCS integrations are supported?

PR Review works with the GitHub and GitLab integrations. A project must be bound to a repository from one of these VCS connections. GitLab merge requests mirror the GitHub PR review flow.

How does PR Review differ from a code audit?

A code audit is a full assessment of your codebase. PR Review is a project-level continuous capability that audits only the changed paths of a pull request and posts inline comments. It is not a full assessment. For complete coverage, run a code audit or use Source Code Audit.

On which repositories can PR Review comment?

PR Review posts comments on pull requests in any repository you grant to the GitHub or GitLab integration and bind to a project. The integration must have pull-request webhook permissions for the target repository.

How much does each review cost?

Each PR review consumes credits per review. Credit spend is idempotent: if a webhook storm triggers duplicate reviews for the same PR, AISafe records one debit. See Credits & billing.

How do I know why a PR was not reviewed?

Open the project's Source tab and inspect the delivery log. Delivery rows show the repository, commit, event type, status, and a readable ignored reason such as an unbound project, branch filter mismatch, or disabled PR review. See How it works.

Is PR Review a full assessment?

No. It reviews only the changed paths of a pull request and returns inline comments, not a full findings report. For a full assessment of your codebase, use code audit.