Documentation Index
Fetch the complete documentation index at: https://docs.qodo.ai/llms.txt
Use this file to discover all available pages before exploring further.
AlphaGitHubGitLabBitbucketAzure DevOps
Available to single-tenant customers on all plans. Currently in early access and being gradually rolled out to all customers.

Analytics
At the top of the page, Qodo displays aggregated metrics for the last 30 days:- Total critical findings: Total number of action-required findings identified across all pull requests.
- Critical findings resolved %: Percentage of action-required findings that were resolved before merge.
- Average critical findings per PR: Average number of action-required findings per reviewed pull request.
Filtering and search
Use the filters to narrow findings by repository, PR, state, action level, category, and type. Use search to find findings from a specific pull request without navigating into the PR directly.Findings table
The Findings table lists all findings across your repositories. Each row includes:| Column | Description |
|---|---|
| Findings | A short description of the finding. |
| PR | A link to the pull request where the finding was identified. |
| Repository | The repository where the finding was identified. |
| State | Current status of the finding. |
| Action level | Priority: Action required, Remediation recommended, or Other. |
| Category | Quality dimension: Correctness, Security, Reliability, Performance, Architecture, Testability, Quality, Privacy, Maintainability, or Observability. |
| Type | Finding type: Bug, Rule violation, or Requirement gap. |
Finding states
| State | Description |
|---|---|
| Pending | The PR is still open and the finding has not been addressed. |
| Fixed | The finding was resolved through code changes or a fix prompt. |
| Ignored | The PR was merged without the finding being resolved. |
| Dismissed | The finding was closed without being resolved or fixed. |
Finding details
Click any row to open a detail panel showing the full context of that finding: what the issue is, where it appears in the code, and why Qodo flagged it. Each finding is associated with a specific pull request, so you can see whether the issue was resolved before merge. The detail panel includes:- Full description and code reference: the exact location in the code where the issue was identified.
- Evidence: Qodo’s reasoning for why this was flagged.