Gitlab hero border pattern left svg Gitlab hero border pattern right svg

Category Direction - Package Registry

Package Registry

Our goal is for you to rely on GitLab as a universal package manager, so that you can reduce costs and drive operational efficiencies. The backbone of this category is your ability to easily publish and install packages, no matter where they are hosted.

You can view the list of supported and planned formats in our documentation here.

This page is maintained by the Product Manager for Package, Tim Rizzi (E-mail)

What's Next & Why

We are currently focused on two epics for the GitLab Package Registry.

The first, gitlab-#2614, captures our plan to improve our existing integrations by expanding our existing product to include the creation, management and usage of remote and virtual repositories.

The second, gitlab-#2867 will move the Package Registry to GitLab Core, so you can rely on GitLab for all of your Package management needs, regardless of your pricing tier.

Maturity Plan

This category is currently at the "Viable" maturity level, and our next maturity target is "Complete" (see our definitions of maturity levels).

For a list of key deliverables and expected outcomes, check out the epic, gitlab-#2891, which includes links and expected timing for each issue.

Competitive Landscape

  GitLab Artifactory Nexus GitHub JetBrains
Composer ✔️ ✔️ ✔️️️️ - -
Conan ✔️ ✔️ ☑️ - -
Debian - ✔️ ✔️ - -
Maven ✔️ ✔️ ✔️ ️✔️ ️ ✔️
NPM ✔️ ✔️ ✔️ ✔️ -
NuGet ✔️ ✔️ ✔️ ✔️ -
PyPI ✔️ ✔️ ✔️ - -
RPM - ✔️ ✔️ - -
RubyGems - ✔️ ✔️ ✔️ -

☑️ indicates support is through community plugin or beta feature

Top Customer Success/Sales Issue(s)

Top Customer Issue(s)

Top Internal Customer Issue(s)

Top Vision Item(s)

Our top vision item is gitlab-#2614 which will add support for remote and virtual repositories.

GIT is a trademark of Software Freedom Conservancy and our use of 'GitLab' is under license