Open source implementation of the Turborepo custom remote cache server.
C-Rank Grade: A (Welcoming) - 68/100
External PR Merge Rate: 100%
Response Time: 11d
First Timer Success: 100%
ducktors/turborepo-remote-cache has a recorded first-timer success rate of 100.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in ducktors/turborepo-remote-cache respond to incoming external pull requests in approximately 264.1 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 67.7 places ducktors/turborepo-remote-cache in the A tier.
The external contributor pull request merge rate for ducktors/turborepo-remote-cache is 100.0%, based on public PR activity from non-core contributors.
ducktors/turborepo-remote-cache currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Open source implementation of the Turborepo custom remote cache server.
Active maintainer team in ducktors/turborepo-remote-cache welcoming community pull requests and bug fixes.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/ducktors/turborepo-remote-cache?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 17:00 UTC (17:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 16:00 to 20:00 UTC (16:00 - 20:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~172 hours (96% approval). Large PRs (>500 lines) take ~1267 hours (45% approval). Keep your diff compact for rapid review.
🚀 Feature Proposal Turborepo has a cachemaxage & cachemaxsize option, but sadly only for local cache. Motivation We've recently hit a cache size limit with our remote cache deployment (as we use Azure disk and didn't set up lifecycles), forcing us to manually clean the cache, would be nice if the server could also handle that similar to the options turborepo provides for local cache. Example Set through env variable, e.g. TURBO_REMOTE_CACHE_MAX_AGE=2w
Please read this entire template before posting any issue. If you ignore these instructions and post an issue here that does not follow the instructions, your issue might be closed, locked, and assigned the missing discussion label. 🚀 Feature Proposal It seems that currently uploads are buffered fully in memory before being uploaded to the storage. It would be better if they are streamed as they are uploaded. Motivation If you want to handle large cache artifacts you have to not only increase BODY_LIMIT but also the memory assigned to the server. This is not nice... Example You won't have to do anything special, you just won't need as much memory to handle large uploads.
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to ducktors/turborepo-remote-cache, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of ducktors/turborepo-remote-cache acknowledge new external contributions in approximately 11 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 100.0% were successfully merged into the primary branch.
ducktors/turborepo-remote-cache has a recorded first-timer success rate of 100.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~11 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 67.7 places ducktors/turborepo-remote-cache in the Welcoming tier.
The external pull request merge rate is 100.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, ducktors/turborepo-remote-cache currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for ducktors/turborepo-remote-cache are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.