Public package sources
Use familiar public sources for PyPI, npm, and Maven through a private Ravenstash URL.
Use supported public registries or connect an external PyPI, npm, or Maven repository, whether it is public or protected by authentication. Access the cache directly or place it upstream of a private repository.
package manager -> private Ravenstash URL
package request -> approved source
first download -> fetched and cached
repeat download -> served fasterGive developers and CI one authenticated Ravenstash URL while keeping external package sources behind a controlled cache.
Choose a supported public registry or connect your own package source.
Add source credentials when the external repository requires them.
Use its private URL directly or connect it to one of your private repositories.
Ravenstash fetches packages on demand and keeps repeat installs fast.
Use familiar public sources for PyPI, npm, and Maven through a private Ravenstash URL.
Connect an external package repository with or without source authentication.
Give the cache its own private package-manager URL for a clean, read-only dependency endpoint.
Connect the cache behind a matching PyPI, npm, or Maven repository without changing normal install commands.
Packages are retrieved when requested and kept ready for faster repeat builds.
Review cached packages, connected repositories, downloads, storage, and recent activity.
Connect the sources your team already uses and keep the developer workflow simple.
Yes. A custom cache can connect to a public or private HTTPS package repository. Add source credentials when the external repository requires authentication.
Yes. Every cache can provide its own private package-manager URL, and it can also be connected as an upstream to one or more private repositories.
No. Ravenstash retrieves package content as it is requested and keeps cached copies for repeat installs.