Kiali project, observability for the Istio service mesh
C-Rank Grade: S (Elite) - 72/100
External PR Merge Rate: 86%
Response Time: 2d
First Timer Success: 67%
kiali/kiali has a recorded first-timer success rate of 66.7%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in kiali/kiali respond to incoming external pull requests in approximately 59.8 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.3 places kiali/kiali in the S tier.
The external contributor pull request merge rate for kiali/kiali is 86.3%, based on public PR activity from non-core contributors.
kiali/kiali currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in kiali/kiali. Reviews community pull requests with focus on project quality.
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/kiali/kiali?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 14:00 UTC (14:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 12:00 to 16:00 UTC (12:00 - 16:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~39 hours (96% approval). Large PRs (>500 lines) take ~287 hours (39% approval). Keep your diff compact for rapid review.
What do you want to improve? Finish internationalization of the Kiali UI by wrapping remaining hardcoded user-facing strings with t() from utils/I18nUtils, so all labels can be extracted and translated. Also restore the original i18n workflow where frontend/public/locales/en/translation.json is generated locally but not committed to git. What is the current behavior? Much of the UI is already internationalized (~842 keys in frontend/public/locales/en/translation.json), but a scan of frontend/src still finds roughly 285 unique hardcoded strings (~447 occurrences) in props like label, title, aria-label, and placeholder. Approximate progress: ~75% of UI strings use t(). Main gaps: Area ~Strings remaining Istio config wizards ~97 Graph / traffic panels ~54 Workload details ~24 Tracing ~17 ChatBot / AI ~17 Envoy details ~16 Mesh page ~8 Notable files: SummaryPanelGraph.tsx, SummaryPanelNamespaceBox.tsx, WorkloadPodLogs.tsx, AccessLogModal.tsx, ServiceEntryForm.tsx, Spa
What do you want to improve? Add Japanese (ja) as a supported Kiali UI language so OSSMC matches the language set offered by OpenShift Console. OpenShift Console lists ja in its supported locales (frontend/i18n-scripts/languages.sh). Kiali currently supports en, es, zh, and ko only. Japanese-speaking users in OSSMC therefore cannot use the Service Mesh console in Japanese. What is the current behavior? frontend/public/locales/ has no ja locale. The Language enum in frontend/src/types/Common.ts has no Japanese entry. LanguageUtils.matchBrowserLanguage() does not match ja / ja-JP browser locales. The Preferences language selector does not offer Japanese. i18next-parser.config.ts does not include ja in its locales array. When the browser or OpenShift Console preference is Japanese, Kiali falls back to English (or another configured fallback). What is the new behavior? Follow the steps in frontend/README.adoc#internationalization-i18n ("Adding a new language"), modeled on the Korean work
What do you want to improve? Add French (fr) as a supported Kiali UI language so OSSMC matches the language set offered by OpenShift Console. OpenShift Console lists fr in its supported locales (frontend/i18n-scripts/languages.sh). Kiali currently supports en, es, zh, and ko only. French-speaking users in OSSMC therefore cannot use the Service Mesh console in French. What is the current behavior? frontend/public/locales/ has no fr locale. The Language enum in frontend/src/types/Common.ts has no French entry. LanguageUtils.matchBrowserLanguage() does not match fr / fr-FR browser locales. The Preferences language selector does not offer French. i18next-parser.config.ts does not include fr in its locales array. When the browser or OpenShift Console preference is French, Kiali falls back to English (or another configured fallback). What is the new behavior? Follow the steps in frontend/README.adoc#internationalization-i18n ("Adding a new language"), modeled on the Korean work in #10013 /
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 kiali/kiali, 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 kiali/kiali acknowledge new external contributions in approximately 2 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 86.3% were successfully merged into the primary branch.
kiali/kiali has a recorded first-timer success rate of 66.7%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~2 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 72.3 places kiali/kiali in the Elite tier.
The external pull request merge rate is 86.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, kiali/kiali currently has 3 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for kiali/kiali 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.