Develop Desktop, Embedded, Mobile and WebAssembly apps with C# and XAML. The future of .NET UI
C-Rank Grade: A (Welcoming) - 65/100
External PR Merge Rate: 65%
Response Time: 24h
First Timer Success: 63%
AvaloniaUI/Avalonia has a recorded first-timer success rate of 62.8%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in AvaloniaUI/Avalonia respond to incoming external pull requests in approximately 23.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 65.2 places AvaloniaUI/Avalonia in the A tier.
The external contributor pull request merge rate for AvaloniaUI/Avalonia is 64.7%, based on public PR activity from non-core contributors.
AvaloniaUI/Avalonia currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in AvaloniaUI/Avalonia. Maintains strict focus on technical quality and test standards.
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/AvaloniaUI/Avalonia?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 Monday - Wednesday from 08:00 to 12:00 UTC (08:00 - 12:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (81% approval). Large PRs (>500 lines) take ~115 hours (29% approval). Keep your diff compact for rapid review.
WindowImpl gates per-monitor DPI on the reported Windows version: if (ShCoreAvailable && Win32Platform.WindowsVersion >= PlatformConstants.Windows8_1) { ... GetDpiForMonitor(monitor, MDT_EFFECTIVE_DPI, out _dpi, out _) ... _scaling = _dpi / StandardDpi; } WindowsVersion comes from RtlGetVersion, which returns whatever an application compatibility layer on the process says it is. Under one of those, a process on Windows 11 can read 6.0.6000, the comparison against 8.1 fails, _scaling keeps its initializer of 1, and the window is sized for scale 1 while its content lays out at 1.5. At 150% that is about two thirds the size it should be. In that state shcore.dll still loads and GetDpiForMonitor still returns 144, and Screens.ScreenFromWindow().Scaling is correct too. It is only RenderScaling that ends up at 1. Win32PlatformSettings in the same assembly gates theme detection on WinRTApiInformation.IsTypePresent(...), i.e. on whether the API is there rather than on the version. Doin
Describe the bug Avalonia 11.3.11 .NET 10 Windows 11 23H2 x64 I am running some UI tests and this bug shows up and crashes the app. Seems to be related to text font and typefaces. This bug didn't happen with Avalonia 11.0.5. Stack trace: > Avalonia.Base.dll!Avalonia.Media.FontManager.TryGetGlyphTypeface(Avalonia.Media.Typeface typeface, out Avalonia.Media.IGlyphTypeface glyphTypeface) Linha 73 C# Avalonia.Base.dll!Avalonia.Media.Typeface.GlyphTypeface.get() Linha 24 C# Avalonia.Base.dll!Avalonia.Media.TextFormatting.TextCharacters.CreateShapeableRun(System.ReadOnlyMemory<char> text, Avalonia.Media.TextFormatting.TextRunProperties defaultProperties, sbyte biDiLevel, Avalonia.Media.FontManager fontManager, ref Avalonia.Media.TextFormatting.TextRunProperties previousProperties) Linha 46 C# Avalonia.Base.dll!Avalonia.Media.TextFormatting.TextFormatterImpl.CoalesceLevels(System.Collections.Generic.IReadOnlyList<Avalonia.Media.TextFormatting.TextRun> textCharacters, System.ReadOnlySpa
Describe the bug Reproduction: Set SuggestedStartLocation to a network drive path Open file picker → works Close/cancel Open file picker again → dialog doesn't appear Keep trying → multiple dialogs appear at once later Workaround: Don't use SuggestedStartLocation, let system remember last location Environment: Avalonia Windows Desktop Network drive (UNC or mapped drive) To Reproduce Set SuggestedStartLocation to a network drive path Open file picker → works Close/cancel Open file picker again → dialog doesn't appear Keep trying → multiple dialogs appear at once later Expected behavior No response Avalonia version 11.3.9 ~ 11.3.11 OS Windows Additional context No response
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 AvaloniaUI/Avalonia, 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 AvaloniaUI/Avalonia acknowledge new external contributions in approximately 23 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 64.7% were successfully merged into the primary branch.
AvaloniaUI/Avalonia has a recorded first-timer success rate of 62.8%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~23 hours. 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 65.2 places AvaloniaUI/Avalonia in the Welcoming tier.
The external pull request merge rate is 64.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, AvaloniaUI/Avalonia 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 AvaloniaUI/Avalonia 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.