// the take
cacache-rs is a content-addressable disk cache for Rust, basically a port of zkat's JS cacache library that backs npm's own cache. It's aimed at tool authors — package managers, build systems, bundlers — who need correctness guarantees (dedup, hash verification) on cached blobs rather than a plain key-value store.
Content-addressable storage with automatic deduplication and multi-hash support (sha1, sha512, etc. side by side in one cache) is the right design for anything that needs integrity guarantees, not just storage. Subresource Integrity (SRI) support is built in, so you get spec-compliant hash verification instead of hand-rolling it. Feature flags let you pick async-std, tokio, or drop async entirely for a sync-only build, which matters if you're trying to keep a CLI tool's dependency tree small. It targets real disk-cache failure modes directly — atomic writes for large files, lockless concurrent access — rather than only handling the happy path.
There's no eviction policy: no TTL, no LRU, no max-size cap. `rm::all` wipes the whole cache, but staying under a size budget is entirely on the caller. async-std is the default runtime even though tokio is more commonly used in current Rust projects, so tokio users have to remember to disable default features or end up with two async runtimes in their dependency tree. The fault-tolerance and "lockless high-concurrency" claims in the README aren't backed by any visible benchmark or stress-test documentation in the repo — you're taking those on trust. Adoption is modest for infrastructure-level code (719 stars, 44 forks) compared to the JS sibling project it's based on, which has npm's entire user base exercising its edge cases.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →