GitCache

GitCache

Speed up builds by caching Git dependencies

3 followers

Visit website
GitCache (CLI + proxy) adds the missing cache layer for Git-hosted dependencies. It caches and servesgit URLs from package.json so CI reuses built artifacts instead of recloning and rebuilding packages every run saving time and bandwidth, and actions minutes
GitCache gallery image
GitCache gallery image
GitCache gallery image
Free
Launch tags:Software Engineering•Developer Tools•GitHub
Launch Team
Wispr Flow: Dictation That Works Everywhere
Wispr Flow: Dictation That Works Everywhere
Stop typing. Start speaking. 4x faster.
Promoted

What do you think? …

Michael Smith
Maker
📌
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.