> 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/start-a-repository-scan.md).

# Start a Repository Scan

{% hint style="info" %}
Repository scans are in **early access** and rolling out soon. If you don't see the **Repositories** tab under Code Quality yet, contact us via Chat.
{% endhint %}

Enabling repository scanning kicks off a full scan of **existing code** in the repo: everything already merged, not just in-flight changes. That unlocks category scores, the issues list, and the scatter plot. See [Understand Repository Scan Results](/code-quality/repository-scans/understand-repository-scan-results.md) for how to read the output.

Already running [PR checks](/code-quality/code-quality-setup.md) on new code? The two work independently and are designed to be used together.

## Prerequisites

Before you start, make sure:

* **You have the manage code quality permission** in your Aikido workspace.
* **The repository is connected and active** in Aikido. See [Connect Your Source Code](/code-scanning/connect-your-source-code.md).
* **Your wallet has enough credits** to cover the quoted cost. You can top up from inside the confirmation modal. See [Wallet & Credits](/miscellaneous-info/wallet-and-credits.md).

Repository scanning isn't available for Local Scanning Accounts.

## Enable scanning for a repository

{% stepper %}
{% step %}

### Open the Code Quality Repositories tab

Go to **Code Quality** in the sidebar and open the **Repositories** tab. You'll see every connected repository. Repos that are already tracked show category scores; untracked repos show **Start Tracking**.

<figure><img src="/files/VaBZ1tppCynxxWm5skf4" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Open the confirmation modal

Find the repository you want to scan and click **Start Tracking**.
{% endstep %}

{% step %}

### Confirm the cost and start

Aikido calculates the credit cost before you commit. Review the total, then click **Start Scan**. Aikido deducts the credits from your wallet and kicks off the first full scan immediately.

If your balance is too low, click **Add Credits** in the modal to top up before confirming.

<div data-with-frame="true"><figure><img src="/files/Cw9Mk4zxFG0SSqXIE6Qs" alt="Start Code Quality Scan modal showing yearly credit cost"><figcaption></figcaption></figure></div>
{% endstep %}
{% endstepper %}

After the scan starts, open the repository from the **Repositories** tab to follow progress and read findings as they land. See [Understand Repository Scan Results](/code-quality/repository-scans/understand-repository-scan-results.md).

## Pricing and credits

Repository scanning is sold as a **1-year subscription per repository**, paid with [Aikido credits](/miscellaneous-info/wallet-and-credits.md). The modal shows the total as **Code Quality Scanning (yearly)**.

Your payment covers a full year of continuous scanning for that repository — Aikido keeps the repository's findings up to date with incremental rescans throughout the 12 months. After the year is up, you pay again to keep scanning it.

The cost scales with the size of the repository. Connect the repository to Aikido and open the **Start Code Quality Scan** modal to see the exact credit total for your repo before you commit.

### After the year ends

Scanning runs continuously for one year from the day you enable it. Once that year is up, you pay again to keep the repository tracked. The cost is recalculated against the repository's current file count, so the new total reflects how the repo has grown or shrunk since you first enabled scanning.


---

# 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/start-a-repository-scan.md?ask=<question>&goal=<endgoal>
```

`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.