Repositories & Caching
Model upstream mirrors and pull-through caching so installs are fast, reproducible, and survive an upstream outage.
Chainsaw is a pull-through cache as well as a firewall. Every repository you define maps an ecosystem (npm, PyPI, Maven, …) to one or more upstream mirrors and caches the artifacts it fetches on your network. That gives you faster installs, reproducible builds, and continuity when an upstream registry is slow or down — all while every fetch still passes through policy.
Repository and cache management come first; the per-ecosystem cards below give focused, copy-paste pages for pointing a single client at Chainsaw. For the combined reference covering every ecosystem (plus Gradle, CocoaPods, Swift PM, and sbt), see How to Configure Your Package Manager to Use Chainsaw.
Where to next
Repositories are configured during install — see Getting Started if you have not deployed the proxy yet. To watch cache and traffic behavior in production, see Monitoring & Compliance.