Skip to content

Why do public packages need authentication? #25979

Discussion options

You must be logged in to vote

@meetmangukiya,

However, this still doesn’t allow people to add this package as dependency and be able to build their project without a token, right?

Right. Packages are only accessible to GitHub accounts via a PAT, they’re not completely public. They’re really geared towards private dependencies not public dependencies (like npmjs.com or NuGet.com is).

You might want to use them for dependencies between repositories, when a package isn’t ready to be published to a public repository yet.

Does that make sense?

Replies: 3 comments

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Answer selected
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Packages Host your dependencies, libraries, and production-ready code, right from your repository Product Feedback
2 participants