Github Package Registry Reviews & Product Details

I can now find a unified view of the whole software development lifecycle after a merge to mater is done in one place.

Previously we had 3 apps for the flow, and on top, we had multiple Registries. This was a little tedious going back and forth to apps.

Now, we can track the lifecycle in one view with GitHub Package Registry and GitHub action.

GitHub Package Registry helps us to maintain one registry for all our needs. This has been game-changing.

Users with write access to the repo can only publish to the registry has made things very smooth. Review collected by and hosted on G2.com.

GitHub Package Registry really serves the purpose. To date, we did not face any significant problems with the platform.

Particularly for Maven, we observed vulnerabilities are not listed in the public packages. Review collected by and hosted on G2.com.

As a developer, GitHub Package registery provides the flexibility in development by providing access supports like Docker and also this is the best known platform for high optimisation of your development. Review collected by and hosted on G2.com.

There's nothing to dislike about GitHub Package registery but still I would say that there can be more commands available for more flexibility. Review collected by and hosted on G2.com.

It's in the same page as the code and you can publish and consume from your GitHub account instead of 2 accounts Review collected by and hosted on G2.com.

Complicated to publish and consume worth yarn and yarn2+ Review collected by and hosted on G2.com.

1. Since Github Package Registry supports multiple packages formats, it is easy to collaborate with them in a single place.

2. The Acces control feature enables you to provide limited or restricted access only to people whom you want.

3. Easy to use Review collected by and hosted on G2.com.

1. The pricing is a little off.

2. CI CD pipelining can be better. Review collected by and hosted on G2.com.

1. When we talk about admin controls it's best we have many options like read, write admin control features

2. It supports multiple package formats

3. Tracking of commits is easy Review collected by and hosted on G2.com.

GitHub Package Registry is good but a bit complicated if you are a beginner we will get used to it once used for few days Review collected by and hosted on G2.com.

GitHub Package Registry is home for storing the libraries of Java, Nuget, Ruby, npm Packages, and Docker Images. The native feature in GitHub helps teams quickly upload the packages. Read, Write, and Admin Permissions for the Packages are well thought out for the simplicity of managing them. Easily helps with authentication when using GitHub Actions using GITHUB_TOKEN Review collected by and hosted on G2.com.

Generic Package is not yet supported and maybe we can have support for Conan, Hex, swift, helm, and other such know packages.

RBAC governance will be good to have feature. Review collected by and hosted on G2.com.

it lets you keep your packages right in your repo and organization Review collected by and hosted on G2.com.

Not sure, but in my perspective as a mule developer building pipelines is too confusing. Review collected by and hosted on G2.com.

It is verey useful to track who is committed the code and maintain the code

And we cam create branches based on our need Review collected by and hosted on G2.com.

As per my knowledge there is know history data if it took more then 2 ro 3 months Review collected by and hosted on G2.com.

Fastest way to upload packages for multiple managers such as maven, npm, gem.

DevOps Ready with GitHub Actions.

Better Insights/Analytics of package downloads. Review collected by and hosted on G2.com.

Only allows scoped npm packages.

Not possible to have self hosted packages. Review collected by and hosted on G2.com.

As an organization, this tool is very beneficial for the developers as they are working on many tech stacks and on each tech stack they are dealing with packages so with the GitHub package registry they don't have to give the source code to other developers they simply just have to package the code and upload it to the GitHub package registry and they can say share the password and give to any person in the world for the usage. Review collected by and hosted on G2.com.

As far as I am using the GitHub package registry I and my organization didn't find any flaws just one thing i noticed while using this is that person who is using it for the first time it's a bit hard for them so need to improve a bit on documentation side. Review collected by and hosted on G2.com.