Access to public github packages (maven) only with authentication #38939
Unanswered
bestlinuxgamers
asked this question in
Packages
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Select Topic Area
Product Feedback
Body
I have always wondered why I have seen github packages so little in use. Now that I've tried using github packages for my own project, I understand why this package distribution method is not an alternative for most public projects. The problem is that even with packages that are actually public, you have to authenticate to even download it. This authentication feature is of course great for private projects, but it seems that public projects were not considered when implementing it. Here everyone can download the files from the github website anyway. Nevertheless you have to authenticate yourself in the build-tool. This complicates the usage and weakens the user base of projects that use github packages as a distribution method, because most users don't want to go to the trouble of setting up the authentication in their project. This requires among other things that the github token is stored outside the project (e.g. in an environment variable) and this in turn hurts the project that uses a github package itself, because other people need to have a github account to work on the project and also have to go through the hassle of generating a token and writing it to an environment variable.
In general, github packages are really a great idea. But this little point, where I really absolutely don't understand why it exists like this, is a complete dealbreaker.
Beta Was this translation helpful? Give feedback.
All reactions