> For the complete documentation index, see [llms.txt](https://docs.heeler.com/mrecEO40m5D6bt7Pq5pE/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.heeler.com/mrecEO40m5D6bt7Pq5pE/get-started/registries-and-artifacts/github-packages.md).

# GitHub Packages

Connect GitHub Packages so Heeler treats the libraries your teams publish there as first-party code.

Heeler connects to **GitHub Packages** to analyze the package artifacts your teams publish — treating them as first-party code. It authenticates with a **GitHub Personal Access Token (classic)** that has the `read:packages` scope.

{% hint style="info" %}
GitHub Packages and [GitHub Container Registry](/mrecEO40m5D6bt7Pq5pE/get-started/registries-and-artifacts/github-container-registry.md) share the **GitHub** entry on the **Add Registry** menu — you choose between them with the **Registry Type** radio (**Package** for package artifacts). This page covers **Package**.
{% endhint %}

## Step 1 — Create a GitHub PAT

1. In GitHub, go to **Settings → Developer settings → Personal access tokens → Tokens (classic)** → **Generate new token (classic)**.
2. Give it a note (e.g. `Heeler GitHub Packages`) and an expiration per your policy.
3. Check the **`read:packages`** scope.
4. **Generate** and copy the token.

## Step 2 — Add the registry in Heeler

{% stepper %}
{% step %}

### Open the modal

Go to **Connections → Registries → Add Registry → GitHub**.

<figure><img src="https://414480750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXP3dp2kecwKA2KvYkntz%2Fuploads%2Fgit-blob-c99f27e35403c7121aca057f9e91d53df9b18862%2Fcc-gs-reg-github-menu.png?alt=media" alt="The Add Registry menu in Heeler with the GitHub option selected."><figcaption><p>Choose <strong>GitHub</strong> from the Add Registry menu.</p></figcaption></figure>
{% endstep %}

{% step %}

### Configure it

* **Registry Type** — select **Package**.
* **Package Type** — the ecosystem to analyze: **Maven** (Java), **NPM** (JavaScript), or **NuGet** (C#). Each ecosystem needs its own GitHub Packages connection.
* **Name** — any label for the connection.
* **Organization** — your GitHub organization slug.
* **Username** — the user that generated the PAT.
* **Repository** — the GitHub Packages repository to connect.
* **Personal Access Token** — the PAT from Step 1.

<figure><img src="https://414480750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXP3dp2kecwKA2KvYkntz%2Fuploads%2Fgit-blob-2118a0844023c3365a406ad1dd6f3e33aeadc2b8%2Fcc-gs-reg-ghpkg-form.png?alt=media" alt="The Add Registry modal for GitHub with Registry Type set to Package, showing Package Type, Name, Organization, Username, Repository, and Personal Access Token fields."><figcaption><p>GitHub Packages: choose <strong>Package</strong>, pick the ecosystem, and enter your org, repo, and PAT.</p></figcaption></figure>

Click **Save**.
{% endstep %}

{% step %}

### Verify

Confirm the registry shows **Healthy** under **Connections → Registries**.
{% endstep %}
{% endstepper %}

## Related

* [GitHub Container Registry](/mrecEO40m5D6bt7Pq5pE/get-started/registries-and-artifacts/github-container-registry.md) — for container images (the **Image** mode of the same entry).
* [Connect Registries and Artifacts](/mrecEO40m5D6bt7Pq5pE/get-started/registries-and-artifacts.md) — the common flow.


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.heeler.com/mrecEO40m5D6bt7Pq5pE/get-started/registries-and-artifacts/github-packages.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.