Discofork
Repository brief

bevyengine/bevy

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-30T11:46:48.265Z
3mo ago

bevyengine/bevy

Bevy is a large, active Rust game engine and app framework with a strong emphasis on data-driven ECS design, modularity, and fast iteration. It appears well-maintained, with recent commits on March 30, 2026 and a large community footprint (45k+ stars, 4.4k+ forks).

GitHub
Loading tags...
Stars45,336
Forks4,480
Default branchmain
Last pushed2026-03-30T07:25:36Z
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 this fork only if you want its custom mobile/web/example workflow and are prepared to own a large divergence from upstream. If you want the broadest Bevy feature set, easier upgrades, and community-aligned docs/examples, upstream is the safer choice.

Choose this fork only if OpenXR support is the main requirement and you are comfortable living on an old, highly divergent Bevy branch. For general Bevy development, upstream is the better default.

Choose this fork if UWP support is the priority and you are comfortable owning a heavily diverged Bevy branch. Choose upstream if you want the broadest feature completeness, cleaner migration path, and lower maintenance burden.

Choose this fork only if you specifically want its custom ECS/rendering direction and are prepared to own a large long-term merge burden. If your goal is a stable Bevy baseline with current upstream fixes, upstream main is the safer choice.

Adopt this fork only if you need its specific older behavior or local workflow additions. For most new work, upstream Bevy is the safer choice because this fork is materially stale and likely missing many recent fixes and examples.

Choose this fork only if you need its legacy/custom behavior and are willing to stay on an old Bevy line. For new work or active development, upstream is the safer choice because this fork is materially stale and likely missing many recent fixes and features.

Choose this fork only if you want a custom Bevy branch and are prepared to maintain it yourself. For most adopters, upstream Bevy is the safer default because this fork is stale, deeply diverged, and likely missing common asset and ECS pathways.

Prefer this fork only if you specifically need its older, customized codebase and are prepared to maintain it yourself. For most adopters, upstream Bevy is the better choice because this fork is stale and diverged far enough that it will miss a large amount of recent engine work.

Prefer this fork if you want a rendering-centric Bevy variant and are willing to own divergence. Prefer upstream if you need the broadest compatibility, the standard docs/examples path, or the lowest maintenance risk.

Choose this fork only if you want a deeply customized Bevy baseline and can absorb ongoing merge and migration work. If you want a stable, upstream-compatible Bevy, this fork is too divergent.

bevyengine/bevy · Discofork