{"meta":{"title":"Introduction to GitHub Packages","intro":"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.","product":"GitHub Packages","breadcrumbs":[{"href":"/en/packages","title":"GitHub Packages"},{"href":"/en/packages/learn-github-packages","title":"Learn GitHub Packages"},{"href":"/en/packages/learn-github-packages/introduction-to-github-packages","title":"Introduction"}],"documentType":"article"},"body":"# Introduction to GitHub Packages\n\nGitHub 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.\n\n\n\n## About GitHub Packages\n\nGitHub 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.\n\nYou can integrate GitHub Packages with GitHub's APIs, GitHub Actions, and webhooks to create an end-to-end DevOps workflow that includes your code, CI, and deployment solutions.\n\nGitHub 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](/en/packages/working-with-a-github-packages-registry).\n\nYou 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](/en/packages/learn-github-packages/viewing-packages).\n\n### Overview of package permissions\n\nThe permissions for a package are either inherited from the repository where the package is hosted, or can be defined for specific users or organizations. Some registries only support permissions inherited from a repository. For a list of these registries, see [About permissions for GitHub Packages](/en/packages/learn-github-packages/about-permissions-for-github-packages#permissions-for-repository-scoped-packages). For more information on package access, see [Configuring a package's access control and visibility](/en/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility).\n\n### Overview of package visibility\n\nYou 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.\n\n## About linked artifacts for organizations\n\nThe linked artifacts page is an alternative view that you can also access in the \"Packages\" section of an organization's settings.\n\nLike GitHub Packages, the linked artifacts page allows you to collect information about your organization's builds in a single place. Teams can use the linked artifacts page to find an artifact's source code, build details, and deployment history.\n\nUnlike GitHub Packages, the linked artifacts page does **not** host the package or image files themselves. Instead, it provides an authoritative source for the metadata associated with each package or image.\n\nYour organization may benefit from using the linked artifacts page either:\n\n* **Alongside** GitHub Packages, as a complementary view focused on the compliance and security aspects of package consumption\n* **As an alternative to** GitHub Packages, allowing you to store your packages on an external registry of your choice while maintaining visibility of the packages on GitHub\n\nFor more information, see [About linked artifacts](/en/code-security/concepts/supply-chain-security/linked-artifacts).\n\n## About billing for GitHub Packages\n\nGitHub Packages usage is **free** for **public packages**.\n\nFor **private packages**, each account on GitHub receives an amount of **free storage and data transfer**, determined by the account's plan. Any usage beyond the included amounts is controlled by budgets.\n\nIf your account does not have a valid payment method on file, usage is blocked once you use up your quota.\n\nIf you have a valid payment method on file, spending may be limited by one or more budgets. Check the budgets set for your account to ensure they are appropriate for your usage needs. See [Setting up budgets to control spending on metered products](/en/billing/how-tos/set-up-budgets).\n\nFor more information, see [GitHub Packages billing](/en/billing/concepts/product-billing/github-packages).\n\n## Supported clients and formats\n\n\n\nGitHub Packages uses the native package tooling commands you're already familiar with to publish and install package versions.\n\n### Support for package registries\n\n| Language | Description | Package format | Package client |\n| ---------- | ------------------------------------------------------ | ------------------------------------ | -------------- |\n| JavaScript | Node package manager | `package.json` | `npm` |\n| Ruby | RubyGems package manager | `Gemfile` | `gem` |\n| Java | Apache Maven project management and comprehension tool | `pom.xml` | `mvn` |\n| Java | Gradle build automation tool for Java | `build.gradle` or `build.gradle.kts` | `gradle` |\n| .NET | NuGet package management for .NET | `nupkg` | `dotnet` CLI |\n| N/A | Docker container management | `Dockerfile` | `Docker` |\n\nFor more information about configuring your package client for use with GitHub Packages, see [Working with a GitHub Packages registry](/en/packages/working-with-a-github-packages-registry).\n\nFor more information about Docker and the Container registry, see [Working with the Container registry](/en/packages/working-with-a-github-packages-registry/working-with-the-container-registry).\n\n## Authenticating to GitHub Packages\n\n> \\[!NOTE]\n> GitHub Packages only supports authentication using a personal access token (classic). For more information, see [Managing your personal access tokens](/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens).\n\nYou need an access token to publish, install, and delete private, internal, and public packages.\n\nYou can use a personal access token (classic) to authenticate to GitHub Packages or the GitHub API. When you create a personal access token (classic), you can assign the token different scopes depending on your needs. For more information about packages-related scopes for a personal access token (classic), see [About permissions for GitHub Packages](/en/packages/learn-github-packages/about-permissions-for-github-packages#about-scopes-and-permissions-for-package-registries).\n\nTo authenticate to a GitHub Packages registry within a GitHub Actions workflow, you can use:\n\n* `GITHUB_TOKEN` to publish packages associated with the workflow repository.\n* A personal access token (classic) with at least `read:packages` scope to install packages associated with other private repositories (`GITHUB_TOKEN` can be used if the repository is granted read access to the package. See [Configuring a package's access control and visibility](/en/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)).\n\nFor more information about `GITHUB_TOKEN` used in GitHub Actions workflows, see [Use GITHUB\\_TOKEN for authentication in workflows](/en/actions/tutorials/authenticate-with-github_token#using-the-github_token-in-a-workflow).\n\n## Managing packages\n\nYou can delete a package in the GitHub user interface or using the REST API. For more information, see [Deleting and restoring a package](/en/packages/learn-github-packages/deleting-and-restoring-a-package) and the [REST API endpoints for packages](/en/rest/packages). For certain registries, you can use GraphQL to delete a version of a private package.\n\nYou cannot use the GitHub Packages GraphQL API with registries that support granular permissions. For the registries that **only** support repository-scoped permissions, and can be used with the GraphQL API, see [About permissions for GitHub Packages](/en/packages/learn-github-packages/about-permissions-for-github-packages#permissions-for-repository-scoped-packages).\n\nWhen you use the GraphQL API to query and delete private packages, you must use the same personal access token (classic) you use to authenticate to GitHub Packages.\n\nFor more information, see [Forming calls with GraphQL](/en/graphql/guides/forming-calls-with-graphql).\n\nYou can configure webhooks to subscribe to package-related events, such as when a package is published or updated. For more information, see the [Webhook events and payloads](/en/webhooks/webhook-events-and-payloads#package).\n\n## Contacting support\n\nIf you have feedback or feature requests for GitHub Packages, use a [GitHub Community discussion](https://github.com/orgs/community/discussions/categories/packages).\n\nContact us through the [GitHub Support portal](https://support.github.com/) about GitHub Packages if:\n\n* You experience anything that contradicts the documentation\n* You encounter vague or unclear errors\n* Your published package contains sensitive data, such as GDPR violations, API Keys, or personally identifying information"}