Discofork
Repository brief

AvaloniaUI/Avalonia

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-30T15:49:20.606Z
1mo ago

AvaloniaUI/Avalonia

AvaloniaUI/Avalonia is a mature, production-ready cross-platform .NET UI framework for building desktop, embedded, mobile, and WebAssembly apps with C# and XAML. It is large and active, with 30k+ stars, 2.6k+ forks, and recent commits on March 30, 2026. Forks are most interesting if you care about a widely used XAML-based UI stack with an active upstream and a substantial ecosystem.

GitHub
Loading tags...
Stars30,412
Forks2,647
Default branchmaster
Last pushed2026-03-30T14:53:41Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs
Selected

Prefer upstream unless you specifically need this repository as a personal mirror or staging branch. This fork adds no user-facing features and is simply behind upstream, so it offers little reason to adopt over the canonical project.

Choose this fork only if its local DataGrid/navigation tradeoffs are exactly what you need and you are prepared to own long-term maintenance. For most adopters, upstream Avalonia is the safer default because this fork is stale, highly divergent, and appears to remove core navigation functionality.

Choose this fork only if you need the old Perspex lineage or are doing framework archaeology. For new application or platform work, upstream Avalonia is the clearly better choice because this fork is stale and materially behind.

Choose upstream unless you need this exact older state. This fork appears to add no new capabilities and is 187 commits behind, so it is a weak choice for new adoption or ongoing development.

Prefer this fork only if its control/navigation changes or JetBrains-specific workflow support are directly valuable to you. If you want a broadly current, low-risk Avalonia base, upstream is the safer choice because this fork is far behind and significantly diverged.

Choose this fork only if you need its custom framework changes and can own a large divergence burden. For most adopters, upstream is the safer default because it is far more current and actively maintained.

Choose this fork only if you need its specific local changes and are prepared to maintain a highly divergent codebase. For most adopters, upstream Avalonia is the safer default because this fork is stale and materially behind current framework work.

Choose upstream unless you specifically need this fork's custom behaviors and are prepared to own a large, stale divergence. For new adopters, the maintenance risk outweighs the apparent benefits.

Adopt only if you specifically need this fork’s custom behavior and are willing to own a large, outdated divergence. For most users, upstream Avalonia is the safer choice because this fork is stale, far behind, and likely missing years of fixes and platform support.

Choose upstream unless you specifically need this fork as an internal snapshot. It offers no additional capabilities in the supplied evidence and is behind on recent upstream fixes and improvements, so it is a poorer default for new adopters.