Skip to main content

Introduction to GitHub Packages

GitHub Packages 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 Packages está disponible con GitHub Free, GitHub Pro, GitHub Free para organizaciones, GitHub Team, GitHub Enterprise Cloud, GitHub Enterprise Server 3.0 o superior y GitHub AE.
GitHub Packages no está disponible para repositorios privados que pertenezcan a cuentas que utilicen planes tradicionales por repositorio. Las cuentas que utilicen los planes tradicionales por repositorio tampoco podrán acceder al Container registry ya que estas cuentas se facturan por repositorio. Para más información, vea "Productos de GitHub".

About GitHub Packages

GitHub Packages is a platform for hosting and managing packages, including containers and other dependencies. 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.

GitHub Packages offers different package registries for commonly used package managers, such as npm, RubyGems, Apache Maven, Gradle, Docker, and NuGet. GitHub's Container registry is optimized for containers and supports Docker and OCI images. For more information on the different package registries that GitHub Packages supports, see "Working with a GitHub Packages registry."

Diagram showing packages support for the Container registry, RubyGems, npm, Apache Maven, NuGet, and Gradle

You can view a package's README, as well as metadata such as licensing, download statistics, version history, and more on GitHub. For more information, see "Viewing packages."

Overview of package permissions and visibility

PermissionsThe permissions for a package are either inherited from the repository where the package is hosted or, for packages in the Container registry and npm registry, they can be defined for specific user or organization accounts. For more information, see "Configuring a package’s access control and visibility."
VisibilityPuede publicar paquetes en un repositorio público (paquetespúblicos) para compartir con todo GitHub, o en un repositorio privado (paquetes privados) para compartir con colaboradores o con una organización.

For more information, see "About permissions for GitHub Packages."

About billing for GitHub Packages

El uso de GitHub Packages es gratuito para los paquetes públicos. En el caos de los paquetes privados, cada cuenta en GitHub.com recibe cierta cantidad de almacenamiento gratuito y transferencia de datos, dependiendo de los productos que se utilicen con la cuenta. Cualquier uso que supere las cantidades incluidas se controla mediante límites de gasto. Si eres un cliente que factura mensualmente, tu cuenta tendrá un límite de gastos predeterminado de 0 dólares Estadounidenses (USD), lo cual previene el uso adicional de almacenamiento o transferencia de datos después de que alcanzas las cantidades que se incluyen. Si paga su cuenta mediante factura, la cuenta tendrá un límite de gasto predeterminado ilimitado. For more information, see "About billing for GitHub Packages."

Supported clients and formats

GitHub Packages uses the native package tooling commands you're already familiar with to publish and install package versions.

Support for package registries

LanguageDescriptionPackage formatPackage client
JavaScriptNode package managerpackage.jsonnpm
RubyRubyGems package managerGemfilegem
JavaApache Maven project management and comprehension toolpom.xmlmvn
JavaGradle build automation tool for Javabuild.gradle or build.gradle.ktsgradle
.NETNuGet package management for .NETnupkgdotnet CLI
N/ADocker container managementDockerfileDocker

For more information about configuring your package client for use with GitHub Packages, see "Working with a GitHub Packages registry."

For more information about Docker and the Container registry, see "Working with the Container registry."

Authenticating to GitHub Packages

You need an access token to publish, install, and delete private, internal, and public packages.

You can use a personal access token (PAT) to authenticate to GitHub Packages or the GitHub API. When you create a personal access token, you can assign the token different scopes depending on your needs. For more information about packages-related scopes for a PAT, see "About permissions for GitHub Packages."

To authenticate to a GitHub Packages registry within a GitHub Actions workflow, you can use:

  • GITHUB_TOKEN to publish packages associated with the workflow repository.
  • a PAT with at least packages:read scope to install packages associated with other private repositories (which GITHUB_TOKEN can't access).

Para más información sobre el uso de GITHUB_TOKEN en flujos de trabajo de GitHub Actions, vea "Autenticación en un flujo de trabajo".

Managing packages

You can delete a package in the GitHub.com user interface or using the REST API. For more information, see "Deleting and restoring a package" and the "GitHub Packages API."

La API de GraphQL de GitHub Packages no admite contenedores ni imágenes de Docker que usan el espacio de nombres del paquete https://ghcr.io/OWNER/PACKAGE-NAME ni imágenes npm que usan el espacio de nombres del paquete https://npm.pkg.github.com/OWNER/PACKAGE-NAME.

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 "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."

Contacting support

If you have feedback or feature requests for GitHub Packages, use a GitHub Community discussion.

Contact Soporte de GitHub 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