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

# Security scans

> How to configure and track dependency vulnerability scans by repository.

Security scans help you identify vulnerabilities in the dependencies of your connected repositories. When scans are available for a repository, the `Security scans` section appears on the repository detail page.

## Where to configure

Security scans are configured under `Repositories`, which requires a Workspace admin (platform admins also have access). Open the target repository and find the `Security scans` section.

<Frame>
  <img src="https://mintcdn.com/techdriven/eiJQrWxdoD9fo1DY/images/guides/security-scans.png?fit=max&auto=format&n=eiJQrWxdoD9fo1DY&q=85&s=4d4eb2c7d5c1a84c7ae61d6054fb43d0" alt="Repository Security scans section with the recurring-scan toggle and the latest scan summary" width="2213" height="1262" data-path="images/guides/security-scans.png" />
</Frame>

From this section you can:

* enable or disable recurring scans;
* choose the scan interval;
* start an on-demand scan when allowed;
* open the latest result;
* track the vulnerability count, affected packages, and worst severity.

## What appears in the result

A scan result can include:

| Information      | Purpose                               |
| ---------------- | ------------------------------------- |
| affected package | dependency with a known vulnerability |
| current version  | version detected in the repository    |
| fixed version    | recommended version when available    |
| severity         | remediation priority                  |
| advisory         | public vulnerability reference        |
| affected paths   | where the dependency appears          |

## How to enable

<Steps>
  <Step title="Open the repository">
    Go to `Repositories` and select the repository you want to scan.
  </Step>

  <Step title="Find Security scans">
    Confirm the section is available for the repository's provider.
  </Step>

  <Step title="Enable recurring scans">
    Turn on recurring scans and choose the interval for the main branch.
  </Step>

  <Step title="Save">
    Confirm the change, then track the next scan from the repository detail page.
  </Step>
</Steps>

## On-demand scans

When on-demand scans are available, use one to validate a fix, review a newly connected repository, or investigate an alert.

For automations, use API keys with:

* `SecurityScans.Read` to list and retrieve results;
* `SecurityScans.Write` to start scans.

## Common limitations

A scan might not run when:

* the repository is not ready yet;
* the linked credential lost permission;
* the provider does not support the required action;
* the repository does not contain recognized dependency manifests;
* another scan is already running for the same repository.

Use the repository detail page, the linked credential, and `Audit Trail` to investigate.