ocornut/imgui

Choose this fork only if legacy Windows support or Win98 styling is the goal. For general Dear ImGui work, upstream is the safer choice because this fork is stale, heavily diverged, and likely missing recent backend and bugfix work.

Choose this fork if you want Spectrum-style UI on top of Dear ImGui and can accept downstream divergence. Stay with upstream if you need the latest ImGui fixes, broad backend freshness, or the simplest possible integration path.

Choose this fork only if its backend and platform customizations match your shipping needs; otherwise upstream is the safer default because this fork is substantially behind and likely to stay that way.

Choose upstream unless you specifically need this fork's custom `Auto()`/helper/backend additions and are willing to maintain an old, highly divergent codebase. For most adopters, the maintenance gap and missing modern upstream support outweigh the fork's extras.

Choose this fork if you want a customized ImGui base with backend-specific changes and can absorb merge debt. Choose upstream if you want the latest Dear ImGui fixes, active backend support, and lower integration risk.

Prefer this fork only if its custom editor/tooling behavior is essential to your product. If you want current Dear ImGui backends, fixes, and active maintenance, upstream is the safer choice.

Choose this fork if you need Mojang's downstream integration and can live without upstream freshness; choose upstream if you want the latest fixes, backend support, and lowest long-term merge risk.

Prefer this fork only if you need its specific local behavior and are prepared to own a long-lived downstream maintenance burden. For most adopters, upstream Dear ImGui is the safer choice because this fork is much older, highly divergent, and missing several years of fixes and backend work.

Choose this fork only if you need its specific legacy backend/integration behavior. For most new adopters, upstream is the better base because this fork is stale and materially behind on core and backend support.

Prefer this fork only if you need its specific custom rendering/backend changes and can own long-term maintenance. If you want current Dear ImGui features, bug fixes, and backend support, upstream is the better default.

Prefer this fork if your priority is using Dear ImGui from D and you value the translated D codebase more than upstream freshness. Prefer upstream if you need the newest fixes, backend support, or lowest maintenance risk.

Prefer upstream unless you already depend on this fork's specific table and internal-behavior changes. This fork is best treated as a legacy customization branch with meaningful divergence, not a drop-in modern replacement.

Choose this fork only if its backend and workflow changes are specifically valuable to you. For most users, upstream is the safer default because it is much more active, much closer to current fixes, and easier to adopt without carrying a large divergence.

Choose this fork only if Zep integration is the goal and you want the editor-oriented stack it already contains. If you need a current, broadly supported Dear ImGui library, upstream is the better fit.

Choose this fork only if its specific UI behavior changes are important and you are comfortable owning an old, diverged codebase. If you want current backend support, active fixes, and low merge cost, upstream is the better default.

Prefer this fork only if you need its historical navigation/input changes and are prepared to own a large forward-port. For most adopters, current upstream Dear ImGui is the better choice.

Prefer this fork only if you are maintaining an existing legacy integration and want to avoid upstream churn. If you are starting new work or need current backend/platform support, upstream Dear ImGui is the better choice.

Prefer upstream unless you explicitly need this fork’s older, customized code path. Adopt the fork only if you are maintaining a legacy integration and value its existing local backend/example changes more than current ImGui features, fixes, and backend support.

Choose this fork if bgfx integration is the main requirement and you want a small, focused delta. Choose upstream if you need the latest fixes, backend coverage, and lower maintenance risk.