Open-source platform for building cross-platform native Mobile, Web, Desktop, and Embedded apps from a single C#/XAML codebase. Work from any IDE/CLI with Hot Reload, Visual Designer, MCPs, and Skills built for modern .NET workflows. 200M+ NuGet downloads.
C-Rank Grade: S (Elite) - 72/100
External PR Merge Rate: 66%
Response Time: 12h
First Timer Success: 68%
unoplatform/uno has a recorded first-timer success rate of 68.0%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in unoplatform/uno respond to incoming external pull requests in approximately 11.6 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.8 places unoplatform/uno in the S tier.
The external contributor pull request merge rate for unoplatform/uno is 66.0%, based on public PR activity from non-core contributors.
unoplatform/uno currently has 46 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Open-source platform for building cross-platform native Mobile, Web, Desktop, and Embedded apps from a single C#/XAML codebase. Work from any IDE/CLI with Hot Reload, Visual Designer, MCPs, and Skills built for modern .NET workflows. 200M+ NuGet downloads.
Collaborative maintainer environment in unoplatform/uno. 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/unoplatform/uno?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 02:00 UTC (02:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 16:00 to 20:00 UTC (16:00 - 20:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~8 hours (83% approval). Large PRs (>500 lines) take ~56 hours (30% approval). Keep your diff compact for rapid review.
Current behavior 🐛 In the SamplesApp WinAppSDK (Windows) head, unchecking Quick settings > "Use Fluent styles" (or the Fluent styles toggle in Settings) crashes the app within a few seconds. Windows reports an Application Error in Microsoft.UI.Xaml.dll with exception 0xc000027b (stowed exception), HRESULT 80070057 (E_INVALIDARG). It reproduced 3 times on the net11.0-windows10.0.19041.0 head (Microsoft.UI.Xaml.dll 3.2.3.0). The crash happened even when the Settings view was never opened, so the Settings ToggleSwitch code is not involved. Expected behavior 🎯 The toggle should not crash the app on the WinUI head. Skia heads toggle fine. How to reproduce it (as minimally and precisely as possible) 🔬 Build and run the SamplesApp WinAppSDK head. Open Quick settings and uncheck "Use Fluent styles". Wait a few seconds: the app dies with the error above. Workaround 🛠️ Do not toggle it on the WinUI head. Anything else we need to know? 💬 Root cause (suspected, from code inspect
Current behavior 🐛 In SamplesApp, removing a sample from favorites leaves its star filled when the sample is not in the currently selected library category. The stored favorites list and the star then disagree, and the next toggle looks like it "does nothing" (it re-adds a sample whose star already looks set). Expected behavior 🎯 The star reflects the stored favorites list immediately after every toggle, regardless of which category is selected in the library. How to reproduce it (as minimally and precisely as possible) 🔬 Run SamplesApp (Skia desktop). Open a sample that is not in the library's selected category, for example via a deep link such as sample=Input_InputScope_Email (category TextBox) while another category is selected. Toggle favorite with the star button or Ctrl+Shift+D: the sample is added and the star fills. Toggle again (remove): the sample is removed from the stored favorites, but the star stays filled. Toggle again: the sample is re-added instead of the sta
Current behavior 🐛 In SamplesApp, removing a sample from favorites leaves its star filled when the sample is not in the currently selected library category. The stored favorites list and the star then disagree, and the next toggle looks like it "does nothing" (it re-adds a sample whose star already looks set). Expected behavior 🎯 The star reflects the stored favorites list immediately after every toggle, regardless of which category is selected in the library. How to reproduce it (as minimally and precisely as possible) 🔬 Run SamplesApp (Skia desktop). Open a sample that is not in the library's selected category, for example via a deep link such as sample=Input_InputScope_Email (category TextBox) while another category is selected. Toggle favorite with the star button or Ctrl+Shift+D: the sample is added and the star fills. Toggle again (remove): the sample is removed from the stored favorites, but the star stays filled. Toggle again: the sample is re-added instead of the sta
Current behavior src/Uno.UI/UI/Xaml/Controls/CalendarView/RowOrColumnMajor.cs declares an internal enum RowOrColumnMajor : uint in the Microsoft.UI.Xaml.Controls namespace. The public Microsoft.UI.Xaml.Automation.RowOrColumnMajor enum already exists. Any friend assembly (via InternalsVisibleTo on Uno.UI, e.g. Uno.UI.RuntimeTests) that has both using Microsoft.UI.Xaml.Automation; and using Microsoft.UI.Xaml.Controls; gets: error CS0104: 'RowOrColumnMajor' is an ambiguous reference between 'Microsoft.UI.Xaml.Automation.RowOrColumnMajor' and 'Microsoft.UI.Xaml.Controls.RowOrColumnMajor' I hit this porting the WinUI TableView_AutomationPeer_APITests test to the runtime tests. Expected behavior The same source compiles unchanged against WinUI, where the CalendarView equivalent lives in internal C++ code and never shows up in Microsoft.UI.Xaml.Controls. How to reproduce it In a project with InternalsVisibleTo access to Uno.UI (e.g. Uno.UI.RuntimeTests), add a file with: using Microsoft.UI.
Current behavior 🐛 VisualStateManager.GoToState does not follow WinUI's precedence when a CustomVisualStateManager is set on the template root: It calls the root's GoToElementStateCore before looking at the custom VSM. If the override returns true, the custom VSM is never called. If the state name is not found in the root's VisualStateGroups, it returns false without calling the custom VSM's GoToStateCore. Expected behavior 🎯 Like WinUI, when a custom VSM is present, GoToState should call only its GoToStateCore: GoToElementStateCore on the root is skipped (it is only used when there is no custom VSM). GoToStateCore is called even if the state/group was not found (with null group and state), because the custom VSM may want to handle states the default implementation doesn't know about. Backed by the WinUI C++ sources, VisualStateManager::GoToStateImpl: https://github.com/microsoft/microsoft-ui-xaml/blob/winui3/release/2.5.1/src/dxaml/xcp/dxaml/lib/VisualStateManager_Partial.cp
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 unoplatform/uno, 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 unoplatform/uno acknowledge new external contributions in approximately 11 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 66.0% were successfully merged into the primary branch.
unoplatform/uno has a recorded first-timer success rate of 68.0%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~11 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 71.8 places unoplatform/uno in the Elite tier.
The external pull request merge rate is 66.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, unoplatform/uno currently has 46 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for unoplatform/uno 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.