Skip to main content
| A pull request diff shows what changed, not what the change affects, and a check that looks only at the diff misses vulnerabilities that already sit in the committed code. The code also keeps changing, so what you learned about a repository’s security goes out of date with every merge. CodeRabbit Secure brings repository-level security analysis to CodeRabbit. During pull request review, it raises security issues and, through Security Architecture Review and Security Blast Radius in Change Stack, shows how a change reaches trust boundaries, controls, and downstream dependencies. For the committed codebase, Deep Scan analyzes source code and infrastructure configuration for exploitable vulnerabilities and exposed secrets beyond the current pull request diff, and shows the results, including secret findings, under Security > Findings. The Attack surface map organizes security-relevant code into subsystems and tracks verification coverage, findings, and drift as pull requests merge. Delta scans refresh it between full Deep Scans, and Steer Deep Scans explains how to guide what a scan checks. With the CodeRabbit Security check, you can publish Security results to your Git provider for merge enforcement, and Runtime verification gives you reproduction guides for Deep Scan findings.
CodeRabbit Security findings are separate from Security > PR security reviews. PR security reviews shows issues raised during pull request reviews, while Findings shows results from Deep Scans.

Security capabilities at a glance

Deep Scan does not perform dependency or software composition analysis (SCA) or generate a software bill of materials (SBOM).

PR security reviews

Open PR security reviews under Security or Analytics to review security issues raised during pull request reviews. Each finding shows its status and severity, plus separate Reachability and Exploitability badge columns. On GitHub, GitLab, Bitbucket, and Azure DevOps, including their supported self-managed variants, you can enable the CodeRabbit Security check for individual repositories. Publication is off by default, and the default blocking threshold is Critical. Merge blocking requires separate provider configuration; see the provider support and enforcement table for plan requirements and limitations.

PR security reviews filters

Use the PR status filter to show All, Open, Merged, or Closed pull requests. Author is a searchable multi-select filter for choosing one or more pull request authors. Its menu continues to list all authors while filters are active, so you can switch authors without first clearing the current selection. Filters apply to the full organization-wide PR security reviews result set before pagination, and the reported total reflects the filtered set. Changing either filter returns the list to page one and closes any open pull request detail. The PR status filter describes the lifecycle of a pull request. It is separate from the status of each individual security finding. If an active filter returns no results, PR security reviews shows No pull requests match these filters. This is distinct from the existing empty state shown when the organization has no security findings from pull request reviews.

Reachability tiers

Exploitability tiers

A dash means no valid tier was available from the live provider review comment. This can happen for older findings or provider responses without the enriched comment body.

Who can use CodeRabbit Secure

Supported providers

  • GitHub Cloud and GitHub Enterprise Server
  • GitLab Cloud and self-hosted GitLab
  • Azure DevOps Services and Azure DevOps Server
  • Bitbucket Cloud and Bitbucket Data Center
The providers above support repository security settings and code context links. Fix with AI is available for supported Deep Scan findings on all of them except Azure DevOps Server; fixes for PR review comments have separate provider requirements. Custom scan branches and recurring Deep Scan schedules are currently available only for GitHub repositories.

Azure DevOps Server support

Azure DevOps Server connected to CodeRabbit Cloud supports Deep Scan, PR security reviews, and the CodeRabbit Security pull request check. Fix with AI is not available for its Deep Scan findings. Follow the Azure DevOps Server setup guide to connect your instance. Merge blocking requires a separate branch status policy for coderabbit/security. Linked repository source access for Deep Scan is available on GitHub Cloud, GitHub Enterprise Server, and GitLab Cloud. Its platform and plan requirements are separate from those for scanning a single repository.

Access and billing

  • Viewing Security requires Security read access. Running a Deep Scan requires Security write access, which organization admins have by default.
  • Advanced and Enterprise include continuous pull request security review.
  • Deep Scan is usage-based and is not included with Advanced or Enterprise. Some organizations can have a separate free allowance; otherwise, usage billing must be enabled.
For detailed usage and billing behavior, see Usage and limits.

Automate with the API and MCP

Automate this with the CodeRabbit API and MCP server.

What’s next

Deep Scan

Run a scan of committed source code and infrastructure configuration, then triage and fix what it finds.

Attack surface

Understand how CodeRabbit maps security-relevant code and keeps verification posture current as pull requests merge.

Architecture Review

Assess the security implications of architecture-level changes in a pull request.