Library / SDK
termux/termux-packages avatar
termux/termux-packages

termux-packages publishes weekly bootstrap archives, not versions

A package build system for Termux.

17,371 stars4,562 forksShellNOASSERTION

At a glance

What is it?
termux-packages is the build system behind the Termux Android application: a directory of shell scripts and patches, one per package, with separate sets for root and X11 packages and a directory of disabled ones. Its releases are dated weekly bootstrap archives, and its own documentation treats the repository being under maintenance as an expected state with a documented recovery.
Who is it for?
termux-packages fits someone who needs a package the Android repositories do not carry and who is willing to read a build script before running it. It does not fit someone who needs a stable version string, because the releases here are dated bootstrap archives rather than versions.
Can I use it commercially?
Check first. The repository uses a licence we do not classify automatically, so read its LICENSE file before any commercial use.
Is it still maintained?
Yes. The repository received new commits within the last day.
What is it written in?
Mainly Shell, 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.

From daily snapshots

Star history

  • termux/termux-packages17,371 ★ · +551
Star history
Repository2026-08-212026-11-15
termux/termux-packages16.8k17.4k

551 Stars in the last 86 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

The releases are dated bootstrap archives, not version numbers

The release list is the clearest signal about how this project is versioned, and it is not the way a library is. The three recent tags are bootstrap archives for the Termux application, named 2026.11.01, 2026.10.25 and 2026.10.18, each with a revision marker and an identifier for the package manager generation they were built for. So the cadence is weekly, and a tag encodes three things at once: a date, a rebuild number, and which apt generation the archive belongs to. There is no semantic version to depend on and no changelog of features, because the artefact is not a library. A Termux installation is identified by the bootstrap archive it came from, and that is a different kind of handle from a version number, with a different failure mode when a rebuild goes wrong.

The repository being under maintenance is a state, and the wiki has the fix

The most operationally useful sentence in this file is about an error message. It points to a package management how-to in the project wiki and says that page also has information on how to fix a repository is under maintenance or down error when running the package manager's commands. The consequence for a user is practical: when the client reports that, the project has already decided what you should do and written it down, rather than leaving you to read the client's own error.

disabled-packages/ is the honest inventory of what does not build

The top level of the tree is organised by what a package is rather than by what it depends on, and three directory names carry most of the information. There is the main set of packages, one directory per package. There is a set named for root packages, and a set named for X11 packages, which the visible file does not explain but whose existence tells you the collection is not one flat list. And there is a directory of disabled packages, which is the one to read first. A project that keeps its list of things that do not build in the repository, in a directory anyone can see, has saved you the afternoon that a failed build would have cost, and it has also told you that a package missing from the main directory might be disabled, root-level, or under the other set. Consequence: the first question about any package is which of those four directories it is in, not what it depends on.

One shell script per package, and a sample directory that is the contract

The build system is three shell scripts at the top of the tree, one to build everything, one to build a single package and one to clean, plus directories for the shared scripts, the documentation site, the patches applied to the Android native development kit, and a single JSON file describing the repository. Then there is the sample directory, which contains a build script, a subpackage sample and an alternatives file, and that trio is the contribution template. It is a good design for a project with hundreds of packages, because it keeps the per-package work to one file and makes review mechanical. It also explains the primary language recorded for the repository, since a shell script that patches a native toolchain for an Android device is a different kind of build description from a conventional build system, and the toolchain patches are the part that needs the most care.

The build runs in a published container, and repology watches the output

The badges at the top of the file tell you how the work happens. There is a build status badge for the actions, a badge for a package builder image published on a container registry, and two links to a service that tracks package versions across distributions and repositories. The container is the important one, because it means the environment a package is built in is a published image you can pull and inspect, rather than whatever happens to be on the machine of whoever pushed the commit. The version tracking service is the useful cross-check: when a package in the repository looks wrong, an independent index of what was published gives you a second opinion that does not come from the project.

Three funding programmes, and one of them serves the downloads

The sponsor section lists three programmes and a company, and the last one comes with a package repository link. So the README lists GitHub Accelerator, the GitHub Secure Open Source Fund and NLnet NGI Mobifree as funders, and links Cloudflare to packages-cf.termux.dev. None of that is a criticism, and all of it is a fact about availability that belongs in an evaluation: a package set built by a small team on donated infrastructure has a different availability profile from one shipped by a vendor, and the funding section is where you can see which kind of project this is before anything goes wrong. The grant announcements are also linked.

Codeowners per path, a security file, and a licence the metadata does not name

Three small files describe how the project is governed. There is a code owners file, which for a repository of one-script-per-package is the only mechanism that makes review work at that scale, since it assigns a reviewer by directory. There is a security file, which is where a report about a package goes rather than the issue tracker. And there is a licence file, while the repository's own licence field carries no identifier at all, so a tool reading metadata finds nothing and a person has to open the file. That combination is worth thirty seconds of checking before you decide what you can do with a package built from it.

Editorial conclusion

termux-packages fits someone who needs a package the Android repositories do not carry and who is willing to read a build script before running it. It does not fit someone who needs a stable version string, because the releases here are dated bootstrap archives rather than versions. Before you use it, check two things. Whether the package you want sits in the disabled directory, which answers the question faster than a failed build will. And the wiki page on package management, because the failure this project documents, the repository being under maintenance or down, has a fix described there. And if you are contributing, the sample directory is the contract: one build script, a subpackage sample and an alternatives file, reviewed through the code owners file.

Frequently asked questions

Is Termux still maintained?

The last push recorded for this repository is 2026-11-02, and the recent releases are weekly bootstrap archives dated 2026-11-01, 2026-10-25 and 2026-10-18. The build status badge in the project file is for the continuous integration actions, and contributing goes through a contributing file and a developer wiki.

how to use termux packages

Packages are installed and updated with the package manager commands inside the Termux application, and the project points to a package management page in its wiki for the details. That same page also covers how to recover from the repository is under maintenance or down error.

how to install termux packages

Through the package manager in the Termux application, using the documented commands. This repository is the build system behind those packages rather than something you install yourself: it contains the scripts and patches that produce them, and the quick how-to for using them lives in the project wiki.

how to install all termux packages

The top level of the repository has a script that builds every package, alongside one that builds a single package and one that cleans. The sample directory contains a build script, a subpackage sample and an alternatives file, which together are the template for a new package, and the shared scripts directory holds the rest of the build logic.

What are some available Termux add-ons?

The tree separates them into four sets: the main packages directory with one directory per package, a set named for root packages, a set named for X11 packages, and a directory of disabled packages. The last one is the useful list to read first, because it holds the packages that are disabled.

What is the best package to install in Termux?

The project does not rank its packages. It holds one directory per package, with a separate set for root packages, one for X11 packages and one for disabled packages, and a sample directory that shows the shape a new package takes. Recommendations are not part of what this repository publishes.

Official sources

  1. Official documentation
  2. Official README
  3. Project repository
  4. Release notes
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.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/termux-termux-packages.svg)](https://hysenlabs.com/projects/termux-termux-packages)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/termux-termux-packages.svg)](https://hysenlabs.com/projects/termux-termux-packages)

Was this useful?