Ravenstash CLI

Private package workflows from your terminal.

Sign in through your browser, choose a personal or organization repository, and use your existing package tools without managing registry credentials by hand.

MIT licensed · Ubuntu 20.04+ and Debian 11+ · Linux amd64

  █████████████████████████▄▄▄
  █████████████████████████████▄▄
  ████████████████████████████████▄
  █████████████████████████████████▄
  ██████████████████████████████████▄
  ███████▀▀▀▀▀      ▀▀███████████████▄
  ████████▀      ▄▄▄▄   ▀▀▀███████████
  ██████▀         ▀▀         ▀████████
  ████▀                  ▄▄▄▄▄▄███████
  ███▀               ▄███████████████▀
  ██▀               ████████████████▀
  ▀▀               ▄███████████████▀
                   ▀█████████████▀
                    ██████████▀▀
                     █████████
                      ▀████████▄
                       ▀████████▄
                        ▀████████▄
                          █████████
                           ▀▀███████
                                ▀▀▀██▄

              RAVENSTASH

Install rvsbash

curl -fsSL https://ravenstash.com/install.sh | bash

One-command install

Install once, then sign in through your browser

The installer verifies Ravenstash's APT signing key and installs the current rvs package.

rvs auth login --profile work
rvs account use org:acme
rvs art select platform/backend
rvs context current

Install from a private repository or mirrorbash

rvs art select platform/backend
rvs pip install internal-lib

rvs art mirror select pypiorg
rvs pip install requests

Update safelybash

rvs update
rvs update --apply

The installer source is available directly at ravenstash.com/install.sh. Review it before running if your environment requires installer auditing. Updates continue through the signed APT repository. System unattended-upgrades update rvs when an administrator allows the Ravenstash origin in that system's policy.

Developer workflow

One CLI around the tools your team already uses

rvs adds Ravenstash authentication and a clear repository or mirror selection without replacing familiar ecosystem clients.

Local profiles and accounts

Sign in through the browser, keep independent CLI configurations in named local profiles, and choose a personal or organization account for each terminal.

Clear active repository

Choose a private repository or mirror once, then keep the effective local profile, acting account, and selection visible in your shell prompt.

Native package tools

Run pip, uv, Twine, npm, Maven, Docker, Helm, and ORAS with temporary Ravenstash authentication while those tools keep their familiar behavior.

Developer runtimes

Install and select Python, Node.js, and Java versions for a project from the same developer CLI.

Start in the terminal

Install rvs and keep every package command on the right repository.

Use browser login for local development, choose a personal or organization repository or mirror, and keep CI consistent with automation tokens.

Read the CLI docs