deeptesh-rout/ImHex
stale
significant_divergence
Selected Choose upstream unless you specifically need this fork's custom web/mobile and UI tweaks. This fork looks more like a long-lived customization branch than an actively maintained alternative, so it is only attractive if its added behavior matters more than staying current.
Ch4kr4k/ImHex
stale
significant_divergence
Choose this fork only if you need its older local behavior or specific pattern/editor tweaks. If you want an actively maintained ImHex with the latest fixes, plugin compatibility, and less risk, upstream is the safer choice.
Hacking-Ethic/ImHex
stale
significant_divergence
Choose this fork only if its specific workflow changes matter enough to justify falling behind upstream. For most adopters, upstream ImHex is the safer default; this fork is for users who want the added editor/disassembly tweaks and can tolerate maintenance risk.
kuralisko/ImHex_space
stale
significant_divergence
Prefer upstream unless you specifically need the fork’s added tools or its older UI behavior. This fork is best seen as a dated customization branch, not a maintained alternative.
bkerler/ImHex
stale
significant_divergence
Prefer upstream unless you specifically need this fork’s older packaging or vendoring changes. This fork looks like a long-abandoned, highly divergent snapshot, so it is best suited for niche build/research use rather than everyday adoption.
inflex/ImHex
stale
significant_divergence
Prefer this fork only if you need its older customizations and are willing to own a large upstream gap. For most users, upstream ImHex is the better choice because this fork is stale and materially behind on fixes and backend updates.
mrexodia/ImHex
stale
significant_divergence
Prefer upstream unless you specifically want this fork's custom pattern/visualization work and are prepared to carry a stale, highly diverged codebase. This fork looks best for experimenters and maintainers, not for users seeking an up-to-date, low-risk ImHex installation.
MoneyReady/ImMoney
stale
significant_divergence
Prefer upstream unless you specifically need the fork's extra analysis tools or its frozen behavior. This fork is useful as a customized snapshot, but its age and divergence make it a poor default choice for most adopters.
HoMeCracKeR/ImHex
stale
significant_divergence
Prefer upstream unless you specifically need this fork's historical 2021-era experiments or are willing to maintain a stale, highly diverged codebase yourself. For most adopters, the maintenance cost and missing modern fixes outweigh the small feature additions.
nmantani/ImHex
stale
significant_divergence
Prefer this fork if C#-driven extensibility is the main requirement and you are comfortable owning a stale, highly diverged codebase. Prefer upstream if you want active maintenance, newer fixes, and lower operational risk.