utmapp/UTM

Choose this fork only if you need its iOS Hypervisor.framework experiment or its specific SPICE/console path. For most users, upstream UTM is the safer and more maintainable choice.

Choose this fork only if you specifically need its visionOS/build tweaks. For general UTM use, upstream is the better default because this fork is very stale and far behind in fixes and runtime improvements.

Prefer upstream UTM unless you specifically need this exact older snapshot for experimentation. For normal adoption, this fork offers no visible advantages and is substantially behind on maintenance and fixes.

Choose this fork only if you specifically need its older iOS/gamepad-oriented behavior. For most users, upstream UTM is the better choice because this fork is stale and significantly behind.

Prefer this fork only if you need its early iOS-specific configuration changes or are studying historical UTM behavior. For normal use, upstream UTM is far more current and lower risk.

Choose this fork if you want UTM with better Chinese localization and little else changed. If you want new VM features or platform changes, upstream is effectively the same product.

Choose this fork only if you specifically need an older UTM snapshot; otherwise upstream is the better choice because this fork has no visible added functionality and is materially behind.

Prefer upstream UTM unless you specifically need an old, unchanged snapshot. This fork adds no visible value and is materially stale, so it is not a good adoption target for users who want current fixes or active development.

Prefer this fork only if you need its older macOS-focused behavior or custom patches and are prepared to maintain a deep divergence; otherwise upstream UTM is the safer choice.