Discofork
Repository brief

termux/termux-app

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:50:44.465Z
3mo ago

termux/termux-app

Termux/termux-app is the Android terminal emulator and Linux environment app itself, with the app UI and terminal emulation in this repo and packages handled separately in termux/termux-packages. It is actively maintained, widely used, and still seeing recent commits and dependency/tooling updates.

GitHub
Loading tags...
Stars52,665
Forks6,294
Default branchmaster
Last pushed2026-03-23T19:42:57Z
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
Selected

Choose this fork if your primary goal is running Nix on Android and you want the app, bootstrap, and build pipeline optimized for that workflow. Choose upstream Termux if you want the broadest compatibility, freshest fixes, and the full general-purpose Termux ecosystem.

Choose this fork if you want a customized, expert-focused Termux build and can tolerate stale upstream parity and higher maintenance risk. Stick with upstream if you want the safest path for fixes, compatibility, and long-term updates.

Prefer this fork if your goal is graphical X11 support and richer mobile interaction inside Termux. Prefer upstream if you want the smallest-risk, most up-to-date baseline terminal app.

Choose this fork only if you specifically want its docs or debug-build workflow tweaks. For normal users or anyone wanting the latest Termux behavior and fixes, upstream is the better choice.

Choose this fork if you want a launcher-centric Termux with voice/notification features and custom startup behavior. Choose upstream if you want the most current, actively maintained Termux app and plugin compatibility.

Prefer upstream unless you explicitly need this fork's legacy/custom behavior. The divergence is large enough that adopting it means accepting stale maintenance and a substantial catch-up cost.

Choose upstream unless you specifically need this fork's custom automation/bootstrap workflow; otherwise the staleness and upstream lag make it a poor default adoption target.

Adopt only if your goal is to revive the VR experiment or mine it for ideas. For normal Termux use, this fork is too old and divergent to be a practical base.

Choose this fork only if you specifically need its older, customized Termux baseline and build naming/versioning behavior. For most adopters, upstream is the safer choice because this fork is stale and substantially behind current maintenance.

Prefer this fork only if you want a maintenance shell around upstream Termux. If you want app improvements, plugin work, or bugfixes, upstream is the better choice.