Discofork
Repository brief

tauri-apps/tauri

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-29T22:25:44.685Z
3mo ago

tauri-apps/tauri

Tauri is a stable, actively maintained framework for building smaller, faster, more secure desktop and mobile apps with a web frontend. The repo is large and mature, with 104,729 stars, 3,473 forks, and recent commits as of 2026-03-28. It appears most interesting for forks that want a Rust-based app framework with broad platform coverage and a sizable ecosystem rather than a tiny starter project.

GitHub
Loading tags...
Stars104,729
Forks3,473
Default branchdev
Last pushed2026-03-28T17:02:51Z
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

6 of 6 fork briefs
Selected

Choose this fork only if you specifically need its customized, older Tauri behavior and are prepared to maintain a large divergence. For most adopters, upstream Tauri is the safer choice because this fork is stale and likely missing many recent fixes and features.

Choose this fork only if its local changes are valuable enough to justify long-term merge work. It fits a downstream team customizing Tauri’s CLI, bundler, runtime, or mobile workflows; it is a poor fit if you want the newest upstream fixes and broad ecosystem compatibility.

Choose this fork only if you need its downstream-specific runtime/CLI/config behavior and can own long-term maintenance. If you want the current Tauri feature set, upstream compatibility, or low migration risk, upstream is the safer choice.

Prefer this fork only if its custom runtime behavior is a requirement. If you want active maintenance, upstream compatibility, or the latest Tauri fixes, upstream is the safer choice.

Prefer upstream Tauri unless you specifically need this fork's older custom behavior. The fork looks stale and substantially divergent, so it is better as a legacy reference or migration source than as a base for new work.

Prefer this fork only if you need its older pinned behavior or a specific downstream customization already built into it. For new adopters, upstream Tauri is the better default because this fork is stale, heavily behind, and likely missing many recent platform and packaging improvements.