GitHub Java Weekly Trending Repositories

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).

dbeaver/dbeaver

Free universal database tool and SQL client

DBeaver

Free multi-platform database tool for developers, SQL programmers, database administrators and analysts.

Has a lot of features including schema editor, SQL editor, data editor, AI integration, ER diagrams, data export/import/migration, SQL execution plans, database administration tools, database dashboards, Spatial data viewer, proxy and SSH tunnelling, custom database drivers editor, etc.
Out of the box supports more than 100 database drivers.
Supports any database which has JDBC or ODBC driver (basically - almost all existing databases).
Supports smart AI completion and code generation with OpenAI or Copilot

Download

You can download prebuilt binaries from official website or directly from GitHub releases.
You can also download Early Access version. We publish daily.

Running

Just run an installer and then click on app icon. Or unzip an archive and run dbeaver from command line.

Note: DBeaver needs Java to run. OpenJDK 21 is included in all DBeaver distributions. You can change default JDK version by replacing directory jre in dbeaver installation folder.

Documentation

Architecture

DBeaver is written mostly on Java. However, it also uses a set of native OS-specific components for desktop UI, high performance database drivers and networking.
Basic frameworks:
- OSGI platform for plugins and dependency management. Community version consists of 130+ plugins.
- Eclipse RCP platform for rich user interface build.
- JDBC for basic database connectivity API.
- JSQLParser and Antlr4 for SQL grammar and semantic parser.
For networking and additional functionality we use wide range of open source libraries such as SSHJ, Apache POI, JFreeChart, JTS, Apache JEXL etc.
We separate model plugins from desktop UI plugins. This allows us to use the same set of "back-end" plugins in both DBeaver and CloudBeaver.
Dependencies: being an OSGI application we use P2 repositories for third party dependencies. For additional Maven dependencies we use our own DBeaver P2 repo.

Supported databases

Community version

Out of the box DBeaver supports following database drivers: MySQL, MariaDB, Oracle, DB2, PostgreSQL, SQL Server, Sybase, Apache Hive, Drill, Presto, Trino, Phoenix, Exasol, Informix, Teradata, Vertica, Netezza, Firebird, Derby, H2, H2GIS, WMI, Snowflake, Greenplum, Redshift, Athena, SAP HANA, MaxDB, NuoDB, MS Access, SQLite, CSV, DBF, Firebird, TimescaleDB, Yellowbrick, CockroachDB, OrientDB, MonetDB, Google BigQuery, Google Spanner, Apache Hive/Impala/Spark, Apache Ignite, MapD, Azure SQL, CrateDB, Elasticsearch, Ocient, Ingres, OmniSci, Yugabyte, IRIS, Data Virtuality, Denodo, Virtuoso, Machbase, DuckDB, Babelfish, OceanBase, Salesforce, EnterpriseDB, Apache Druid, Apache Kylin, Databricks, OpenSearch, TiDB, TDEngine, Materialize, JDBCX, Dameng, Altibase, StarRocks, CUBRID, GaussDB, DolphinDB, LibSQL, GBase 8s, Databend, Cloudberry, Teiid, Kingbase, GreptimeDB.

PRO versions

Commercial versions extends functionality of many popular drivers and also support non-JDBC datasources such as: ODBC, MongoDB, Cassandra, Couchbase, CouchDB, Redis, InfluxDB, Firestore, BigTable, DynamoDB, Kafka KSQL, Neo4j, AWS Neptune, AWS Timestream, Azure CosmosDB, Yugabyte, Salesforce, etc.
Also, we support flat files as databases: CSV, XLSX, Json, XML, Parquet.
You can find the list of all databases supported in commercial versions here.

Feedback

For bug reports and feature requests - please create a ticket.
To promote a ticket to a higher priority - please vote for it with 👍 under the ticket description.
If you have any questions, ideas, etc - please start a discussion.
Pull requests are welcome. See our guide for contributors.
Visit https://dbeaver.com for more information.
Follow us on X and watch educational video on YouTube
Thanks for using DBeaver! Star if you like it.

Contribution: help the Beaver!

Hooray, we have reached 50k+ stars on GitHub and continue to grow!
That's really cool, and we are glad that you like DBeaver.

We are actively looking for new source code contributors. We have added labels “Good first issue” and “Help wanted” to some tickets. If you want to be a part of our development team, just be brave and take a ticket. We are happy to reward our most active contributors every major sprint.
You can buy one of our commercial versions. They include NoSQL databases support, additional extensions, and official online support. Also, licensed users have priorities in bug fixes and the development of new features.

Thank you!

DBeaver Team (contributors)

Our other open-source products:

CloudBeaver - web-based database management tool built on the DBeaver platform.
Runs as server (docker) and provides rich web interface (SPA).
dbvr - CLI database management tool. Useful in CI/CD pipelines and all sort of automations.

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.

spring-projects/spring-framework

Spring Framework

This is the home of the Spring Framework: the foundation for all Spring projects. Collectively the Spring Framework and the family of Spring projects are often referred to simply as "Spring".

Spring provides everything required beyond the Java programming language for creating enterprise applications for a wide range of scenarios and architectures. Please read the Overview section of the reference documentation for a more complete introduction.

Code of Conduct

This project is governed by the Spring Code of Conduct. By participating, you are expected to uphold this code of conduct. Please report unacceptable behavior to spring-code-of-conduct@spring.io.

Access to Binaries

For access to artifacts or a distribution zip, see the Spring Framework Artifacts wiki page.

Documentation

The Spring Framework maintains reference documentation (published and source), GitHub wiki pages, and an API reference. There are also guides and tutorials across Spring projects.

Micro-Benchmarks

See the Micro-Benchmarks wiki page.

Build from Source

See the Build from Source wiki page and the CONTRIBUTING.md file.

Continuous Integration Builds

CI builds are defined with GitHub Actions workflows.

Stay in Touch

Follow @SpringCentral, @SpringFramework, and its team members on 𝕏. In-depth articles can be found at The Spring Blog, and releases are announced via our releases feed.

License

The Spring Framework is released under version 2.0 of the Apache License.

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)

TheAlgorithms/Java

All Algorithms implemented in Java

The Algorithms - Java

You can run and edit the algorithms, or contribute to them using Gitpod.io (a free online development environment) with a single click.

All algorithms are implemented in Java (for educational purposes)

These implementations are intended for learning purposes. As such, they may be less efficient than the Java standard library.

Contribution Guidelines

Please read our Contribution Guidelines before you contribute to this project.

Algorithms

Our directory has the full list of applications.

ashishps1/awesome-system-design-resources

Learn System Design concepts and prepare for interviews using free resources.

Awesome System Design Resources

This repository contains free resources to learn System Design concepts and prepare for interviews.

👉 Subscribe to my AlgoMaster Newsletter and get a FREE System Design Interview Handbook in your inbox.

✅ If you are new to System Design, start here: System Design was HARD until I Learned these 30 Concepts

⚙️ Core Concepts

🌐 Networking Fundamentals

🔌 API Fundamentals

🗄️ Database Fundamentals

⚡ Caching Fundamentals

🔄 Asynchronous Communication

🧩 Distributed System and Microservices

🖇️ Architectural Patterns

⚖️ System Design Tradeoffs

✅ How to Answer a System Design Interview Problem

💻 System Design Interview Problems

Easy

Medium

Hard

📇 Courses

📩 Newsletters

AlgoMaster Newsletter

📚 Books

Designing Data-Intensive Applications

📺 YouTube Channels

📜 Must-Read Engineering Articles

🗞️ Must-Read Distributed Systems Papers

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

questdb/questdb

QuestDB is a high performance, open-source, time-series database

English | 简体中文

QuestDB is an open-source time-series database offering blazingly fast ingestion and dynamic, low-latency SQL queries.

QuestDB delivers a multi-tier storage engine (WAL → native → Parquet on object storage), and the core engine is implemented in zero-GC Java and C++; QuestDB Enterprise includes additional components in Rust.

We achieve high performance via a column-oriented storage model, parallelized vector execution, SIMD instructions, and low-latency techniques. In addition, QuestDB is hardware efficient, with quick setup and operational efficiency.

Ready to go? Jump to the Get started section.

QuestDB Web Console - click to launch demo

Benefits of QuestDB

Feature highlights include:

Low-latency, high-throughput ingestion — from single events to millions/sec
Low-latency SQL with time-series extensions (ASOF JOIN, WINDOW JOIN, HORIZON JOIN, SAMPLE BY, LATEST ON)
SIMD-accelerated, parallel execution
Multi-tier storage: WAL → native columnar → Parquet (time-partitioned and time-ordered)
Postgres protocol (PGwire) and REST API
Views, materialized views, and n-dimensional arrays (incl. 2D arrays for order books)
Web console for queries and data management
Apache 2.0 open source and open formats — no vendor lock-in
Finance functions and orderbook analytics

QuestDB excels with:

financial market data (tick data, trades, order books, OHLC)
Sensor/telemetry data with high data cardinality
real-time dashboards and monitoring
AI coding agents for automated data pipelines and analytics

And why use a time-series database?

Beyond performance and efficiency, with a specialized time-series database, you don't need to worry about:

out-of-order data
deduplication and exactly one semantics
Continuous streaming ingest with many concurrent queries
streaming data (low latency)
volatile and "bursty" data
adding new columns - change schema "on the fly" while streaming data

Try QuestDB, demo and dashboards

The live, public demo is provisioned with the latest QuestDB release and sample datasets:

Trades: live crypto trades with 30M+ rows per month (OKX exchange)
FX order book: live charts with orderbook FX pairs.
Trips: 10 years of NYC taxi trips with 1.6 billion rows

We also have some public, real-time demo dashboards using our Grafana-native plugin:

Real-time crypto trades: executed trades on OKX from more than 20 assets in real time
FX order book: live depth/imbalance charts for major FX pairs

QuestDB performance vs. other databases

QuestDB performs very well in performance benchmarks compared to alternatives.

For deep dives into internals and performance, see the following blog posts:

As always, we encourage you to run your own benchmarks.

AI coding agents

QuestDB works out of the box with AI coding agents. Install the QuestDB agent skill and go from prompt to production in under 60 seconds: streaming ingestion, materialized views, and real-time analytics with zero manual code.

Get started

Use Docker to start quickly:

docker run -p 9000:9000 -p 9009:9009 -p 8812:8812 questdb/questdb

Or macOS users can use Homebrew:

brew install questdb
brew services start questdb

questdb start
questdb stop

Alternatively, to kickoff the full onboarding journey, start with our concise quick start guide.

First-party clients

QuestDB clients for ingesting data and running queries over the QuestDB Wire Protocol:

Connect to QuestDB

See the Connect overview for the full picture.

The QuestDB Wire Protocol (QWP) is the native protocol and the recommended way to talk to QuestDB. It is binary, streams in both directions over a single connection on port 9000, and covers ingestion and queries through one connect string. The first-party clients listed above speak it.

QuestDB also speaks compatibility protocols, so existing tooling works unchanged:

InfluxDB Line Protocol for collectors and pipelines that already emit ILP, on port 9000
PostgreSQL Wire Protocol for Postgres drivers, BI tools, and ORMs, on port 8812
REST API for HTTP scripting, cURL, and CSV import, on port 9000

For interactive use, the Web Console provides a SQL editor, charts, and CSV import on port 9000.

Popular third-party tools

Popular tools that integrate with QuestDB include:

End-to-end code scaffolds

From streaming ingestion to visualization with Grafana, start with code scaffolds from our quickstart repository.

Configure QuestDB for production workloads

Find our capacity planning to fine-tune QuestDB for production workloads.

QuestDB Enterprise

For secure operation at greater scale or within larger organizations.

Additional features include:

high availability and read replica(s)
multi-primary ingestion
cold storage integration
role-based access control
TLS encryption
native querying of Parquet files via object storage
support SLAs, enhanced monitoring and more

Visit the Enterprise page for further details and contact information.

Additional resources

📚 Read the docs

QuestDB documentation: begin the journey
Product roadmap: check out our plan for upcoming releases
Tutorials: learn what's possible with QuestDB, step by step

❓ Get support

Community Discourse forum: join technical discussions, ask questions, and meet other users!
Public Slack: chat with the QuestDB team and community members
GitHub issues: report bugs or issues with QuestDB
Stack Overflow: look for common troubleshooting solutions

🚢 Deploy QuestDB

Contribute

Contributions welcome!

We appreciate:

source code
documentation (see our documentation repository)
bug reports
feature requests or feedback.

To get started with contributing:

Have a look through GitHub issues labelled "Good first issue"
For Hacktoberfest, see the relevant labelled issues
Read the contribution guide
For details on building QuestDB, see the build instructions
Create a fork of QuestDB and submit a pull request with your proposed changes
Stuck? Join our public Slack for assistance

✨ As a sign of our gratitude, we send QuestDB swag to our contributors!

A big thanks goes to the following wonderful people who have contributed to QuestDB emoji key:

_{clickingbuttons} 💻 🤔 📓	_ideoma 💻 📓 ⚠️	_tonytamwk 💻 📓	_sirinath 🤔	_{igor-suhorukov} 💻 🤔	_mick2004 💻 📦	_rawkode 💻 🚇
_solidnerd 💻 🚇	_solanav 💻 📖	_{shantanoo-desai} 📝 💡	_alexprut 💻 🚧	_lbowman 💻 ⚠️	_{chankeypathak} 📝	_{upsidedownsmile} 💻
_Nagriar 💻	_piotrrzysko 💻 ⚠️	_mpsq 💻	_{siddheshlatkar} 💻	_Yitaek ✅ 💡	_gabor-boros ✅ 💡	_kovid-r ✅ 💡
_TimBo93 🐛 📓	_zikani03 💻	_jaugsburger 💻 🚧	_TheTanc 📆 🖋 🤔	_davidgs 🐛 🖋	_kaishin 💻 💡	_bluestreak01 💻 🚧 ⚠️
_{patrickSpaceSurfer} 💻 🚧 ⚠️	_chenrui333 🚇	_bsmth 📖 🖋	_Ugbot 💬 📓 📢	_lepolac 💻 🔧	_tiagostutz 📓 🐛 📆	_Lyncee59 🤔 💻
_rrjanbiah 🐛	_{sarunas-stasaitis} 🐛	_RiccardoGiro 🐛	_duggar 🐛	_postol 🐛	_petrjahoda 🐛	_t00 🐛
_snenkov 📓 🐛 🤔	_marregui 💻 🤔 🎨	_bratseth 💻 🤔 📓	_welly87 🤔	_fuzzthink 🤔 📓	_nexthack 💻	_g-metan 🐛
_tim2skew 🐛 📓	_ospqsp 🐛	_SuperFluffy 🐛	_nu11ptr 🐛	_comunidadio 🐛	_mugendi 🤔 🐛 📖	_paulwoods222 🐛
_mingodad 🤔 🐛 📖	_houarizegai 📖	_jjsaunier 🐛	_zanek 🤔 📆	_Geekaylee 📓 🤔	_lg31415 🐛 📆	_null-dev 🐛 📆
_ultd 🤔 📆	_ericsun2 🤔 🐛 📆	_{giovannibonetti} 📓 🐛 📆	_wavded 📓 🐛	_puzpuzpuz 📖 💻 📓	_rstreics 💻 🚇 📖	_{mariusgheorghies} 💻 🚇 📖
_pswu11 🖋 🤔 🎨	_insmac 💻 🤔 🎨	_eugenels 💻 🤔 🚧	_bziobrowski 💻 📆	_Zapfmeister 💻 📓	_mkaruza 💻	_DylanDKnight 📓 🐛
_enolal826 💻	_glasstiger 💻	_argshook 💻 🤔 🎨 🐛	_amunra 💻 📖 🐛	_GothamsJoker 💻	_kocko 💻	_jerrinot 💻 🤔 🐛
_rberrelleza 💻	_Cobalt-27 💻	_eschultz 💻	_XinyiQiao 💻	_terasum 📖	_{PlamenHristov} 💻	_tris0laris 📝 🤔
_HeZean 💻 🐛	_iridess 💻 📖	_{selmanfarukyilmaz} 🐛	_donet5 🤔 🐛	_Zahlii 🐛	_salsasepp 🐛	_EmmettM 🐛 ⚠️
_robd003 🤔	_AllenEdison 🐛	_CSharpDummy 🐛	_{shimondoodkin} 🐛 🤔	_huuhait 🐛 🤔	_{alexey-milovidov} 🐛	_suconghou 🐛
_{allegraharris} 💻	_{oliver-daniel} 💻	_{kerimsenturk5734} 📖

This project adheres to the all-contributors specification. Contributions of any kind are welcome!

apache/fluss

Apache Fluss is a streaming storage built for real-time analytics.

Documentation | QuickStart | Development

What is Apache Fluss?

Apache Fluss is a streaming storage built for real-time analytics & AI which can serve as the real-time data layer for Lakehouse architectures.

It bridges the gap between data streaming and data Lakehouse by enabling low-latency, high-throughput data ingestion and processing while seamlessly integrating with popular compute engines like Apache Flink and Apache Spark, with StarRocks coming soon.

Fluss (German: river, pronounced /flus/) enables streaming data continuously converging, distributing and flowing into lakes, like a river 🌊

Features

Sub-Second Data Freshness: Continuous ingestion and immediate availability of data enable low-latency analytics and real-time decision-making at scale.
Streaming & Lakehouse Unification: Streaming-native storage with low-latency access on top of the lakehouse, using tables as a single abstraction to unify real-time and historical data across engines.
Columnar Streaming: Based on Apache Arrow it allows database primitives on data streams and techniques like column pruning and predicate pushdown. This ensures engines read only the data they need, minimizing I/O and network costs.
Compute–Storage Separation: Stream processors focus on pure computation while Fluss manages state and storage, with features like deduplication, partial updates, delta joins, and aggregation merge engines.
ML & AI–Ready Storage: A unified storage layer supporting row-based, columnar, vector, and multi-modal data, enabling real-time feature stores and a centralized data repository for ML and AI systems.
Changelogs & Decision Tracking: Built-in changelog generation provides an append-only history of state and decision evolution, enabling auditing, reproducibility, and deep system observability.

Building

Prerequisites for building Apache Fluss:

Unix-like environment (we use Linux, Mac OS X, Cygwin, WSL)
Git
Maven (we require version >= 3.8.6)
Java 11

git clone https://github.com/apache/fluss.git
cd fluss
./mvnw clean package -DskipTests

Apache Fluss is now installed in build-target. The build command uses Maven Wrapper (mvnw) which ensures the correct Maven version is used.

Contributing

Apache Fluss is open-source, and we’d love your help to keep it growing! Join the discussions, open issues if you find a bug or request features, contribute code and documentation, or help us improve the project in any way. All contributions are welcome!

License

Apache Fluss project is licensed under the Apache License 2.0.

kunal-kushwaha/DSA-Bootcamp-Java

This repository consists of the code samples, assignments, and notes for the Java data structures & algorithms + interview preparation bootcamp of WeMakeDevs.

DSA + Interview preparation bootcamp

Subscribe to the YouTube channel
Lectures
Course website
Assignments (solutions can be found on LeetCode)

Mininglamp-OSS/octo-android

OCTO Android Client — Open-source enterprise IM

OCTO — the open workplace built for humans × AI agents.
_{Let Lobsters (OpenClaw-powered digital doubles) do the thinking and doing. You focus on taste.}

🏠 OCTO Home · 🚀 Quickstart · 📦 Ecosystem · 🤝 Contributing

🌐 Read in: English · 简体中文

OCTO Android

Native Android client for the OCTO messaging platform — Kotlin / Java, talking to octo-server over REST + WebSocket.

octo-android is the official Android front-end for OCTO. It is a native Kotlin / Java app (not a webview wrapper) that talks to octo-server over REST + WebSocket, and drives the same Lobster-agent conversation surface as octo-web.

🌟 Why OCTO Android

Native, not a webview. AndroidX-based, Material-themed, uses platform features (Foreground Service for message push, Scoped Storage for attachments, Jetpack Compose / XML views) rather than shipping a browser shell. First-class mobile UX for Lobster conversations.
Ships without secrets. No google-services.json, no keystore, no Play Store listing bound to the upstream. You bring your own Firebase project, your own Bundle ID (com.example.octo placeholder → com.yourcompany.octo), your own keystore. All baked-out via the octo-release pipeline before this repo is published.
Mirrors the web surface. Same REST + WebSocket protocol as octo-web, same i18n resource keys (English · 简体中文), same Lobster identity / streaming / typing indicators — so feature work can land on both clients without a protocol fork.

📥 Download

Download the latest APK from Releases, install it on your device, and enter your own octo-server address on the login screen.

No build required — just install and connect to your deployment.

🚀 Quickstart

⚠️ Mandatory pre-flight — this fork will not build a distributable APK until you swap three placeholder artefacts:

Bundle ID / applicationId — see README-BUNDLE-ID.md for the full rename checklist (com.example.octo → your reverse-DNS).
Firebase configuration — see firebase-template.md for how to obtain and drop in your own google-services.json.
Release keystore — see keystore-template.md for how to generate a signing keystore and wire it into Gradle.

Once those are done, a dev debug build is straightforward:

git clone https://github.com/Mininglamp-OSS/octo-android.git
cd octo-android

# Open in Android Studio (Giraffe+) and let it sync, or from CLI:
./gradlew :app:assembleDebug

# Install on a connected device:
./gradlew :app:installDebug

By default the app points at http://localhost:8080 for octo-server. Edit app/src/main/res/values/config.xml (or the flavor-specific equivalent) to aim at your own deployment.

📦 Modules / Architecture

Top-level layout (typical OCTO Android tree):

Path	Purpose
`app/`	Main application module — activities, fragments, navigation graph
`app/src/main/java/.../ui/`	Screen surfaces: chat, channels, org, settings
`app/src/main/java/.../data/`	REST + WebSocket client, local cache, Room DAOs
`app/src/main/java/.../agent/`	Lobster-aware UI components (streaming, tool-call previews, agent identity)
`app/src/main/java/.../push/`	Firebase Messaging receiver + notification routing
`app/src/main/res/`	Layouts, drawables, XML configs, i18n (`values-en`, `values-zh-rCN`)
`wukong-sdk/`	WuKongIM Android client wrapper (real-time messaging transport)
`common/`	Shared utilities (crypto, time, JSON)
`buildSrc/`	Gradle convention plugins, dependency versions

Runtime pillars:

Auth — token / refresh-token stored in EncryptedSharedPreferences.
Transport — OkHttp for REST + the WuKongIM Android SDK for the persistent WebSocket.
Persistence — Room database for message cache and offline drafts; Scoped-Storage-safe attachment handling.
Push — Firebase Cloud Messaging → foreground service → local notification channel.
UI — single-Activity + fragments (or Compose screens depending on flavour), Material 3 theming, RTL-safe layouts.

🔗 OCTO Ecosystem

graph TD
  subgraph Clients[Clients]
    Web[octo-web<br/>Web / PC]
    Android[octo-android<br/>Android]
    iOS[octo-ios<br/>iOS]
  end

  subgraph Core[Core Services]
    Server[octo-server<br/>Backend API]
    Matter[octo-matter<br/>Task / Todo]
    Summary[octo-smart-summary<br/>AI Summary]
    Admin[octo-admin<br/>Admin Console]
  end

  subgraph Shared[Shared Libraries & Integrations]
    Lib[octo-lib<br/>Core Go Library]
    Adapters[octo-adapters<br/>Third-party Adapters]
  end

  Web --> Server
  Android --> Server
  iOS --> Server
  Admin --> Server
  Server --> Matter
  Server --> Summary
  Server --> Adapters
  Server -.uses.-> Lib
  Matter -.uses.-> Lib
  Adapters -.uses.-> Lib

Repository	Language	Role
`octo-server`	Go	Backend API · business orchestration · Lobster agent scheduling
`octo-matter`	Go	Task / Todo / Matter micro-service
`octo-smart-summary`	Go	LLM-powered conversation summarisation
`octo-web`	TypeScript / React	Web & PC (Electron) client
`octo-android`	Kotlin / Java	Native Android client
`octo-ios`	Swift / Objective-C	Native iOS client
`octo-admin`	TypeScript / React	Admin console (tenant / org / user / channel management)
`octo-lib`	Go	Shared core library (protocol, crypto, storage, HTTP)
`octo-adapters`	TypeScript / Python	Third-party integrations (IM bridges, AI channels)

🧭 Philosophy

OCTO ships under three shared principles that apply to every repository in this matrix:

Local-first. Anything that can run on the user's own box — chats, embeddings, agents — should. Your data stays yours; cloud is a choice, not a requirement.
Humans judge, AI thinks and acts. Humans focus on taste (what matters, what's right, what to ship). Lobster agents — OpenClaw-powered digital doubles — carry the thinking and execution load.
Release-as-product. Every open-source cut is shipped as a self-contained product, not a code dump: one squash per release, Apache 2.0, no internal baggage, reproducible from this repo alone.

🤝 Contributing

We love pull requests! Before you open one, please read:

CONTRIBUTING.md — workflow, branch model, commit style
CODE_OF_CONDUCT.md — community expectations

For security issues please follow SECURITY.md instead of the public tracker.

📄 License

Apache License 2.0 — see LICENSE for the full text and NOTICE for third-party attributions.

🙏 Acknowledgments

octo-android owes its original scaffolding to:

TangSengDaoDaoAndroid — our upstream, by the TangSengDaoDao team.
WuKongIM — the real-time messaging core that octo-server drives behind this client.

See NOTICE for the full attribution list and third-party component licenses.

_{Made with 🐙 by OCTO Contributors · Mininglamp-OSS}

OpenLineage/OpenLineage

An Open Standard for lineage metadata collection

Overview

OpenLineage is an Open standard for metadata and lineage collection designed to instrument jobs as they are running. It defines a generic model of run, job, and dataset entities identified using consistent naming strategies. The core lineage model is extensible by defining specific facets to enrich those entities.

OpenLineage is an LF AI & Data Foundation Graduate project under active development, and we welcome contributions.

Problem

Before

Duplication of effort: each project has to instrument all jobs
Integrations are external and can break with new versions

With OpenLineage

The effort of integration is shared
An integration can be pushed in each project: no need to play catch up

Scope

OpenLineage defines the metadata for running jobs and the corresponding events. A configurable backend allows the user to choose what protocol to send the events to.

Core model

A facet is an atomic piece of metadata attached to one of the core entities. See the spec for more details.

Spec

The specification is defined using OpenAPI and allows extension through custom facets.

Integrations

OpenLineage supports integrations with Spark, Airflow, dbt, Flink, and more. For the most up-to-date and complete list of supported integrations, their capabilities, and matrices, please refer to the official OpenLineage Integrations Documentation.

Related projects

Marquez: Marquez is an LF AI & DATA project to collect, aggregate, and visualize a data ecosystem's metadata. It is the reference implementation of the OpenLineage API.
- OpenLineage collection implementation
Egeria: Egeria offers open metadata and governance for enterprises - automatically capturing, managing and exchanging metadata between tools and platforms, no matter the vendor.

Community

Website: openlineage.io
Slack: OpenLineage.slack.com
Twitter: @OpenLineage
Mailing list: openlineage-tsc
Wiki: OpenLineage+Home
LinkedIn: 13927795
YouTube: channel
Mastodon: @openlineage@fostodon.org

Talks

Contributing

See CONTRIBUTING.md for more details about how to contribute.

Report a Vulnerability

If you discover a vulnerability in the project, please open an issue and attach the "security" label.

Star History

SPDX-License-Identifier: Apache-2.0
Copyright 2018-2026 contributors to the OpenLineage project

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.

YunaiV/ruoyi-vue-pro

🔥 官方推荐 🔥 RuoYi-Vue 全新 Pro 版本，优化重构所有功能。基于 Spring Boot + MyBatis Plus + Vue & Element 实现的后台管理系统 + 微信小程序，支持 RBAC 动态权限、数据权限、SaaS 多租户、Flowable 工作流、三方登录、支付、短信、商城、CRM、ERP、MES、IM、AI 大模型、IoT 物联网等功能。你的 ⭐️ Star ⭐️，是作者生发的动力！

严肃声明：现在、未来都不会有商业版本，所有代码全部开源!！

「我喜欢写代码，乐此不疲」
「我喜欢做开源，以此为乐」

我 🐶 在上海艰苦奋斗，早中晚在 top3 大厂认真搬砖，夜里为开源做贡献。

如果这个项目让你有所收获，记得 Star 关注哦，这对我是非常不错的鼓励与支持。

🐶 新手必读

演示地址【Vue3 + element-plus】：http://dashboard-vue3.yudao.iocoder.cn
演示地址【Vue3 + vben(ant-design-vue)】：http://dashboard-vben.yudao.iocoder.cn
演示地址【Vue2 + element-ui】：http://dashboard.yudao.iocoder.cn
启动文档：https://doc.iocoder.cn/quick-start/
视频教程：https://doc.iocoder.cn/video/

🐰 版本说明

版本	JDK 8 + Spring Boot 2.7	JDK 17/21 + Spring Boot 3.5	JDK 25 + Spring Boot 4.x
【完整版】ruoyi-vue-pro	`master` 分支	`master-jdk17` 分支	`master-jdk25` 分支
【精简版】yudao-boot-mini	`master` 分支	`master-jdk17` 分支	`master-jdk25` 分支

【完整版】：包括系统功能、基础设施、会员中心、数据报表、工作流程、商城系统、微信公众号、CRM、ERP、WMS、MES、IM 即时通讯、AI 大模型、IoT 物联网等功能
【精简版】：只包括系统功能、基础设施功能，不包括会员中心、数据报表、工作流程、商城系统、微信公众号、CRM、ERP、WMS、MES、IM 即时通讯、AI 大模型、IoT 物联网等功能

可参考《迁移文档》，只需要 5-10 分钟，即可将【完整版】按需迁移到【精简版】

🐯 平台简介

芋道，以开发者为中心，打造中国第一流的快速开发平台，全部开源，个人与企业可 100% 免费使用。

有任何问题，或者想要的功能，可以在 Issues 中提给艿艿。

😜 给项目点点 Star 吧，这对我们真的很重要！

Java 后端：master 分支为 JDK 8 + Spring Boot 2.7，master-jdk17 分支为 JDK 17/21 + Spring Boot 3.5，master-jdk25 分支为 JDK 25 + Spring Boot 4.x
管理后台的电脑端：Vue3 提供 element-plus、vben(ant-design-vue) 两个版本，Vue2 提供 element-ui 版本
管理后台的移动端：采用 uni-app 方案，一份代码多终端适配，同时支持 APP、小程序、H5！
后端采用 Spring Boot 多模块架构、MySQL + MyBatis Plus、Redis + Redisson
数据库可使用 MySQL、Oracle、PostgreSQL、SQL Server、MariaDB、国产达梦 DM、TiDB 等
消息队列可使用 Event、Redis、RabbitMQ、Kafka、RocketMQ 等
权限认证使用 Spring Security & Token & Redis，支持多终端、多种用户的认证系统，支持 SSO 单点登录
支持加载动态权限菜单，按钮级别权限控制，Redis 缓存提升性能
支持 SaaS 多租户，可自定义每个租户的权限，提供透明化的多租户底层封装
工作流使用 Flowable，支持动态表单、在线设计流程、会签 / 或签、多种任务分配方式
高效率开发，使用代码生成器可以一键生成 Java、Vue 前后端代码、SQL 脚本、接口文档，支持单表、树表、主子表
实时通信，采用 Spring WebSocket 实现，内置 Token 身份校验，支持 WebSocket 集群
集成微信小程序、微信公众号、企业微信、钉钉等三方登陆，集成支付宝、微信等支付与退款
集成阿里云、腾讯云等短信渠道，集成 MinIO、阿里云、腾讯云、七牛云等云存储服务
集成报表设计器、大屏设计器，通过拖拽即可生成酷炫的报表与大屏

🐳 项目关系

三个项目的功能对比，可见社区共同整理的国产开源项目对比表格。

后端项目

项目	Star	简介
ruoyi-vue-pro		基于 Spring Boot 多模块架构
yudao-cloud		基于 Spring Cloud 微服务架构
Spring-Boot-Labs		系统学习 Spring Boot & Cloud 专栏

前端项目

项目	Star	简介
yudao-ui-admin-vue3		基于 Vue3 + element-plus 实现的管理后台
yudao-ui-admin-vben		基于 Vue3 + vben(ant-design-vue) 实现的管理后台
yudao-mall-uniapp		基于 uni-app 实现的商城小程序
yudao-ui-admin-vue2		基于 Vue2 + element-ui 实现的管理后台
yudao-ui-admin-uniapp		基于 Vue2 + element-ui 实现的管理后台
yudao-ui-go-view		基于 Vue3 + naive-ui 实现的大屏报表

😎 开源协议

为什么推荐使用本项目？

① 本项目采用比 Apache 2.0 更宽松的 MIT License 开源协议，个人与企业可 100% 免费使用，不用保留类作者、Copyright 信息。

② 代码全部开源，不会像其他项目一样，只开源部分代码，让你无法了解整个项目的架构设计。国产开源项目对比

③ 代码整洁、架构整洁，遵循《阿里巴巴 Java 开发手册》规范，代码注释详细，113770 行 Java 代码，42462 行代码注释。

🤝 项目外包

我们也是接外包滴，如果你有项目想要外包，可以微信联系【Aix9975】。

团队包含专业的项目经理、架构师、前端工程师、后端工程师、测试工程师、运维工程师，可以提供全流程的外包服务。

项目可以是商城、SCRM 系统、OA 系统、物流系统、ERP 系统、CMS 系统、HIS 系统、支付系统、IM 即时通讯、微信公众号、微信小程序等等。

🐼 内置功能

系统内置多种多种业务功能，可以用于快速你的业务系统：

通用模块（必选）：系统功能、基础设施
通用模块（可选）：工作流程、支付系统、数据报表、会员中心
业务系统（按需）：Mall 电子商城、OA 办公自动化、ERP 企业资源计划系统、WMS 仓库管理系统、CRM 客户关系管理、CMS 内容管理系统、MES 执行制造系统、AI 大模型平台、IoT 物联网系统、IM 即时通讯系统、Mobile 手机移动端、Report 数据大屏

友情提示：本项目基于 RuoYi-Vue 修改，重构优化后端的代码，美化前端的界面。

额外新增的功能，我们使用 🚀 标记。

重新实现的功能，我们使用 ⭐️ 标记。

🙂 所有功能，都通过 单元测试 保证高质量。

系统功能

	功能	描述
	用户管理	用户是系统操作者，该功能主要完成系统用户配置
⭐️	在线用户	当前系统中活跃用户状态监控，支持手动踢下线
	角色管理	角色菜单权限分配、设置角色按机构进行数据范围权限划分
	菜单管理	配置系统菜单、操作权限、按钮权限标识等，本地缓存提供性能
	部门管理	配置系统组织机构（公司、部门、小组），树结构展现支持数据权限
	岗位管理	配置系统用户所属担任职务
🚀	租户管理	配置系统租户，支持 SaaS 场景下的多租户功能
🚀	租户套餐	配置租户套餐，自定每个租户的菜单、操作、按钮的权限
	字典管理	对系统中经常使用的一些较为固定的数据进行维护
🚀	短信管理	短信渠道、短息模板、短信日志，对接阿里云、腾讯云等主流短信平台
🚀	邮件管理	邮箱账号、邮件模版、邮件发送日志，支持所有邮件平台
🚀	站内信	系统内的消息通知，提供站内信模版、站内信消息
🚀	操作日志	系统正常操作日志记录和查询，集成 Swagger 生成日志内容
⭐️	登录日志	系统登录日志记录查询，包含登录异常
🚀	错误码管理	系统所有错误码的管理，可在线修改错误提示，无需重启服务
	通知公告	系统通知公告信息发布维护
🚀	敏感词	配置系统敏感词，支持标签分组
🚀	应用管理	管理 SSO 单点登录的应用，支持多种 OAuth2 授权方式
🚀	地区管理	展示省份、城市、区镇等城市信息，支持 IP 对应城市

工作流程

基于 Flowable 构建，可支持信创（国产）数据库，满足中国特色流程操作：

BPMN 设计器	钉钉/飞书设计器

历经头部企业生产验证，工作流引擎须标配仿钉钉/飞书 + BPMN 双设计器！！！

前者支持轻量配置简单流程，后者实现复杂场景深度编排

功能列表	功能描述	是否完成
SIMPLE 设计器	仿钉钉/飞书设计器，支持拖拽搭建表单流程，10 分钟快速完成审批流程配置	✅
BPMN 设计器	基于 BPMN 标准开发，适配复杂业务场景，满足多层级审批及流程自动化需求	✅
会签	同一个审批节点设置多个人（如 A、B、C 三人，三人会同时收到待办任务），需全部同意之后，审批才可到下一审批节点	✅
或签	同一个审批节点设置多个人，任意一个人处理后，就能进入下一个节点	✅
依次审批	（顺序会签）同一个审批节点设置多个人（如 A、B、C 三人），三人按顺序依次收到待办，即 A 先审批，A 提交后 B 才能审批，需全部同意之后，审批才可到下一审批节点	✅
抄送	将审批结果通知给抄送人，同一个审批默认排重，不重复抄送给同一人	✅
驳回	（退回）将审批重置发送给某节点，重新审批。可驳回至发起人、上一节点、任意节点	✅
转办	A 转给其 B 审批，B 审批后，进入下一节点	✅
委派	A 转给其 B 审批，B 审批后，转给 A，A 继续审批后进入下一节点	✅
加签	允许当前审批人根据需要，自行增加当前节点的审批人，支持向前、向后加签	✅
减签	（取消加签）在当前审批人操作之前，减少审批人	✅
撤销	（取消流程）流程发起人，可以对流程进行撤销处理	✅
终止	系统管理员，在任意节点终止流程实例	✅
表单权限	支持拖拉拽配置表单，每个审批节点可配置只读、编辑、隐藏权限	✅
超时审批	配置超时审批时间，超时后自动触发审批通过、不通过、驳回等操作	✅
自动提醒	配置提醒时间，到达时间后自动触发短信、邮箱、站内信等通知提醒，支持自定义重复提醒频次	✅
父子流程	主流程设置子流程节点，子流程节点会自动触发子流程。子流程结束后，主流程才会执行（继续往下下执行），支持同步子流程、异步子流程	✅
条件分支	（排它分支）用于在流程中实现决策，即根据条件选择一个分支执行	✅
并行分支	允许将流程分成多条分支，不进行条件判断，所有分支都会执行	✅
包容分支	（条件分支 + 并行分支的结合体）允许基于条件选择多条分支执行，但如果没有任何一个分支满足条件，则可以选择默认分支	✅
路由分支	根据条件选择一个分支执行（重定向到指定配置节点），也可以选择默认分支执行（继续往下执行）	✅
触发节点	执行到该节点，触发 HTTP 请求、HTTP 回调、更新数据、删除数据等	✅
延迟节点	执行到该节点，审批等待一段时间再执行，支持固定时长、固定日期等	✅
拓展设置	流程前置/后置通知，节点（任务）前置、后置通知，流程报表，自动审批去重，自定流程编号、标题、摘要，流程报表等	✅

支付系统

	功能	描述
🚀	应用信息	配置商户的应用信息，对接支付宝、微信等多个支付渠道
🚀	支付订单	查看用户发起的支付宝、微信等的【支付】订单
🚀	退款订单	查看用户发起的支付宝、微信等的【退款】订单
🚀	回调通知	查看支付回调业务的【支付】【退款】的通知结果
🚀	接入示例	提供接入支付系统的【支付】【退款】的功能实战

基础设施

	功能	描述
🚀	代码生成	前后端代码的生成（Java、Vue、SQL、单元测试），支持 CRUD 下载
🚀	系统接口	基于 Swagger 自动生成相关的 RESTful API 接口文档
🚀	数据库文档	基于 Screw 自动生成数据库文档，支持导出 Word、HTML、MD 格式
	表单构建	拖动表单元素生成相应的 HTML 代码，支持导出 JSON、Vue 文件
🚀	配置管理	对系统动态配置常用参数，支持 SpringBoot 加载
⭐️	定时任务	在线（添加、修改、删除)任务调度包含执行结果日志
🚀	文件服务	支持将文件存储到 S3（MinIO、阿里云、腾讯云、七牛云）、本地、FTP、数据库等
🚀	WebSocket	提供 WebSocket 接入示例，支持一对一、一对多发送方式
🚀	API 日志	包括 RESTful API 访问日志、异常日志两部分，方便排查 API 相关的问题
	MySQL 监控	监视当前系统数据库连接池状态，可进行分析SQL找出系统性能瓶颈
	Redis 监控	监控 Redis 数据库的使用情况，使用的 Redis Key 管理
🚀	消息队列	基于 Redis 实现消息队列，Stream 提供集群消费，Pub/Sub 提供广播消费
🚀	Java 监控	基于 Spring Boot Admin 实现 Java 应用的监控
🚀	链路追踪	接入 SkyWalking 组件，实现链路追踪
🚀	日志中心	接入 SkyWalking 组件，实现日志中心
🚀	服务保障	基于 Redis 实现分布式锁、幂等、限流功能，满足高并发场景
🚀	日志服务	轻量级日志中心，查看远程服务器的日志
🚀	单元测试	基于 JUnit + Mockito 实现单元测试，保证功能的正确性、代码的质量等

数据报表

	功能	描述
🚀	报表设计器	支持数据报表、图形报表、打印设计等
🚀	大屏设计器	拖拽生成数据大屏，内置几十种图表组件

微信公众号

	功能	描述
🚀	账号管理	配置接入的微信公众号，可支持多个公众号
🚀	数据统计	统计公众号的用户增减、累计用户、消息概况、接口分析等数据
🚀	粉丝管理	查看已关注、取关的粉丝列表，可对粉丝进行同步、打标签等操作
🚀	消息管理	查看粉丝发送的消息列表，可主动回复粉丝消息
🚀	模版消息	配置和发送模版消息，用于向粉丝推送通知类消息
🚀	自动回复	自动回复粉丝发送的消息，支持关注回复、消息回复、关键字回复
🚀	标签管理	对公众号的标签进行创建、查询、修改、删除等操作
🚀	菜单管理	自定义公众号的菜单，也可以从公众号同步菜单
🚀	素材管理	管理公众号的图片、语音、视频等素材，支持在线播放语音、视频
🚀	图文草稿箱	新增常用的图文素材到草稿箱，可发布到公众号
🚀	图文发表记录	查看已发布成功的图文素材，支持删除操作

商城系统

演示地址：https://doc.iocoder.cn/mall-preview/

会员中心

	功能	描述
🚀	会员管理	会员是 C 端的消费者，该功能用于会员的搜索与管理
🚀	会员标签	对会员的标签进行创建、查询、修改、删除等操作
🚀	会员等级	对会员的等级、成长值进行管理，可用于订单折扣等会员权益
🚀	会员分组	对会员进行分组，用于用户画像、内容推送等运营手段
🚀	积分签到	回馈给签到、消费等行为的积分，会员可订单抵现、积分兑换等途径消耗

演示地址（Vue3 + Element Plus）：http://dashboard-vue3.yudao.iocoder.cn

聊天界面	聊天管理

🐨 技术栈

模块

项目	说明
`yudao-dependencies`	Maven 依赖版本管理
`yudao-framework`	Java 框架拓展
`yudao-server`	管理后台 + 用户 APP 的服务端
`yudao-module-system`	系统功能的 Module 模块
`yudao-module-member`	会员中心的 Module 模块
`yudao-module-infra`	基础设施的 Module 模块
`yudao-module-bpm`	工作流程的 Module 模块
`yudao-module-pay`	支付系统的 Module 模块
`yudao-module-mall`	商城系统的 Module 模块
`yudao-module-erp`	ERP 系统的 Module 模块
`yudao-module-crm`	CRM 系统的 Module 模块
`yudao-module-mes`	MES 系统的 Module 模块
`yudao-module-wms`	WMS 系统的 Module 模块
`yudao-module-im`	IM 即时通讯的 Module 模块
`yudao-module-ai`	AI 大模型的 Module 模块
`yudao-module-iot`	IoT 物联网的 Module 模块
`yudao-module-mp`	微信公众号的 Module 模块
`yudao-module-report`	大屏报表 Module 模块

框架

框架	说明	版本	学习指南
Spring Boot	应用开发框架	2.7.18	文档
MySQL	数据库服务器	5.7 / 8.0+
Druid	JDBC 连接池、监控组件	1.2.28	文档
MyBatis Plus	MyBatis 增强工具包	3.5.16	文档
Dynamic Datasource	动态数据源	4.5.0	文档
Redis	key-value 数据库	5.0 / 6.0 /7.0
Redisson	Redis 客户端	4.6.1	文档
Spring MVC	MVC 框架	5.3.39	文档
Spring Security	Spring 安全框架	5.8.16	文档
Hibernate Validator	参数校验组件	6.2.5	文档
Flowable	工作流引擎	6.8.1	文档
Quartz	任务调度组件	2.3.2	文档
Springdoc	Swagger 文档	1.8.0	文档
SkyWalking	分布式应用追踪系统	8.12.0	文档
Spring Boot Admin	Spring Boot 监控平台	2.7.15	文档
Jackson	JSON 工具库	2.13.5
MapStruct	Java Bean 转换	1.6.3	文档
Lombok	消除冗长的 Java 代码	1.18.46	文档
JUnit	Java 单元测试框架	5.8.2	-
Mockito	Java Mock 框架	4.11.0	-

🐷 演示图

系统功能

模块	biu	biu	biu
登录 & 首页
用户 & 应用
租户 & 套餐			-
部门 & 岗位			-
菜单 & 角色			-
审计日志			-
短信
字典 & 敏感词
错误码 & 通知			-

工作流程

模块	biu	biu	biu
流程模型
表单 & 分组			-
我的流程
待办 & 已办
OA 请假

基础设施

模块	biu	biu	biu
代码生成			-
文档			-
文件 & 配置
定时任务			-
API 日志			-
MySQL & Redis			-
监控平台

支付系统

模块	biu	biu	biu
商家 & 应用
支付 & 退款			---

数据报表

模块	biu	biu	biu
报表设计器
大屏设计器

移动端（管理后台）

biu	biu	biu

目前已经实现登录、我的、工作台、编辑资料、头像修改、密码修改、常见问题、关于我们等基础功能。

keycloak/keycloak

Open Source Identity and Access Management For Modern Applications and Services

Open Source Identity and Access Management

Add authentication to applications and secure services with minimum effort. No need to deal with storing users or authenticating users.

Keycloak provides user federation, strong authentication, user management, fine-grained authorization, and more.

Help and Documentation

Documentation
User Mailing List - Mailing list for help and general questions about Keycloak
Join #keycloak for general questions, or #keycloak-dev on Slack for design and development discussions, by creating an account at https://slack.cncf.io/.

Reporting Security Vulnerabilities

If you have found a security vulnerability, please look at the instructions on how to properly report it.

Reporting an issue

If you believe you have discovered a defect in Keycloak, please open an issue. Please remember to provide a good summary, description as well as steps to reproduce the issue.

Getting started

To run Keycloak, download the distribution from our website. Unzip and run:

bin/kc.[sh|bat] start-dev

Alternatively, you can use the Docker image by running:

docker run quay.io/keycloak/keycloak start-dev

For more details refer to the Keycloak Documentation.

Building from Source

To build from source, refer to the building and working with the code base guide.

Testing

To run tests, refer to the running tests guide.

Writing Tests

To write tests, refer to the writing tests guide.

Contributing

Before contributing to Keycloak, please read our contributing guidelines. Participation in the Keycloak project is governed by the CNCF Code of Conduct.

Joining a community meeting is a great way to get involved and help shape the future of Keycloak.

Code of Conduct

We are committed to providing a safe, welcoming, and constructive environment for all Keycloak contributors and users. To protect this space, we actively enforce our Code of Conduct. If you wish to report an incident or appeal a moderation decision, please email keycloak-coc@googlegroups.com.

Other Keycloak Projects

Keycloak - Keycloak Server and Java adapters
Keycloak Client - Keycloak client libraries
Keycloak QuickStarts - QuickStarts for getting started with Keycloak
Keycloak Node.js Connect - Node.js adapter for Keycloak

License

Apache License, Version 2.0

FCL-Team/FoldCraftLauncher

Fold Craft Launcher, an Android Minecraft : Java Edition launcher.

Fold Craft Launcher

🌍 语言
简体中文 | English | Русский язык

你说得对，但是「FoldCraft Launcher」是由FCL-Team基于HMCL的核心功能，使用PojavLauncher后端开发的Minecraft Java版启动器。启动器运行在一个被称作「安卓」的系统，在这里，被系统选中的人将被授予「JVM」，导引Java之力。你将扮演一位名为「小白」的神秘用户，在自由的使用中安装不同版本、各有千秋独特的模组，和它们一起运行，找出崩溃闪退的原因，同时逐步发掘「xxException:」的真相。

✨ 项目简介
「Fold Craft Launcher」是由FCL团队开发的Android平台Minecraft: Java Edition启动器。基于HMCL的核心功能，使用PojavLauncher后端，让您能在移动设备上畅玩Java版MC，支持模组加载与全版本运行。

🚀 核心特性

✅ 全版本支持

原生支持 Minecraft 全版本（包括最新快照）
模组加载器支持：Forge/NeoForge/LiteLoader/OptiFine/Fabric/Quilt/Cleanroom...

⚙️ 功能亮点

内置多版本 Java 运行时（Java 8/17/21/25）同时支持导入Java
虚拟鼠标与自定义按键映射
光影支持（需VirGL/Zink/MG渲染器）
动态资源管理（模组/整合包/材质/光影/存档）
个性化主题定制（背景/颜色方案）
支持渲染器插件化

🎮 使用截图

📜 开源协议

本项目采用 GPL-3.0 License 授权

🤝 贡献与致谢

贡献者墙

依赖

PojavLauncher: [GLGPL]
Android Support Libraries: Apache License 2.0
GL4ES: MIT License
NG-GL4ES (Krypton Wrapper)
OpenJDK: GNU GPLv2 License
LWJGL3: BSD-3 License
LWJGLX (LWJGL2 API compatibility layer for LWJGL3): unknown license
Mesa 3D Graphics Library: MIT License
bhook (Used for exit code trapping): MIT license.
libepoxy: MIT License.
virglrenderer: MIT License.
OpenAL-Soft: GNU GPLv2
- oboe: Apache License 2.0.
- pfffft: ARR
control-converter (FCL→ZL2 控制布局转换，Go 实现，打包为 libcc.so): MIT License

neoforged/NeoForge

Neo Modding API for Minecraft: Java Edition, based on Forge

NeoForge

NeoForge is a free, open-source, community-oriented modding API for Minecraft.

Version	Support
1.21.x	Active

Installing NeoForge

Go to the Download page, select the Minecraft version and installer, and run it. The installer will attempt to install NeoForge into your vanilla launcher environment, where you can then create a new profile using that version and play the game!

For support and questions, visit the NeoForged Discord server.

Creating Mods

See the "Getting Started" section in the NeoForged Documentation.

Contribute to NeoForge

If you wish to actually inspect NeoForge, submit PRs or otherwise work with NeoForge itself, you're in the right place!

Check the contribution workflow for details.

Translations

Translations are done on Crowdin.

Pull requests

Please read the contributing guidelines found here before making a pull request.

Contributor License Agreement

We require all contributors to acknowledge the NeoForged Contributor License Agreement. Please ensure you have a valid email address associated with your GitHub account to do this. If you have previously signed it, you should be OK.

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

GitHub Java Weekly Trending Repositories

google/guava

Guava: Google Core Libraries for Java

Adding Guava to your build

Snapshots and Documentation

Learn about Guava

Links

IMPORTANT WARNINGS

dbeaver/dbeaver

DBeaver

Download

Running

Documentation

Architecture

Supported databases

Community version

PRO versions

Feedback

Contribution: help the Beaver!

NationalSecurityAgency/ghidra

Ghidra Software Reverse Engineering Framework

Security Warning

Install

Build

Install build tools:

Download and extract the source:

Download additional build dependencies into source repository:

Create development build:

Develop

User Scripts and Extensions

Advanced Development

Install build and development tools:

Prepare the development environment:

Import Ghidra projects into Eclipse:

Contribute

spring-projects/spring-framework

Spring Framework

Code of Conduct

Access to Binaries

Documentation

Micro-Benchmarks

Build from Source

Continuous Integration Builds

Stay in Touch

License

termux/termux-app

Termux application

Contents

Termux App and Plugins

Installation

F-Droid

GitHub

Google Play Store (Experimental branch)

Uninstallation

Important Links

Community

Wikis

Miscellaneous

Terminal

Terminal resources

Terminal emulators

Debugging

Log Levels

For Maintainers and Contributors

Commit Messages Guidelines

Forking

Sponsors and Funders

TheAlgorithms/Java

The Algorithms - Java

All algorithms are implemented in Java (for educational purposes)

Contribution Guidelines

Algorithms

ashishps1/awesome-system-design-resources

Awesome System Design Resources

⚙️ Core Concepts

🌐 Networking Fundamentals

🔌 API Fundamentals

🗄️ Database Fundamentals

⚡ Caching Fundamentals

🔄 Asynchronous Communication