Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for heavy Claude Code users who want more control over cache behavior and observability when session cost jumps do not match the visible work.
Who should use it
Who should skip it
Pass on cnighswonger/claude-code-cache-fix if its scope or audience does not match what your team is building right now.
About this signal
cnighswonger/claude-code-cache-fix is tracked by RepoRadar as a cli proxy in the Developer Tools section. It was first seen on 2026-06-30 and last updated on 2026-06-30. The current verdict is 'try now' with a Silver tier and moderate setup difficulty. cnighswonger/claude-code-cache-fix leads on workflow potential (9.4) and open-source/build quality (8.4); its lowest signal is maturity (5.8), so factor that in before investing setup time. This page summarizes the evidence RepoRadar has captured from captured source metadata. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.
How this item is evaluated
RepoRadar assigned cnighswonger/claude-code-cache-fix a composite score of 7.9 out of 10, placing it in the Silver tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 1.0 and never affects the composite score or tier. The risk label of 'conditional' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
Putting this into practice? Read How to evaluate an AI tool before you adopt it for the checklist behind this score.
Risk explanation
It sits in the middle of Claude Code API traffic and can observe prompts, context, and responses, so run it only on a machine and repo you trust; It changes the request path between Claude Code and Anthropic, so benchmark one controlled workflow before treating its cache metrics as policy.