- Package workflows
- View packages
- Authenticate with the registry
- Use GitLab CI/CD
- Reduce storage usage
- Disable the Package Registry
- Package Registry visibility permissions
- Accepting contributions
Moved from GitLab Premium to GitLab Free in 13.3.
With the GitLab Package Registry, you can use GitLab as a private or public registry for a variety of supported package managers. You can publish and share packages, which can be consumed as a dependency in downstream projects.
Learn how to use the GitLab Package Registry to build your own custom package workflow:
Use a project as a package registry to publish all of your packages to one project.
Publish multiple different packages from one monorepo project.
You can view packages for your project or group.
- Go to the project or group.
- Go to Deploy > Package Registry.
You can search, sort, and filter packages on this page. You can share your search results by copying and pasting the URL from your browser.
You can also find helpful code snippets for configuring your package manager or installing a given package.
When you view packages in a group:
- All projects published to the group and its projects are displayed.
- Only the projects you can access are displayed.
- If a project is private, or you are not a member of the project, it is not displayed.
For information on how to create and upload a package, view the GitLab documentation for your package type.
Authentication depends on the package manager being used. For more information, see the docs on the specific package format you want to use.
For most package types, the following credential types are valid:
- Personal access token: authenticates with your user permissions. Good for personal and local use of the package registry.
- Project deploy token: allows access to all packages in a project. Good for granting and revoking project access to many users.
- Group deploy token: allows access to all packages in a group and its subgroups. Good for granting and revoking access to a large number of packages to sets of users.
- Job token: allows access to packages in the project running the job for the users running the pipeline. Access to other external projects can be configured.
- If your organization uses two factor authentication (2FA), you must use a personal access token with the scope set to
- If you are publishing a package via CI/CD pipelines, you must use a CI job token.
You can use GitLab CI/CD to build or import packages into a package registry.
For Maven, NuGet, npm, Conan, Helm, and PyPI packages, and Composer dependencies, you can
authenticate with GitLab by using the
CI/CD templates, which you can use to get started, are in this repository.
For more information about using the GitLab Package Registry with CI/CD, see:
If you use CI/CD to build a package, extended activity information is displayed when you view the package details:
You can view which pipeline published the package, and the commit and user who triggered it. However, the history is limited to five updates of a given package.
If you already have packages built in a different registry, you can import them into your GitLab package registry with the package importer.
For a list of supported packages, see Importing packages from other repositories.
For information on reducing your storage use for the Package Registry, see Reduce Package Registry storage use.
The Package Registry is automatically enabled.
If you are using a self-managed instance of GitLab, your administrator can remove the menu item, Packages and registries, from the GitLab sidebar. For more information, see the administration documentation.
You can also remove the Package Registry for your project specifically:
- In your project, go to Settings > General.
- Expand the Visibility, project features, permissions section and disable the Packages feature.
- Select Save changes.
The Deploy > Package Registry entry is removed from the sidebar.
Project-level permissions determine actions such as downloading, pushing, or deleting packages.
The visibility of the Package Registry is independent of the repository and can be controlled from your project’s settings. For example, if you have a public project and set the repository visibility to Only Project Members, the Package Registry is then public. Disabling the Package Registry disables all Package Registry operations.
|Project visibility||Action||Minimum role required|
|Public||View Package Registry||
|Public||Publish a package||Developer|
|Public||Pull a package||
|Internal||View Package Registry||Guest|
|Internal||Publish a package||Developer|
|Internal||Pull a package||Guest (1)|
|Private||View Package Registry||Reporter|
|Private||Publish a package||Developer|
|Private||Pull a package||Reporter (1)|
Introduced in GitLab 15.7.
To allow anyone to pull from the Package Registry, regardless of project visibility:
- On the left sidebar, select Search or go to and find your private or internal project.
- On the left sidebar, select Settings > General.
- Expand Visibility, project features, permissions.
- Turn on the Allow anyone to pull from Package Registry toggle.
- Select Save changes.
Anyone on the internet can access the Package Registry for the project.
- You must be an administrator.
To hide the Allow anyone to pull from Package Registry toggle globally:
Change the application setting
Anonymous downloads are disabled, even for projects that turned on the Allow anyone to pull from Package Registry toggle.
Several known issues exist when you allow anyone to pull from the Package Registry:
- Project-level endpoints are supported. Group-level and instance-level endpoints are not supported. Support for group-level endpoints is proposed in issue 383537.
- It does not work with the Composer, because Composer only has a group endpoint.
- It works with Conan, but using
conan searchdoes not work.
This table lists unsupported package manager formats that we are accepting contributions for. Consider contributing to GitLab. This development documentation guides you through the process.