Skip to content

Private npm registry quickstart

Ravenstash exposes npm-compatible package data, version data, tarballs, and registry ping routes for private packages.

When a repository supports multiple ecosystems, its npm packages, URLs, usage, and upstream settings remain separate from PyPI and Maven.

  • Scoped and unscoped packages.
  • JavaScript, TypeScript, Node.js, and WebAssembly packages distributed through npm conventions.
  • Authenticated npm publish uploads.
  • Package, version, and tarball downloads.
  • npm, pnpm, Yarn, and Bun-compatible registry configuration.
  • An optional private npmjs.org mirror with security scanning and minimum package age.
  1. Create a package repository with npm enabled, or add npm to an existing repository.
  2. Sign in with rvs and select the repository.
  3. Configure and publish the package.
  4. Configure the private registry and install.
  5. Confirm the package and tarball appear in Ravenstash.

The examples use:

Owner: acme
Repository: packages
Download: https://npm.rvsta.sh/in_wsabc123/r_repo1234/
Upload: https://push.npm.rvsta.sh/in_wsabc123/r_repo1234/