Manage a repository
The repository page has one tab for each area. Content from every enabled format appears together and can be filtered by format.
| Tab | What you do there |
|---|---|
| Contents | Browse packages, versions, and files, and container image and Helm chart paths with their tags, digests, and manifests. Filter by format, see which source supplies each package, upload files, and open the trash. |
| Upstreams | Connect private mirrors and other private repositories to a PyPI, npm, or Maven format, and set their order and package age. |
| Rules | Set package resolution rules for PyPI, npm, and Maven packages. |
| Quick start | Copy the package-tool setup and commands for each enabled format. |
| Protection | Review Package Protection results, quarantined versions, and policies. |
| Metrics | Review storage and delivery over time. |
| Access | See and grant access to the repository. Shown for organization repositories. |
| Settings | See the repository’s name-based and ID-based targets, enable or remove package formats, rename the repository, or delete it. |
Upstreams, Rules, and Protection appear when the repository has a format that supports them.
Personal owners can change everything. In an organization, what you can do depends on your repository role: Reader views and downloads, Publisher also publishes, Maintainer also deletes versions and manages upstreams, Protection, and access, and Admin also changes settings and deletes the repository. Organization administrators, and namespace administrators in their namespaces, have full access.
Open the repository’s Upstreams tab to connect upstreams and private mirrors, and its Rules tab to choose which of those upstreams can supply specific PyPI, npm, and Maven packages.
Open the repository’s Access tab to see your access, the roles on this repository, roles inherited from the organization and namespace, and everyone who can use it. Maintainers and Admins can grant access to this repository there; broader grants are changed where they were made. See Roles and grants.
For shared automation, use an organization-owned API token.