GitHub Packages is a package hosting service, fully integrated with GitHub. GitHub Packages combines your source code and packages in one place to provide integrated permissions management and billing, so you can centralize your software development on GitHub.
You can integrate GitHub Packages with GitHub APIs, GitHub Actions, and webhooks to create an end-to-end DevOps workflow that includes your code, CI, and deployment solutions.
You can host multiple packages in one repository and see more information about each package by viewing the package's README, download statistics, version history, and more.
When you create a GitHub Actions workflow, you can use the
GITHUB_TOKEN to publish and install packages in GitHub Packages without needing to store and manage a personal access token. Weitere Informationen findest Du unter „Informationen zu GitHub Container Registry“.
Note: GitHub Container Registry is currently in public beta and subject to change. During the beta, storage and bandwidth are free. To use GitHub Container Registry, you must enable the feature preview. For more information, see "About GitHub Container Registry" and "Enabling improved container support."
You can configure webhooks to subscribe to package-related events, such as when a package is published or updated. Weitere Informationen findest Du unter „Anzeigen von Paketen."
|Hosting locations||You can host multiple packages in one repository.|
|Permissions||You can publish packages in a public repository (public packages) to share with all of GitHub, or in a private repository (private packages) to share with collaborators or an organization. You can use GitHub roles and teams to limit who can install or publish each package, as packages inherit the permissions of the repository. Anyone with read permissions for a repository can install a package as a dependency in a project, and anyone with write permissions can publish a new package version.|
|Visibility||You can publish packages in a public repository (public packages) to share with all of GitHub, or in a private repository (private packages) to share with collaborators or an organization.|
Die GitHub Packages-Nutzung ist für öffentliche Pakete kostenlos. Für private Pakete erhält jedes GitHub-Konto eine bestimmte Menge an kostenlosem Speicher und Datenübertragung, abhängig vom Produkt, das mit dem Konto verwendet wird. Any usage beyond the included amounts is controlled by spending limits. If you are a monthly-billed customer, your account will have a default spending limit of $0, which prevents additional usage of storage or data transfer after you reach the included amounts. If you pay your account by invoice, your account will have an unlimited default spending limit. For more information, see "About billing for GitHub Packages."
Billing update for container image storage: During the beta phase of GitHub Container Registry, Docker image storage and bandwidth are free for the old
docker.pkg.github.com and new
ghcr.io hosting services. Weitere Informationen findest Du unter „Informationen zu GitHub Container Registry“.
GitHub Packages uses the native package tooling commands you're already familiar with to publish and install package versions.
|Ruby||RubyGems package manager|
|Java||Apache Maven project management and comprehension tool|
|Java||Gradle-Tool für die Build-Automatisierung für Java|
|.NET||NuGet-Paketmanagement für .NET|
|N/A||Docker container management|
For more information about configuring your package client for use with GitHub Packages, see "Package client guides for GitHub Packages."
For more information about Docker and GitHub Container Registry, see "Container guides for GitHub Packages."
You need an access token to publish, install, and delete packages. Du kannst ein persönliches Zugriffstoken verwenden, um Dich mit Deinem Benutzernamen direkt bei GitHub Packages oder beim GitHub-API zu authentifizieren. When you create a personal access token, you can assign the token different scopes depending on your needs.
To authenticate using a GitHub Actions-workflow:
- For package registries (
PACKAGE-REGISTRY.pkg.github.com), you can use a
- For the container registry (
ghcr.io/OWNER/IMAGE-NAME), you can use a
GITHUB_TOKENor a personal access token. We strongly recommend you use a
GITHUB_TOKENto avoid unncessary access to your repositories.
To install or publish a package, you must use a token with the appropriate scope, and your user account must have appropriate permissions for that repository.
- To download and install packages from a repository, your token must have the
read:packagesscope, and your user account must have read permissions for the repository.
- To delete a package on GitHub, your token must at least have the
reposcope is also required for repo-scoped packages. For more information, see "Deleting and restoring a package."
|Download and install packages from GitHub Packages||Lesen|
|Upload and publish packages to GitHub Packages||schreiben|
|Delete packages from GitHub Packages|
|Upload and delete packages (along with ||write, or admin|
When you create a GitHub Actions workflow, you can use the
GITHUB_TOKEN to publish and install packages in GitHub Packages without needing to store and manage a personal access token.
Weitere Informationen findest Du unter:
You can delete a package in the GitHub user interface or using the REST API. For more information, see the "GitHub Packages API."
When you use the GraphQL API to query and delete private packages, you must use the same token you use to authenticate to GitHub Packages. For more information, see "Deleting and restoring a package" and "Forming calls with GraphQL."
You can configure webhooks to subscribe to package-related events, such as when a package is published or updated. For more information, see the "
package webhook event."
If you have feedback or feature requests for GitHub Packages, use the feedback form for GitHub Packages.
Contact GitHub-Support about GitHub Packages using our contact form if:
- You experience anything that contradicts the documentation
- You encounter vague or unclear errors
- Your published package contains sensitive data, such as GDPR violations, API Keys, or personally identifying information