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

# Running Scans

> How to trigger and monitor security scans

Learn how to run security scans manually, view real-time progress, and interpret results.

## Trigger a Manual Scan

<Steps>
  <Step title="Select Repository">
    From dashboard, click on the repository you want to scan
  </Step>

  <Step title="Click Scan Now">
    Click **Scan Now** button in the top right
  </Step>

  <Step title="Confirm Scan">
    Click **Start Scan** in confirmation modal
  </Step>
</Steps>

***

## Scan Status

Scans progress through states:

| Status        | What It Means                   | Duration           |
| ------------- | ------------------------------- | ------------------ |
| **PENDING**   | Scan queued, waiting for worker | Seconds to minutes |
| **SCANNING**  | Actively analyzing code         | 2-15 minutes       |
| **COMPLETED** | Scan finished successfully      | -                  |
| **FAILED**    | Scan encountered an error       | -                  |

### Real-Time Progress

During scanning, you'll see:

* Current phase: Cloning, SAST, SCA, Secrets, IaC
* Progress percentage: Estimated completion
* Time elapsed: How long scan has been running
* Preliminary findings: Violations as they're discovered

<Info>
  Most scans complete within 2-5 minutes. Large repositories may take up to 15 minutes.
</Info>

***

## Scan Results Dashboard

After a scan completes, the results dashboard shows:

### Summary Metrics

<CardGroup cols={4}>
  <Card title="Critical" icon="circle-exclamation">
    Violations requiring immediate attention
  </Card>

  <Card title="High" icon="triangle-exclamation">
    Significant security issues
  </Card>

  <Card title="Medium" icon="circle-info">
    Moderate security concerns
  </Card>

  <Card title="Low" icon="circle">
    Minor issues and improvements
  </Card>
</CardGroup>

### Breakdown by Type

See violations categorized by scan type:

* **SAST**: Code-level vulnerabilities
* **SCA**: Dependency vulnerabilities
* **Secrets**: Exposed credentials
* **IaC**: Infrastructure misconfigurations

### Security Score

A numeric score (0-100) representing overall security posture:

* **90-100**: Excellent
* **70-89**: Good
* **50-69**: Moderate risk
* **0-49**: High risk

***

## Viewing Individual Violations

Click any violation to see detailed information:

* **Violation title** and description
* **Severity** and type
* **Code location** with context
* **CVSS and EPSS scores**
* **Remediation guidance**
* **Actions**: Fix, suppress, assign, comment

***

## Scan History

View all past scans for a repository:

1. Navigate to repository
2. Click **Scan History** tab
3. See chronological list of scans

Each scan shows:

* Completion time
* Violation counts
* Security score
* Comparison to previous scan

***

## Next Steps

<CardGroup cols={2}>
  <Card title="Interpreting Results" icon="chart-line" href="/scanning/interpreting-results">
    Understand scan results
  </Card>

  <Card title="Automated Scanning" icon="repeat" href="/scanning/automated-scanning">
    Set up automatic scans
  </Card>
</CardGroup>