> ## Documentation Index
> Fetch the complete documentation index at: https://docs.secally.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Full Scan

> Request a full repository scan via a GitHub issue and review results in GitHub.

**Full scans** analyze the repository’s default branch (for example, `main`) and post results back to GitHub. Use them when you want a broader view than a PR scan (for example, before a release or after a large refactor).

<Frame>
  <img src="https://mintcdn.com/secally/LD1ZSEMnsWaBnpcr/assets/full-scan.png?fit=max&auto=format&n=LD1ZSEMnsWaBnpcr&q=85&s=8fb592b92d0474f387927d1d9f976dd6" alt="Full scan request and results" width="1918" height="1360" data-path="assets/full-scan.png" />
</Frame>

## When to run a full scan

* Once a week
* Before shipping a release to the app store
* After large dependency upgrades or auth changes
* When onboarding a new repository

## How to request a full scan

1. Make sure the repository is **Monitored** in SecAlly.
2. Open a **new GitHub issue** in that repository.
3. Include:

```
@SecAllyApp scan repo
```

in the issue title or description.

## Results and remediation

SecAlly posts scan progress and results as **issue comments**. You’ll also see a **GitHub check run** tied to the scanned commit.

<Note>
  Full scans analyze the entire repository. The associated commit is used only for reporting results in GitHub.
</Note>

<Frame>
  <img src="https://mintcdn.com/secally/LD1ZSEMnsWaBnpcr/assets/full-scan-results.png?fit=max&auto=format&n=LD1ZSEMnsWaBnpcr&q=85&s=bbc436c77bf1614d3206f20e762ee609" alt="Full scan request results" width="1904" height="2626" data-path="assets/full-scan-results.png" />
</Frame>

## Best practices

* Run full scans on a schedule (for example weekly) and before releases.
* Treat the results like a backlog: fix critical issues first, then work down by severity.