Skip to main content
Analytics requires workspace access and feature availability. By default, only admins can open it. An admin can use Settings > Grant Analytics access to include team owners, where supported, or all workspace members. This grants read access to Analytics without granting configuration, billing, member management, or pull request actions.
The Analytics dashboard in the Qodo portal shows how your team responds to Qodo findings across pull requests, repositories, and PR authors. Each finding is tracked through its response. An acted-on finding is one with a final outcome: accepted, not accepted, or dismissed. Findings still pending a decision aren’t included. An accepted finding is one that resulted in an accepted code change. Keeping these metrics separate shows both whether findings reach a decision and whether those decisions lead to code changes. Break down the data by repository, PR author, severity, category, and finding type. Finding types include bugs and security issues, as well as violations of your organization’s rules, gaps against PR requirements, team insights, skills, and changes that affect related repositories. Use the dashboard to understand Qodo’s impact over time, identify high-severity findings that remain unaddressed, and compare finding activity and response across repositories and PR authors. To find the view that answers a specific question, see the Analytics cheat sheet. Code review analytics dashboard Admins control the independent Show author analytics setting, which is on by default. Everyone granted Analytics access can see per-author data while this setting is on. Turning it off hides the Authors tab, author filters, author-identifying details, and Analytics exports while preserving aggregate totals. An existing legacy hide-author setting continues to hide authors even when Show author analytics is on. This setting controls Analytics, not author identities across Qodo. Findings and pull request pages can still identify authors. In Findings CSV exports, the author column follows the Analytics restriction for users with Analytics access; users without Analytics access retain their ordinary Findings export.

Filter analytics

You can filter analytics by:
  • Time range: Today, Last 7 days, Last 30 days, Last 90 days, or a custom range. The time range filters by when Qodo raised the finding. Today starts at midnight UTC. A custom range can cover up to 365 days.
  • Severity: Low, Medium, High, or All levels.
  • Category: Accessibility, Architecture, Compliance, Correctness, Maintainability, Observability, Performance, Quality, Reliability, Security, and Testability. For more information, see the Finding categories table.
  • Type: Bug, Rule violation, Requirement gap, Team insight, Skill, Cross-repo, and Security.
    • Bug: Logic errors, edge cases, and anti-patterns in the change.
    • Rule violation: Code that breaks one of your organization’s rules.
    • Requirement gap: The pull request does not fully implement a requirement from its linked ticket or specification.
    • Team insight: A finding raised from a team profile, which reviews the pull request the way the most relevant teammates would.
    • Skill: A finding raised by a skill defined in your repository.
    • Cross-repo: A change that breaks code in a related repository.
    • Security: A vulnerability in the change, such as an OWASP or CWE-class issue.
  • Repository: One or more indexed repositories.
  • PR author: One or more PR authors. Available only when author analytics are visible.

Finding categories

Understand analytics metrics

Analytics metrics are calculated from Qodo findings data. The dashboard counts findings raised on a pull request or linked to one. Local findings and findings detected after merge are excluded.

Measure the impact of Qodo findings

The Impact view gives you an organization-wide view of how Qodo findings affect pull requests. Use it to understand how often findings lead to action, how many result in accepted code changes, and how broadly Qodo findings reach across your organization.

Identify where findings have the most impact by repository

The By repository view breaks down finding activity by repository. Use it to understand how findings are acted on across repositories and where acceptance rates differ. Analytics dashboard by repository The table includes:
  • Repository: The repository where findings were raised.
  • Findings acted on: The number of findings with a final outcome: accepted, not accepted, or dismissed.
  • Findings accepted: The number of findings that resulted in an accepted code change.
  • Acceptance rate: The percentage of findings that were accepted.
The table counts the findings that match your filters. To focus on high-severity findings, filter by Severity: High. Select a repository to drill down into its analytics.

Understand finding response by PR author

This view is available only when author analytics are visible. The By PR author view shows how authors respond to Qodo findings across their pull requests. Use it to compare finding activity and acceptance rates across PR authors. Analytics dashboard by PR author The table includes:
  • PR author: The author of the pull requests where findings were raised.
  • Findings acted on: The number of the author’s findings with a final outcome: accepted, not accepted, or dismissed.
  • Findings accepted: The number of findings that resulted in an accepted code change.
  • Acceptance rate: The percentage of the author’s findings that were accepted.
Select an author to drill down into their findings and activity.

Export and share analytics

Use the ⋯ menu at the top of the dashboard to export or share your analytics.

Export CSV

CSV export is available only when author analytics are visible. Download your findings as a CSV file named findings.csv for reporting, audits, or analysis in your own tools. Each row represents a single Qodo finding. The export includes up to 10,000 findings. It can also include outdated findings and findings detected after merge, which the dashboard excludes, so CSV totals may not match the dashboard.

Share dashboard

Share the current view of the dashboard with others in your organization.

Analytics cheat sheet

Use this cheat sheet to quickly find the analytics section that answers your question.

Impact

By repository

By PR author