For R teams
Reproducible R package environments with rpx
rrepo exposes the package metadata rpx needs to resolve compatible R dependency sets. Use the public registry today, or create an organization to host private packages for your team.
Why teams use it
A package workflow that starts before download
rpx resolves against rrepo metadata, writes a lockfile, and syncs an isolated project library so R projects can stay reproducible without global library drift.
- Resolve before installingrrepo exposes package metadata that rpx uses to choose compatible dependency versions before downloading package archives.
- Local project librariesrpx creates an isolated library for each project and runs R commands inside that environment with rpx run.
- Private packages for teamsUse the public registry today, or create an organization to publish private packages through repositories and API keys.
Use the public registry now, add private packages when your team needs them
Start with rpx for public R package dependencies. Create an organization when you want repositories, dashboard uploads, and private package API keys.