rehex: six distributions, three packaging systems, and a repository line ending in the word CODENAME
Reverse Engineers' Hex Editor
At a glance
- What is it?
- A hex editor for reverse engineering, written in C++ on wxWidgets, with Lua scripting, inline disassembly and binary templates, packaged as standalone binaries, APT lines, COPR builds, an OBS repository, a FreeBSD port and a Gentoo overlay. The build system detects features by compiling, and the two names of the program disagree with each other.
- Who is it for?
- Use rehex when you are reading or writing binary formats at a scale where a built-in disassembler, virtual address mapping and Lua scripting save you more time than a general purpose editor would. Three things to know before you install it.
- Can I use it commercially?
- Yes, with conditions. GPL-2.0 is a copyleft licence: if you distribute software that includes it, you must release that software's source code under the same licence. Running it internally without distributing it does not trigger that obligation.
- Is it still maintained?
- Yes. The repository last received commits 8 days ago.
- What is it written in?
- Mainly C++, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- solemnwarning/rehex2,484 ★ · +3
| Repository | 2026-09-29 | 2026-11-15 |
|---|---|---|
| solemnwarning/rehex | 2.5k | 2.5k |
3 Stars in the last 47 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The readme and the source disagree on the name
The readme heads itself Reverse Engineers' Hex Editor, with the plural possessive. The header comment at the top of the Makefile calls the same program Reverse Engineer's Hex Editor, singular. Both also carry the same licence text, GPL version 2, with the Makefile naming Daniel Collins and a copyright range of 2017 to 2026. It is the kind of small divergence that survives in a repository nobody rereads, and it matters for anyone searching the source or the documentation for the project by name. The project description in the metadata is shorter again, Reverse Engineers' Hex Editor, matching the readme rather than the source.
Packages are built for commits, not just releases
The installation section says the releases page has standalone packages for Windows and macOS as well as installable packages for popular Linux distributions. Then it adds that the same packages are also produced for Git commits, to be found by looking for a tick, if you want to try development or unreleased versions. So the distribution repositories carry development builds alongside the tagged ones, and the only thing separating them in the package list is a marker. The consequence is that a version you install from the repository tells you less than you would expect, and pinning to a release rather than accepting whatever the repository currently offers is a decision you have to make deliberately.
Six distributions and three packaging systems
The install instructions cover Debian, Ubuntu, Fedora, CentOS, openSUSE, FreeBSD and Gentoo, and they do not share a mechanism. Fedora and CentOS go through a COPR project with dnf copr enable, and CentOS needs the epel-release package installed first. openSUSE uses the Open Build Service with zypper ar pointing at an editors repository. FreeBSD is a single pkg install. Gentoo is the outlier: the instructions tell you to add the pentoo overlay through eselect, sync it with emaint, and only then emerge the package, so the editor is not in Gentoo proper but in a security distribution's overlay. Debian and Ubuntu share an APT repository and are described separately for one reason given below.
The APT line ends in the literal word CODENAME
Both APT sections ask you to download a signing key into a keyrings directory with wget, then add two lines to your sources list, one for packages and one for sources. The lines end with the repository path, the literal word CODENAME, and the component main, and a note underneath tells you to replace CODENAME with the release you are running, giving trixie and bookworm for Debian and noble or resolute for Ubuntu. That is a manual edit in a file that has to be exactly right, and the Ubuntu variant adds arch=amd64 to the signed-by clause while the Debian variant does not, so the Ubuntu line as written will not serve an arm64 machine. The repository URL itself is http rather than https. A further note says Ubuntu users need the universe repository enabled for some dependencies.
Gentoo users have to adopt the pentoo overlay
The Gentoo block is four commands and one of them is a repository add. It installs eselect-repository with the git use flag, enables the pentoo overlay, syncs with emaint, and then emerges the package with verbose and ask flags. Everything except the last command is about getting hold of an overlay that rehex lives in, which means the editor is packaged by a security-focused distribution rather than by Gentoo itself. For anyone tracking upstream closely, the git use flag on eselect-repository is a deliberate choice: it fetches the repository list from git rather than from a snapshot, so the overlay list follows upstream changes immediately. The overlay also carries whatever else pentoo maintains, which is the trade for having the package at all.
Features are detected by compiling a test program
The Makefile has no configure step. Instead it carries two helper functions that probe the system. One returns whichever of two packages pkg-config knows about, and errors if neither is found. The other takes a source file and a flag, and compiles a small program to decide whether the flag is required, printing whether it is checking for the flag or deciding it is not needed. The probe writes marker files with two different extensions and treats their presence as a cache, so a second build skips the compile. The comment above that helper explains it takes a file under a tools directory, and the flag argument is passed straight through. Two typos sit in those comments, one where it should say if the flags were not required.
The wxWidgets libraries live in the tree
Three third-party trees are committed. wxLua and wxFreeChart sit at the root next to googletest, which is the test framework the tests directory is written against. There is also a shell script whose only job is updating the Lua binding. Beyond that, the root holds five build files: a general Makefile, an AppImage one, and three more for MSVC, macOS and Windows, matching the four platforms the project targets. The Windows installer is built with NSIS from its own directory, the MSVC files have their own directory, and there is a plugins directory that the readme never mentions. Nothing here is fetched at build time, so a checkout is self-contained at the cost of carrying the dependencies.
Binary templates, disassembly, and a named comparison
The feature list is the honest part of this project. It handles files over a terabyte, decodes integer and floating point types, disassembles machine code inline, highlights and annotates ranges, compares two files or two selections side by side, maps virtual addresses, and reads common text encodings. It imports and exports Intel HEX, visualises bitmap data, edits bits, and checksums a file or a selection. Binary templates annotate data automatically, and there the readme compares the feature to 010 Editor rather than describing it. Lua scripting is supported with its own API reference published separately. The release list moves through 0.63.3, 0.63.4 and 0.64.0, with the newest release six months before the last recorded push.
Editorial conclusion
Use rehex when you are reading or writing binary formats at a scale where a built-in disassembler, virtual address mapping and Lua scripting save you more time than a general purpose editor would. Three things to know before you install it. The repository line you paste into your sources file contains a placeholder you must edit by hand, and the Ubuntu variant pins the architecture. Building from source is not a configure script: the Makefile probes for libraries by compiling test programs, so a broken toolchain surfaces as a failed probe rather than a clear message. And the vendored wxWidgets libraries mean the toolkit is part of the tree, which is why there is a script for updating the Lua binding.
Frequently asked questions
How do I install rehex on Debian or Ubuntu?
Download the APT signing key into /etc/apt/keyrings with wget, add the deb and deb-src lines for repos.solemnwarning.net with signed-by, replace CODENAME with your release codename, then run sudo apt-get update and sudo apt-get install rehex. Ubuntu users also need the universe repository enabled for some dependencies.
How do I install rehex on Fedora or CentOS?
On Fedora run sudo dnf copr enable solemnwarning/rehex and then sudo dnf install rehex. On CentOS install epel-release first, then enable the same COPR project and install the package.
Which platforms does rehex support?
Windows, Linux, macOS and BSD. The releases page carries standalone packages for Windows and macOS and installable packages for popular Linux distributions, and FreeBSD installs it with pkg install rehex.
Does rehex have scripting support?
Yes, Lua scripting, with the API reference published separately. The repository vendors wxLua and wxFreeChart and includes a script for updating the Lua binding.
What are binary templates in rehex?
A way to annotate data automatically, and the readme compares it to what 010 Editor does. The editor also decodes integer and floating point types, disassembles machine code inline, maps virtual addresses, imports and exports Intel HEX, visualises bitmap data, edits bits and checksums files or selections.
Can I install an unreleased build of rehex?
Yes. The same packages are produced for Git commits as well as for releases, marked with a tick in the list, so development builds are available from the same repositories as the tagged ones.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/solemnwarning-rehex)Star history chart for your README
[](https://hysenlabs.com/projects/solemnwarning-rehex)Was this useful?