Works with · CodeRabbit

Does CodeRabbit approval count for SOC 2?

No. CodeRabbit posts a summary and line comments from the coderabbitai[bot] account and can mark a PR as approved; an auditor sampling merged PRs for SOC 2 CC8.1 is looking for a qualified person other than the author, and a bot is not one. Keep CodeRabbit for the findings; PSCO adds the named Officer whose approval is the evidence.

How CodeRabbit reviews

CodeRabbit posts a walkthrough summary of the change, inline comments with suggested fixes, and the results of any custom instructions you configure in .coderabbit.yaml. It re-reviews on each push.

What it cannot do

CodeRabbit cannot be the independent human approver an auditor is looking for. SOC 2 CC8.1, ISO 27001 A.5.3, PCI DSS 6.2.3.1 and SOX program-change controls all assume a qualified person other than the author approved the change and understood it. A bot account posting "Approve" is a review record, not an accountable person, and as of mid-2026 no auditor reports accepting it as standard practice.

How PSCO reads its output

PSCO parses the CodeRabbit summary and every line comment into findings on the Officer’s packet, including the results of your custom instructions. The Officer sees which findings were addressed and which remain, and the attestation records that CodeRabbit reviewed the PR.

Recognized asbot logins
coderabbitai[bot]Summary · Line comments · Custom-instruction results

Two-step setup

Keep CodeRabbit.

Keep CodeRabbit configured as it is.

Add PSCO.

Install the PSCO GitHub App, pick the repos in scope, and add one required approval from @psco-officers and the psco/approved check to branch protection.

The shared-model tip

Point it at the same model the Officer uses.

Point CodeRabbit at the same rulebook the Officer uses. Put the model’s forbidden patterns and sensitive paths in .coderabbit.yaml under reviews.path_instructions, or reference psco.model.yaml from there. Keep the sensitive paths, required checks and forbidden patterns identical in both places so the robot and the human check the same rules, and so the Officer's packet shows the AI's findings next to the clause they map to.

psco.model.yamlv1 · customer-owned
frameworks: [soc2, iso27001]
sensitive_paths:
  auth/**: deep
  infra/**: deep
required_checks: [ci, tests, sast, secrets]
forbidden: [hardcoded_secret, tls_verify_off]

Keep CodeRabbit. Add the human who signs.

Connect GitHub and PSCO detects the reviewers already on your repos. Your price comes from your real PR history.