Seamless multi-primary syncing database with an intuitive HTTP/JSON API, designed for reliability
C-Rank Grade: A (Welcoming) - 62/100
External PR Merge Rate: 50%
Response Time: 14h
First Timer Success: 67%
apache/couchdb has a recorded first-timer success rate of 66.7%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in apache/couchdb respond to incoming external pull requests in approximately 14.3 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 61.7 places apache/couchdb in the A tier.
The external contributor pull request merge rate for apache/couchdb is 50.0%, based on public PR activity from non-core contributors.
apache/couchdb currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in apache/couchdb. Reviews community pull requests with focus on project quality.
Discussions in apache/couchdb focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
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/apache/couchdb?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 13:00 UTC (13:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 13:00 to 17:00 UTC (13:00 - 17:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~9 hours (62% approval). Large PRs (>500 lines) take ~69 hours (22% approval). Keep your diff compact for rapid review.
Since OTP29, there will be a warning when using the catch operator, which has been deprecated for a long time. It is recommended to instead use try…catch. Here is a list of locations, where only a catch ... is used (commit 75a77a7): src/proper/src/proper_statem.erl:770:46: Warning: 'catch ...' is deprecated; please use 'try ... catch ... end' instead. src/couch_epi/src/couch_epi_module_keeper.erl:59:5: Warning: 'catch ...' is deprecated; please use 'try ... catch ... end' instead. src/couch_epi/src/couch_epi_functions_gen.erl:343:10: Warning: 'catch ...' is deprecated; please use 'try ... catch ... end' instead. src/couch_epi/src/couch_epi_functions_gen.erl:352:6: Warning: 'catch ...' is deprecated; please use 'try ... catch ... end' instead. src/couch_log/src/couch_log_trunc_io.erl:99:10: Warning: 'catch ...' is deprecated; please use 'try ... catch ... end' instead. src/couch_log/src/couch_log_trunc_io_fmt.erl:291:10: Warning: 'catch ...' is deprecated; please use 'try ... catch ..
Provide a brief overview of what the new feature is all about If a _view has an impossible start_key/end_key combination we send a helpful error; {"error":"query_parse_error","reason":"No rows can match your key range, reverse your start_key and end_key or set descending=false","ref":457284027} We should do the same for _all_docs Tell us how the new feature should work. Be specific A similar check_range function when parsing query params of _all_docs calls, returning a 400 status code and the same error reason as for _view. Not required. Suggest how to implement the addition or change No response Additional Context No response
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 apache/couchdb, 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 apache/couchdb acknowledge new external contributions in approximately 14 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 50.0% were successfully merged into the primary branch.
apache/couchdb has a recorded first-timer success rate of 66.7%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~14 hours. 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 61.7 places apache/couchdb in the Welcoming tier.
The external pull request merge rate is 50.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, apache/couchdb currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for apache/couchdb 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.