The CARL GitHub App installs at the organization or repository level and runs a CARL assessment on every pull request. It posts:
- A status check that can be required in branch protection rules (e.g., "CARL level may not drop below L3").
- A comment with the assessment summary and the level delta (e.g., "L3 → L3, pillar scores unchanged") so reviewers see it inline.
- A dashboard at organization scope showing every repo's current level and trend.
When it's the right tool
- You're running an organization of many repositories and want CARL to apply uniformly without wiring a workflow into each one.
- You want to gate merges on CARL level without writing any YAML.
- You want historical trend data without running your own infrastructure.
When to use the CLI or hosted app instead
- You're running locally, in a fork, or in an air-gapped environment — the CLI fits better.
- You want a one-off, one-time assessment with a PDF export — the hosted app fits better.
Related
- CLI — the same underlying engine, used locally or in CI.
- CI integration — wire up the CLI in Actions today.
- Private-repo assessment — how the ephemeral-container architecture applies to GitHub App installs.