Treat this as an upstream snapshot, not a differentiated fork. Adopt it only if you specifically want a frozen baseline; otherwise upstream Helix is the better choice because this fork shows no added features and is 111 commits behind.
Prefer this fork if you want Helix plus extra workflow and UI enhancements, especially around plugins and editor ergonomics. If you want the most conservative, upstream-standard Helix experience, upstream is still the safer default.
RoastBeefer00/evilhelix
stale
significant_divergence
Choose this fork if you want a substantially different Helix experience centered on custom modal behavior and are comfortable losing some upstream parity. Avoid it if you want a low-risk Helix install with the broadest current feature set and backend support.
AlexanderDickie/helix
stale
significant_divergence
Prefer this fork only if Copilot integration is the main requirement. If you want a broadly current Helix build with the latest upstream fixes and language support, upstream is the safer choice.
Axlefublr/helix
active
significant_divergence
Choose this fork if you want a personalized Helix with deeper workflow and UI changes and you are willing to own the maintenance burden. Choose upstream if you want the latest Helix fixes, lower drift, and less risk.
SoraTenshi/helix
slowing
significant_divergence
Choose this fork if you want a customized Helix with editor-workflow and language-support changes and you are willing to absorb the maintenance cost. Avoid it if you want upstream parity, current fixes, and low-risk adoption.
Prefer this fork if you want Helix with practical UX polish and a more opinionated workflow. Prefer upstream if you want maximum compatibility, configurability, and the least divergence from the main project.
deeptesh-rout/helix
stale
significant_divergence
Prefer this fork only if its specific downstream changes matter to you and you are willing to absorb staleness and merge risk. For most adopters, upstream Helix is the safer choice because this fork is materially behind and appears to be a long-unmaintained customization branch.
ymgyt/helix
active
significant_divergence
Choose this fork if your priority is a Helix-based editor with a patched file-explorer workflow and you can tolerate lag behind upstream. Choose upstream Helix if you want the fullest set of current features, fixes, and language support.
g1ibby/helix-zellij-nav
slowing
significant_divergence
Choose this fork if Zellij integration is the main requirement and you want that workflow baked into the editor. Avoid it if you want the latest upstream Helix features, broad language support, or a low-maintenance editor baseline.