🌐
GitHub
docs.github.com › en › packages › learn-github-packages › introduction-to-github-packages
Introduction to GitHub Packages - GitHub Docs
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.
Home
Get started, troubleshoot, and make the most of GitHub. Documentation for new users, developers, administrators, and all of GitHub's products.
Npm registry
You can configure npm to publish packages to GitHub Packages and to use packages stored on GitHub Packages as dependencies in an npm project.
Docker registry
The Docker registry has now been replaced by the Container registry.
Container registry
You need an access token to publish, install, and delete private, internal, and public packages. You 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 ...
🌐
GitHub
docs.github.com › en › packages
GitHub Packages documentation - GitHub Docs
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.
Discussions

What is GitHub Packages storage for?
When in doubt read the docs. https://docs.github.com/en/packages/learn-github-packages/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. More on reddit.com
🌐 r/github
3
0
February 4, 2025
GitHub Package Registry

Reposting my comment about this from r/node/

This is fascinating to me. Github could never have done this without Microsoft, and developers would never have adopted this if Microsoft did it.

Currently NPM (the company) has a business model which relies mainly on selling to enterprise customers (surely not all their business, but most likely the bulk).

Microsoft is the best poised company in the market to eat their lunch, because enterprise is Microsoft’s core competency. Think what you will of the company and its relevancy today, but they have deep experience selling to enterprise, and preexisting relationships with many enterprises.

What does Microsoft hope to get from this though? Surely its a small line of business, and wont make Github all that much money. Github has a relationship primarily with individual developers first and foremost, that is their target market. Those devs influence their employer’s decision to pay for GitHub because the devs want to use what they’re familiar with. So that relationship with individual devs is really Github’s bread and butter.

Well, I think thats exactly what Microsoft hopes to get; that virtuous cycle of making a product that is loved and widely adopted by individuals and then championed by by those individuals within their organizations. Similar to Slack’s growth model, and also Zoom’s.

Its no secret Microsoft is trying to win back the common developer. At a time when apple is fumbling on caring about devs (re: escape key), and AWS has become the default for cloud production, there is a real opportunity to be the company that makes development better for devs. If Microsoft ever wants to succeed in Cloud, they need to win back developers by having services which are genuinely better and friendlier to use. If they can become the default choice for developers in certain areas (VSCode, Github) and then make it dead simple to integrate with their cloud services, thats a compelling reason for individuals to use their services. And if its actually better (clearly no one is a delighted by the AWS interface) then Azure could become some folks preference for their personal work. And with those services being available where your company already hosts its code and does it developing, Github, then all the better.

Microsoft made a very smart move acquiring Github, and I think they will take great care not to upset the common developer as that is the lifeblood of this whole cycle.

Note, I said common developer. There is a lot of mistrust of Microsoft among the Hacker News and silicon valley crowd. There are definitely valid concerns held by folks at the upper percentile of developers, who tend to both take a longer view and are more cynical (to put it nicely). But thats not the vast majority of devs. Most devs don’t work at FAANG, or live somewhere on the west coast. Most work at smaller companies around the world. Github/Microsoft only need to appeal to most devs.

I wasn’t sure what Microsoft would do to capitalize on their Github acquisition. But this is a great start. There is a lot of drama around npm the company, and their interests are no longer aligned with the common developer. There really are problems there that Github can solve.

GitHub can afford to prioritize the common dev with Microsoft’s help. GitHub already has a great reputation in the open source community, and they are certainly a safer bet for longevity and keeping your package publicly available than npm.

Anyway, I’ve been reading too much Stratechery it seems!

TLDR; This is npm the company’s current business model. Microsoft is way better at enterprise than almost anyone, certainly npm the company. npm’s interests are no longer aligned with common devs, but GitHub’s certainly are and Microsoft is willing to pay to make sure it can stay that way.

Also note: NPM is really at least 3 things. The package registry, which is a public database of all the packages in the JS ecosystem. The website frontend to find packages. The npm cli, which is an open source project. And lastly npm, Inc the company, founded in 2014, who foots the bill for the public registry. I love the npm ecosystem and the people who build the tools, but Im not so hot on the company, since they are essentially rent seeking.

More on reddit.com
🌐 r/javascript
47
242
May 10, 2019
How to use the GitHub Package Registry

This has potential to be really awesome for enterprise development. My previous employer had a number of internal registry systems for docker, pip, maven, and npm. Getting all of that in one and integrated with your source code could be great

More on reddit.com
🌐 r/programming
5
3
October 5, 2019
GitHub Package Registry: Your packages, at home with their code

What no Python?

More on reddit.com
🌐 r/github
4
20
May 11, 2019
🌐
GitHub
github.com › orgs › community › packages
Packages · GitHub Community · GitHub
A free and open source package manager used for the Microsoft development platforms including .NET.
🌐
GitHub
docs.github.com › en › packages › learn-github-packages
Learn GitHub Packages - GitHub Docs
You can find out more about using packages in GitHub, including viewing and installing existing packages, publishing new packages to GitHub Packages, and, in special circumstances, deleting packages.
🌐
GitHub
docs.github.com › en › packages › learn-github-packages › viewing-packages
Viewing packages - GitHub Docs
You can find and view a package located in a particular repository. On GitHub, navigate to the main page of the repository.
🌐
GitHub
github.blog › home › developer skills › 5 simple things you can do with github packages to level up your workflows
5 simple things you can do with GitHub Packages to level up your workflows - The GitHub Blog
August 23, 2022 - GitHub Packages connects to your industry and community-standard package managers including npm, Gradle, Maven, RubyGems, NuGet, and even Docker and OCI for containers to help centralize your development workflows on GitHub.
🌐
GitHub
docs.github.com › en › packages › quickstart
Quickstart for GitHub Packages - GitHub Docs
You can view all of the packages you have published. On GitHub, navigate to the main page of the repository.
Find elsewhere
🌐
GitHub
docs.github.com › en › billing › concepts › product-billing › github-packages
GitHub Packages billing - GitHub Docs
Learn how usage of GitHub Packages is measured against your free allowance and how to pay for additional use.
🌐
Microsoft Learn
learn.microsoft.com › en-us › training › modules › introduction-github-packages
Introduction to GitHub Packages - Training | Microsoft Learn
This module introduces you to GitHub Packages, a package hosting service fully integrated with GitHub. Learn how to publish packages from repositories, install packages in projects, manage package lifecycle through deletion and restoration, ...
🌐
GitHub
docs.github.com › en › packages › learn-github-packages › publishing-a-package
Publishing a package - GitHub Docs
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. A repository can be connected to more than one package.
🌐
GitHub
github.com › github-packages-examples
github-packages-examples · GitHub
github-packages-examples has 12 repositories available. Follow their code on GitHub.
🌐
GitHub
docs.github.com › en › packages › learn-github-packages › installing-a-package
Installing a package - GitHub Docs
You can install a package from GitHub Packages and use the package as a dependency in your own project.
🌐
GitHub
docs.github.com › en › packages › working-with-a-github-packages-registry › working-with-the-npm-registry
Working with the npm registry - GitHub Docs
You can configure npm to publish packages to GitHub Packages and to use packages stored on GitHub Packages as dependencies in an npm project.
🌐
GitHub
docs.github.com › en › packages › working-with-a-github-packages-registry › working-with-the-container-registry
Working with the Container registry - GitHub Docs
You need an access token to publish, install, and delete private, internal, and public packages. You 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 ...
🌐
GitHub
docs.github.com › en › packages › working-with-a-github-packages-registry › working-with-the-apache-maven-registry
Working with the Apache Maven registry - GitHub Docs
You need an access token to publish, install, and delete private, internal, and public packages. You 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.
🌐
GitHub
docs.github.com › en › packages › learn-github-packages › about-permissions-for-github-packages
About permissions for GitHub Packages - GitHub Docs
For packages scoped to an organization, you can give any person or team in the organization an access role. If you are using a GitHub Actions workflow to manage your packages, you can grant an access role to the repository the workflow is stored in by using the Add Repository button under "Manage Actions access" in the package's settings.
🌐
GitHub
docs.github.com › en › packages › learn-github-packages › connecting-a-repository-to-a-package
Connecting a repository to a package - GitHub Docs
If you connect a package to a repository, the package's landing page will show information and links from the repository, such as the README. You can also choose to have the package inherit its access permissions from the linked repository. For more information, see Configuring a package's access control and visibility. On GitHub, navigate to the main page of your personal account.