Private packages

The public rrepo registry is available to anyone through rpx. Private package hosting starts with an organization in the dashboard.

Create an organization when your team needs private package repositories.

Dashboard setup

In the dashboard, create a repository for your organization and upload package source tarballs. Create an API key with package read access for developers or CI jobs that install private packages.

Repository URLs use rrepo.dev in production:

https://<org-slug>.rrepo.dev/<repo-slug>

Add the repository

Run this from the project root:

rpx repo add https://<org-slug>.rrepo.dev/<repo-slug>

See Repositories for repository ordering, fallback repositories, and default registry behavior.

Then add the private package like any other dependency.

rpx add internalpkg

Authenticate

When a private repository needs an API key, rpx prompts in the terminal and stores the key securely for that repository URL.

Use a packages:read key for installs. Use a packages:write key only for publishing workflows.