Upstream cache

Ravenstash private repositories can configure upstream read-through for supported PyPI, npm, and Maven misses.

How it works

1. A package client requests a package from a private Ravenstash repository.
2. Ravenstash checks the private repository first.
3. If there is an upstream entry and the miss is allowed by policy, Ravenstash resolves the official upstream.
4. Cold artifact file requests enqueue Ravenstash-managed cache population.
5. Warm artifacts are served from Ravenstash remote storage through the private repository access flow.

Minimum age

Repositories send a minimum-age value for the attached upstream. Maven uses Maven Central Last-Modified data when available. PyPI and npm enqueue bounded recent-version ingest on metadata misses.

Remote-cache visibility

The app exposes remote repository and remote package pages for cache contents, attached private repositories, download counts, bandwidth usage, and cache-removal actions.

Current status

This is not a public anonymous mirror and not bulk preseeding. It is private-repository upstream fallback with bounded cache population.