Event Driven Orchestration & Scheduling Platform for Mission Critical Applications
C-Rank Grade: S (Elite) - 71/100
External PR Merge Rate: 75%
Response Time: -
First Timer Success: 57%
kestra-io/kestra has a recorded first-timer success rate of 57.4%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in kestra-io/kestra respond to incoming external pull requests in approximately 0.0 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 71.0 places kestra-io/kestra in the S tier.
The external contributor pull request merge rate for kestra-io/kestra is 74.9%, based on public PR activity from non-core contributors.
kestra-io/kestra currently has 136 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in kestra-io/kestra. Prompt code reviews with positive guidance for new contributors.
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/kestra-io/kestra?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 Wednesday - Friday from 07:00 to 11:00 UTC (07:00 - 11:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (94% approval). Large PRs (>500 lines) take ~115 hours (34% approval). Keep your diff compact for rapid review.
ui/src/components/executions/date-select/TimeSelect.vue uses 2 Bootstrap utility classes. Bootstrap is being removed from the design system, so each one should become CSS written with the --ks-* tokens from ui/packages/design-system, in the component's existing <style scoped lang="scss"> block. Where Line Element Classes 14 <div class="mt-2 duration-examples"> mt-2 25 <KsInput class="mt-2"> mt-2 Done when No Bootstrap class is left in TimeSelect.vue: none of the utilities above. The PR has before and after screenshots in light and dark mode, and the component looks the same. cd ui && npm run check:types && npm run test:unit && npm run lint && npm run check:ts-any passes.
ui/src/components/ErrorToastContainer.vue uses 2 Bootstrap utility classes. Bootstrap is being removed from the design system, so each one should become CSS written with the --ks-* tokens from ui/packages/design-system, in the component's existing <style scoped lang="scss"> block. Where Line Element Classes 7 <AiIcon class="me-1"> me-1 14 <li class="font-monospace"> font-monospace Done when No Bootstrap class is left in ErrorToastContainer.vue: none of the utilities above. The PR has before and after screenshots in light and dark mode, and the component looks the same. cd ui && npm run check:types && npm run test:unit && npm run lint && npm run check:ts-any passes.
ui/src/components/content/ProseImg.vue uses 2 Bootstrap utility classes. Bootstrap is being removed from the design system, so each one should become CSS written with the --ks-* tokens from ui/packages/design-system, in the component's existing <style scoped lang="scss"> block. Where Line Element Classes 2 <span class="text-center d-block img-block"> text-center, d-block Done when No Bootstrap class is left in ProseImg.vue: none of the utilities above. The PR has before and after screenshots in light and dark mode, and the component looks the same. cd ui && npm run check:types && npm run test:unit && npm run lint && npm run check:ts-any passes.
ui/src/components/content/CardLogos.vue uses 2 Bootstrap utility classes. Bootstrap is being removed from the design system, so each one should become CSS written with the --ks-* tokens from ui/packages/design-system, in the component's existing <style scoped lang="scss"> block. Where Line Element Classes 2 <div class="row card-group mb-4 pb-2"> mb-4, pb-2 Bootstrap's spacing steps stop matching the token steps after 2: -4 is --ks-spacing-5. So mb-4 takes var(--ks-spacing-5), not var(--ks-spacing-4). Also remove These Bootstrap names have no CSS behind them in Kestra, so they do nothing today: row (line 2), col-12 (lines 3, 20 and 37), col-sm-4 (lines 3, 20 and 37). Delete them, and if the layout needs what they were meant to do, write it as CSS. For the row/col* grid, use KsRow/KsCol instead. Done when No Bootstrap class is left in CardLogos.vue: none of the utilities above, and none of the names under Also remove. The PR has before and after screenshots in light and dark m
ui/src/components/admin/triggers/TriggersManage.vue uses 2 Bootstrap utility classes. Bootstrap is being removed from the design system, so each one should become CSS written with the --ks-* tokens from ui/packages/design-system, in the component's existing <style scoped lang="scss"> block. Where Line Element Classes 76 <LogsWrapper class="m-3"> m-3 91 <div class="text-nowrap"> text-nowrap Bootstrap's spacing steps stop matching the token steps after 2: -3 is --ks-spacing-4. So m-3 takes var(--ks-spacing-4), not var(--ks-spacing-3). Also remove These look like Bootstrap utilities but aren't Bootstrap 5 classes and have no rule anywhere: mr-1 (lines 241, 249, 257, 266 and 276). Delete them, and if the layout needs what they were meant to do, write it as CSS. Done when No Bootstrap class is left in TriggersManage.vue: none of the utilities above, and none of the names under Also remove. The PR has before and after screenshots in light and dark mode, and the component looks t
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 kestra-io/kestra, 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 kestra-io/kestra acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 74.9% were successfully merged into the primary branch.
kestra-io/kestra has a recorded first-timer success rate of 57.4%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. 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 71.0 places kestra-io/kestra in the Elite tier.
The external pull request merge rate is 74.9%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, kestra-io/kestra currently has 136 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for kestra-io/kestra 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.