> For the complete documentation index, see [llms.txt](https://learn.heeler.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.heeler.com/tenant-admin-guide/connections/registries.md).

# Registries

A **Registry** is a container or package registry that Heeler can read to attribute images and packages back to their source. Heeler uses these connections to link runtime images to the repositories that built them, and to surface fix versions for vulnerable packages.

### Where to find it

Administration → **Connections** → **Registries** in the left sidebar.

URL: `https://app.heeler.com/administration/connections/registries`

### Quick start

[See Code Setup documentation.](/getting-started/code-setup.md)

### Reference

#### Table columns

| Column            | Description                                                              |
| ----------------- | ------------------------------------------------------------------------ |
| **Name**          | Display name for the registry.                                           |
| **Domain**        | Hostname / endpoint of the registry.                                     |
| **Registry Type** | Provider type (ECR, GAR, Docker Hub, Artifactory, GHCR, etc.).           |
| **Health**        | Whether Heeler can currently authenticate to and read from the registry. |
| **Date Added**    | When the connection was first created.                                   |

#### Actions

* **Add Registry** — start a new registry connection.
* Clicking a row opens detail including last-probed timestamp, recent errors, and the ability to update credentials.

### First-party vs. third-party registries

The Operational Health page surfaces a *First-Party Package Registries* section showing which of your registries Heeler considers first-party — registries you publish into. This affects how Heeler attributes dependencies vs. open-source supply.


---

# 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:

```
GET https://learn.heeler.com/tenant-admin-guide/connections/registries.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.