VeriFlow on every repo you ship from

Every PR gets an inline review, a suggestion block, a severity badge, and a check-run status — the same loop on every connected repository.

• Scope set maps cleanly to the GitHub App: Contents read & write, Pull requests read & write, Metadata read-only, Checks read & write, and Issues read & write.
• Webhook envelopes the App subscribes to on each connected repo: pull_request, pull_request_review, and check_run.
• Inline comments, suggestion blocks, and check run status — no separate bot identity required.

Planned for GitLab.com, GitLab SaaS groups, and self-hosted instances. The planned integration would subscribe to the envelopes that match merge-request activity.

• Planned scope shape, subject to implementation review: api/read_repository + api/write_repository, api/merge_requests, and read_api + read_user. No catch-all admin scope.
• Planned webhook envelopes would mirror the GitHub PR loop: Push Hook, Merge Request Hook, and Note Hook.
• Approval rules, MR descriptions, and pipeline status are intended to be read inline; this behavior is not available yet.

Planned for Bitbucket Cloud workspaces and Bitbucket Data Center deployments. The planned integration would subscribe to the pull-request lifecycle envelopes that could drive the review loop.

• Planned OAuth scope shape, subject to implementation review: repository:read + repository:write, pullrequest:read + pullrequest:write, and account:read. No workspace-admin scope.
• Planned webhook envelopes would mirror the GitHub PR loop: repo:push, pullrequest:created, pullrequest:updated, and pullrequest:approved.
• Builds, branch restrictions, and default reviewers are intended to be read inline; this behavior is not available yet.