Works with · Sourcery

Does a Sourcery review count for SOC 2?

No. Sourcery posts a summary and comments from a bot account. It is not an approval by a qualified person other than the author. PSCO adds that person and reads Sourcery’s output first.

How Sourcery reviews

Sourcery posts a summary of the change and review comments with suggested refactors and fixes on each push.

What it cannot do

Sourcery 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

The summary and each comment are parsed into the Officer’s packet.

Recognized asbot logins
sourcery-ai[bot]Summary · Comments

Two-step setup

Keep Sourcery.

Keep Sourcery enabled.

Add PSCO.

Install the PSCO GitHub App, select the repos in scope, and require psco/approved and one approval from @psco-officers.

The shared-model tip

Point it at the same model the Officer uses.

Point Sourcery at the same rulebook the Officer uses. Add the model’s rules to .sourcery.yaml or reference psco.model.yaml from it. 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 Sourcery. Add the human who signs.

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