Production-ready C++ Asynchronous Framework with rich functionality
C-Rank Grade: D (Risky) - 30/100
External PR Merge Rate: -
Response Time: 7d
First Timer Success: -
userver-framework/userver has a recorded first-timer success rate of 0.0%. Repositories ranked D typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in userver-framework/userver respond to incoming external pull requests in approximately 161.6 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 29.8 places userver-framework/userver in the D tier.
The external contributor pull request merge rate for userver-framework/userver is 0.0%, based on public PR activity from non-core contributors.
userver-framework/userver currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly encouraging & supportive maintainers (100% positive review sentiment). Active code reviews with constructive guidance for new contributors in userver-framework/userver.
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/userver-framework/userver?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 09:00 UTC (09:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 09:00 to 13:00 UTC (09:00 - 13:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~105 hours (81% approval). Large PRs (>500 lines) take ~776 hours (29% approval). Keep your diff compact for rapid review.
Summary Currently, userver's testing story has a gap when it comes to testing code that depends on real external services (PostgreSQL, MongoDB, Redis, etc.): Unit tests (utest) require mocks that may diverge from real service behavior Functional tests (testsuite) require pre-installed database binaries on the host system, which makes them impractical in many environments This feature request is to provide utest integration with testcontainers-native - the C/C++ adapter for Testcontainers - so that developers can spin up real services via Docker directly from utest-based tests, without any pre-installed binaries. Motivation A common complaint from the userver community (paraphrased from community discussions): "I really miss being able to work with Docker instead of binaries. Because setting it up is so much work, I end up writing unit tests with mocks instead. Testsuite doesn't work out of the box for me - I have no PostgreSQL, MongoDB or other DB binaries locally, especially not m
Add a description Replacing socket to engine::io::Socket something here shuld help to remove threads here and remove dedicated event loop This work seems to be hard due to leads to rewrite a big part of curl-ev
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 userver-framework/userver, 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 userver-framework/userver acknowledge new external contributions in approximately 6 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 0.0% were successfully merged into the primary branch.
userver-framework/userver has a recorded first-timer success rate of 0.0%. Repositories ranked Risky typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~6 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 29.8 places userver-framework/userver in the Risky tier.
The external pull request merge rate is 0.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, userver-framework/userver 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 userver-framework/userver 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.