GitCache

I realized that all of our JavaScript package tools have a missing cache layer for when you really want to use a .git host as the source of your package. Developers use .git URLs to pin exact commits, pull private repos, or reference monorepo subpackages — patterns that are convenient but brittle at scale. In CI this becomes painful: every pipeline clones, installs, and often rebuilds those packages anew, which wastes time, blows up CI minutes, and makes builds flaky when the upstream host is slow or rate-limited. GitCache is my answer: a lightweight CLI + proxy that transparently caches .git-hosted packages and serves pre-built artifacts to package managers. Instead of recloning and rebuilding on every run, CI reuses cached artifacts (or a locally served proxy) so installs are fast, repeatable, and resilient to upstream outages. It supports private repos and monorepos, and is intentionally low-friction to adopt. One-time setup, secure by default, and no changes to how you write dependencies in package.json.