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

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

Stars104,729

Forks3,473

Default branchdev

Last pushed2026-03-28T17:02:51Z

Best maintainedNone

Closest to upstreammultijump/tauri

Most feature-richaustin-starks/tauri

Most opinionatedlencx/tauri

Forks

Choose a fork to inspect

6 cached fork briefs

Fork comparison

multijump/tauri

stale

significant_divergence

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.

Likely purpose

A heavily diverged Tauri fork for teams that want to stay on an older 2024-era codebase while reshaping core window, webview, config, and CLI behavior to fit their own app workflow.

Best for

Teams maintaining an internal desktop app on an older Tauri lineage.; Users who value customization over staying current with upstream.; Projects that need a forked framework and are willing to own long-term maintenance.

Additional features

Updated core window/webview handling beyond upstream's older baseline.
Large config and schema reshaping in `tauri-utils` and `tauri-cli`, suggesting a more opinionated or customized app configuration workflow.
CLI and bundler/icon workflow changes that likely alter how apps are scaffolded and packaged.
Removal of legacy `config_v1` code, which may simplify the supported configuration surface for adopters.
Adds or extends platform-specific client support, such as mobile, Android, iOS, or desktop packaging.
Expands API, schema, or SDK surface area for downstream integrations and generated clients.

Missing features

It is far behind current upstream Tauri activity, so recent upstream fixes and platform improvements are missing.
Legacy upstream capabilities around older config paths are removed, which can make migration from older projects harder.
Recent upstream work such as mobile multi-window support, newer bundler/icon updates, and WebView2 minimum-version handling are not present in this fork.
Users depending on the broad, fast-moving upstream ecosystem should expect substantial merge debt.
Some upstream behavior appears to be removed, disabled, or intentionally stripped down in this fork.
It trails upstream by 200 commits, so some recent upstream features and fixes are likely not present yet.

Strengths

Could fit teams that want a pinned, internally modified Tauri base rather than upstream churn.
Likely offers a narrower, more controlled configuration and CLI surface.
May be easier to reason about if the goal is to standardize on a specific app framework behavior set.

Risks

Very stale relative to upstream activity.
High divergence makes rebasing or pulling upstream fixes expensive.
Potential incompatibilities with modern Tauri docs, plugins, and ecosystem expectations.
The large amount of deletion suggests removed pathways that may break existing projects.