DioxusLabs/dioxus

Choose this fork only if its older custom CLI and platform tooling are the point; otherwise upstream is the safer default because this fork is substantially diverged and stale.

Treat this as a stale snapshot, not a meaningfully differentiated fork. Prefer upstream unless you specifically want an untouched base to build on.

Choose this fork only if you specifically need this fork identity; otherwise upstream is the better default because it is current and this fork shows no added functionality.

Prefer this fork only if its customized build/bundling behavior is the point. If you want the newest Dioxus features, fixes, and the least maintenance risk, upstream is the safer choice.

Choose this fork only if its local runtime, bundling, or integration changes match a specific need you control. If you want the current Dioxus ecosystem, active fixes, and compatibility with upstream docs and releases, upstream is the better default.

Prefer this fork only if you specifically want its customized older CLI/fullstack behavior and are prepared to maintain a large divergence. If you want current Dioxus features, fixes, and release support, upstream is the better choice.

Prefer this fork only if you need its specific older customizations. For most adopters, upstream is the better base because it is far newer, actively maintained, and already includes newer release, CLI, desktop, mobile, and bundling fixes.

Prefer this fork if you need a maintained but customized Dioxus distribution and are comfortable owning divergence. Prefer upstream if you want the broadest, freshest, and least risky path for general framework adoption.

Prefer this fork only if you want an almost-unmodified Dioxus base and can tolerate being behind upstream. If you need current fixes or active maintenance, upstream is the better choice.