KEDA is a Kubernetes-based Event Driven Autoscaling component. It provides event driven scale for any container running in Kubernetes
C-Rank Grade: A (Welcoming) - 59/100
External PR Merge Rate: 67%
Response Time: 1d
First Timer Success: 52%
kedacore/keda has a recorded first-timer success rate of 52.4%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in kedacore/keda respond to incoming external pull requests in approximately 26.9 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 59.2 places kedacore/keda in the A tier.
The external contributor pull request merge rate for kedacore/keda is 66.7%, based on public PR activity from non-core contributors.
kedacore/keda currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Rigorous architecture standards (72% critical review signals). Ensure PRs strictly follow guidelines before requesting review in kedacore/keda.
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/kedacore/keda?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 08:00 UTC (08:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 11:00 to 15:00 UTC (11:00 - 15:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~17 hours (83% approval). Large PRs (>500 lines) take ~129 hours (30% approval). Keep your diff compact for rapid review.
Report There are currently two identified latency metrics that are incorrectly implemented as gauges keda_scaler_metrics_latency_seconds keda_internal_scale_loop_latency_seconds These originate from #5174 (which was rebased and merged through #5687). They deprecated keda_scaler_metrics_latency and keda_internal_scale_loop_latency, which were also gauges, but at the same time lacked the _seconds suffix recommended as best practice for naming prometheus metrics. During that PR, I should have also changed it from a gauge to a histogram but I didn't realize this at the time. There are other metrics reported by keda-operator that relate to some form of latency. They come from vendored dependencies or golang core, all use histograms. A few examples I found are here: controller_runtime_reconcile_time_seconds controller_runtime_webhook_latency_seconds workqueue_work_duration_seconds workqueue_queue_duration_seconds go_sched_latencies_seconds keda_internal_metricsservice_grpc_server_handling
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 kedacore/keda, 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 kedacore/keda acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 66.7% were successfully merged into the primary branch.
kedacore/keda has a recorded first-timer success rate of 52.4%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~1 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 59.2 places kedacore/keda in the Welcoming tier.
The external pull request merge rate is 66.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, kedacore/keda 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 kedacore/keda 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.