/jump to repo

Repos Recent Bookmarks Watched Notes Tags Discover Compare Stats GitHub

Repository brief

WerWolv/ImHex

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-30T12:01:07.089Z

3mo ago

WerWolv/ImHex

ImHex is an actively maintained hex editor aimed at reverse engineers and programmers. It has a large user base and contributor interest, with 52,998 stars and 2,343 forks, and it was updated on 2026-03-30 after a commit on 2026-03-29. The repository appears mature and feature-rich, with docs, plugins, tests, build tooling, and release assets present.

Loading tags...

Stars52,998

Forks2,343

Default branchmaster

Last pushed2026-03-29T00:53:17Z

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

Maintenance:

Magnitude:

Sort:

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

Fork comparison

deeptesh-rout/ImHex

38/100

stale

significant_divergence

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.

Likely purpose

To provide a more tailored ImHex experience for reverse engineering workflows, especially around web/mobile UX and editor behavior, rather than to stay in sync with upstream releases.

Best for

Users who specifically want this fork's older customizations and do not need current upstream parity.; People embedding or demoing ImHex in a web/mobile-oriented workflow.; Adopters comfortable maintaining their own fork and reconciling upstream changes manually.

Additional features

Improved web and mobile behavior, including touch input and mobile logo sizing.
Added toolbar button tooltips for easier discoverability.
Pattern-language and pattern-data-view changes, including updated pattern language support and fixes to static array offsets/sizes.
UI/editor behavior tweaks such as keeping the welcome screen in the background and fixing selection/scrolling behavior.
Bundled third-party UI/editor dependency changes that suggest a broader custom UI stack.
Adds or extends platform-specific client support, such as mobile, Android, iOS, or desktop packaging.

Missing features

Falls far behind upstream: the fork is about 200 commits behind and also 200 commits ahead of the comparison base, with 945 changed files.
Likely missing newer upstream fixes and improvements to the hex editor, pattern editor, data inspector, ImGui, GLFW, and web display behavior from 2026.
Upstream appears actively maintained with frequent fixes; this fork has no recent pushes since 2024-07-03, so adopters should expect lag on bugfixes and compatibility updates.
Large deletion-heavy changes to third-party components suggest some upstream behavior or tooling may have been removed or replaced, increasing the chance of regressions or compatibility gaps.
Some upstream behavior appears to be removed, disabled, or intentionally stripped down in this fork.
Some upstream plugin, tool, or MCP-style integration paths may be reduced or disabled.

Strengths

Useful if you want a fork with explicit mobile/web UX attention.
May better fit a customized reverse-engineering workflow than upstream stock behavior.
Includes targeted fixes in editor and pattern handling areas that can matter in day-to-day use.

Risks

Very stale maintenance status makes it risky for users who need current bugfixes or compatibility.
Large divergence increases merge pain and makes upstream sync difficult.
Heavy third-party churn raises the chance of subtle UI or build regressions.
Because the fork is old, it may not be a good choice for plugin or ecosystem compatibility with newer ImHex changes.

WerWolv/ImHex · Discofork