GitHub Packages

Package hosting tied to GitHub repositories, with storage allowances by plan. Our artifact repository managers ranking puts GitHub Packages at #11 of 13.

A vendor never writes its own entry here, GitHub Packages included, although paid placement exists; see the disclosure for how links are marked.

Visit GitHub Packages See it in the artifact repository managers ranking

01

Key facts about GitHub Packages

HeadquartersNot stated by the vendor
Best forTeams whose code and CI already live in GitHub
Free planNo free tier on record
DeploymentNothing recorded
Pricing modelUsage free for public packages; storage allowance by plan, with budgets controlling overage
APINothing recorded about an API
02

What is GitHub Packages?

GitHub Packages is the package hosting service of GitHub, offered by GitHub, Inc. under terms the company says are governed by United States federal law and the laws of the State of California. It lets a team host packages privately or publicly alongside the repository that holds the code. The documentation lists npm, RubyGems, Apache Maven and Gradle, NuGet and Docker as supported registries, with the container registry covering Docker and OCI images.

Permissions can be inherited from the repository or set per user or organisation, and within GitHub Actions workflows the GITHUB_TOKEN can publish packages linked to the workflow's repository. The features page describes downloads served through a global CDN and packages connected to Actions through APIs and webhooks. The country of establishment is not stated on the terms pages we read, and storage allowances are small on the lower plans: 500MB on Free, 2GB on Team and 50GB on Enterprise.

03

GitHub Packages key features

  • Five registry types. npm, RubyGems, Apache Maven and Gradle, NuGet and Docker are listed, with the container registry accepting Docker and OCI images.
  • Public or private hosting. Packages can be public or private, and the documentation says usage is free for public packages.
  • Repository-linked permissions. Access can be inherited from the repository or set separately per user or organisation, so package access can differ from code access.
  • Actions integration. Inside a workflow, GITHUB_TOKEN can publish packages linked to that workflow's repository, and webhook events report package activity.
  • Package metadata views. Packages show a README, licence, download statistics and version history, which helps consumers judge a package before installing.
  • Linked artifacts page. A linked artifacts page tracks metadata about builds without hosting the files themselves.
  • Deletion by UI or API. Packages can be deleted through the web interface or the REST API, which supports clean-up scripts.
04

Who GitHub Packages suits

  • Open source maintainers. Maintainers publishing public libraries can host packages beside the source, since the documentation says public package usage is free.
  • Container-based delivery teams. A team building Docker or OCI images in GitHub Actions can push them to the container registry under the same repository permissions.
  • Organisations sharing internal libraries. A company can keep private packages under organisation control and let build jobs install them with a token.
05

Getting started with GitHub Packages

Packages are reached from a GitHub repository or organisation, so anyone with an account can begin. The documentation says publishing, installing and deleting packages with a personal access token only works with classic tokens, while Actions workflows can use GITHUB_TOKEN for packages linked to their own repository.

A sensible first test is a workflow that publishes a container image or an npm package to the repository, followed by an install from a second project. The pages we read do not give a step by step tutorial for each format. Each account receives free storage and data transfer based on its plan, and without a valid payment method usage is blocked once the quota is used.

06

Strengths and limits of GitHub Packages

Where GitHub Packages earns its place
  • GitHub Packages hosts npm, RubyGems, Maven and Gradle, NuGet and container images, with permissions inherited from the repository or set per user.
  • Catalogue tag: Repository-linked.
  • Marked in our records as actions integration.
  • Best for: Teams whose code and CI already live in GitHub.
  • Marked in our records as plan-based storage.
GitHub Packages: limits
  • Without a valid payment method, usage is blocked when the included quota runs out, so private CI can stall.
  • Look elsewhere if you are Teams needing Python or Debian packages, which the documentation does not list.
  • Only classic personal access tokens work for publishing, installing and deleting outside Actions, which limits fine-grained credential policies.
07

Verdict: GitHub Packages

GitHub Packages hosts npm, RubyGems, Maven and Gradle, NuGet and container images, with permissions inherited from the repository or set per user.

Public packages cost nothing, while storage depends on plan: 500MB on Free, 2GB on Team and 50GB on Enterprise. Publishing outside Actions needs classic personal access tokens, and use stops at the quota when no payment method is on file.

GitHub Packages is entry #11 of 13 in the artifact repository managers list: the products next to it are GitLab Package Registry above and Azure Artifacts below. Established names take the places after the first three, in ranked order, and we give no numeric score.

The vendor states no country of establishment, so GitHub Packages is left out of the regional count for this list.

08

GitHub Packages pros and cons in practice

Works well
  • Public packages are free, according to the documentation.
  • Packages sit next to code, issues and Actions, with one permission model.
  • A global CDN serves downloads, according to the features page.
  • Version history, licence and download statistics are visible on each package.
Gets in the way
  • Storage is 500MB on the Free plan and 2GB on Team.
  • Only classic personal access tokens work for publishing, installing and deleting.
  • Without a valid payment method, usage is blocked once the quota is used up.
  • The formats listed are npm, RubyGems, Maven, Gradle, NuGet and Docker, a shorter list than several rivals.
09

What GitHub Packages costs

Charging model: Usage free for public packages; storage allowance by plan, with budgets controlling overage.

The pricing page lists three plans for Packages storage: Free with 500MB, Team with 2GB and Enterprise with 50GB, and it says public repositories are free. No data transfer figures appear on that page. The documentation adds that each account receives free storage and data transfer determined by its plan, that usage beyond the included amounts is controlled by budgets, and that without a valid payment method usage is blocked after the quota is used up. The features page lists GitHub Advanced Security, Copilot for business and Premium Support as add-ons without showing prices, so the cost of overage is not stated in the pages we read.

Where this comes from: the vendor pages at github.com, checked for Best Artifact Repository Managers in 2026 on 15 November 2026.

10

GitHub Packages in practice

The documentation lists npm, RubyGems, Apache Maven and Gradle, NuGet and Docker as supported registries, and the list names no Python or Cargo registry.

Downloads are served through a global CDN.

The terms are governed by United States federal law and California law, and no registered address or country is stated.

11

GitHub Packages: data and security

The GitHub terms name the company as GitHub, Inc. and say the terms are governed by United States federal law and the laws of the State of California. They do not state a registered address or country of establishment. Permissions are inherited from repositories or set per user or organisation.

The documentation notes that only classic personal access tokens work for publishing, installing and deleting packages, which affects how access is managed. The pages we read do not list certifications or data location options for the package service.

12

GitHub Packages integrations and ecosystem

Integrations the vendor names (9):

  • GitHub Actions
  • npm
  • RubyGems
  • Apache Maven
  • Gradle
  • NuGet
  • Docker
  • OCI images
  • Webhooks

Also in our records:

  • Catalogue tags that point to the ecosystem: Actions integration.
13

GitHub Packages fact sheet

ProductGitHub Packages
Vendor websitegithub.com
HeadquartersNot stated by the vendor
Not in our datauptime history and customer numbers
Catalogue tagsRepository-linked, Actions integration, Plan-based storage
Primary guideBest Artifact Repository Managers in 2026
Head-to-head pagesNo comparison written
Price visibilityA price or free offer is shown
Rank there#11 of 13
Alternatives pageNot part of the alternatives set
14

What to look at instead of GitHub Packages

4 products in this guide come closest to GitHub Packages on tags, pricing and region.

  • Gemfury (#2 of 13): Hosted package repositories for ten ecosystems, priced by collaborators or packages. Watch out: team plans cap private packages and Personal plans cap collaborators, so one of the two limits will bind as the organisation grows.
  • Bytesafe (#7 of 13): Dependency firewall that screens package requests before they install. Watch out: self-serve Cloud stops at three namespaces and 500 active users, so on-premise or larger setups move to the contract-priced Enterprise plan. (Sweden)
  • Sonatype Nexus Repository (#8 of 13): A good match for: Mid-sized engineering organisations needing HA, SSO and many formats in one product. (United States)
  • GitLab Package Registry (#10 of 13): Package registry bundled with GitLab projects and groups, in cloud or self-managed. Best for: Teams on GitLab who want packages governed by existing project roles.
15

Every guide that lists GitHub Packages

16

Questions about GitHub Packages

9 answers
How much does GitHub Packages cost?

Usage free for public packages; storage allowance by plan, with budgets controlling overage is how we record the pricing of GitHub Packages. On free access, we found no free tier.

Who should choose GitHub Packages?

Teams whose code and CI already live in GitHub. It does not fit as well for teams needing Python or Debian packages, which the documentation does not list.

Where is GitHub Packages based?

The vendor pages we reviewed state no country of establishment for GitHub Packages, so we do not give one.

How does GitHub Packages rank for artifact repository managers?

The artifact repository managers ranking has GitHub Packages at position 11 out of 13.

What else should I look at besides GitHub Packages?

The closest products in the same guide are Gemfury, Bytesafe, Sonatype Nexus Repository and GitLab Package Registry. You will find each one reviewed in the artifact repository managers ranking.

Are public packages free?

The documentation says GitHub Packages usage is free for public packages.

How much storage does the Free plan include?

The pricing page lists 500MB on Free, 2GB on Team and 50GB on Enterprise.

Which tokens can publish?

Classic personal access tokens, and GITHUB_TOKEN inside Actions workflows for the workflow's own repository.

Which company runs it?

GitHub, Inc.; the terms state US federal and California law but give no country of establishment.

17

GitHub Packages: sources

Read from the vendor’s own pages on 14 November 2026.

18

How we rank

We test for four things rather than for features: setup time, price in practice, exit and audience. The result for GitHub Packages: #11, out of 13 ranked. Details: how we rank software.