GitHub Java Monthly Trending Repositories

termux/termux-app

Termux - a terminal emulator application for Android OS extendible by variety of packages.

Termux application

Termux is an Android terminal application and Linux environment.

Note that this repository is for the app itself (the user interface and the terminal emulation). For the packages installable inside the app, see termux/termux-packages.

Quick how-to about Termux package management is available at Package Management. It also has info on how to fix repository is under maintenance or down errors when running apt or pkg commands.

We are looking for Termux Android application maintainers.

NOTICE: Termux may be unstable on Android 12+. Android OS will kill any (phantom) processes greater than 32 (limit is for all apps combined) and also kill any processes using excessive CPU. You may get [Process completed (signal 9) - press Enter] message in the terminal without actually exiting the shell process yourself. Check the related issue #2366, issue tracker, phantom cached and empty processes docs and this TLDR comment on how to disable trimming of phantom and excessive cpu usage processes. A proper docs page will be added later. An option to disable the killing should be available in Android 12L or 13, so upgrade at your own risk if you are on Android 11, specially if you are not rooted.

Termux App and Plugins

The core Termux app comes with the following optional plugin apps.

Installation

Latest version is v0.118.3.

NOTICE: It is highly recommended that you update to v0.118.0 or higher ASAP for various bug fixes, including a critical world-readable vulnerability reported here. See below for information regarding Termux on Google Play.

Termux can be obtained through various sources listed below for only Android >= 7 with full support for apps and packages.

Support for both app and packages was dropped for Android 5 and 6 on 2020-01-01 at v0.83, however it was re-added just for the app without any support for package updates on 2022-05-24 via the GitHub sources. Check here for the details.

The APK files of different sources are signed with different signature keys. The Termux app and all its plugins use the same sharedUserId com.termux and so all their APKs installed on a device must have been signed with the same signature key to work together and so they must all be installed from the same source. Do not attempt to mix them together, i.e do not try to install an app or plugin from F-Droid and another one from a different source like GitHub. Android Package Manager will also normally not allow installation of APKs with different signatures and you will get errors on installation like App not installed, Failed to install due to an unknown error, INSTALL_FAILED_UPDATE_INCOMPATIBLE, INSTALL_FAILED_SHARED_USER_INCOMPATIBLE, signatures do not match previously installed version, etc. This restriction can be bypassed with root or with custom roms.

If you wish to install from a different source, then you must uninstall any and all existing Termux or its plugin app APKs from your device first, then install all new APKs from the same new source. Check Uninstallation section for details. You may also want to consider Backing up Termux before the uninstallation so that you can restore it after re-installing from Termux different source.

In the following paragraphs, "bootstrap" refers to the minimal packages that are shipped with the termux-app itself to start a working shell environment. Its zips are built and released here.

F-Droid

Termux application can be obtained from F-Droid from here.

You do not need to download the F-Droid app (via the Download F-Droid link) to install Termux. You can download the Termux APK directly from the site by clicking the Download APK link at the bottom of each version section.

It usually takes a few days (or even a week or more) for updates to be available on F-Droid once an update has been released on GitHub. The F-Droid releases are built and published by F-Droid once they detect a new GitHub release. The Termux maintainers do not have any control over the building and publishing of the Termux apps on F-Droid. Moreover, the Termux maintainers also do not have access to the APK signing keys of F-Droid releases, so we cannot release an APK ourselves on GitHub that would be compatible with F-Droid releases.

The F-Droid app often may not notify you of updates and you will manually have to do a pull down swipe action in the Updates tab of the app for it to check updates. Make sure battery optimizations are disabled for the app, check https://dontkillmyapp.com/ for details on how to do that.

Only a universal APK is released, which will work on all supported architectures. The APK and bootstrap installation size will be ~180MB. F-Droid does not support architecture specific APKs.

GitHub

Termux application can be obtained on GitHub either from GitHub Releases for version >= 0.118.0 or from GitHub Build Action workflows. For android >= 7, only install apt-android-7 variants. For android 5 and 6, only install apt-android-5 variants.

The APKs for GitHub Releases will be listed under Assets drop-down of a release. These are automatically attached when a new version is released.

The APKs for GitHub Build action workflows will be listed under Artifacts section of a workflow run. These are created for each commit/push done to the repository and can be used by users who don't want to wait for releases and want to try out the latest features immediately or want to test their pull requests. Note that for action workflows, you need to be logged into a GitHub account for the Artifacts links to be enabled/clickable. If you are using the GitHub app, then make sure to open workflow link in a browser like Chrome or Firefox that has your GitHub account logged in since the in-app browser may not be logged in.

The APKs for both of these are debuggable and are compatible with each other but they are not compatible with other sources.

Both universal and architecture specific APKs are released. The APK and bootstrap installation size will be ~180MB if using universal and ~120MB if using architecture specific. Check here for details.

Security warning: APK files on GitHub are signed with a test key that has been shared with community. This IS NOT an official developer key and everyone can use it to generate releases for own testing. Be very careful when using Termux GitHub builds obtained elsewhere except https://github.com/termux/termux-app. Everyone is able to use it to forge a malicious Termux update installable over the GitHub build. Think twice about installing Termux builds distributed via Telegram or other social media. If your device get caught by malware, we will not be able to help you.

The test key shall not be used to impersonate @termux and can't be used for this anyway. This key is not trusted by us and it is quite easy to detect its use in user generated content.

Keystore information

Alias name: alias
Creation date: Oct 4, 2019
Entry type: PrivateKeyEntry
Certificate chain length: 1
Certificate[1]:
Owner: CN=APK Signer, OU=Earth, O=Earth
Issuer: CN=APK Signer, OU=Earth, O=Earth
Serial number: 29be297b
Valid from: Wed Sep 04 02:03:24 EEST 2019 until: Tue Oct 26 02:03:24 EEST 2049
Certificate fingerprints:
         SHA1: 51:79:55:EA:BF:69:FC:05:7C:41:C7:D3:79:DB:BC:EF:20:AD:85:F2
         SHA256: B6:DA:01:48:0E:EF:D5:FB:F2:CD:37:71:B8:D1:02:1E:C7:91:30:4B:DD:6C:4B:F4:1D:3F:AA:BA:D4:8E:E5:E1
Signature algorithm name: SHA1withRSA (disabled)
Subject Public Key Algorithm: 2048-bit RSA key
Version: 3

Google Play Store (Experimental branch)

There is currently a build of Termux available on Google Play for Android 11+ devices, with extensive adjustments in order to pass policy requirements there. This is under development and has missing functionality and bugs (see here for status updates) compared to the stable F-Droid build, which is why most users who can should still use F-Droid or GitHub build as mentioned above.

Currently, Google Play will try to update installations away from F-Droid ones. Updating will still fail as sharedUserId has been removed. A planned 0.118.1 F-Droid release will fix this by setting a higher version code than used for the PlayStore app. Meanwhile, to prevent Google Play from attempting to download and then fail to install the Google Play releases over existing installations, you can open the Termux apps pages on Google Play and then click on the 3 dots options button in the top right and then disable the Enable auto update toggle. However, the Termux apps updates will still show in the PlayStore app updates list.

If you want to help out with testing the Google Play build (or cannot install Termux from other sources), be aware that it's built from a separate repository (https://github.com/termux-play-store/) - be sure to report issues there, as any issues encountered might very well be specific to that repository.

Uninstallation

Uninstallation may be required if a user doesn't want Termux installed in their device anymore or is switching to a different install source. You may also want to consider Backing up Termux before the uninstallation.

To uninstall Termux completely, you must uninstall any and all existing Termux or its plugin app APKs listed in Termux App and Plugins.

Go to Android Settings -> Applications and then look for those apps. You can also use the search feature if it’s available on your device and search termux in the applications list.

Even if you think you have not installed any of the plugins, it's strongly suggested to go through the application list in Android settings and double-check.

Important Links

Community

All community links are available here.

The main ones are the following.

Wikis

Miscellaneous

Terminal

Terminal resources

Terminal emulators

VTE (libvte): Terminal emulator widget for GTK+, mainly used in gnome-terminal. Source, Open Issues, and All (including closed) issues.
iTerm 2: OS X terminal application. Source, Issues and Documentation (which includes iTerm2 proprietary escape codes).
Konsole: KDE terminal application. Source, in particular tests, Bugs and Wishes.
hterm: JavaScript terminal implementation from Chromium. Source, including tests, and Google group.
xterm: The grandfather of terminal emulators. Source.
Connectbot: Android SSH client. Source
Android Terminal Emulator: Android terminal app which Termux terminal handling is based on. Inactive. Source.

Debugging

You can help debug problems of the Termux app and its plugins by setting appropriate logcat Log Level in Termux app settings -> <APP_NAME> -> Debugging -> Log Level (Requires Termux app version >= 0.118.0). The Log Level defaults to Normal and log level Verbose currently logs additional information. Its best to revert log level to Normal after you have finished debugging since private data may otherwise be passed to logcat during normal operation and moreover, additional logging increases execution time.

The plugin apps do not execute the commands themselves but send execution intents to Termux app, which has its own log level which can be set in Termux app settings -> Termux -> Debugging -> Log Level. So you must set log level for both Termux and the respective plugin app settings to get all the info.

Once log levels have been set, you can run the logcat command in Termux app terminal to view the logs in realtime (Ctrl+c to stop) or use logcat -d > logcat.txt to take a dump of the log. You can also view the logs from a PC over ADB. For more information, check official android logcat guide here.

Moreover, users can generate termux files stat info and logcat dump automatically too with terminal's long hold options menu More -> Report Issue option and selecting YES in the prompt shown to add debug info. This can be helpful for reporting and debugging other issues. If the report generated is too large, then Save To File option in context menu (3 dots on top right) of ReportActivity can be used and the file viewed/shared instead.

Users must post complete report (optionally without sensitive info) when reporting issues. Issues opened with (partial) screenshots of error reports instead of text will likely be automatically closed/deleted.

Log Levels

Off - Log nothing.
Normal - Start logging error, warn and info messages and stacktraces.
Debug - Start logging debug messages.
Verbose - Start logging verbose messages.

For Maintainers and Contributors

The termux-shared library was added in v0.109. It defines shared constants and utils of the Termux app and its plugins. It was created to allow for the removal of all hardcoded paths in the Termux app. Some of the termux plugins are using this as well and rest will in future. If you are contributing code that is using a constant or a util that may be shared, then define it in termux-shared library if it currently doesn't exist and reference it from there. Update the relevant changelogs as well. Pull requests using hardcoded values will/should not be accepted. Termux app and plugin specific classes must be added under com.termux.shared.termux package and general classes outside it. The termux-shared LICENSE must also be checked and updated if necessary when contributing code. The licenses of any external library or code must be honoured.

The main Termux constants are defined by TermuxConstants class. It also contains information on how to fork Termux or build it with your own package name. Changing the package name will require building the bootstrap zip packages and other packages with the new $PREFIX, check Building Packages for more info.

Check Termux Libraries for how to import termux libraries in plugin apps and Forking and Local Development for how to update termux libraries for plugins.

The versionName in build.gradle files of Termux and its plugin apps must follow the semantic version 2.0.0 spec in the format major.minor.patch(-prerelease)(+buildmetadata). When bumping versionName in build.gradle files and when creating a tag for new releases on GitHub, make sure to include the patch number as well, like v0.1.0 instead of just v0.1. The build.gradle files and attach_debug_apks_to_release workflow validates the version as well and the build/attachment will fail if versionName does not follow the spec.

Commit Messages Guidelines

Commit messages must use the Conventional Commits spec so that chagelogs as per the Keep a Changelog spec can automatically be generated by the create-conventional-changelog script, check its repo for further details on the spec. The first letter for type and description must be capital and description should be in the present tense. The space after the colon : is necessary. For a breaking change, add an exclamation mark ! before the colon :, so that it is highlighted in the chagelog automatically.

<type>[optional scope]: <description>

[optional body]

[optional footer(s)]

Only the types listed below must be used exactly as they are used in the changelog headings. For example, Added: Add foo, Added|Fixed: Add foo and fix bar, Changed!: Change baz as a breaking change, etc. You can optionally add a scope as well, like Fixed(terminal): Fix some bug. Do not use anything else as type, like add instead of Added, etc.

Added for new features.
Changed for changes in existing functionality.
Deprecated for soon-to-be removed features.
Removed for now removed features.
Fixed for any bug fixes.
Security in case of vulnerabilities.

Forking

Check TermuxConstants javadocs for instructions on what changes to make in the app to change package name.
You also need to recompile bootstrap zip for the new package name. Check building bootstrap, here and here.
Currently, not all plugins use TermuxConstants from termux-shared library and have hardcoded com.termux values and will need to be manually patched.
If forking termux plugins, check Forking and Local Development for info on how to use termux libraries for plugins.

Sponsors and Funders

GitHub Accelerator (1)

GitHub Secure Open Source Fund (1, 2)

NLnet NGI Mobifree (1, 2)

Cloudflare (1)

OtterMind/Chat2DB

Chat2DB is a free, cross-platform, local-first database client and SQL workspace for developers, DBAs, analysts, and data teams. Connect to 40+ databases, manage data, edit and run SQL, and use your own AI model to generate, explain, and optimize queries. Available on desktop, web, Docker, and CLI, with MCP support.

An AI-powered database client and SQL workspace for developers, DBAs, analysts, and data teams.

What is Chat2DB?

Chat2DB Community is a free, cross-platform database client for Windows, macOS, and Linux. It runs entirely on your machine and combines a full-featured SQL workspace with an AI assistant that you connect to your own model.

40+ databases — MySQL, PostgreSQL, Oracle, SQL Server, ClickHouse, MongoDB, Redis, SQLite, MariaDB, TiDB, Hive, DB2, Snowflake, BigQuery, Elasticsearch, Trino, TimescaleDB, Greenplum, YugabyteDB, CrateDB, QuestDB, Apache IoTDB, Firebird, HSQLDB, Apache Derby, and more via plugins — new JDBC databases can be added through configuration only, without code changes.
SQL workspace — editing, completion, formatting, execution, saved SQL, and execution history.
AI assistant — bring your own AI model to generate, explain, and optimize SQL in natural language.
Database management — browse metadata, manage tables and objects (DDL/DML), and edit data in place.
Data import and export, dashboards and charts, and an open-source CLI with MCP support.

Screenshots

Dashboards and charts	ER diagrams

Visual data management	Data import and export

Quick Start

Option 1: Desktop App

Download the installer for your platform from GitHub Releases, install it, and start connecting to your databases. No further setup is required.

Option 2: Docker

Requirements: Docker 19.03.0+, Docker Compose 2.0.0+ (Compose V2, only for the Compose variant), 2+ CPU cores, 4+ GiB RAM.

First create the encryption key (see Encryption Key for why it matters), then start the container:

# Run once from a repository checkout. Re-running reuses the same valid key.
git clone https://github.com/OtterMind/Chat2DB.git && cd Chat2DB
./script/security/init-community-encryption-key.sh

docker run --detach \
  --name chat2db-community \
  --restart unless-stopped \
  --publish 127.0.0.1:10825:10825 \
  --volume "$HOME/.chat2db-community-docker:/root/.chat2db-community" \
  --env CHAT2DB_COMMUNITY_ENCRYPTION_KEY_FILE=/run/secrets/chat2db-community-encryption.key \
  --volume "$HOME/.config/chat2db-community/encryption.key:/run/secrets/chat2db-community-encryption.key:ro" \
  chat2db/chat2db:latest

Then open http://localhost:10825 in your browser.

Alternatively, use the bundled Compose definition:

./script/security/init-community-encryption-key.sh
docker compose --file docker/docker-compose.yml up --detach

Notes:

To update, pull the new image, remove the old container, and run the start command again. Keep ~/.config/chat2db-community/encryption.key across rebuilds.
The docker run example stores application data in $HOME/.chat2db-community-docker; the Compose definition uses the chat2db-community-data named volume. These locations do not share data.
Chat2DB Community 5.3.0 uses the independent /root/.chat2db-community directory and does not automatically migrate data from earlier images that used /root/.chat2db.

Security Notes

Chat2DB Community is a single-user, local-first application. It has no user accounts or authorization boundaries between users. Keep the HTTP service bound to 127.0.0.1 or ::1 and do not expose it to other users or untrusted networks.

Custom JDBC drivers are executable Java code — install them only from sources you trust. Imported configuration files, archives, SQL files, database contents, and AI responses remain untrusted data. See the Security Policy for the complete trust boundary and vulnerability reporting process.

If you find this project useful, please give us a Star ⭐️ — it really helps!

Encryption Key

Chat2DB Community encrypts stored datasource passwords and AI model API keys with AES-256-GCM using a per-installation key. Create it once from a repository checkout (requires openssl):

./script/security/init-community-encryption-key.sh

The key is written to ~/.config/chat2db-community/encryption.key. Back this file up separately and keep it across upgrades and container rebuilds — replacing or losing it makes previously stored datasource passwords and AI model API keys unreadable. Web/headless startup fails when no valid key is provided; only Desktop mode creates a missing key automatically.

Key configuration reference (custom paths, resolution order, validation)

The key must be valid Base64 that decodes to exactly 32 bytes. The bundled initializer generates the standard padded form: 44 Base64 characters ending in =. It is cryptographic key material, not a human-readable password. Datasource passwords and AI API keys use the same key with separate authenticated AAD values, so ciphertext from one purpose cannot be decrypted as the other.

To use a custom path, pass it to the script and configure the same path when starting Chat2DB:

./script/security/init-community-encryption-key.sh /secure/path/chat2db-community.key

java -Dloader.path=chat2db-community-server/chat2db-community-start/target/lib \
    -Dchat2db.runtime.mode=community \
    -Dchat2db.mode=WEB \
    -Dchat2db.gui=false \
    -Dchat2db.network.status=OFFLINE \
    -Dchat2db.community.encryption-key-file=/secure/path/chat2db-community.key \
    -Dserver.address=127.0.0.1 \
    -Dserver.port=10825 \
    -jar chat2db-community-server/chat2db-community-start/target/chat2db-community.jar

The script's key-file path priority is the positional argument, CHAT2DB_COMMUNITY_ENCRYPTION_KEY_FILE, then the default path. It reuses a valid regular file, rejects symbolic links and non-regular files, and refuses to overwrite an invalid file. Keep the key readable only by the Chat2DB process owner.

Key configuration is resolved in this order:

JVM property chat2db.community.encryption-key containing the Base64 key.
Environment variable CHAT2DB_COMMUNITY_ENCRYPTION_KEY containing the Base64 key.
JVM property chat2db.community.encryption-key-file containing a key-file path.
Environment variable CHAT2DB_COMMUNITY_ENCRYPTION_KEY_FILE containing a key-file path.
Default file ~/.config/chat2db-community/encryption.key.

The first configured value is authoritative. A blank value, malformed Base64, a key that does not decode to 32 bytes, or an invalid key file fails startup instead of falling through to the next source. File-based configuration is recommended because it avoids placing the key value directly in process arguments or environment variables.

Automatic key-file creation depends on chat2db.mode, not chat2db.gui. Community Desktop mode (chat2db.runtime.mode=community with chat2db.mode=DESKTOP) creates the selected key file when no inline key is configured and the file is missing. Any non-Desktop mode, including normal Web/headless startup, never creates a missing key and fails until a valid key is provided or initialized. The resolved key is cached for the process lifetime, so changing key configuration requires an application restart.

Build from Source

Prerequisites

Java runtime: Eclipse Temurin 17
Node.js 18.17.0 or later
Maven 3.8 or later

Clone the Repository

git clone https://github.com/OtterMind/Chat2DB.git

Frontend

Use Yarn with the checked-in lockfile.

cd Chat2DB/chat2db-community-client
yarn install --frozen-lockfile
yarn run start:community:hot

Backend

cd Chat2DB
mvn -B clean package -Dmaven.test.skip=true -Dchat2db.finalName=chat2db-community \
    -f chat2db-community-server/pom.xml \
    -pl chat2db-community-start -am
./script/security/init-community-encryption-key.sh
java -Dloader.path=chat2db-community-server/chat2db-community-start/target/lib \
    -Dchat2db.gui=false \
    -Dchat2db.runtime.mode=community \
    -Dchat2db.mode=WEB \
    -Dchat2db.network.status=OFFLINE \
    -Dchat2db.community.encryption-key-file="$HOME/.config/chat2db-community/encryption.key" \
    -Dserver.address=127.0.0.1 \
    -Dserver.port=10825 \
    -Dspring.profiles.active=dev \
    -jar chat2db-community-server/chat2db-community-start/target/chat2db-community.jar

Build a Local Docker Image

./docker/docker-build.sh 5.3.0 chat2db/chat2db:5.3.0

Database guides

Step-by-step guides for connecting Chat2DB Community to specific databases:

BigQuery — Google BigQuery via a Google Cloud service account.

Community vs Commercial Editions

The Community edition contains the full local database client described above, including custom AI model support. The commercial Pro and Enterprise editions build on the same core and add hosted AI services, user accounts, cloud storage and multi-device sync, and team collaboration and governance features. See chat2db.ai for details.

Contributing

We welcome bug reports, feature requests, documentation improvements, testing feedback, and pull requests from the community.

Before opening an issue or submitting a pull request, please read our Contributing Guide. It explains how to report bugs, suggest improvements, and make contributions easier for maintainers to review.

For bugs and feature requests, please use GitHub Issues.
For questions, setup help, and open-ended discussions, please use GitHub Discussions.
If your pull request is related to an issue, please link it in the PR description.

Community and Support

GitHub Issues: report a bug or request a feature
GitHub Discussions: ask questions and share ideas
Discord: join our Discord server
Email: Chat2DB@ch2db.com

Acknowledgments

Thanks to everyone who has contributed to Chat2DB.

License

Chat2DB Community version 5.3.0 and later is available under the license terms in this repository. This is a source-available license based on the Apache License 2.0 with additional conditions. Chat2DB releases published before version 5.3.0, including version 0.3.7 and the earlier historical tags, remain under the Apache License 2.0.

zalexdev/strykerapp

Magic tool for pentest from your android device!

StrykerOSS

A free and open-source mobile pentest suite for Android. Authorized testing only.

StrykerOSS bundles a curated set of network, wireless and web security tools into a single rooted-Android application, exposing them through a unified, modern UI. It runs a Debian trixie (arm64) chroot under /data/local/stryker/release so heavyweight tools (Nmap, Metasploit, Nuclei, Hydra, SearchSploit, etc.) execute natively on the device — the same rootfs the rootless QEMU VM boots when root is unavailable. A built-in terminal (drawer → Terminal, or the Stryker Terminal launcher icon) drops straight into that chroot — no external shell app required.

Package: com.zalexdev.stryker
Version: 6.0
Min SDK: 24 (Android 7.0) · Target SDK: 28
License: GNU GPL v3.0 (bundled third-party components keep their own licenses — see in-app About → Open-source licenses)
Project site: zalexdev.com
Source: github.com/zalexdev/strykerapp

Capabilities

Module	Description
Dashboard	Live overview of the chroot, USB adapters, mounted state and quick actions.
WiFi networks	Scan, deauth, handshake capture, WPS attacks (Pixie Dust, common pins, custom pins) via external monitor-mode adapters.
Handshakes	Local handshake storage with rename, share, export to OnlineHashCrack and on-device cracking via Hashcat.
MAC changer	Inline + dedicated MAC randomizer with persistent profiles.
WhisperPair (BLE)	Fast Pair device discovery, CVE-2025-36911 vulnerability check and full exploit chain (RAW/RETROACTIVE/EXTENDED_RESPONSE), post-pair account-key write and HFP audio capture/passthrough.
Local network	Nmap host discovery, port scans, OS fingerprinting, per-device exploit dispatch with a live terminal.
Nmap	Direct Nmap interface with custom scripts, NSE, and exported reports.
Web scanner (Nuclei)	Multi-target Nuclei scans with severity-grouped findings and per-finding evidence.
Arsenal	Custom exploit / scanner database with template arguments (`{IP}`, `{PORT}`, `{MAC}`, `{GW}`, `{MASK}`).
HID Attacks	DuckyScript-compatible USB HID injection — pure-Java parser (Hak5 v1 + v3 superset), 7 bundled keyboard layouts (US/GB/DE/FR/ES/IT/RU), live execution log and bundled sample payloads.
USB Arsenal	USB-gadget profile manager — toggle HID keyboard/mouse, mass-storage, RNDIS/ECM/ACM functions on the fly, customise VID/PID/serial, mount `.img`/`.iso` images as removable disks.
Metasploit	Native MSF console inside the chroot with sessions, payload generation and module browser.
GeoMac	OSM-based map of captured BSSIDs / handshakes with WiGLE-style export (KML/CSV).
VNC desktop	Stand-up an in-chroot XFCE/Xfce-VNC session and view it locally.
Core manager	Mount / unmount / repair the chroot, manage installed components.

Requirements

Rooted Android device (Magisk or KernelSU recommended).
~1 GB free internal storage for the chroot, bundled tools and signatures.
External monitor-mode USB Wi-Fi adapter for handshake capture and deauthentication (Atheros AR9271 / Realtek 88XXAU recommended).
Gadget-capable kernel (optional) for HID Attacks and USB Arsenal. Required kernel options:
- CONFIG_USB_CONFIGFS=y
- CONFIG_USB_CONFIGFS_F_HID=y
- CONFIG_USB_CONFIGFS_MASS_STORAGE=y (for mass-storage profiles)
- CONFIG_USB_CONFIGFS_RNDIS=y / CONFIG_USB_CONFIGFS_ECM=y (for network profiles)
- kernel ≥ 3.19, /sys/class/udc/ populated
- NetHunter / KernelSU-Next kernels and most modern OEM kernels meet these requirements out of the box.

Build

Standard Android Gradle build. Java 8 sources, ndk-build for native code, R8 minification for release.

# Debug APK
./gradlew assembleDebug

# Release APK (minified + R8)
./gradlew assembleRelease

# Install on a connected device
./gradlew installDebug

# Lint
./gradlew lint

Output APKs land in app/build/outputs/apk/.

Release signing

Configure these in ~/.gradle/gradle.properties (or pass via -P / environment):

STRYKER_RELEASE_STORE_FILE=/path/to/keystore.jks
STRYKER_RELEASE_STORE_PASSWORD=...
STRYKER_RELEASE_KEY_ALIAS=...
STRYKER_RELEASE_KEY_PASSWORD=...

If the variables are not set, the release build is left unsigned so CI / contributors can still produce an APK.

Installation (end users)

Install the APK on a rooted device (adb install StrykerOSS-6.0.apk or sideload).
On first launch the in-app installer (AppIntroActivity) will:
- Request root (su).
- Request runtime permissions (storage, location, notifications, Bluetooth, audio).
- Download and unpack the Debian trixie arm64 chroot core (chroot64-debian.tar.gz).
- Mount the chroot at /data/local/stryker/release.
- Install optional components (Metasploit, Nuclei, Hydra, SearchSploit).
Open the built-in terminal (drawer → Terminal) for a shell straight into the chroot.
Plug in a supported USB Wi-Fi adapter for monitor-mode features.

Project layout

app/
├── src/main/java/com/zalexdev/stryker/
│   ├── MainActivity.java            # Single-Activity host, drawer navigation
│   ├── about/                       # About / info page
│   ├── appintro/                    # First-launch installer & slides
│   ├── arsenal/                     # Custom exploit/scanner database
│   ├── coremanger/                  # Chroot manage / repair UI
│   ├── custom/                      # POJO domain models
│   ├── dashboard/                   # Home dashboard
│   ├── geomac/                      # OSM map for captured BSSIDs
│   ├── handshakes/                  # Handshake browser + cracking
│   ├── hid/                         # HID Attacks: DuckyScript engine, keymaps, executor, UI
│   ├── hydra/                       # Hydra integration
│   ├── localnetwork/                # LAN scan + exploit dispatch
│   ├── macchanger/                  # MAC randomizer
│   ├── metasploit/                  # MSF integration
│   ├── nmap/                        # Nmap UI
│   ├── nuclei/                      # Web vuln scanner
│   ├── searchsploit/                # ExploitDB browser
│   ├── settings/                    # User settings
│   ├── usbarsenal/                  # USB Arsenal: gadget profiles, configfs orchestration
│   ├── utils/                       # Core helpers, process wrappers
│   ├── vnc/                         # In-chroot VNC desktop
│   ├── wifi/                        # WiFi scan / attack
│   └── wpair/                       # WhisperPair (BLE Fast Pair) module
├── src/main/jni/                    # Native code (ndk-build)
├── src/main/assets/                 # Chroot scripts, wordlists, busybox
└── src/main/res/                    # Layouts, drawables, strings, themes

Contributing

PRs and issues are welcome at github.com/zalexdev/strykerapp.

When adding a feature:

Keep modules self-contained under com.zalexdev.stryker.<module>.
Reuse Core.java helpers for SharedPreferences, SQLite, asset extraction and root process execution rather than re-rolling them.
Funnel root commands through Core.generateSuProcess() (direct su or chroot dispatch).
Match the existing Material 3 design language — MaterialCardView, MaterialButton, dashboard accent colors, monospace terminals.
Keep targetSdk = 28 unless you are ready to migrate all storage / permission code paths.

License

StrykerOSS is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License v3.0 as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. The full text is in LICENSE.

StrykerOSS — a mobile pentest suite for Android.
Copyright (C) 2021-2026 zalexdev

This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
GNU General Public License for more details.

You should have received a copy of the GNU General Public License
along with this program.  If not, see <https://www.gnu.org/licenses/>.

Bundled third-party components (terminal emulator, SDL/Xorg, custom-tabs, wordlists, PoCs, etc.) are distributed under their own GPLv3-compatible licenses — see THIRD-PARTY-NOTICES.md and the in-app About → Open-source licenses screen for attributions.

Disclaimer

StrykerOSS is provided for authorized security testing, education and research only. You are responsible for complying with all applicable laws and obtaining explicit permission before testing any system or device you do not own. The authors accept no liability for misuse.

iluwatar/java-design-patterns

Design patterns implemented in Java

Design Patterns Implemented in Java

Read in different language : zh, zh-TW ,ko, fr, tr, ar, es, pt, id, ru, de, ja, vi, bn, np, it, da

Introduction

Design patterns are the best, formalized practices a programmer can use to solve common problems when designing an application or system.

Design patterns can speed up the development process by providing tested, proven development paradigms.

Reusing design patterns helps prevent subtle issues that cause major problems, and it also improves code readability for coders and architects who are familiar with the patterns.

Getting Started

This site showcases Java Design Patterns. The solutions have been developed by experienced programmers and architects from the open-source community. The patterns can be browsed by their high-level descriptions or by looking at their source code. The source code examples are well commented and can be thought of as programming tutorials on how to implement a specific pattern. We use the most popular battle-proven open-source Java technologies.

Before you dive into the material, you should be familiar with various Software Design Principles.

All designs should be as simple as possible. You should start with KISS, YAGNI, and Do The Simplest Thing That Could Possibly Work principles. Complexity and patterns should only be introduced when they are needed for practical extensibility.

Once you are familiar with these concepts you can start drilling down into the available design patterns by any of the following approaches:

Search for a specific pattern by name. Can't find one? Please report a new pattern here.
Using tags such as Performance, Gang of Four or Data access.
Using pattern categories, Creational, Behavioral, and others.

Hopefully, you find the object-oriented solutions presented on this site useful in your architectures and have as much fun learning them as we had while developing them.

How to Contribute

If you are willing to contribute to the project you will find the relevant information in our developer wiki. We will help you and answer your questions in the Gitter chatroom.

The Book

The design patterns are now available as an e-book. Find out more about "Open Source Java Design Patterns" here: https://payhip.com/b/bNQFX

The project contributors can get the book for free. Contact the maintainer via Gitter chatroom or email (iluwatar (at) gmail (dot) com ). Send a message that contains your email address, Github username, and a link to an accepted pull request.

License

This project is licensed under the terms of the MIT license.

Contributors

_{Ilkka Seppälä} 📆 🚧 🖋	_{Subhrodip Mohanta} 💻 👀 🚧	_amit1307 💻	_{Narendra Pathai} 💻 🤔 👀	_{Jeroen Meulemeester} 💻	_{Joseph McCarthy} 💻
_Thomas 💻	_{Anurag Agarwal} 💻	_{Markus Moser} 🎨 💻 🤔	_{Sabiq Ihab} 💻	_{Amit Dixit} 💻	_{Piyush Kailash Chaudhari} 💻
_joshzambales 💻	_{Kamil Pietruszka} 💻	_{Zafar Khaydarov} 💻 📖	_{Paul Campbell} 💻	_{Argyro Sioziou} 💻	_{TylerMcConville} 💻
_saksham93 💻	_nikhilbarar 💻	_{Colin But} 💻	_Ruslan 💻	_{Juho Kang} 💻	_{Dheeraj Mummareddy} 💻
_{Bernardo Sulzbach} 💻	_{Aleksandar Dudukovic} 💻	_{Yusuf Aytaş} 💻	_{Mihály Kuprivecz} 💻	_{Stanislav Kapinus} 💻	_GVSharma 💻
_{Srđan Paunović} 💻	_{Petros G. Sideris} 💻	_{Pramod Gupta} 👀	_{Amarnath Chandana} 💻	_Anurag870 💻 📖	_{Wes Gilleland} 💻
_{Harshraj Thakor} 💻	_{Martin Vandenbussche} 💻	_{Alexandru Somai} 💻	_{Artur Mogozov} 💻	_anthony 💻	_{Christian Cygnus} 💻
_{Dima Gubin} 💻	_{Joshua Jimenez} 💻	_{Kai Winter} 💻	_lbroman 💻	_Przemek 💻	_{Prafful Agarwal} 🖋
_{Sanket Panhale} 🖋	_staillebois 💻	_{Krisztián Nagy} 💻	_{Alexander Ivanov} 💻	_{Yosfik Alqadri} 💻	_{Agustí Becerra Milà} 💻
_{Juan Manuel Suárez} 💻	_{Luigi Cortese} 💻	_{Katarzyna Rzepecka} 💻	_adamski.pro 💻	_{Shengli Bai} 💻	_Boris 💻
_{Dmitry Avershin} 💻	_靳阳 💻	_hoangnam2261 💻	_{Arpit Jain} 💻	_{Jón Ingi Sveinbjörnsson} 💻	_{Kirill Vlasov} 💻
_{Mitchell Irvin} 💻	_Ranjeet 💻	_PhoenixYip 💻	_{M Saif Asif} 💻	_{kanwarpreet25} 💻	_{Leon Mak} 💻
_{Per Wramdemark} 💻	_{Evan Sia Wai Suan} 💻	_{AnaghaSasikumar} 💻	_{Christoffer Hamberg} 💻	_{Dominik Gruntz} 💻	_Hannes 💻
_{Leo Gutiérrez Ramírez} 💻	_{Zhang WH} 💻	_{Christopher O'Connell} 💻	_{George Mavroeidis} 💻	_{Hemant Bothra} 💻 🎨	_{Kevin Peters} 💻
_{George Aristy} 💻	_{Mahendran Mookkiah} 💻	_Azureyjt 💻	_gans 💻	_Matt 🖋	_{Gopinath Langote} 💻
_Hoswey 💻	_{Amit Pandey} 💻	_gwildor28 🖋	_田浩 🖋	_{Stamatis Pitsios} 💻	_qza 💻
_{Rodolfo Forte} 🖋	_{Ankur Kaushal} 💻	_{Ovidijus Okinskas} 💻	_{Robert Kasperczyk} 💻	_{Tapio Rautonen} 💻	_{Yuri Orlov} 💻
_{Varun Upadhyay} 💻	_{Aditya Pal} 💻	_{grzesiekkedzior} 💻 👀	_{Sivasubramani M} 💻	_{Sami Airaksinen} 💻	_{Janne Sinivirta} 💻
_{Boris-Chengbiao Zhou} 🖋	_{Jacob Hein} 🖋	_{Richard Jones} 🖋	_{Rachel M. Carmena} 🖋	_{Zaerald Denze Lungos} 🖋	_{Lars Kappert} 🖋
_{Mike Liu} 🌍	_{Matt Dolan} 💻 👀	_Manan 👀	_{Nishant Arora} 💻	_Peeyush 💻	_Rakesh 💻 👀
_{Wei Seng} 💻	_{Ashish Trivedi} 💻	_洪月阳 💻	_xdvrx1 👀 🤔	_{Bethan Palmer} 💻	_{Toxic Dreamz} 💻
_{Edy Cu Tjong} 📖	_{Michał Krzywański} 💻	_{Stefan Birkner} 💻	_{Fedor Skvorcov} 💻	_samilAyoub 💻	_{Vladislav Golubinov} 💻
_Swaraj 💻	_{Christoph Flick} 📖	_Ascênio 👀	_{Domenico Sibilio} 📖	_{Akash Chandwani} 👀	_{Pavlo Manannikov} 💻
_Eiman 💻	_Rocky 📖	_{Ibrahim ali abdelghany} 👀	_{Girish Kulkarni} 📖	_{Omar Karazoun} 💻	_{Jeff Evans} 💻
_{Vivek Singh} 💻	_siavash 💻	_ruchpeanuts 📖	_warp125 🌍	_{KHADIR Tayeb} 🌍	_ignite1771 💻
_{Halil Demir} 🌍	_{Rohit Singh} 💻	_byoungju94 💻	_{Moustafa Farhat} 🌍	_{Martel Richard} 💻	_va1m 💻
_{Noam Greenshtain} 💻	_{yonghong Xu} 📖	_jinishavora 👀 💻	_{Elvys Soares} 💻	_zWeBrain 💻	_余林颖 🌍
_Alain 🌍	_VR 📖	_JackieNim 💻	_EdisonE3 💻	_Tao 💻	_{Juan Manuel Abate} 🌍
_Xenilo137 💻	_{Samuel Souza} 💻 📖	_{Marlo Henrique} 🌍	_AndriyPyzh 💻	_{karthikbhat13} 💻	_{Morteza Adigozalpour} 💻
_{Nagaraj Tantri} 💻	_{Francesco Scuccimarri} 💻	_{Conny Hansson} 📖	_{Muklas Rahmanto} 🌍	_Vadim 🌍	_{Simran Keshri} 💻
_JCarlos 🌍	_{Ali Ghasemi} 💻	_{Carl Dea} 💻	_Mozartus 🌍	_{Manvi Goel} 📖	_{Anum Amin} 📖
_{Reo Uehara} 🌍	_Fiordy 📖	_Harshal 💻	_{Abhinav Vashisth} 📖	_Kevin 👀 💻	_Shrirang 👀 💻
_{interactwithankush} 💻	_CharlieYu 💻	_{Leisterbecker} 💻	_{DragonDreamer} 💻	_{ShivanshCharak} 💻	_HattoriHenzo 💻
_{Arnab Sen} 💻	_{MohanaRao SV} 💻	_{Yonatan Karp-Rudin} 💻 👀	_Oliani 💻	_{Renjie LIU} 💻	_{perfect guy} 📖
_xyllq999 💻	_{Mohamed Bilal} 📖	_{Karshil sheth} 💻	_kongleong86 💻	_{Aitor Fidalgo Sánchez} 🌍 📖 👀	_{Victor He} 💻
_{Minh Nguyen} 🌍 📖	_{Victor He} 📖	_yiichan 📖	_{Pan Sem} 📖	_zhoumengyks 💻	_you 🌍
_Thanks 🌍	_{LazyProgrammer} 📖	_{Mohammed Faizan Ahmed} 📖	_{Bruno Fernandes} 💻	_SammanPali 📖	_{Qixiang Chen} 📖
_{Shourya Manekar} 🌍	_Alan 🌍	_JanFidor 💻 📖	_{Anton Yakutovich} 💻	_steph88ss 📖	_{Yujan Ranjitkar} 🌍
_yusha-g 🌍	_{Robert Volkmann} 💻 👀	_{Bipin Kumar Chaurasia} 📖	_KyleSong30 📖	_u7281975 📖	_{harshalkhachane} 💻
_{Tejas Singh} 📖 🌍	_{Sudarsan Balaji} 💻	_{Vaibhav Agrawal} 📖	_u7275858 💻	_prasad-333 📖	_JurenXu 💻
_murphShaw 📖	_XianWu99 📖	_{JoshuaSinglaANU} 💻	_{Ricardo Ramos} 🌍	_{Farid Zouheir} 🌍	_{Vinícius A. B.} 🌍
_{Stefanel Stan} 💻	_{Prince bhati} 🌍	_WuLang 📖	_{Hugo Kat} 💻	_{Shivanagouda Agasimani} 💻	_Aparna 💻
_{Girolamo Giordano} 🌍	_Chak-C 💻	_{Nakul Nambiar} 💻	_{KarmaTashiCat} 🌍	_marikattt 💻	_{Hashvardhan Parmar} 🌍
_YongHwan 📖 🌍	_{Shogo Hida} 🌍	_Eugene 💻	_Piyush 📖	_{Rahul Raj} 💻	_{Bharath Kalyan S} 💻
_{Saiteja Reddy} 🌍	_{Enrique Clerici} 🌍	_{Ramil Sayetov} 🌍	_东方未白 💻	_{Fredrik Sejr} 🌍	_{akshatarora0013} 💻
_{Mughees Qasim} 💻	_behappyleee 🌍	_{Ayush Thakur} 🌍	_{Anthony Bosch} 💻	_trananso 📖	_{Giammaria Biffi} 🌍
_{Saiful Haque} 💻	_JabezBrew 💻	_{konstantin-goldman} 📖	_{Tien Nguyen Minh} 💻 🌍	_Vladimir 🌍	_Surjendu 🌍 💻
_bakazhou 💻	_{Owen Leung} 💻	_{Stavros Barousis} 📖	_{Syyed Ibrahim Abdullah} 🌍	_{JiaDi Zhang} 🌍	_{Sanchit Bansal} 📖
_{Md Saiful Islam} 📖	_{Antonio Addeo} 📖 💻	_{Allagadda Sai Upendranath} 📖	_{Matheus Braga} 🌍 📖	_{Appari Satya Barghav} 📖	_{Marcel Ribeiro-Dantas} 📖
_{Muhammad Hanif Amrullah} 🌍	_JackH408 📖	_Shubham 🌍	_{Nishant Jain} 📖	_{Rhitam Chaudhury} 📖	_JerryZhao275 📖
_{Leonardo Lisanti} 🌍	_{Yennifer Herrera} 🌍 👀	_jnniu-n 🌍 📖	_{Miguel Angel Perez Garcia} 👀 🌍	_{Suwan Sankaja} 🌍	_alok 📖
_{Daniel Lisboa} 🌍	_{Sam Powell} 📖	_{João Fernandes} 🌍	_{Hong Geon-ui} 🌍	_Doksanbir 💻 📖 👀	_Chant3ll3 📖 🌍
_{YongHwan Kwon} 💻	_{Jakub Klimek} 💻	_believe 🌍	_{egg0102030405} 🌍 📖	_{Ved Asole} 💻	_NewMorning 🌍
_{资深老萌新} 🌍	_{Seunghwan Jeon} 🌍	_sugavanesh 💻	_FinnS-F 💻	_jerryyummy 🌍	_{Manoj Chowdary} 💻
_Aditya 📖 💻	_nooynayr 📖	_CYBERCRUX2 📖	_{Luis Mateo Hincapié Martinez} 🌍 👀	_guqing 💻	_{Sashir Estela} 💻
_omahs 📖	_{leif e.} 💻	_{Jun Kang} 💻	_{Kishalay Pandey} 💻	_drishtii7 💻	_{David Medina Orozco} 🌍 👀
_{Roman Leontev} 💻	_Riley 💻	_k1w1dev 💻	_dev-yugantar 💻	_Adelya 💻	_{gatlanagaprasanna} 📖
_{Avinash Shukla} 💻	_{Mayank Choudhary} 💻	_romannimets 💻	_Joel 💻	_{Walyson Moises} 💻	_Xcyq 💻
_Ritabrata 👀	_{Trivikram Kamat} 💻	_{Vincent Vanghelle} 🌍	_{Antoine Héritier} 🌍	_QinShower 🌍	_{LakshyaPunyani-01} 💻
_jasonjyu 💻	_jeffmorrison 💻	_{David M.} 💻	_{Patrick Kleindienst} 💻	_Juyeon 🌍	_{Mammad Yahyayev} 📖
_Salma 💻	_{Arpit Sarang} 💻	_Maya 🌍	_HabibaMekay 💻	_{Ahmed-Taha-981} 💻	_{Malak Elbanna} 💻
_BiKangNing 📖	_{Tarun Vishwakarma} 💻	_{Shahd Hossam} 💻	_{Mehdi Rahimi} 💻	_{Clint Airé} 💻	_darkhyper24 💻
_{Mohaned Atef} 💻	_{Maxim Evtush} 💻	_{Harshita Vidapanakal} 💻	_smile-ab 🌍 💻	_{Francisco-G-P} 🌍	_{Gabriel Duarte} 📖
_{Deniz Altunkapan} 🌍	_{John Klint} 💻	_{Sanura Hettiarachchi} 💻	_{Kim Gi Uk} 💻	_{Suchismita Deb} 💻	_{ssrijan-007-sys} 💻
_e5LA 💻 📖	_{Maziyar Gerami} 🌍	_{yoobin_mion} 💻	_{Soumik Sarker} 📖	_{Naman Srivastava} 💻	_{Thanh Nguyen Duc} 💻
_{Soham Kamble} 💻	_Olexandr88 📖	_{Nils Reichardt} 🛡️	_{Christopher Lusk} 🛡️	_dagecko 🛡️	_jackmisbach 🛡️
_avivdon 🛡️	_{Aditya Kumawat} 💻	_devch37 💻	_{HY-love-sleep} 💻	_CMD137 💻	_QuantumRange 📖
_{Dhiraj Birajdar} 📖	_{Stefan Siebers} 🌍	_{OrbisAI Security} 🛡️	_{Raju Gupta} 💻	_김정모 💻	_{Anakin Yen} 🌍
_{Giuliano Oliveira} 🌍	_Priyanshu 💻	_{Arnab Nandy} 📖	_{BAGHDAD Mohamed} 💻	_{Anvesh Srivastava} 💻	_{Mukul Howale} 💻

NationalSecurityAgency/ghidra

Ghidra is a software reverse engineering (SRE) framework

Ghidra Software Reverse Engineering Framework

Ghidra is a software reverse engineering (SRE) framework created and maintained by the National Security Agency Research Directorate. This framework includes a suite of full-featured, high-end software analysis tools that enable users to analyze compiled code on a variety of platforms including Windows, macOS, and Linux. Capabilities include disassembly, assembly, decompilation, graphing, and scripting, along with hundreds of other features. Ghidra supports a wide variety of processor instruction sets and executable formats and can be run in both user-interactive and automated modes. Users may also develop their own Ghidra extension components and/or scripts using Java or Python.

In support of NSA's Cybersecurity mission, Ghidra was built to solve scaling and teaming problems on complex SRE efforts, and to provide a customizable and extensible SRE research platform. NSA has applied Ghidra SRE capabilities to a variety of problems that involve analyzing malicious code and generating deep insights for SRE analysts who seek a better understanding of potential vulnerabilities in networks and systems.

If you are a U.S. citizen interested in projects like this, to develop Ghidra and other cybersecurity tools for NSA to help protect our nation and its allies, consider applying for a career with us.

Security Warning

WARNING: There are known security vulnerabilities within certain versions of Ghidra. Before proceeding, please read through Ghidra's Security Advisories for a better understanding of how you might be impacted.

Install

To install an official pre-built multi-platform Ghidra release:

Install JDK 21 64-bit
Download a Ghidra release file
- NOTE: The official multi-platform release file is named ghidra_<version>_<release>_<date>.zip which can be found under the "Assets" drop-down. Downloading either of the files named "Source Code" is not correct for this step.
Extract the Ghidra release file
- NOTE: Do not extract on top of an existing installation
Launch Ghidra: ./ghidraRun (ghidraRun.bat for Windows)
- or launch PyGhidra: ./support/pyghidraRun (support\pyghidraRun.bat for Windows)

For additional information and troubleshooting tips about installing and running a Ghidra release, please refer to the Getting Started document which can be found at the root of a Ghidra installation directory.

Build

To create the latest development build for your platform from this source repository:

Install build tools:

JDK 25 64-bit
Gradle 9.1.0+ (or provided Gradle wrapper if Internet connection is available)
Python3 (version 3.9 to 3.14) with bundled pip
GCC or Clang, and make (Linux/macOS-only)
Microsoft Visual Studio 2017+ or Microsoft C++ Build Tools with the following components installed (Windows-only):
- MSVC
- Windows SDK
- C++ ATL

Download and extract the source:

Download from GitHub

unzip ghidra-master
cd ghidra-master

NOTE: Instead of downloading the compressed source, you may instead want to clone the GitHub repository: git clone https://github.com/NationalSecurityAgency/ghidra.git

Download additional build dependencies into source repository:

NOTE: If an Internet connection is available and you did not install Gradle, the ./gradlew (or gradlew.bat) command may be used in place of the gradle command in the following instructions.

gradle -I gradle/support/fetchDependencies.gradle

Create development build:

gradle buildGhidra

The compressed development build will be located at build/dist/.

For more detailed information on building Ghidra, please read the Developer's Guide.

For issues building, please check the Known Issues section for possible solutions.

Develop

User Scripts and Extensions

Ghidra installations support users writing custom scripts and extensions via the GhidraDev plugin for Eclipse. The plugin and its corresponding instructions can be found within a Ghidra release at Extensions/Eclipse/GhidraDev/ or at this link. Alternatively, Visual Studio Code may be used to edit scripts by clicking the Visual Studio Code icon in the Script Manager. Fully-featured Visual Studio Code projects can be created from a Ghidra CodeBrowser window at Tools -> Create VSCode Module project.

NOTE: Both the GhidraDev plugin for Eclipse and Visual Studio Code integrations only support developing against fully built Ghidra installations which can be downloaded from the Releases page.

Advanced Development

To develop the Ghidra tool itself, it is highly recommended to use Eclipse, which the Ghidra development process has been highly customized for.

Install build and development tools:

Follow the above build instructions so the build completes without errors
Install Eclipse IDE for Java Developers

Prepare the development environment:

gradle prepdev eclipse buildNatives

Import Ghidra projects into Eclipse:

File -> Import...
General | Existing Projects into Workspace
Select root directory to be your downloaded or cloned ghidra source repository
Check Search for nested projects
Click Finish

When Eclipse finishes building the projects, Ghidra can be launched and debugged with the provided Ghidra Eclipse run configuration.

For more detailed information on developing Ghidra, please read the Developer's Guide.

Contribute

If you would like to contribute bug fixes, improvements, and new features back to Ghidra, please take a look at our Contributor's Guide to see how you can participate in this open source project.

openjdk/jdk

JDK main-line development https://openjdk.org/projects/jdk

Welcome to the JDK!

For build instructions please see the online documentation, or either of these files:

doc/building.html (html version)
doc/building.md (markdown version)

See https://openjdk.org/ for more information about the OpenJDK Community and the JDK and see https://bugs.openjdk.org for JDK issue tracking.

jenkinsci/jenkins

Jenkins automation server

About

In a nutshell, Jenkins is the leading open-source automation server. Built with Java, it provides over 2,000 plugins to support automating virtually anything, so that humans can spend their time doing things machines cannot.

What to Use Jenkins for and When to Use It

Use Jenkins to automate your development workflow, so you can focus on work that matters most. Jenkins is commonly used for:

Building projects
Running tests to detect bugs and other issues as soon as they are introduced
Static code analysis
Deployment

Execute repetitive tasks, save time, and optimize your development process with Jenkins.

Downloads

The Jenkins project provides official distributions as WAR files, Docker images, native packages and installers for platforms including several Linux distributions and Windows. See the Downloads page for references.

For all distributions Jenkins offers two release lines:

Weekly - Frequent releases which include all new features, improvements, and bug fixes.
Long-Term Support (LTS) - Older release line which gets periodically updated via bug fix backports.

Latest releases:

Getting Started (Development)

For more information on setting up your development environment, contributing, and working with Jenkins internals, check the contributing guide and the Jenkins Developer Documentation.

Source

Our latest and greatest source of Jenkins can be found on GitHub. Fork us!

Contributing to Jenkins

New to open source or Jenkins? Here’s how to get started:

Read the Contribution Guidelines
Check our good first issues
Join our Gitter chat for questions and help

For more information about participating in the community and contributing to the Jenkins project, see this page.

Documentation for Jenkins core maintainers is in the maintainers guidelines.

News and Website

All information about Jenkins can be found on our official website, including documentation, blog posts, plugin listings, community updates, and more.

Stay up-to-date with the latest Jenkins news, tutorials, and release notes:

Follow Jenkins on social media to stay connected with the community:

Governance

The Jenkins project is governed by an open source community. To learn more about the governance structure, project leadership, and how decisions are made, visit the Governance Page.

Adopters

Jenkins is trusted by millions of users and adopted by thousands of companies around the world — from startups to enterprises — to automate their software delivery pipelines.

Explore the Adopters Page and https://stories.jenkins.io to see:

Companies and organizations using Jenkins
Success stories and case studies
How Jenkins is used in different industries

If your company uses Jenkins and you'd like to be featured, feel free to submit your story!

License

Jenkins is licensed under the MIT License.

kestra-io/kestra

Event Driven Orchestration & Scheduling Platform for Mission Critical Applications

Open-source orchestration platform for data, AI, and infrastructure workflows

Click on the image to learn how to get started with Kestra in 3 minutes.

🌟 What is Kestra?

Kestra is an open-source, event-driven orchestration platform for data, AI, and infrastructure workflows. It unifies scheduled and event-driven automation behind a declarative, language-agnostic interface. By bringing Infrastructure as Code best practices to your data, process, and microservice pipelines, you can build reliable workflows directly from the UI in just a few lines of YAML.

📖 Table of Contents

Key Features:

Everything as Code and from the UI: keep workflows as code with a Git Version Control integration, even when building them from the UI.
Event-Driven & Scheduled Workflows: automate both scheduled and real-time event-driven workflows via a simple trigger definition.
Declarative YAML Interface: define workflows using a simple configuration in the built-in code editor.
Rich Plugin Ecosystem: hundreds of plugins built in to extract data from any database, cloud storage, or API, and run scripts in any language.
Intuitive UI & Code Editor: build and visualize workflows directly from the UI with syntax highlighting, auto-completion and real-time syntax validation.
Scalable: designed to handle millions of workflows, with high availability and fault tolerance.
Version Control Friendly: write your workflows from the built-in code Editor and push them to your preferred Git branch directly from Kestra, enabling best practices with CI/CD pipelines and version control systems.
Structure & Resilience: tame chaos and bring resilience to your workflows with namespaces, labels, subflows, retries, timeout, error handling, inputs, outputs that generate artifacts in the UI, variables, conditional branching, advanced scheduling, event triggers, backfills, dynamic tasks, sequential and parallel tasks, and skip tasks or triggers when needed by setting the flag disabled to true.

🧑‍💻 The YAML definition gets automatically adjusted any time you make changes to a workflow from the UI or via an API call. Therefore, the orchestration logic is always managed declaratively in code, even if you modify your workflows in other ways (UI, CI/CD, Terraform, API calls).

🚀 Quick Start

Launch on AWS (CloudFormation)

Deploy Kestra on AWS using our CloudFormation template:

Launch on Google Cloud (Terraform deployment)

Deploy Kestra on Google Cloud Infrastructure Manager using our Terraform module.

Get Started Locally in 5 Minutes

Launch Kestra in Docker

Make sure that Docker is running. Then, start Kestra in a single command:

docker run --pull=always -it -p 8080:8080 --user=root \
  --name kestra --restart=always \
  -v kestra_data:/app/storage \
  -v /var/run/docker.sock:/var/run/docker.sock \
  -v /tmp:/tmp \
  kestra/kestra:latest server local

If you're on Windows and use PowerShell:

docker run --pull=always -it -p 8080:8080 --user=root `
  --name kestra --restart=always `
  -v "kestra_data:/app/storage" `
  -v "/var/run/docker.sock:/var/run/docker.sock" `
  -v "C:/Temp:/tmp" `
  kestra/kestra:latest server local

If you're on Windows and use Command Prompt (CMD):

docker run --pull=always -it -p 8080:8080 --user=root ^
  --name kestra --restart=always ^
  -v "kestra_data:/app/storage" ^
  -v "/var/run/docker.sock:/var/run/docker.sock" ^
  -v "C:/Temp:/tmp" ^
  kestra/kestra:latest server local

If you're on Windows and use WSL (Linux-based environment in Windows):

docker run --pull=always -it -p 8080:8080 --user=root \
  --name kestra --restart=always \
  -v kestra_data:/app/storage \
  -v "/var/run/docker.sock:/var/run/docker.sock" \
  -v "/mnt/c/Temp:/tmp" \
  kestra/kestra:latest server local

Check our Installation Guide for other deployment options (Docker Compose, Podman, Kubernetes, AWS, GCP, Azure, and more).

Access the Kestra UI at http://localhost:8080 and start building your first flow!

Your First Hello World Flow

Create a new flow with the following content:

id: hello_world
namespace: dev

tasks:
  - id: say_hello
    type: io.kestra.plugin.core.log.Log
    message: "Hello, World!"

Run the flow and see the output in the UI!

🧩 Plugin Ecosystem

Kestra's functionality is extended through a rich ecosystem of plugins that empower you to run tasks anywhere and code in any language, including Python, Node.js, R, Go, Shell, and more. Here's how Kestra plugins enhance your workflows:

Run Anywhere:
- Local or Remote Execution: Execute tasks on your local machine, remote servers via SSH, or scale out to serverless containers using Task Runners.
- Docker and Kubernetes Support: Seamlessly run Docker containers within your workflows or launch Kubernetes jobs to handle compute-intensive workloads.
Code in Any Language:
- Scripting Support: Write scripts in your preferred programming language. Kestra supports Python, Node.js, R, Go, Shell, and others, allowing you to integrate existing codebases and deployment patterns.
- Flexible Automation: Execute shell commands, run SQL queries against various databases, and make HTTP requests to interact with APIs.
Event-Driven and Real-Time Processing:
- Real-Time Triggers: React to events from external systems in real-time, such as file arrivals, new messages in message buses (Kafka, Redis, Pulsar, AMQP, MQTT, NATS, AWS SQS, Google Pub/Sub, Azure Event Hubs), and more.
- Custom Events: Define custom events to trigger flows based on specific conditions or external signals, enabling highly responsive workflows.
Cloud Integrations:
- AWS, Google Cloud, Azure: Integrate with a variety of cloud services to interact with storage solutions, messaging systems, compute resources, and more.
- Big Data Processing: Run big data processing tasks using tools like Apache Spark or interact with analytics platforms like Google BigQuery.
Monitoring and Notifications:
- Stay Informed: Send messages to Slack channels, email notifications, or trigger alerts in PagerDuty to keep your team updated on workflow statuses.

Kestra's plugin ecosystem is continually expanding, allowing you to tailor the platform to your specific needs. Whether you're orchestrating complex data pipelines, automating scripts across multiple environments, or integrating with cloud services, there's likely a plugin to assist. And if not, you can always build your own plugins to extend Kestra's capabilities.

🧑‍💻 Note: This is just a glimpse of what Kestra plugins can do. Explore the full list on our Plugins Page.

📚 Key Concepts

Flows: the core unit in Kestra, representing a workflow composed of tasks.
Tasks: individual units of work, such as running a script, moving data, or calling an API.
Namespaces: logical grouping of flows for organization and isolation.
Triggers: schedule or events that initiate the execution of flows.
Inputs & Variables: parameters and dynamic data passed into flows and tasks.

🎨 Build Workflows Visually

Kestra provides an intuitive UI that allows you to interactively build and visualize your workflows:

Drag-and-Drop Interface: add and rearrange tasks from the Topology Editor.
Real-Time Validation: instant feedback on your workflow's syntax and structure to catch errors early.
Auto-Completion: smart suggestions as you type to write flow code quickly and without syntax errors.
Live Topology View: see your workflow as a Directed Acyclic Graph (DAG) that updates in real-time.

🔧 Extensible and Developer-Friendly

Plugin Development

Create custom plugins to extend Kestra's capabilities. Check out our Plugin Developer Guide to get started.

Infrastructure as Code

Version Control: store your flows in Git repositories.
CI/CD Integration: automate deployment of flows using CI/CD pipelines.
Terraform Provider: manage Kestra resources with the official Terraform provider.

🌐 Join the Community

Stay connected and get support:

Slack: Join our Slack community to ask questions and share ideas.
LinkedIn: Follow us on LinkedIn — next to Slack and GitHub, this is our main channel to share updates and product announcements.
YouTube: Subscribe to our YouTube channel for educational video content. We publish new videos every week!
X: Follow us on X if you're still active there.

🤝 Contributing

We welcome contributions of all kinds!

Report Issues: Found a bug or have a feature request? Open an issue on GitHub.
Contribute Code: Check out our Contributor Guide for initial guidelines, and explore our good first issues for beginner-friendly tasks to tackle first.
Develop Plugins: Build and share plugins using our Plugin Developer Guide.
Contribute to our Docs: Contribute edits or updates to keep our documentation top-notch.

📄 License

Kestra is licensed under the Apache 2.0 License © Kestra Technologies.

⭐️ Stay Updated

Give our repository a star to stay informed about the latest features and updates!

Thank you for considering Kestra for your workflow orchestration needs. We can't wait to see what you'll build!

apache/doris

Apache Doris is a real-time analytics and hybrid search database for AI agents.

🌍 Read this in other language

English • العربية • বাংলা • Deutsch • Español • فارسی • Français • हिन्दी • Bahasa Indonesia • Italiano • 日本語 • 한국어 • Polski • Português • Română • Русский • Slovenščina • ไทย • Türkçe • Українська • Tiếng Việt • 简体中文 • 繁體中文

Apache Doris

Apache Doris is an open-source, real-time analytics and search database built on MPP architecture. It provides fast SQL analytics, lakehouse query acceleration, and hybrid search across structured, text, and vector data.

Explore the official website for the latest product overview, use cases, ecosystem updates, blogs, and user stories. For version updates, see all release notes.

📈 Use Cases

Use Case	What it provides
Customer-Facing Analytics	Ship sub-second interactive analytics to external users.
Data Warehousing	Build one real-time warehouse across business domains.
Observability	Analyze high-throughput logs, events, and metrics with SQL.
Doris for AI	Use vector, text, JSON, and structured search in one SQL engine.

🚀 Core Capabilities

Apache Doris is built around three core capabilities. The website is the source of truth for detailed product descriptions and examples.

Capability	What it provides
Real-Time Analytics	Streaming ingestion, incremental transformation, and sub-second queries under high concurrency.
Lakehouse Analytics	Fast SQL analytics over open table formats such as Iceberg, Delta Lake, and Hudi.
Hybrid Search	SQL-native analytics across JSON, full-text, and vector data for AI and search workloads.

🔌 Ecosystem

Doris sits at the center of the modern data stack. It connects upstream databases, streaming systems, and lakehouse storage with downstream BI, AI, analytics, and observability tools.

For the latest ecosystem coverage, visit the official website and the connection and integration documentation.

👣 Get Started

🧱 Architecture

Apache Doris supports both compute-storage coupled and compute-storage decoupled deployments. In decoupled mode, stateless compute groups run over shared object storage, so you can scale compute on demand and isolate workloads.

Learn more in the deployment guide and deployment mode guide.

📣 Project Updates

Resource	What it provides
Community Report	Weekly updates on community activity, merged PRs, contributors, and feature progress.
Roadmap 2026	The 2026 planning discussion for AI and hybrid search, query engine, storage, and data lake work.

🧩 Components

Doris provides connectors and tools for common data engineering workflows.

👨‍👩‍👧‍👦 Users

Apache Doris is used in production by thousands of companies worldwide across internet services, finance, retail, logistics, manufacturing, energy, telecommunications, AI, and other industries.

🙌 Contributors

Apache Doris graduated from the Apache Incubator and became an Apache Top-Level Project in June 2022. Thanks to all community contributors who help build Doris.

🌈 Community and Support

💬 Contact Us

🧰 Links

Apache Doris official website: doris.apache.org
X: @doris_apache
Medium: @ApacheDoris

📜 License

Apache License, Version 2.0

Note Some licenses of the third-party dependencies are not compatible with Apache 2.0 License. So you need to disable some Doris features to comply with Apache 2.0 License. For details, refer to the thirdparty/LICENSE.txt

StarRocks/starrocks

The world's fastest open query engine for sub-second analytics both on and off the data lakehouse. With the flexibility to support nearly any scenario, StarRocks provides best-in-class performance for multi-dimensional analytics, real-time analytics, and ad-hoc queries. A Linux Foundation project.

Download | Docs | Benchmarks | Demo

StarRocks is the world's fastest open query engine for sub-second, ad-hoc analytics both on and off the data lakehouse. With average query performance 3x faster than other popular alternatives, StarRocks is a query engine that eliminates the need for denormalization and adapts to your use cases, without having to move your data or rewrite SQL. A Linux Foundation project.

Learn more 👉🏻 What Is StarRocks: Features and Use Cases, Join StarRocks Summit 2025!

Features

🚀 Native vectorized SQL engine: StarRocks adopts vectorization technology to make full use of the parallel computing power of CPU, achieving sub-second query returns in multi-dimensional analyses, which is 5 to 10 times faster than previous systems.
📊 Standard SQL: StarRocks supports ANSI SQL syntax (fully supported TPC-H and TPC-DS). It is also compatible with the MySQL protocol. Various clients and BI software can be used to access StarRocks.
💡 Smart query optimization: StarRocks can optimize complex queries through CBO (Cost Based Optimizer). With a better execution plan, the data analysis efficiency will be greatly improved.
⚡ Real-time update: The updated model of StarRocks can perform upsert/delete operations according to the primary key, and achieve efficient query while concurrent updates.
🪟 Intelligent materialized view: The materialized view of StarRocks can be automatically updated during the data import and automatically selected when the query is executed.
✨ Querying data in data lakes directly: StarRocks allows direct access to data from Apache Hive™, Apache Iceberg™, Delta Lake™ and Apache Hudi™ without importing.
🎛️ Resource management: This feature allows StarRocks to limit resource consumption for queries and implement isolation and efficient use of resources among tenants in the same cluster.
💠 Easy to maintain: Simple architecture makes StarRocks easy to deploy, maintain and scale out. StarRocks tunes its query plan agilely, balances the resources when the cluster is scaled in or out, and recovers the data replica under node failure automatically.

Architecture Overview

StarRocks’s streamlined architecture is mainly composed of two modules: Frontend (FE) and Backend (BE). The entire system eliminates single points of failure through seamless and horizontal scaling of FE and BE, as well as replication of metadata and data.

Starting from version 3.0, StarRocks supports a new shared-data architecture, which can provide better scalability and lower costs.

Resources

📚 Read the docs

Section	Description
Quick Starts	How-tos and Tutorials.
Deploy	Learn how to run and configure StarRocks.
Docs	Full documentation.
Blogs	StarRocks deep dive and user stories.

❓ Get support

Slack community: join technical discussions, ask questions, and meet other users!
YouTube channel: subscribe to the latest video tutorials and webcasts.
GitHub issues: report an issue with StarRocks.

Contributing to StarRocks

We welcome all kinds of contributions from the community, individuals and partners. We owe our success to your active involvement.

See Contributing.md to get started.
Set up StarRocks development environment:

Understand our GitHub workflow for opening a pull request; use this PR Template when submitting a pull request.
Pick a good first issue and start contributing.

📝 License: StarRocks is licensed under Apache License 2.0.

👥 Community Membership: Learn more about different contributor roles in StarRocks community.

💬 Developer Group： Please join our Google Groups to discuss StarRocks features, project directions, issues, pull requests, or share suggestions.

Used By

This project is used by the following companies. Learn more about their use cases:

LawnchairLauncher/lawnchair

No clever tagline needed.

Lawnchair 16

Warning

This branch contains major changes from the rebase of Launcher3, including changes that can cause Lawnchair to crash or break.

For regular users, we recommend staying on Lawnchair 15 Beta 3.

Lawnchair is a free, open-source home app for Android. Taking Launcher3—Android’s default home app—as a starting point, it ports Pixel Launcher features and introduces rich customization options.

This branch houses the codebase of Lawnchair 16, which is currently in development and is based on Launcher3 from Android 16. For Lawnchair 9 to 15, see the branches with the 9- to 15- prefixes, respectively.

Features

Material 3 Expressive theming that follows your wallpaper and system colors.
At a Glance widget support, with integration for Smartspacer.
QuickSwitch support for Android Recents integration on Android 10-15 (root required).
Global search for apps, contacts, and web results from the home screen.
Customization options for icon packs, fonts, and color settings.

Download

Lawnchair on Play Store will install as a different app compared to other sources. Features may be restricted to comply with Google Play’s publishing rules.

You can also verify your installation to check if you have installed an official build.

Development builds

Interested in keeping yourself up-to-date with every Lawnchair development? Try our development builds!

These builds offer the latest features and bug fixes at a cost of performance and additional issues. Make backups before installing.

Download: Obtainium • GitHub • nightly.link

Support Lawnchair

If you love what we do, consider supporting us on Open Collective! Your contributions help keep Lawnchair independent and enable us to develop faster.

A huge thank you to our Core Backers ($5+): (These backers directly fund our Project Velocity Fund)

Become a supporter to help us cover our operational costs, or become a Core Backer to be featured here!

Contribute

Visit the Lawnchair contributing guidelines for information and tips on contributing to Lawnchair.

Quick links

Anuken/Mindustry

The automation tower defense RTS

The automation tower defense RTS, written in Java.

Trello Board
Wiki
Javadoc

Contributing

See CONTRIBUTING for general code style and PR guidelines.

If you are a first-time contributor looking for features to implement or bugs to fix, see the issues tagged with 'candidate' in the Mindustry-Suggestions repostiory.

Building

Bleeding-edge builds are generated automatically for every commit. You can see them here.

If you'd rather compile on your own, follow these instructions. First, make sure you have JDK 17 installed. Other JDK versions will not work. Open a terminal in the Mindustry directory and run the following commands:

Windows

Running: gradlew desktop:run
Building: gradlew desktop:dist
Sprite Packing: gradlew tools:pack

Linux/Mac OS

Running: ./gradlew desktop:run
Building: ./gradlew desktop:dist
Sprite Packing: ./gradlew tools:pack

Server

Server builds are bundled with each released build (in Releases). If you'd rather compile on your own, replace 'desktop' with 'server', e.g. gradlew server:dist.

Android

Install the Android SDK here. Make sure you're downloading the "Command line tools only", as Android Studio is not required.
In the unzipped Android SDK folder, find the cmdline-tools directory. Then create a folder inside of it called latest and put all of its contents into the newly created folder.
In the same directory run the command sdkmanager --licenses (or ./sdkmanager --licenses if on linux/mac)
Set the ANDROID_HOME environment variable to point to your unzipped Android SDK directory.
Enable developer mode on your device/emulator. If you are on testing on a phone you can follow these instructions, otherwise you need to google how to enable your emulator's developer mode specifically.
Run gradlew android:assembleDebug (or ./gradlew if on linux/mac). This will create an unsigned APK in android/build/outputs/apk.

To debug the application on a connected device/emulator, run gradlew android:installDebug android:run.

Troubleshooting

Permission Denied

If the terminal returns Permission denied or Command not found on Mac/Linux, run chmod +x ./gradlew before running ./gradlew. This is a one-time procedure.

Where is the `mindustry.gen` package?

As the name implies, mindustry.gen is generated at build time based on other code. You will not find source code for this package in the repository, and it should not be edited by hand.

The following is a non-exhaustive list of the "source" of generated code in mindustry.gen:

Call, *Packet classes: Generated from methods marked with @Remote.
All entity classes (Unit, EffectState, Posc, etc): Generated from component classes in the mindustry.entities.comp package, and combined using definitions in mindustry.content.UnitTypes.
Sounds, Musics, Tex, Icon, etc: Generated based on files in the respective asset folders.

Gradle may take up to several minutes to download files. Be patient.
After building, the output .JAR file should be in /desktop/build/libs/Mindustry.jar for desktop builds, and in /server/build/libs/server-release.jar for server builds.

Feature Requests

Post feature requests and feedback here.

Downloads

termux/termux-api

Termux add-on app which exposes device functionality as API to command line programs.

Termux API

This is an app exposing Android API to command line usage and scripts or programs.

When developing or packaging, note that this app needs to be signed with the same key as the main Termux app for permissions to work (only the main Termux app are allowed to call the API methods in this app).

Installation

Latest version is v0.53.0.

Termux:API application can be obtained from F-Droid.

Additionally we provide per-commit debug builds for those who want to try out the latest features or test their pull request. This build can be obtained from one of the workflow runs listed on Github Actions page.

Signature keys of all offered builds are different. Before you switch the installation source, you will have to uninstall the Termux application and all currently installed plugins. Check https://github.com/termux/termux-app#Installation for more info.

License

Released under the GPLv3 license.

How API calls are made through the termux-api helper binary

The termux-api client binary in the termux-api package generates two linux anonymous namespace sockets, and passes their address to the TermuxApiReceiver broadcast receiver as in:

/system/bin/am broadcast ${BROADCAST_RECEIVER} --es socket_input ${INPUT_SOCKET} --es socket_output ${OUTPUT_SOCKET}

The two sockets are used to forward stdin from termux-api to the relevant API class and output from the API class to the stdout of termux-api.

Client scripts

Client scripts which processes command line arguments before calling the termux-api helper binary are available in the termux-api package.

Ideas

Wifi network search and connect.
Add extra permissions to the app to (un)install apps, stop processes etc.

emanuele-f/PCAPdroid

No-root network monitor, firewall and PCAP dumper for Android

PCAPdroid

PCAPdroid is a privacy-friendly open source app which lets you track, analyze and block the connections made by the other apps in your device. It also allows you to export a PCAP dump of the traffic, inspect HTTP, decrypt TLS traffic and much more!

PCAPdroid simulates a VPN in order to capture the network traffic without root. It does not use a remote VPN server, instead data is processed locally on the device.

Features:

Log and examine the connections made by user and system apps
Extract the SNI, DNS query, HTTP URL and the remote IP address
Inspect HTTP requests and replies thanks to the built-in decoders
Inspect the full connections payload as hexdump/text
Decrypt the HTTPS/TLS traffic and export the SSLKEYLOGFILE
Dump the traffic to a PCAP file, download it from a browser, or stream it to a remote receiver for real-time analysis (e.g. Wireshark)
Create rules to filter out the good traffic and easily spot anomalies
Identify the country and ASN of remote server via offline DB lookups
On rooted devices, capture the traffic while other VPN apps are running

Paid features:

Firewall: create rules to block individual apps, domains and IP addresses
Malware detection: detect malicious connections by using third-party blacklists
PCAPng format: makes it easier to export and analyze decrypted traffic

If you plan to use PCAPdroid to perform packet analysis, please check out the specific section of the manual.

You can test the latest features before the official release by adding the Beta repository to the F-Droid app.

User Guide

Check out the quick start instructions or the full User Guide.

Community

You can help the PCAPdroid project in many ways:

Make a donation
Translate the app on Weblate
Discuss new features
Improve the app theme and layout
Star the project on Github and on Google Play
Of course provide code pull requests!

Join the international PCAPdroid community on Telegram or on Matrix.

Integrating into your APP

Some features of PCAPdroid can be integrated into a third-party app to provide packet capture capabilities.

For rooted devices, the pcapd daemon can be directly integrated into your APK to capture network packets.
For all the devices, PCAPdroid exposes an API to control the packet capture and send the captured packets via UDP to your app. This requires to install PCAPdroid along with your app.

Open Source

PCAPdroid is powered by open source technologies.

nDPI: deep packet inspection library, provides the connections metadata
mitmproxy: a local proxy for the TLS decryption
zdtun: minimal TCP/IP stack for the non-root capture

For the complete list of third party libraries check out the "About" page in the app.

Building

On Windows, install gitforwindows
Clone this repo
Inside the repo dir, run git submodule update --init. The submodules directory should get populated.
Open the project in Android Studio, install the appropriate SDK and the NDK
Build the app

Note: If you get "No valid CMake executable was found", be sure to install the CMake version used by PCAPdroid (currently 3.22.1) from the SDK manager

DrKLO/Telegram

Telegram for Android source

Telegram messenger for Android

Telegram is a messaging app with a focus on speed and security. It’s superfast, simple and free. This repo contains the official source code for Telegram App for Android.

Creating your Telegram Application

We welcome all developers to use our API and source code to create applications on our platform. There are several things we require from all developers for the moment.

Obtain your own api_id for your application.
Please do not use the name Telegram for your app — or make sure your users understand that it is unofficial.
Kindly do not use our standard logo (white paper plane in a blue circle) as your app's logo.
Please study our security guidelines and take good care of your users' data and privacy.
Please remember to publish your code too in order to comply with the licences.

API, Protocol documentation

Telegram API manuals: https://core.telegram.org/api

MTproto protocol manuals: https://core.telegram.org/mtproto

Compilation Guide

Note: In order to support reproducible builds, this repo contains dummy release.keystore, google-services.json and filled variables inside BuildVars.java. Before publishing your own APKs please make sure to replace all these files with your own.

You will require Android Studio 2025.1.4, Android NDK 27.2.12479018 and Android SDK 35.

Clone the Telegram source code with its submodules:

git clone --recursive --shallow-submodules https://github.com/DrKLO/Telegram.git Telegram

In case you forgot the --recursive flag, change to the Telegram directory and run:

git submodule init && git submodule update --init --recursive --depth=1

Copy your release.keystore into TMessagesProj/config
Fill out RELEASE_KEY_PASSWORD, RELEASE_KEY_ALIAS, RELEASE_STORE_PASSWORD in gradle.properties to access your release.keystore
Go to https://console.firebase.google.com/, create two android apps with application IDs org.telegram.messenger and org.telegram.messenger.beta, turn on firebase messaging and download google-services.json, which should be copied to the same folder as TMessagesProj.
Open the project in the Studio (note that it should be opened, NOT imported).
Fill out values in TMessagesProj/src/main/java/org/telegram/messenger/BuildVars.java – there’s a link for each of the variables showing where and which data to obtain.
You are ready to compile Telegram.

Localization

We moved all translations to https://translations.telegram.org/en/android/. Please use it.

apache/fineract

Apache Fineract

Apache Fineract is an open-source core banking platform providing a flexible, extensible foundation for a wide range of financial services. By making robust banking technology openly available, it lowers barriers for institutions and innovators to reach underserved and unbanked populations.

Have a look at the documentation, the wiki or at the FAQ, if this README does not answer what you are looking for.

COMMUNITY

If you are interested in contributing to this project, but perhaps don't quite know how and where to get started, please join our developer mailing list and chat server, listen into our conversations, chime into threads, or just send us a "Hello!" introduction message; we're a friendly bunch, and look forward to hearing from you.

For the developer wiki, see Contributor's Zone. Maybe these how-to articles help you to get started.

In any case visit our JIRA Dashboard to find issues to work on, see what others are doing, or open new issues.

In the moment you get started writing code, please consult our CONTRIBUTING guidelines, where you will find more information on subjects like coding style, testing and pull requests.

REQUIREMENTS

See Fineract Development Environment in the docs for hardware, software, and tool prerequisites and recommendations.

SECURITY

For a list of known vulnerabilities, see Apache Fineract Security Reports.

If you believe you have found a new vulnerability, let us know privately.

For details about security during development and deployment, see the documentation here.

PRIVATE FORKS

If you’re running Apache Fineract on a private fork, you might want to consider disabling GitHub Actions CI. This is because the usage minutes and artifact costs (including the built workspace and logs generated during execution) could incur additional expenses, that you should be aware!

INSTRUCTIONS

Quick Start

Follow these steps to quickly set up and run Apache Fineract locally.

Prerequisites

Java JDK
PostgreSQL running locally, listening on port 5432 with proper permissions (see below for how to run PostgreSQL in Docker)

# get code
git clone https://github.com/apache/fineract.git
cd fineract

# create dbs
./gradlew createPGDB -PdbName=fineract_tenants
./gradlew createPGDB -PdbName=fineract_default

# start backend
./gradlew devRun

After a minute or two, Fineract will be listening for API requests on port 8443.

Tip

Java properties or environment variables can be used to override default settings. See fineract-provider/src/main/resources/application.properties.

Verify the application is running

Confirm Fineract is ready with, for example:

curl --insecure https://localhost:8443/fineract-provider/actuator/health

Expected response for fresh instance:

{"status":"UP","groups":["liveness","readiness"]}

To test authenticated endpoints, include credentials in your request:

# basic auth header uses colon-delimited and base64-encoded default "mifos:password" login
curl --location --insecure \
  https://localhost:8443/fineract-provider/api/v1/clients \
  --header 'Content-Type: application/json' \
  --header 'Fineract-Platform-TenantId: default' \
  --header 'Authorization: Basic bWlmb3M6cGFzc3dvcmQ='

Expected response for fresh instance:

{"totalFilteredRecords":0,"pageItems":[]}

How to run for production

Running Fineract just to try it out is relatively easy. If you intend to use it in a production environment, be aware that a proper deployment can be complex, costly, and time-consuming. Considerations include: Security, privacy, compliance, performance, service availability, backups, and more. The Fineract project does not provide a comprehensive guide for deploying Fineract in production. You might need skills in enterprise Java applications and more. Alternatively, you could pay a vendor for Fineract deployment and maintenance. You will find tips and tricks for deploying and securing Fineract in our official documentation.

How to build the JAR file

Build a modern, cloud native, fully self contained JAR file:

./gradlew clean bootJar

The JAR will be created in the fineract-provider/build/libs directory. If you intend to use MariaDB or MySQL (warning: both are deprecated), you must download the appropriate JDBC driver yourself and override default database settings. When you start the JAR, specify the directory containing the JDBC driver.

MariaDB example:

# Assumes mariadb-java-client.jar exists in current dir.
# For MariaDB or MySQL, override default settings such as these:
export FINERACT_HIKARI_DRIVER_SOURCE_CLASS_NAME=org.mariadb.jdbc.Driver
export FINERACT_DEFAULT_TENANTDB_PORT=3306
export FINERACT_HIKARI_JDBC_URL=jdbc:mariadb://localhost:3306/fineract_tenants
java -Dloader.path=. -jar fineract-provider/build/libs/fineract-provider.jar

This does not require an external Tomcat.

Note

Versions of mariadb driver and Fineract JARs are omitted from filenames above for brevity.

How to build the WAR file

Build a traditional WAR file:

./gradlew :fineract-war:clean :fineract-war:war

The WAR will be created in the fineract-war/build/libs directory. Afterwards deploy the WAR to your Tomcat Servlet Container.

We recommend using the JAR instead of the WAR file deployment, because it's much easier.

How to run using Docker or Podman

It is possible to do a 'one-touch' installation of Fineract using containers (AKA "Docker") for dev/test convenience and local/offline demos. This includes the database running in the container.

As prerequisites, you must have docker and docker-compose installed on your machine; see Docker Install and Docker Compose Install.

Alternatively, you can also use Podman (e.g. via dnf install podman-docker), and Podman Compose (e.g. via pip3 install podman-compose) instead of Docker.

Caution

Our images are NOT production-ready. For example, notice how the test Spring profile is enabled via fineract-common.env, included by docker-compose.yml, but test must not be enabled in production. YOU are responsible for securing your production instances. See How to run for production.

To run a new Fineract instance on Linux you can simply:

git clone https://github.com/apache/fineract.git
cd fineract
./gradlew :fineract-provider:jibDockerBuild -x test

On Windows, do this instead:

git clone https://github.com/apache/fineract.git --config core.autocrlf=input
cd fineract
gradlew :fineract-provider:jibDockerBuild -x test

Install the Loki log driver and start:

docker plugin install grafana/loki-docker-driver:latest \
  --alias loki --grant-all-permissions
docker compose -f docker-compose-development.yml up -d

The Fineract (back-end) should be running at https://localhost:8443/fineract-provider/ now. Wait for https://localhost:8443/fineract-provider/actuator/health to return {"status":"UP"}. You must go to https://localhost:8443 and remember to accept the self-signed SSL certificate of the API once in your browser.

Docker Hub has a pre-built container image of this project, built continuously.

The official Fineract Docker image includes the PostgreSQL JDBC driver only. MySQL and MariaDB JDBC drivers are not included due to license incompatibility (see LICENSE section below). To use Fineract with MySQL or MariaDB, download the driver from the vendor and either build your own Docker image on top of the official one, mount it via a Docker volume, or install it from the OS package manager inside a custom image.

You must specify the tenants database JDBC URL by passing it to the fineract container via environment variables; please consult the docker-compose.yml for exact details how to specify those.

The logfiles and the Java Flight Recorder output are available in PROJECT_ROOT/build/fineract/logs. If you use IntelliJ then you can double-click on the .jfr file and open it with the IDE. You can also download Azul Mission Control to analyze the Java Flight Recorder file.

NOTE: If you have issues with the file permissions and Docker Compose then you might need to change the variable values for FINERACT_USER and FINERACT_GROUP in PROJECT_ROOT/config/docker/env/fineract-common.env. You can find out what values you need to put there with the following commands:

id -u ${USER}
id -g ${GROUP}

Please make sure that you are not checking in your changed values. The defaults should work for most people.

How to run on Kubernetes

General Clusters

You can also run Fineract using containers on a Kubernetes cluster. Make sure you set up and connect to your Kubernetes cluster. You can follow this guide to set up a Kubernetes cluster on GKE. Make sure to replace apache-fineract-cn with apache-fineract

Now e.g. from your Google Cloud shell, run the following commands:

git clone https://github.com/apache/fineract.git
cd fineract/kubernetes
./kubectl-startup.sh

To shutdown and reset your Cluster, run:

./kubectl-shutdown.sh

Using Minikube

Alternatively, you can run fineract on a local kubernetes cluster using minikube. As prerequisite you must have minikube and kubectl installed on your machine; see Minikube & Kubectl install.

To run a new Fineract instance on Minikube you can simply:

git clone https://github.com/apache/fineract.git
cd fineract/kubernetes
minikube start
./kubectl-startup.sh

Wait for all pods to be ready:

kubectl get pods -w

Once all pods are running, access the Mifos web application:

minikube service mifos-community

This opens the Mifos X web application in your browser. The nginx reverse proxy in the mifos-community pod forwards API requests to the fineract-server backend.

Default credentials:

Username: mifos
Password: password

You can also access the Fineract API directly:

minikube service fineract-server --url --https

Fineract is now running at the printed URL, which you can check e.g. using:

http --verify=no --timeout 240 --check-status get $(minikube service fineract-server --url --https)/fineract-provider/actuator/health

To check the status of your containers on your local minikube Kubernetes cluster, run:

minikube dashboard

You can check Fineract logs using:

kubectl logs deployment/fineract-server

You can check Mifos web app logs using:

kubectl logs deployment/mifos-community

To shutdown and reset your cluster, run:

./kubectl-shutdown.sh

How to enable External Message Broker (ActiveMQ or Apache Kafka)

There are two use-cases where external message broker is needed:

External Business Events / Reliable Event Framework
Executing Partitioned Spring Batch Jobs

External Events are business events, e.g.: ClientCreated, which might be important for third party systems. Apache Fineract supports ActiveMQ (or other JMS compliant brokers) and Apache Kafka endpoints for sending out Business Events. By default, they are not emitted.

In case of a large deployment with millions of accounts, the Close of Business Day Spring Batch job may run several hours. In order to speed up this task, remote partitioning of the job is supported. The Manager node partitions breaks up the COB job into smaller pieces (sub tasks), which then can be executed on multiple Worker nodes in parallel. The worker nodes are notified either by ActiveMQ or Kafka regarding their new sub tasks.

ActiveMQ

JMS based messaging is disabled by default. In docker-compose-postgresql-activemq.yml an example is shown, where ActiveMQ is enabled. In that configuration one Spring Batch Manager instance and two Spring Batch Worker instances are created. Spring based events should be disabled and jms based event handling should be enabled. Furthermore, proper broker JMS URL should be configured.

FINERACT_REMOTE_JOB_MESSAGE_HANDLER_JMS_ENABLED=true
FINERACT_REMOTE_JOB_MESSAGE_HANDLER_SPRING_EVENTS_ENABLED=false
FINERACT_REMOTE_JOB_MESSAGE_HANDLER_JMS_BROKER_URL=tcp://activemq:61616

For additional ActiveMQ related configuration please take a look to the application.properties where the supported configuration parameters are listed with their default values.

Kafka

Kafka support is also disabled by default. In docker-compose-postgresql-kafka.yml an example is shown, where self-hosted Kafka is enabled for both External Events and Spring Batch Remote Job execution.

During the development Fineract was tested with PLAINTEXT Kafka brokers without authentication and with AWS MSK using IAM authentication. The extra JAR file required for IAM authentication is already added to the classpath. An example MSK setup can be found in docker-compose-postgresql-kafka-msk.yml.

The full list of supported Kafka related properties is documented in the Fineract Platform documentation.

DATABASE AND TABLES

You can run the required version of the database server in a container, instead of having to install it, like this:

# start postgresql in background
docker run --name postgres -p 5432:5432 -e POSTGRES_USER=root -e POSTGRES_PASSWORD=postgres -u nobody:nogroup -d postgres:18.3
# stop and destroy container
docker rm -f postgres

Similarly, for one of the deprecated database backends:

# start mariadb in background
docker run --name mariadb-12.2 -p 3306:3306 -e MARIADB_ROOT_PASSWORD=mysql -d mariadb:12.2.2 --innodb-snapshot-isolation=OFF
# stop and destroy container
docker rm -f mariadb-12.2

Beware that this container database keeps its state inside the container and not on the host filesystem. It is lost when you destroy (rm) this container. This is typically fine for development. See Caveats: Where to Store Data on the database container documentation regarding how to make it persistent instead of ephemeral.

MySQL/MariaDB and UTC timezone

With release 1.8.0 we introduced improved date time handling in Fineract. Date time is stored in UTC, and UTC timezone enforced even on the JDBC driver, e. g. for MySQL:

serverTimezone=UTC&useLegacyDatetimeCode=false&sessionVariables=time_zone='-00:00'

If you use MySQL as Fineract database, the following configuration is highly recommended:

Run the application in UTC (the default command line in our Docker image has the necessary parameters already set)
Run the MySQL database server in UTC (if you use managed services like AWS RDS, then this should be the default anyway, but it would be good to double-check)

In case Fineract and MySQL do not run in UTC, MySQL might save date time values differently from PostgreSQL

Example scenario: If the Fineract instance runs in timezone: GMT+2, and the local date time is 2022-08-11 17:15 ...

... then PostgreSQL saves the LocalDateTime as is: 2022-08-11 17:15
... and MySQL saves the LocalDateTime in UTC: 2022-08-11 15:15
... but when we read the date time from PostgreSQL or from MySQL, both systems give us the same value: 2022-08-11 17:15 GMT+2

If a previously used Fineract instance didn't run in UTC (backward compatibility), all prior dates will be read wrongly by MySQL. This can cause issues, when you run the database migration scripts.

Recommendation: Shift all dates in your database by the timezone offset that your Fineract instance used.

CONNECTION POOL CONFIGURATION

Please check application.properties to see which connection pool settings can be tweaked. The associated environment variables are prefixed with FINERACT_HIKARI_*. You can find more information about specific connection pool settings at the HikariCP Github repository.

NOTE: We keep backwards compatibility until one of the next releases to ensure that things are working as expected. Environment variables prefixed fineract_tenants_* can still be used to configure the database connection, but we strongly encourage using FINERACT_HIKARI_* with more options.

RELEASES

Official releases are created quarterly, at the end of each quarter. Our documented release procedure follows the ASF release policy.

See https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Releases for an archive of historical release notes along with JIRA issues relevant to each release.

See https://github.com/apache/fineract/releases for a list of PRs and contributors for each release.

EOL/unsupported releases are archived.

Versioned build products created from the develop branch will include -SNAPSHOT. See related settings near version and gitVersioning in build.gradle for details.

LICENSE

This project is licensed under Apache License Version 2.0.

The following libraries are not included in Fineract binary distribution artifacts (binary tarball, WAR, bootJar, or Docker image) because their licenses are Category X under the Apache Software Foundation third-party license policy:

MariaDB Connector/J (org.mariadb.jdbc:mariadb-java-client) — LGPL
MySQL Connector/J (com.mysql:mysql-connector-j) — GPL with FOSS exception
SpotBugs Annotations (com.github.spotbugs:spotbugs-annotations) — LGPL

These libraries may be present on the compile classpath during development and testing but are excluded from all distributed artifacts. If you need MySQL or MariaDB support (both are deprecated; PostgreSQL is the recommended database), download the appropriate JDBC driver from the vendor's website and provide it at runtime via -Dloader.path as shown in the How to build the JAR file section above.

As discussed in LEGAL-462 and LEGAL-726, this project therefore complies with the Apache Software Foundation third-party license policy.

PLATFORM API

Fineract does not provide a UI, but provides an API. Running Fineract locally, the Swagger documentation can be accessed under https://localhost:8443/fineract-provider/swagger-ui/index.html. A live version can be accessed via this Sandbox (not hosted by us).

Apache Fineract supports client code generation using Swagger Codegen based on the OpenAPI Specification. For more instructions on how to generate client code, check this section of the Fineract documentation. This video documents the use of the Swagger-UI.

google/guava

Google core libraries for Java

Guava: Google Core Libraries for Java

Guava is a set of core Java libraries from Google that includes new collection types (such as multimap and multiset), immutable collections, a graph library, and utilities for concurrency, I/O, hashing, primitives, strings, and more! It is widely used on most Java projects within Google, and widely used by many other companies as well.

Guava comes in two flavors:

The JRE flavor requires JDK 1.8 or higher.
If you need support for Android, use the Android flavor. You can find the Android Guava source in the android directory.

Adding Guava to your build

Guava's Maven group ID is com.google.guava, and its artifact ID is guava. Guava provides two different "flavors": one for use on a (Java 8+) JRE and one for use on Android or by any library that wants to be compatible with Android. These flavors are specified in the Maven version field as either 33.6.0-jre or 33.6.0-android. For more about depending on Guava, see using Guava in your build.

To add a dependency on Guava using Maven, use the following:

<dependency>
  <groupId>com.google.guava</groupId>
  <artifactId>guava</artifactId>
  <version>33.6.0-jre</version>
  <!-- or, for Android: -->
  <version>33.6.0-android</version>
</dependency>

To add a dependency using Gradle:

dependencies {
  // Pick one:

  // 1. Use Guava in your implementation only:
  implementation("com.google.guava:guava:33.6.0-jre")

  // 2. Use Guava types in your public API:
  api("com.google.guava:guava:33.6.0-jre")

  // 3. Android - Use Guava in your implementation only:
  implementation("com.google.guava:guava:33.6.0-android")

  // 4. Android - Use Guava types in your public API:
  api("com.google.guava:guava:33.6.0-android")
}

For more information on when to use api and when to use implementation, consult the Gradle documentation on API and implementation separation.

Snapshots and Documentation

Snapshots of Guava built from the master branch are available through Maven using version 999.0.0-HEAD-jre-SNAPSHOT, or 999.0.0-HEAD-android-SNAPSHOT for the Android flavor.

Snapshot API Javadoc as well as Snapshot API Diffs are also available.

Another easy way to get to the Javadoc is to open guava.dev/api. You can also jump right to a specific class by appending the class name to guava.dev. For example, guava.dev/ImmutableList!

Learn about Guava

Our users' guide, Guava Explained
A nice collection of other helpful links

IMPORTANT WARNINGS

APIs marked with the @Beta annotation at the class or method level are subject to change. They can be modified in any way, or even removed, at any time. If your code is a library itself (i.e., it is used on the CLASSPATH of users outside your own control), you should not use beta APIs unless you repackage them. If your code is a library, we strongly recommend using the Guava Beta Checker to ensure that you do not use any @Beta APIs!
APIs without @Beta will remain binary-compatible for the indefinite future. (Previously, we sometimes removed such APIs after a deprecation period. The last release to remove non-@Beta APIs was Guava 21.0.) Even @Deprecated APIs will remain (again, unless they are @Beta). We have no plans to start removing things again, but officially, we're leaving our options open in case of surprises (like, say, a serious security problem).
Guava has one dependency that is needed for linkage at runtime: com.google.guava:failureaccess:1.0.3. It also has some annotation-only dependencies, which we discuss in more detail at that link.
Serialized forms of ALL objects are subject to change unless noted otherwise. Do not persist these and assume they can be read by a future version of the library.
Our classes are not designed to protect against a malicious caller. You should not use them for communication between trusted and untrusted code.
For the mainline flavor, we test the libraries using a range of OpenJDK versions on Linux and Windows. Some features, especially in com.google.common.io, may not work correctly in non-Linux environments. For the Android flavor, our unit tests also run on API level 24 (Nougat).

ashishps1/awesome-low-level-design

Learn Low Level Design (LLD) and prepare for interviews using free resources.

Join Free Newsletter

This repository contains resources to learn Low Level Design (LLD) / Object Oriented Design (OOD) and prepare for interviews. It covers OOP fundamentals, design patterns, UML, concurrency and commonly asked interview questions.

👉 For a better and more comprehensive experience, checkout the LLD page at AlgoMaster.io

🧱 OOP Fundamentals

🔗 Class Relationships

🧭 Design Principles

🧩 Design Patterns

Creational Patterns	Structural Patterns	Behavioral Patterns
Singleton	Adapter	Iterator
Factory Method	Bridge	Observer
Abstract Factory	Composite	Strategy
Builder	Decorator	Command
Prototype	Facade	State
	Flyweight	Template Method
	Proxy	Visitor
		Mediator
		Memento
		Chain of Responsibility

🗂️ UML

⏱️ Concurrency and Multi-threading Concepts

Concurrency 101

Synchronization Primitives

Concurrency Challenges

Concurrency Patterns

✅ How to Answer a LLD Interview Problem

💻 Low Level Design Interview Problems

Easy Problems

Medium Problems

Hard Problems

⏱️ Concurrency and Multi-threading Problems

📇 Courses

📚 Books

📩 Newsletter

AlgoMaster Newsletter

Additional resources

🤝 Contributing

Contributions are welcome! If you'd like to add a new problem, improve existing content, or fix errors:

Fork the repository
Create a feature branch: git checkout -b feature/your-feature-name
Commit your changes: git commit -m 'Add some feature'
Push to the branch: git push origin feature/your-feature-name
Submit a pull request

Please make sure to update Readme files and documentation as appropriate.

If you find this resource helpful, please give it a star and share it with others!

yuliskov/SmartTube

Browse media content with your own rules on Android TV

Important announcement about the app

My development environment was infected by unknown malicious software, as a result of which a few builds may have been affected. Once the issue was detected, I secured everything with a full disk wipe, restored a clean setup, and now all builds are scanned with VirusTotal. The F-Droid version will also be verified before release.

Public keys may have been compromised, which is why I am sharing this issue. You can download the new version and the new public key below, and instructions for restoring backups are provided.

No extra actions are required since the app uses one-time connection codes. These codes have very limited permissions (for example, they cannot change your password). Still, you can revoke them if you want full peace of mind.

How to revoke access:

Open myaccount.google.com/security
Find “Your connections to third-party apps & services”
Tap “See all connection” and locate YouTube TV or Google Drive
Select the app → “Remove access”

Please keep built-in security features enabled to stay protected.

SmartTube

SmartTube is a free and open-source media client for Android TVs and TV boxes. It allows you to browse and play content from various public sources in a TV-optimized interface.

✅ Features

Clean interface
SponsorBlock integration
Adjustable playback speed
8K resolution support
60fps playback
HDR compatibility
View live chat
Customizable buttons
Does not require Google Services
Helpful international community

❌ Limitations

Not supported on phones and tablets
Comment functionality is unstable
Voice search and casting performance may be inferior to official apps, depending on your device

Give it a try!

Do you have any question? Ctrl+F or ⌘F this readme first!

Device support

Important

Starting in October 2025 new Amazon FireTV devices no longer run Android under the hood. SmartTube will not be compatibile with the Fire Stick 4k Select and newer devices which run Amazon's own VegaOS.

Supported: all Android TVs and TV boxes (incl. All FireTV devices released before Oct. 2025, NVIDIA Shield & Chromecast with Google TV), even older ones with Android 4.3 (Kitkat).
Not supported: Smartphones, non-Android platforms like Samsung Tizen, LG webOS, Apple TV, etc.

Installation

video of the installation (note: download url changed to kutt.to/stn_beta or kutt.to/stn_stable)

Do not download SmartTube from any app store, APK websites or blogs; these were uploaded by other people and may contain malware or ads. SmartTube is not officially published on any app store.

There is a beta release (recommended) and a stable release. Beta gets new features and bugfixes faster than the stable release.

You can use either of the following methods to install the app:

(Easiest) Install Downloader by AFTVnews on your Android TV, open it and enter kutt.to/stn_beta or kutt.to/stn_stable, then read, understand and confirm the security prompts. (You can also enter 79015 (for beta) or 28544 (for stable), but this requires an extra step to install the AFTVnews Downloader browser addon if you haven't already.)
Install a file transfer app on your Android TV, download the APK on your phone or computer and transfer it to your TV (e.g. Send Files to TV from the Google Play Store / Amazon AppStore)
Download the APK onto a USB stick, put the USB stick into your TV and use a file manager app from the Google Play Store / Amazon AppStore (e.g. FX File Explorer or X-plore). Android's preinstalled file manager does not work! Do not get the ad-infested FileCommander.
If you are an advanced user, you can install it using ADB. guide | alternative guide

Troubleshooting: See device specific notes below. If installation fails, either your disk space is full or the APK file didn't download correctly; clear up space and try downloading again. If the app installed, but crashes when opening, make sure to install it to internal memory, not to an SD card / external storage.

The app has a built-in updater with changelog. You can also find all releases and the changelog on the Telegram channel @SmartTubeNewsEN (readable without account) or on Github.

latest beta download

latest stable download

Installation (Chromecast with Google TV)

On Chromecast with Google TV, installation of apps is blocked by default, so an extra step is required:

4.1. Enable Developer Options

On your Chromecast, open the side menu and go to Settings > System > About. Scroll down to the Android TV OS build section and click that repeatedly. A toast message will appear, explaining that you are a few steps away from being a developer. Continue clicking until you trigger it.

4.2. Turn on the "unknown sources" setting

Go back to the main Settings page and select Apps > Security & Restrictions > Unknown sources. Turn on the toggle for [Downloader by AFTVnews or] whichever file browser you decided to use [...].

[source & picture guide]

After this, you can follow the general installation guide above.

Installation (Xiaomi devices with Chinese firmware)

Xiaomi's Chinese firmware might block the installation of the beta version. The international firmware is not affected. Solutions:

Use SmartTube's stable version instead (recommended)
Use the international firmware for your device
(if your device is from 2020 or before) You can do a factory reset and then install SmartTube beta before doing any system updates. You can then safely update your system, SmartTube should continue working.

Updating

The app has a built-in updater. You only need to follow the installation procedure once. A few seconds after launching SmartTube, it will notify you if there is any update and also show a changelog. You can disable automatic update checks or manually update in the settings under "about".

If the installation fails, either your disk space is full or the update didn't download correctly; clear up space and try updating again (Settings > About > Check for updates).

Compatibility

SmartTube requires Android 4.3 or above. It does not work on non-Android devices (incl. LG or Samsung TVs). On unsupported TVs, you can use a TV stick or TV box. Though this app technically runs on smartphones and tablets, it is not optimized for such and offers no official support!

It has been successfully tested on TVs, TV boxes and TV sticks that are based on Android, including:

Android TVs & Google TVs (e.g. Philips, Sony)
Chromecast with Google TV & TVs with Chromecast built-in
Amazon FireTV stick (all generations)
NVIDIA Shield
TV boxes running Android (many cheap chinese no-name boxes)
Xiaomi Mi Box

Features

Interface

SmartTube focuses on a clean and distraction-free interface for watching media content. The app does not include advertising UI elements and focuses on playback and browsing experience instead.

SponsorBlock

SmartTube includes optional SponsorBlock integration. From the SponsorBlock website:

SponsorBlock is an open-source crowdsourced browser extension and open API for skipping sponsor segments in YouTube videos. [...] the extension automatically skips sponsors it knows about using a privacy preserving query system. It also supports skipping other categories, such as intros, outros and reminders to subscribe [and non-music parts in music videos].

You can select which categories you want to skip in the settings. Unlike the browser addon, in SmartTube you cannot submit new segments (TVs and TV remotes aren't great devices for such precise operations). Note that SponsorBlock is a free and voluntary project based on user submissions, so don't expect it to 100% work every time. Sometimes, sponsor segments are not yet submitted to the database, sometimes the SponsorBlock servers are offline/overloaded.

Casting

To cast videos from your phone (or other devices), you must link that device to your TV. Unlike the original YouTube app, SmartTube does not automatically show up when you are in the same wifi network. How to link your smartphone and TV:

open SmartTube and go to settings
go to "Remote control" (2nd option)
open your YouTube app on your phone, go to settings > General > watch on TV
click on connect using TV-code and enter the code from your TV

Screenshot guide

Due to technical limitations, you need to open the app on the TV before casting; SmartTube cannot automatically wake up the TV.

Picture-in-Picture (PiP)

SmartTube supports playing videos in PiP mode. This needs to be enabled under Settings > General > Background playback > Picture in picture. The video will go into PiP mode when you press home while playing a video, and also when you press back if enabled in Settings > General > Background playback (activation).

Adjust Speed

You can adjust the playback speed pressing the speed-indicator icon (gauge) in the top row of the player. This is remembered across videos. Some speeds may case frame drops, this is a known issue.

Voice Search

To enable global voice search, an additional app must be installed alongside SmartTube. This bridge app allows the system voice search to open SmartTube instead of the default YouTube app. For this to work, you must uninstall the original YouTube app. We know this sucks, but you can always reinstall it if you change your mind. The bridge app will not show up in your launcher and you cannot launch it directly; it is only used internally by the system's voice search. On some devices, you need to explicitly say "Youtube" when searching (e.g. say "youtube cute cats" instead of just "cute cats").

On Amazon Fire TV:

Uninstall the original YouTube app (no root required)
Download and install the Amazon Bridge SmartTube app: https://kutt.to/stn_bridge_amazon (e.g. via Downloader by AFTVnews)

On Google Chromecast with Google TV:

Uninstall the original YouTube app (no root required)
Download and install the ATV Bridge SmartTube app: https://kutt.to/stn_bridge_atv (e.g. via Downloader by AFTVnews)

On all other Android devices, sadly root is required to enable this:

Root your device (search for a guide for your specific device)
Uninstall the official YouTube app using root (adb shell pm uninstall com.google.android.youtube.tv)
Download and install the ATV Bridge SmartTube app: https://kutt.to/stn_bridge_atv (e.g. via Downloader by AFTVnews)

Donation

If you want to support my developments you are welcome to buy me a cup of coffee 😃

Patreon (Visa, Mastercard, PayPal)
PayPal: firsth ash@gmai l.com

BTC: 1JAT5VVWarVBkpVbNDn8UA8HXNdrukuBSx
LTC: ltc1qgc24eq9jl9cq78qnd5jpqhemkajg9vudwyd8pw
ETH: 0xe455E21a085ae195a097cd4F456051A9916A5064
ETC: 0x209eCd33Fa61fA92167595eB3Aea92EE1905c815
TRX: TJNPY794aSGZf3WGHTna2VCWm2G5Yua7E8
USDT (TRC20): TJNPY794aSGZf3WGHTna2VCWm2G5Yua7E8
USDT (BEP20): 0x64B28da787BE6ac5889D276A5638d4f077840eC5
USDT (ERC20): 0xe455e21a085ae195a097cd4f456051a9916a5064
TON: UQAc9zgnnzwS8yb5wxAu5CB0RddmjPBjWI-n46oQ7XfCQrgI
XMR: 48QsMjqfkeW54vkgKyRnjodtYxdmLk6HXfTWPSZoaFPEDpoHDwFUciGCe1QC9VAeGrgGw4PKNAksX9RW7myFqYJQDN5cHGT

Support

Please check the FAQ first! Also at least have a short look at the recent chat history.

You can report in our Telegram group or via issue tracker on Github (account required).

Telegram group (international): @SmartTubeEN
Discord group (international): SmartTube Official
Telegram group (RU/UA): @SmartTubeUA
Email: firsth ash@gmai l.com

The international group is in English only. But don't worry if your English is not perfect, we have a friendly international community.

Team

SmartTube is developed single-handedly; there is no larger team or company behind this. This is an open source, hobby project. Several others have helped with translations, some of which can be seen on Github, some have sent their translations directly to Yurii. There are also helpful people in the support chat.

Build

NOTE: OpenJDK 14 or older (!) is required. Newer JDK could cause app crash!
To build and install debug version, run these commands:

git clone https://github.com/yuliskov/SmartTube.git
cd SmartTube
git submodule update --init
adb connect <device_ip_address>
gradlew clean installStstableDebug

Video codecs

Video codecs are the algorithms used for video compression.

Which codec to choose / overview

	recommendation	hardware support	compression, bitrate*	quality
AV01 aka. AV1	best choice, if your device supports	first devices started coming in 2020	best (e.g. 1.6 Mbps)	same
VP9	best choice on most devices	most devices since 2015	better (e.g. 2.1 Mbps)	same
AVC	only for old or slow hardware	all devices	good (e.g. 2.7 Mbps)	same

* Examples taken from the video-only track at 1080p @ 25fps for this video: Dua Lipa - New Rules (Official Music Video)

At the same resolution, a lower bitrate is better! YouTube explicitly targets the same quality regardless of the codec. Older codecs have a higher bitrate only because they are less efficient. On Youtube, you do not get better quality by simply choosing a higher bitrate. Newer codecs have a better compression = lower bitrate = use less bandwidth = save the environment. This is a feature, not a bug. You should use the newest codec that works smoothly on your device, not the least efficient one. AVC usually has the highest bitrate. This is bad, not good.

Which quality to choose?

Currently, there is no automatic mode based on your bandwidth. But you can configure a default video preset yourself under settings > video player > video presets. The first option ("none") will remember your last selection within the video player. Any other preset is used initially for each video; if the selected profile is not available, the next best available option is used. You can still override the profile on each video individually within the player.

To decide the optional resolution / video quality for you, you need to consider a few limiting factors:

Your bandwidth (choose only up to the bitrate that your bandwidth can handle; you can do a speedtest using fast.com by Netflix)
Your TV's display resolution (the quality might slightly improve, if you select the next higher resolution, e.g. 1080p on a 720p display; but don't expect a big difference)
Your TV's capabilities (e.g. HDR, 60fps)

Generally 60fps is an improvement, but if you personally don't notice (or mind) the difference, you can save bandwidth (and the environment) by not choosing 60fps.

HDR

HDR works only if your hardware supports it. It's a complicated mess:

Your TV must support it
If you use a TV box, that TV box and your TV cable and the TV must support HDR
Yes, there truly are different HDMI cable versions with different HDR-support, it's complicated
some devices (like the NVIDIA Shield) generally support HDR, but not the specific HDR format that is used on YouTube 😢

If HDR videos look dim or washed out, then check this article. If HDR is not working, it's probably not this app's fault. You might need to search on the web for "HDR" and your device name for any help.

Liability

We take no responsibility for the use of our tool, or external instances provided by third parties. We strongly recommend you abide by the valid official regulations in your country. Furthermore, we refuse liability for any inappropriate use of third-party services. This tool is provided to you in the spirit of free, open software.

You may view the LICENSE in which this software is provided to you here.

Limitation of Liability.

IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

FAQ

Q: Videos buffer a LOT

A: Try to switch to encrypted DNS like NextDNS. You can set-up such DNS either automatically or manually. To automatic set-up you can use the Intra apk at fdroid and the "AutoStart - No root" apk to make it autolaunch after every TV restart. For manual set-up use this guide.

Q: There is no result for the search that I say (Android 11)

A: They're some reports that the latest update for "Google app for Android TV" could cause this bug. Deleting the update should fix the problem.

Q: AV01 does not play / Why is VP9 slow on my device?

A: Because AV01 is very new, most TVs and TV boxes do not offer hardware support and cannot play AV01 at all.

If your device has hardware support for a codec, videos using that codec should play smoothly. High resolutions might also be slow in VP9 on cheap TV boxes that don't officially support 4k. Your device probably can play VP9 videos even without hardware support, however this requires a powerful CPU to run smoothly. Fixing AV01 without hardware support is technically possible, but currently not planned and probably not efficient enough.

Q: Can you make SmartTube look like the original app?

A: Compared to SmartTube's UI, Stock Youtube and YT Kids are far ahead. However, we'd need someone who's skilled and willing to dedicate enough time and energy into making it. And into maintaining it longterm (incl. new features, bug fixes). All of this for free. If you are / got someone like that, please help. Not to mention that SmartTube follows Google's official template & recommendations for Android TV apps. It's Google's fault that the template is somewhat ugly. 😂

Q: Can the search page be improved?

A: It can be, but it takes someone to do it, similar to the above FAQ-entry. SmartTube is following Google's officially recommended design/template for TV apps and is using the official, preinstalled Android TV keyboard. Sadly, Google did a really bad job regarding the search page and keyboard. Maybe a future SmartTube update can add an embedded keyboard, similar to the original YouTube or other major Android TV apps. Maybe it can improve the looks to be as good or better than in the official YouTube app. But for now, it is the way it is due to lack of time and due to Google's official recommendations being bad.

Q: Can I install this on a Samsung Tizen TV / LG webOS TV / Roku / iOS / toaster?

A: No, this only works on Android devices. If you look at an Android TV's product page, it usually says clearly that it's based on Android. The app cannot easily be ported over to other plattforms and we have no plans to even try. Please do not ask. Instead, you can connect a separate TV stick or TV box to your TV.

Q: Can I install this on a smartphone? / Can you add portrait mode? / Scrolling doesn't work.

A: Big No. This app is not for smartphones, we offer zero support for that.

You can cast videos from your smartphone to a TV / TV box running SmartTube, though. Just use the official YouTube app, Morphe or ReVanced, see the casting section for more information.

There will not be a phone version. You can use Morphe, ReVanced, Pure Tuber, LibreTube, NewPipe, or NewPipe x SponsorBlock instead. Please go to their respective support chats for help.

Q: Can I install this on a tablet / car screen / smartphone with docking station?

Yes... maybe.. Requirements:

It is an Android device
It has a large screen
It has a TV remote, controller, or keyboard Touch input is not supported. Mouse/touchpad scrolling neither. You cannot properly use SmartTube with only touch or mouse input.

Some users reported great success (incl. on a car entertainment system). Please share your success stories with us.

Q: I get "unknown codec" / "can't download video" errors

A: please wait 5 seconds for the video to play. If that doesn't help, press the play button. Some users reported, that this issue only appears when they have a USB audio device attached or if their disk storage is full.

Q: I get "the video profile is not supported"

A. Press the "HQ"-button in the bottom-left, select video formats and select anything other than AV01. AV01 is not supported on most devices (apparently including yours), so select VP9 instead. See the section on video codecs for more information.

Q: I get "video unavailable" when watching unlisted videos / my own videos

A: Right, that's currently a bug.

Q: It doesn't show up on my casting list

A: Please read the Casting section.

Q: I get an error saying "Sign in to confirm you're not a bot"

A: Your IP address range might be temporaily/permanently blocked by YouTube from watching videos if you not signed in to your account.

Q: The video is buffering a lot

A: The issue might not be specific to SmartTube, as other unofficial YouTube apps also report this issue. It seems uncommon nowadays, but was very present in the 2nd quarter of 2021. Some users or devices seem to be more affected then others. The official YouTube app & website are apparently only rarely affected. The root cause of the issue is currently unclear, but it appears to be a server-side thing on YouTube's end. Possibly, YouTube is discriminating 3rd party apps.

For now, try to see if it helps to:

Reduce the resolution (or chance it back)
Change the video format to AVC
Increase the buffer in the settings
Hit the back button and try playing the video again

Q: The debug information says my display is 1080p, but I have a 4k/UHD display!

A: Do not worry, the debug information is incorrect. SmartTube works fine even above 1080p and you should be able to see that, when you play a video in 4k or UHD. Also do not worry if it says "720p" and you have a 1080p display.

Q: Why does it not autoselect highest quality?

A: It does (by default). If you set a video profile under settings, that acts as a maximum for automatic selection. Check if you configured a video profile, you can unset it by choosing "none".

Please do not confuse quality with bitrate. See the section on video codecs for more information.

Q: Can I set a (maximum) resolution by default?

A: SmartTube automatically select the highest available quality for your video, up to a maximum resolution that you can set in the settings under "video profile". If available, SmartTube will pick the selected video profile, or otherwise the next best one available will be used. You can still always change the video profile while watching videos.

Q: Can it set the resolution to "auto", depending on my available bandwidth?

A: This is planned, but not available yet (sorry 🙇‍♀️). However, you can set a maximum resolution to something that should work for your bandwidth. See above for details.

Q: Why does it skip video segments?

A: SmartTube has a feature called SponsorBlock. You can select categories should be skipped, if any. See the SponsorBlock section for more details.

Q: How to start the next video automatically / stop after every video?

A: You can switch between different autoplay-modes using the loop-button 🔁

Q: How to remove recommended videos (e.g. news) that are unrelated to me?

A: Recommended videos are defined by YouTube and not by the app, we cannot change the algorithm. They are based on your country, which you can change in the settings. If you are logged in, they are based on your watch history, user profile data, and whatever else Google might use. If you are not logged in, you are like in "incognito mode", so your watch history does not influence your recommendations. Maybe a future version will add optional user profiling without logging in.

Q: Does HDR work?

A: Yes, HDR works if your hardware supports it. The NVIDIA Shield does not. See the section on HDR for more information.

Q: Why do some updates say "don't update if satisfied with the current version" in the changelog?

A: These updates change a lot of code, trying to fix bugs that only affect a few users/devices. Only the affected users should update. For anyone else, there is nothing to gain from updating; however there is the chance of causing new bugs. Do not worry if you updated anyways.

Q: When playing at other speeds, frames are skipped!

A: We currently cannot fix this, sorry.

Q: What is AFR?

A: "Auto Frame Rate". It adjusts the refresh rate of your TV to match the content you're watching. It can slightly improve the smoothness, but the difference is very small; most people barely notice it. It does not work well on every hardware. If you don't know what it does and don't want to test it out yourself, you can safely keep it off.

Recommendation: You can turn it on to see if it works on your device; if it causes issues (or if you don't care to test), turn it off.

Q: Should I choose high or low buffer?

A: The higher your buffer, the more of a video will be preloaded ahead of your current position. A low buffer might minimally reduce your bandwidth usage, if you often close videos before they end. A high buffer can smooth out network issues and prevent the video from pausing to buffer. A higher buffer increases RAM usage, however this shouldn't be an issue.

Recommendation: high.

Q: Can I retain the buffer when seeking back?

A: No, when you seek back (e.g. jump back 5 seconds), SmartTube will have to rebuffer. This might be improved in a future update.

Q: My device freezes when watching YouTube

A: That's a firmware or Android issue. If you are using a custom rom, maybe that rom is buggy. Because this issue is nearly impossible for the developer to debug, we cannot help you, sorry. You can try the usual workarounds: rebooting, clearing cache, reinstalling the app, or factory resetting the device.

Q: Can I download videos?

A: Not with SmartTube

Q: Can updates be installed automatically?

A: No, this is technically not possible. Only the preinstalled app manager (usually Google PlayStore, Amazon AppStore, etc) has the required permission. All other apps, incl. SmartTube can only show open installation prompt. A workaround using root would be possible, but hasn't been implemented yet.

Q: Can I whitelist ads on some channels?

A: No, this is not possible. SmartTube does not have any code to display ads. Adding this functionality would actually take time and effort, which is instead spent on adding useful features and fixing bugs.

crimera/piko

morphe patches for twitter and instagram

Morphe patches focused on Twitter/X & Instagram

🕹️ Usage

Starting with patches v3.0.0, Piko patches use Morphe.

Morphe Manager

Show steps

Use the deep link to add Piko as a patch source in Morphe Manager:

➕ Add Piko to Morphe

Then patch Twitter/X or Instagram:

Tap X or Instagram app icon in Morphe
Download original APKM file from ApkMirror. Do not unspilt or modify the file, Morphe patches APKM directly
Wait for patching to complete, install

Morphe CLI

java -jar cli.jar patch --patches piko.mpp input.apkm

X-Shim

Starting 12.5.0-release.0 you need not apply X-Shim along with Piko patches. X login and XChat will work fine without X-Shim patches.

To patch with Twitter/X version 11.88 and above, you must include patches from another repo/project called [Piko-Shim](https://gitlab.com/inotia00/piko-shim/) developed by [@inotia00](https://github.com/inotia00)
➕ Add X-Shim to Morphe

⚠️Important steps⚠️

Enable expert mode in Morphe Manager.

You must select all patches from the X Shim bundle and recommended/preferred patches from Piko. DO NOT INCLUDE patches from any other bundles.

Select "Proceed anyway" at the prompt warning of using multiple bundles.

⚠️Additional Context⚠️

An active internet connection is required during patching.

XChat decryption and XChat video calls work.

The X Shim patch only adds a compatibility shim layer and pairip is not removed.

For an up-to-date patching guide, follow this Reddit guide.

⚙️ Patch Details

v3.8.0 • main • 128 patches total

📦 X • 74 patches

🎯 Supported versions:

12.7.1-release.0

💊 Patch	📜 Description	⚙️ Options
Add ability to copy media link
Block redirecting to X Lite	Blocks redirecting to the new X Android UI on launch
Bring back twitter	Bring back old twitter logo and name
Change app icon
Change version code	Changes the version code of the app. This will turn off app store updates and allows downgrading an existing app install to an older app version.	• Version code
Clear tracking params	Removes tracking parameters when sharing links
Control video auto scroll	Control video auto scroll in immersive view
Custom download folder	Change the download directory for video downloads
Custom emoji font	Customise emoji font style
Custom font	Customise font style
Custom share menu	Overrides existing share menu and adds a new one
Custom sharing domain	Allows for using domains like fxtwitter when sharing tweets/posts.
Customise post font size
Customize Inline action Bar items
Customize Navigation Bar items
Customize default reply sorting
Customize explore tabs
Customize notification tabs
Customize profile tabs
Customize search suggestions
Customize search tab items
Customize side bar items
Customize timeline top bar
Delete from database	Delete entries from database(cache)
Disable auto timeline scroll on launch
Disable chirp font
Disunify xchat system	Bring back legacy features like messages and share sheet.
Download patch	Unlocks the ability to download videos and gifs from Twitter/X
Dynamic color	Replaces the default Twitter Blue with the user's Material You palette.
Enable PiP mode automatically	Enables PiP mode when you close the app
Enable Undo Posts	Enables ability to undo posts before posting
Enable debug menu for posts
Enable force HD videos	Videos will be played in highest quality always
Export all activities	Makes all app activities exportable.
Force enable translate	Get translate option for all posts
Handle custom twitter links	Adds support for opening custom twitter links such as vxtwitter, fxtwitter, and fixupx within the app. These will have to be manually enabled under the "Open by default" section in the app info!	• Custom sharing domains • Include unofficial vxtwitter/fxtwitter instance links
Hide Banner	Hide new post banner
Hide Community Notes
Hide FAB	Adds an option to hide Floating action button
Hide FAB Menu Buttons
Hide Live Threads
Hide Recommended Users	Hide recommended users that pops up when you follow someone
Hide badges from navigation bar icons	Hides notification nudges & counts from navigation bar icons
Hide bookmark icon in timeline
Hide community badges
Hide followed by context	Hides followed by context under profile
Hide hidden replies
Hide immersive player	Removes swipe up for more videos in video player
Hide nudge button	Hides follow/subscribe/follow back buttons on posts
Hide post metrics	Hides like, reposts etc counts.
Hide promote button	Hides promote button under self posts
Hide recommendation items	Adds options to hide recommendation items such as "Who to follow" and "Today's news" in timeline, search, and replies.
Hook feature flag
Import/Export login token	Adds an feature to export and import the token of accounts. This is useful when logging in on your second device or when re-installing piko.
Legacy share links	Brings back username on post share links. Works post 11.4x.xx
Log server response	Log json responses received from server
More information on profile	Adds more details on the profile page
Native downloader	Requires X 11.0.0-release.0 or higher.
Native reader mode	Requires X 11.0.0-release.0 or higher.
Native translator	Requires X 11.0.0-release.0 or higher.
No shortened URL	Get rid of t.co short urls.
Pause search suggestions	Search suggestions will not be saved locally
Remove Ads	Removed promoted posts, trends and google ads
Remove premium upsell	Removes premium upsell in home timeline
Remove search suggestions	Hide/Remove search suggestion in explore section
Remove view count	Removes the view count from the bottom of tweets
Round off numbers	Enable or disable rounding off numbers
Selectable Text	Makes bio and username selectable
Share Tweet as Image	Share tweets as rendered image. Requires X 11.0.0-release.0 or higher.
Show changelogs	Shows changelogs when new a patch is installed.
Show poll results	Adds an option to show poll results without voting
Show post source label	Source label will be shown only on public posts
Show sensitive media
Support external downloader

📦 Instagram • 54 patches

🎯 Supported versions:

435.0.0.37.76

💊 Patch	📜 Description	⚙️ Options
Add settings	Adds settings to control preferences are patching
Allow user network certificate	Allows user network certificate for whitehat testing
Change like animation	Change the animation to one from existing Rings like animations
Change version code	Changes the version code of the app. This will turn off app store updates and allows downgrading an existing app install to an older app version.	• Version code
Clone	Changes the package name and the app name. This allows you to install the patched app alongside the original Instagram app. Caution: Do not select the official Morphe's "Change package name" universal patch.	• Package name • App name
Copy comment	Adds a button to copy comments on posts and reels.
Customise story ring size
Customise story timestamp	Customise the timestamp that shows when the story was posted
Disable Reels scrolling	Disables the endless scrolling behavior in Instagram Reels, preventing swiping to the next Reel. Note: On a clean install, the 'Tip' animation may appear but will stop on its own after a few seconds.
Disable ads
Disable analytics	Block analytics that are sent to Instagram/Facebook servers.
Disable comments
Disable discover people	Disables discover people section on user profile
Disable double tap like	Disable double tap like on post, reel, comment and message
Disable explore
Disable highlights
Disable screenshot detection	Disables screenshots detection in DM
Disable stories
Disable story flipping	Disable automatic flipping/moving to next story
Disable swipe to create	Prevents opening the creation screen by swiping right on the home tab.
Disable typing status
Disable video autoplay
Download media	Adds ability to download posts, reels, stories and highlights
Download voice message	Enables ability to download voice messages
External downloader	Adds support to share post links directly to external downloader
Filter stories	Filter stories to hide based on different categories
Friendship status indicator	Adds a follows you back status label on the profile page andshows a detailed friendship status breakdown on click
Hide group creation button on sharesheet
Hide navigation buttons	Hides navigation bar buttons, such as the Reels and Create button.
Hide notes tray	Hides notes tray in DM section
Hide reshare button	Hides the reshare button from both posts and reels.
Hide stories tray	Hides stories tray from main feed.
Hide suggested content	Hides suggested stories, reels, threads (Suggested posts will still be shown).
Improve image viewing	Fetches max resolution images from server.
Limit feed to following profiles	Filters the home feed to display only content from profiles you follow.
Make ephemeral media permanent	Changes unexpired view once, view twice media to permanent view.
Mark chat as read manually	Adds option to mark a thread aka message as read manually
More options on post	Adds an overflow menu button to get more options on post/reels, like copy description, copy username etc
More options on profile	Adds a new button to handle user related data like copy handle, download profile picture etc
Open links externally	Changes links to always open in your external browser, instead of the in-app browser.
Remove build expired popup	Removes the popup that appears after a while, when the app version ages.
Remove empty bottom space	Removes empty space below bottom navigation bar
Sanitize share links
Save media comment	Adds a button to save media comments on posts and reels.
Stories audio autoplay
Theme	Applies either amoled or material you theme for Instagram at patch time. [default = material you]	• Pure-black AMOLED theme
Unlock Plus benefits	Unlocks 'Plus' subscription benefits that are checked locally. USE IT AT YOUR OWN RISK
Unlock developer options	Unlocks developer option by long pressing home icon
Unlock employee options	Unlocks all options using by employee for debugging
Validate links	Fixes app crashing issue while opening links from a different app
View DMs anonymously
View live anonymously
View stories anonymously
View story mentions	Add option to view visible and hidden story mentions.

🛠️ Building

To build Piko Patches, follow the Morphe documentation.

✨ Stargazers over time

License

These patches are fully FOSS redistributable and modifiable under the GNU General Public License v3 or later.

spring-projects/spring-boot

Spring Boot helps you to create Spring-powered, production-grade applications and services with absolute minimum fuss.

Spring Boot

Spring Boot helps you to create Spring-powered, production-grade applications and services with absolute minimum fuss. It takes an opinionated view of the Spring platform so that new and existing users can quickly get to the bits they need.

You can use Spring Boot to create stand-alone Java applications that can be started using java -jar or more traditional WAR deployments. We also provide a command-line tool that runs Spring scripts.

Our primary goals are:

Provide a radically faster and widely accessible getting started experience for all Spring development.
Be opinionated, but get out of the way quickly as requirements start to diverge from the defaults.
Provide a range of non-functional features common to large classes of projects (for example, embedded servers, security, metrics, health checks, externalized configuration).
Absolutely no code generation and no requirement for XML configuration.

Installation and Getting Started

The reference documentation includes detailed installation instructions as well as a comprehensive getting started guide.

Here is a quick teaser of a complete Spring Boot application in Java:

import org.springframework.boot.*;
import org.springframework.boot.autoconfigure.*;
import org.springframework.web.bind.annotation.*;

@RestController
@SpringBootApplication
public class Example {

	@RequestMapping("/")
	String home() {
		return "Hello World!";
	}

	public static void main(String[] args) {
		SpringApplication.run(Example.class, args);
	}

}

Getting Help

Are you having trouble with Spring Boot? We want to help!

Check the reference documentation, especially the How-to’s — they provide solutions to the most common questions.
Learn the Spring basics — Spring Boot builds on many other Spring projects; check the spring.io website for a wealth of reference documentation. If you are new to Spring, try one of the guides.
If you are upgrading, read the release notes for upgrade instructions and "new and noteworthy" features.
Ask a question — we monitor stackoverflow.com for questions tagged with spring-boot.
Report bugs with Spring Boot at github.com/spring-projects/spring-boot/issues.

Contributing

We welcome contributions of all kinds! Please read our contribution guidelines before submitting a pull request.

Reporting Issues

Spring Boot uses GitHub’s integrated issue tracking system to record bugs and feature requests. If you want to raise an issue, please follow the recommendations below:

Before you log a bug, please search the issue tracker to see if someone has already reported the problem.
If the issue doesn’t already exist, create a new issue.
Please provide as much information as possible with the issue report. We like to know the Spring Boot version, operating system, and JVM version you’re using.
If you need to paste code or include a stack trace, use Markdown. ``` escapes before and after your text.
If possible, try to create a test case or project that replicates the problem and attach it to the issue.

Building from Source

You don’t need to build from source to use Spring Boot. If you want to try out the latest and greatest, Spring Boot can be built and published to your local Maven cache using the Gradle wrapper. You also need JDK 25.

$ ./gradlew publishToMavenLocal

This command builds all modules and publishes them to your local Maven cache. It won’t run any of the tests. If you want to build everything, use the build task:

$ ./gradlew build

Guides

The spring.io site contains several guides that show how to use Spring Boot step-by-step:

Building an Application with Spring Boot is an introductory guide that shows you how to create an application, run it, and add some management services.
Building a RESTful Web Service with Spring Boot Actuator is a guide to creating a REST web service and also shows how the server can be configured.

License

Spring Boot is Open Source software released under the Apache 2.0 license.