About GitHub Packages
GitHub Package Registry is a software package hosting service that allows you to host your software packages privately or publicly and use packages as dependencies in your projects.
GitHub Package Registry is available with GitHub Free, GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub One. GitHub Package Registry is not available for public or private repositories owned by accounts using legacy per-repository plans. For more information, see "GitHub's products."
- About packages
- Sobre o GitHub Package Registry
- Sobre a cobrança do GitHub Package Registry
- Clientes e formatos compatíveis
- About tokens
- Managing packages
- Entrar em contato com o suporte
A package is a self-contained and reusable piece of software that includes code and metadata, such as current version number, name, and the package's dependencies, that a developer bundles together in a common place for others to use. Packages simplify using and distributing solutions to common problems such as needing a common framework for developing a project, testing runners and linters to improve code quality, or introducing industry-standard machine learning tools to power your application.
Sobre o GitHub Package Registry
GitHub Package Registry is a package hosting service, fully integrated with GitHub. GitHub Package Registry 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 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.
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.
You can integrate GitHub Package Registry with GitHub APIs, GitHub Actions, and webhooks to create an end-to-end DevOps workflow that includes your code, CI, and deployment solutions.
Sobre a cobrança do GitHub Package Registry
GitHub Package Registry usage is free for public packages. For private packages, each GitHub account receives a certain amount of free storage and data transfer, depending on the product used with the account. By default, your account will have a spending limit of $0, which prevents additional usage of storage or data transfer after you reach the included amounts. If you increase your spending limit above the default of $0, you will be billed for any additional storage or data transfer, also called overages, up to your spending limit. For more information, see "About billing for GitHub Package Registry."
Clientes e formatos compatíveis
GitHub Package Registry uses the native package tooling commands you're already familiar with to publish and install package versions.
Atualmente, o GitHub Package Registry aceita estes estes clientes e formatos.
|Cliente do pacote||Linguagem||Formato do pacote||Descrição|
||Node package manager|
||RubyGems package manager|
||Apache Maven project management and comprehension tool|
||Ferramenta de automação do build Gradle para Java|
||Plataforma de gerenciamento de contêiner Docker|
||Gerenciamento de pacotes NuGet para .NET|
For more information about configuring your package client for use with GitHub Package Registry, see "Using GitHub Package Registry with your project's ecosystem."
You need an access token to publish, install, and delete packages in GitHub Package Registry. You can use a personal access token to authenticate with your username directly to GitHub Package Registry or the GitHub API. You can use a
GITHUB_TOKEN to authenticate using a GitHub Actions workflow.
When you create a personal access token, you can assign the token different scopes depending on your needs. For more information, see "Creating a personal access token for the command line" and "Available scopes" in documentação do GitHub Developer.
You can only delete private packages. To install, publish, or delete a certain package, you must use a token with the appropriate scope, and your user account must have appropriate permissions for that repository. For example, to download and install packages from a repository, your token must have the
read:packages scope, and your user account must have read permissions for the repository. If the repository is private, your token must also have the
||Download and install packages from GitHub Package Registry||leitura|
||Upload and publish packages to GitHub Package Registry||gravação|
||Delete specified versions of private packages from GitHub Package Registry||administrador|
||Install, upload, and delete certain packages in private repositories (along with
||read, write, or admin|
When you create a GitHub Actions workflow, you can use the
GITHUB_TOKEN to publish and install packages in GitHub Package Registry without needing to store and manage a personal access token. For more information, see "Using GitHub Package Registry with GitHub Actions."
You can a delete a version of a private package on GitHub or using the GraphQL 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 Package Registry. For more information, see "Deleting a package" and "Forming calls with GraphQL" in documentação do GitHub Developer.
You can configure webhooks to subscribe to package-related events, such as when a package is published or updated. For more information, see "PackageEvent" in documentação do GitHub Developer.
Entrar em contato com o suporte
If you have feedback or feature requests for GitHub Package Registry, use the feedback form for GitHub Package Registry.
Contact Suporte do GitHub about GitHub Package Registry 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