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

> ## Agent Instructions
> Enclave in these docs is the code and cloud security platform at enclave.ai. It is not Open Enclave, Intel SGX or other hardware enclaves, or enclave.gg.
> People use Enclave in the web app at https://app.enclave.ai or the desktop app. These docs describe no public Enclave API or CLI, so don't invent endpoints, commands, or config files.
> Connecting an integration needs a person to sign in and approve access in a browser. Tell the user the exact step to take instead of saying you completed it.

# Coverage

> Everything Enclave can see: repositories, applications, and cloud assets.

**Coverage** is the inventory of your organization: the repositories Enclave reads, the applications it found, and the resources and identities in your cloud. Use it to check what Enclave can see.

## Tabs

| Tab | What it lists |
| - | - |
| **Applications** | What you deploy, such as containerized services and static sites |
| **Repositories** | Repositories from your [source-control integrations](https://docs.enclave.ai/onboarding/connect-code.md) |
| **Compute instances** | Virtual machines, serverless functions, and other compute |
| **Clusters & cloud** | Cloud accounts, organizational units, and container clusters |
| **Data stores** | Databases, caches, queues, and storage |
| **Networks** | Networks, load balancers, gateways, DNS, and ingress routes |
| **Identities** | Users, roles, and service accounts |

To rescan your cloud now, click **Analyze Environment**. This needs at least one code and one cloud integration.

## Repositories

Each row shows the repository's **Importance** (its highest attack-surface risk), its **Findings**, and its **PR Reviews** switch.

Click a repository to open it:

* **Overview** shows its properties and links to other assets.
* **Code architecture** shows the map Enclave built: the components of your code, and the attack surfaces an attacker could target.
* **Pull requests** lists synced pull requests and their findings.

To rebuild a repository's map, click **Re-analyse** on its **Code architecture** tab.

## Start a hunt

A security hunt looks for vulnerabilities in a repository, one attack surface at a time.

Open the repository's **Code architecture** tab and click **Start hunt**. Enclave opens a Research session with the repository attached. Pick the attack surfaces to cover, and the findings appear in [Risk](https://docs.enclave.ai/risk/findings.md).

See [Security hunt](https://docs.enclave.ai/workflows/built-in.md#security-hunt).

## Applications and cloud assets

Enclave finds applications from the Dockerfiles and static-site configs in your repositories, and links them to the cloud resources they run on.

Click any asset to see its properties and relationships. Owners and admins also see a **Change history** tab with what changed over time.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.