GitHub Packages
Overview
Heeler connects with GitHub Packages for analysis analysis of the package artifacts running in your environment. Heeler requires a GitHub Personal Access Token (PAT) with read:packages permission to authenticate with GitHub Packages.
Setup
Navigate to GitHub Developer Settings
Go to GitHub and log in to your account.
Click on your profile picture (top right) and select Settings.
Scroll down and click on Developer settings (left sidebar).
Click Personal access tokens → Tokens (classic).
Click Generate new token (classic).
Configure the Personal Access Token
Note: If prompted, enter your GitHub password or use two-factor authentication.
In the Note field, enter a descriptive name (e.g.,
Heeler GitHub Packages).Expiration: Set an expiration date based on your security policies.
Under Select scopes, check the following permission:
✅
read:packages(to allow Heeler to pull packages from GitHub Packages)
Generate and Save the Token
Scroll down and click Generate token.
Important: Copy and store the token securely. You won’t be able to see it again.
Use this token when configuring Heeler to authenticate with GitHub Packages.
Configure Heeler to Connect to GitHub Packages
Select the
icon from the top navigationSelect Connections -> Registries then select 'Add Registry'
Select
GitHub
Fill the required values for the connection:
Ensure
Packageis selected for the registry typePackage Type- The package ecosystem for the artifacts Heeler should analyze. If multiple ecosystems are needed, each needs a separate GitHub Package connection. Maven and NPM ecosystems are supported.Name- Provide any name you wish for the connectionOrganization- Your GitHub organization name (slug), e.g. https://github.com/<your-org-name>Username- Paste username used to generate PAT from Step 3Repository- GitHub Package repository to connectAccess Token- Paste your access token from Step 3
Click 'Save'

Last updated
Was this helpful?
