Keycloak Benchmark
C-Rank Grade: B (Solid) - 72/100
External PR Merge Rate: 96%
Response Time: <1h
First Timer Success: 100%
keycloak/keycloak-benchmark has a recorded first-timer success rate of 100.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in keycloak/keycloak-benchmark respond to incoming external pull requests in approximately 0.5 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 72.2 places keycloak/keycloak-benchmark in the B tier.
The external contributor pull request merge rate for keycloak/keycloak-benchmark is 95.7%, based on public PR activity from non-core contributors.
keycloak/keycloak-benchmark currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active maintainer team in keycloak/keycloak-benchmark 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/keycloak/keycloak-benchmark?utm_source=github&utm_medium=badge)
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 11:00 UTC (11:00 UTC in your timezone). Recommended submission window is Monday - Thursday from 09:00 to 13:00 UTC (09:00 - 13:00 UTC local).
Limited recent maintainer review activity recorded for this repository. Prediction based on heuristic baseline.
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (96% approval). Large PRs (>500 lines) take ~2 hours (43% approval). Keep your diff compact for rapid review.
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
Alternative open-source projects with active maintainers in Java.
Android app (and widget collection) that displays sunlight and moonlight times.
A fast and easy to use linear algebra library written in Java for dense, sparse, real, and complex matrices.
A cross-platform G-Code sender for GRBL, Smoothieware, TinyG and G2core.
Describe the bug When running the Keycloak benchmark scenario keycloak.scenario.admin.CreateUsers, the CLI parameter --client-id is not correctly applied. The scenario appears to use a hardcoded client_id=gatling when requesting a service account token, even though --client-id=client-0 is provided. This results in a 401 invalid_client error because Keycloak receives a client id that does not exist (or does not match the provided secret). Version 26.4.7 Expected behavior The request should use the client id passed via CLI: Expected form body: grant_type=client_credentials&client_id=client-0&client_secret=client-0-secret And the scenario should proceed to create users instead of failing at token acquisition. Actual behavior Benchmark fails with 401 when requesting token. Log shows it uses client_id=gatling instead of the CLI value (client-0): POST https://login-staging.vecko.dev/realms/benchmark/protocol/openid-connect/token ... body: grant_type=client_credentials&client_id=gatling&clien
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 keycloak/keycloak-benchmark, 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 keycloak/keycloak-benchmark acknowledge new external contributions in approximately <1 hour. Out of all submitted pull requests from non-core authors in the last 180-day window, 95.7% were successfully merged into the primary branch.
keycloak/keycloak-benchmark has a recorded first-timer success rate of 100.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~<1 hour. 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 72.2 places keycloak/keycloak-benchmark in the Solid tier.
The external pull request merge rate is 95.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, keycloak/keycloak-benchmark 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 keycloak/keycloak-benchmark 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.