> For the complete documentation index, see [llms.txt](https://help.aikido.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.aikido.dev/code-quality/repository-scans/understand-repository-scan-results.md).
# Understand Repository Scan Results
Once a repository scan completes, results appear on the **Repositories** tab and on the repository detail page. These reflect **existing code** — open quality issues across the full codebase, not just recent PR changes.
This guide covers how to read scores, triage findings, and spot hotspots.
## Repositories overview
The **Repositories** tab lists every connected repository with a score in four categories:
* **Maintainability** — how easy the code is to change and extend
* **Readability** — clarity, naming, and structure
* **Performance** — efficiency and resource usage
* **Reliability** — correctness, error handling, and bug-prone patterns
Each cell shows a rating label, a color indicator, and a number. The label reflects the worst-severity open finding in that category; the number is the total count of open findings there.
The **PR checks** column shows whether [PR checks](/code-quality/code-quality-setup.md) are enabled for that repository (**ON** / **OFF**). PR checks cover **new code** on pull requests; repository scans cover **existing code** in the full repo. The two are independent — you can enable either or both.
Click a tracked repository to open its detail page.
## Category ratings
Each category rating is based on the **highest-severity open finding** in that category, not the total issue count.
| Rating | Condition |
| ------------- | ------------------------------------------------------------ |
| **Excellent** | Only low or informational findings (nothing medium or above) |
| **Good** | At least one medium finding, but no high or critical |
| **Fair** | At least one high finding, but no critical |
| **Poor** | At least one critical finding |
Findings are grouped into categories based on the rule that triggered them — each default and custom check belongs to one of the four categories above. Low-severity findings don't affect the rating label, but they are included in the issue count.
## Trend over time
Open the **Trend Over Time** tab on a repository detail page to see how its open findings change from week to week.
The chart splits findings by severity, so you can see whether critical, high, medium, or low-priority quality debt is growing or shrinking. Use it to measure the impact of cleanup work and identify regressions that need attention.
## Issues tab
The **Issues** tab on the repository detail page lists every open finding, grouped by rule. Each row shows:
* **Type** — the language of the affected file
* **Name** — the rule title and affected file(s)
* **Severity** — the highest severity in the group
* **Location** — file path(s) where the issue occurs
* **Fix time** — estimated effort to resolve
Click a row to open the detail sidebar. From there you can:
* Read the **TL;DR** and **How do I fix it?** guidance
* Browse **Subissues** with file names, line numbers, and code snippets
* Open **View code analysis** for a deeper look at a specific occurrence
* Ignore individual findings
### Fix findings with AutoFix
Instead of fixing a finding by hand, you can let Aikido generate the change for you. [AutoFix](/autofix-and-remediation/overview-aikido-autofix.md) produces a fix for the finding and can open a pull request with the change, so you review and merge rather than write it yourself.
## File scatter plot
Switch to the **File Scatter Plot** tab to visualize code quality hotspots — files that are both frequently changed and carry open quality debt.
Each dot represents one file in the repository:
* **X-axis** — number of PRs that touched the file in the last 3 months
* **Y-axis** — number of open code quality findings in that file
Files in the **top-right** of the chart are your hotspots: high activity combined with low quality. Prioritize these when planning refactors or cleanup work.
{% hint style="info" %}
The scatter plot requires **both** modes enabled for the same repository: [PR checks](/code-quality/code-quality-setup.md) for **new code** activity data, and repository scans for **existing code** finding counts.
{% endhint %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://help.aikido.dev/code-quality/repository-scans/understand-repository-scan-results.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.