This repo is open source so you can read the code before you run pacman -S. Every package's full contents are here — nothing hidden in binary blobs.

What to check before installing:

1. packages/<name>/PKGBUILD — metadata, dependencies, and what ships inside the package.
2. packages/<name>/<name>.install — lifecycle hooks that run on your device during install and removal. Read them.
3. Files inside <name>-data.tar.gz (where present) — extractable with tar -tzf, no surprises.

Don't understand a hook? Copy it, ask an AI "what does this do and is it safe?" Don't install blindly.

The repository database (termuxvoid.db) and every package are signed with the TermuxVoid GPG key. install-repo.sh imports and locally signs the key automatically; verify manually anytime:

gpg --show-keys termuxvoid.gpg.asc

• No package modifies $PATH, $HOME, $PREFIX, or any Termux env var.
• Ordinary tool packages do not alter your existing Termux configuration.
• Packages whose stated purpose is shell styling, themes, desktop environments, or similar customization may create or change relevant configuration files. Inspect their hook scripts before installation and removal, and keep backups of personal configuration.
• Where appropriate, commands are exposed through symlinks instead of environment mutations.
• Removal hooks are intended to remove files created by the install hooks. Packages cannot restore user changes made after installation, so review cleanup behavior before installing a customization package.

Do not install a package solely because it is available in this repository. Before installing, review its PKGBUILD and <name>.install.

Check the following:

1. Upstream source: Confirm the project URL and license are the ones you expect.
2. Version and integrity: Prefer a pinned release, tag, or commit. When an upstream checksum or signature is available, verify it.
3. Network activity: Identify every URL, Git repository, or upstream package-manager command used during installation.
4. Local changes: Identify files created, commands linked, configuration files changed, and what removal does.
5. Authorization: Security tools may be dual-use. Use them only on systems and data you own or are explicitly authorized to test.

Open a GitHub Issue or contact @nullxvoid on Telegram.

These tools are for educational and authorized security testing only. Do not use your knowledge for illegal things. I won't take responsibility for your shit — you mess up, you face the consequences yourself. Stay ethical.