GitHub Java Weekly Trending

jeecgboot/JeecgBoot

AI低代码平台，支持「低代码 + 零代码」双模式：零代码 5 分钟搭建业务系统，低代码模式一键生成前后端代码。内置AI 应用，支持AI聊天、知识库、流程编排、MCP与插件，支持各种模型。Skills能力实现：一句话画流程图、设计表单、生成系统。引领 AI生成→在线配置→代码生成→手工合并的开发模式，解决Java项目80%的重复工作，快速提高效率，又不失灵活性。

中文 | English | 日本語

JeecgBoot AI低代码平台

当前最新版本： 3.9.2（2026-04-30）

🔥 AI Skills 自然语言编程全新发布 — 一句话生成完整代码、一句话画流程、一句话设计表单、一句话出报表与大屏，覆盖 JeecgBoot 低代码全场景。

📦 Skills 开源仓库：https://github.com/jeecgboot/skills ｜ 🌐 Skills 官网：https://jeecg.com/skills ｜ 📺 实战视频

项目介绍

企业级AI低代码平台

JeecgBoot 是一款 AI 低代码开发平台，支持 "低代码 + 零代码" 双模式。零代码模式下，5 分钟零代码快速搭建完整业务系统；低代码模式下，AI 自动输出前后端代码、建表 SQL 与菜单权限，生成即可运行。平台内置 AI 应用平台：AI 聊天助手、知识库、流程编排、MCP、插件，兼容各大模型！具备 Skills 能力，一句话画流程图、设计表单、甚至生成整个系统！引领AI低代码开发模式： "AI 生成 → 在线配置 → 代码生成 → 手工合并"，帮助解决 Java 项目中 80% 的重复工作，让开发更多关注业务，在大幅提升效率的同时又不失灵活性。

采用最新的前后端分离技术栈（Ant Design&Vue3，SpringBoot3，SpringCloud Alibaba，Mybatis-plus，具备强大且颗粒化的权限控制，支持按钮权限和数据权限设置，满足大型业务系统需求。功能涵盖在线表单、表单设计、流程设计、门户设计、报表与大屏设计、OA办公、AI应用、AI知识库、大模型管理、AI流程编排、AI聊天，支持ChatGPT、DeepSeek、Ollama等多种AI大模型。

零代码能力: 国内首个“低代码+零代码”双模驱动的AI低代码平台！同时支持低代码和零代码; 让开发者用低代码，让业务人员在同一个平台上用零代码！
Skills能力: 全面支持skills能力，支持一句话生成完整系统，提供零代码模式（一句话搭建系统，无需编写代码）和代码生成模式（基于 jeecg-codegen，自动生成完整代码和建表SQL）两种选择。同时支持一句话自动绘制流程图、设计表单，省去手工绘制繁琐步骤。
AI智能报表: JimuReport是一款自主研发的强大开源企业级Web报表工具。它通过零编码的拖拽式操作，赋能用户如同搭积木般轻松构建各类复杂报表，全面满足企业数据可视化与分析需求，助力企业级数据产品的高效打造与应用。
AI智能大屏: JimuBI一款自主研发的强大的大屏和仪表盘设计工具。专注数字孪生与数据可视化，支持交互式大屏、仪表盘、门户和移动端，实现“一次开发，多端适配”。大屏设计类Word风格，支持多屏切换，自由拖拽，轻松打造炫酷动态界面。
AI应用平台: 盖AI应用管理、AI模型管理、智能对话助手、知识库问答、流程编排与设计器、AI建表、MCP插件配置等功能。平台兼容主流大模型，包括ChatGPT、DeepSeek、Ollama、智普、千问等，助力企业高效构建智能化应用，推动低代码开发与AI深度融合。
JEECG宗旨是: JEECG旨在通过OnlineCoding平台实现简单功能的零代码快速搭建，同时针对复杂功能采用代码生成器生成代码并手工合并，打造智能且灵活的低代码开发模式，有效解决了当前低代码产品普遍缺乏灵活性的问题，提升开发效率的同时兼顾系统的扩展性和定制化能力。
JEECG业务流程: JEECG业务流程采用BPM工作流引擎实现业务审批，扩展任务接口供开发人员编写业务逻辑，表单提供表单设计器、在线配置表单和编码表单等多种解决方案。通过流程与表单的分离设计（松耦合）及任务节点的灵活配置，既保障了企业流程的安全性与保密性，又大幅降低了开发人员的工作量。

🔥 AI Skills 重磅能力（自然语言编程）

JeecgBoot 全新推出 AI Skills 自然语言编程——结合 Claude Code，一句话即可生成完整系统，把"想到 → 做到"压缩到一句话之间。

🚀 一站式入口

入口	地址
📦 Skills 开源仓库	https://github.com/jeecgboot/skills
🌐 Skills 官网首页	https://jeecg.com/skills
📺 实战视频教程	JeecgBoot + Skills 自然语言编程
📖 官方使用文档	Skills 技能清单详细说明

两种开发模式，灵活选择：

模式	说明
零代码模式	一句话即可搭建系统，无需编写任何代码
代码生成模式	基于 jeecg-codegen，自动生成完整代码和建表 SQL

Skills 能干什么：

✅ 一句话生成全套 CRUD 代码（前后端 + SQL + 菜单权限）
✅ 一句话创建 Online 表单 / Online 报表 / 设计器表单
✅ 一句话画流程图（BPMN）、画大屏、画仪表盘
✅ 一句话生成积木报表、知识漫画、门户、简流……

AI Skills 技能清单

结合 Claude Code 的 AI Skills 技能，JeecgBoot 实现了自然语言驱动的低代码开发，一句话即可完成从需求到代码/配置的全流程自动化。

👉 Skills 仓库 ｜ Skills 官网 ｜详细文档

Skill	技能	功能介绍	是否需要写代码
`jeecg-codegen`	AI一句话生成全套代码	自然语言需求自动转换为 JeecgBoot 全套 CRUD 代码，包括后端 Java 代码 + 前端 Vue3 代码 + 建表 SQL + 菜单权限 SQL，支持无表生成，甚至生成一套系统全代码	否（AI 自动生成源码）
`jeecg-onlform`	AI一句话创建 Online 表单	自然语言需求自动转换为 JeecgBoot Online 表单，完成从表单配置 → 同步数据库 → 生成菜单 SQL 的全流程自动化	否
`jeecg-onlreport`	AI一句话创建 Online 报表	将自然语言需求自动转换为 JeecgBoot Online 报表，完成从 SQL 编写 → 字段解析 → 报表配置 → 创建报表的全流程自动化	否
`jeecg-desform`	AI一句话画表单	自然语言的表单需求描述自动转换为 JeecgBoot 的设计器表单，完成从需求解析 → JSON 生成 → API 创建的全流程自动化，甚至可以创建一套系统	否
`jeecg-bpmn`	AI一句话画流程	将自然语言的审批流程描述自动转换为 Flowable BPMN 2.0 XML，并通过 API 在 JeecgBoot 系统中自动创建流程	否

适用项目

JeecgBoot低代码平台兼容所有J2EE项目开发，支持信创国产化，特别适用于SAAS、企业信息管理系统（MIS）、内部办公系统（OA）、企业资源计划系统（ERP）、客户关系管理系统（CRM）及AI知识库等场景。其半智能手工Merge开发模式，可显著提升70%以上的开发效率，极大降低开发成本。同时，JeecgBoot还是一款全栈式AI开发平台，助力企业快速构建和部署个性化AI应用。。

信创兼容说明

操作系统：国产麒麟、银河麒麟等国产系统几乎都是基于 Linux 内核，因此它们具有良好的兼容性。
数据库：达梦、人大金仓、TiDB
中间件：东方通 TongWeb、TongRDS，宝兰德 AppServer、CacheDB, 信创配置文档

版本说明

下载	SpringBoot3.5 + Shiro	SpringBoot3.5+ SpringAuthorizationServer	SpringBoot3.5 + Sa-Token	SpringBoot2.7(JDK17/JDK8)
Github	`main`	`springboot3_sas` 分支	`springboot3-satoken` 分支	`springboot2` 分支
Gitee	`main`	`springboot3_sas` 分支	`springboot3-satoken` 分支	`springboot2` 分支

jeecg-boot 是后端JAVA源码项目Springboot3+Shiro+Mybatis+SpringCloudAlibaba（支持单体和微服务切换）.
jeecgboot-vue3 是前端VUE3源码项目（vue3+vite6+ts最新技术栈）.
JeecgUniapp 是配套APP框架适配多个终端，支持APP、小程序、H5、鸿蒙、鸿蒙Next.
jeecg-boot-starter 是jeecg-boot对应的底层封装starter ：微服务启动、xxljob、分布式锁starter、rabbitmq、分布式事务、分库分表shardingsphere等.
参考文档可以删除不需要的demo，制作一个精简版本

启动项目

默认账号密码： admin/123456

技术文档

在线演示：平台演示 | APP演示
官方网站： http://www.jeecg.com
入门指南：快速入门 | 开发文档 | AI应用手册 | 视频教程
技术支持：反馈问题 | 低代码体验一分钟
QQ交流群： 964611995、⑩716488839(满)、⑨808791225(满)、其他(满)

AI 应用平台介绍

一个全栈式 AI 开发平台，旨在帮助开发者快速构建和部署个性化的 AI 应用。

JeecgBoot平台提供了一套完善的AI应用管理系统模块，是一套类似Dify的AIGC应用开发平台+知识库问答，是一款基于LLM大语言模型AI应用平台和 RAG 的知识库问答系统。其直观的界面结合了 AI 流程编排、RAG 管道、知识库管理、模型管理、对接向量库、实时运行可观察等，让您可以快速从原型到生产，拥有AI服务能力。

详细专题介绍，请点击查看
AI视频介绍

为什么选择JeecgBoot?

界内首款AI低代码开发平台，同时具备AI应用平台和低代码平台，通过AI驱动低代码开发！开源界"小普元"超越传统商业平台。引领低代码开发模式(OnlineCoding-> 代码生成器 -> 手工MERGE)，低代码开发同时又支持灵活编码，可以帮助解决Java项目70%的重复工作，让开发更多关注业务。既能快速提高开发效率，节省成本，同时又不失灵活性。

1.提供了一套完善的AI应用管理系统模块，是一套类似Dify的AIGC应用开发平台+知识库问答，是一款基于LLM大语言模型AI应用平台和 RAG 的知识库问答系统。其直观的界面结合了 AI 流程编排、RAG 管道、知识库管理、模型管理、对接向量库、实时运行可观察等，让您可以快速从原型到生产，拥有AI服务能力
2.采用最新主流前后分离框架（Spring Boot3 + MyBatisPlus + Vue3.0 + TypeScript + Vite6 + Ant Design Vue4 ）等新技术方案。便于学习容易上手，代码生成器依赖性低，灵活的扩展能力，可快速实现二次开发。
3.支持微服务Spring Cloud Alibaba（Nacos、Gateway、Sentinel、Skywalking），提供简易机制，支持单体和微服务自由切换（这样可以满足各类项目需求）。
4.开发效率高，支持在线建表和AI建表，提供强大代码生成器，单表、树列表、一对多、一对一等数据模型，增删改查功能一键生成，菜单配置直接使用。
5.代码生成器提供强大模板机制，支持自定义模板，目前提供四套风格模板（单表两套、树模型一套、一对多三套）。
6.提供强大的报表和大屏可视化工具，支持丰富的数据源连接，能够通过拖拉拽方式快速制作报表、大屏和门户设计；支持多种图表类型：柱形图、折线图、散点图、饼图、环形图、面积图、漏斗图、进度图、仪表盘、雷达图、地图等。
7.低代码能力：在线表单（无需编码，通过在线配置表单，实现表单的增删改查，支持单表、树、一对多、一对一等模型，实现人人皆可编码），在线配置零代码开发、所见即所得支持23种类控件。
8.低代码能力：在线报表、在线图表（无需编码，通过在线配置方式，实现数据报表和图形报表，可以快速抽取数据，减轻开发压力，实现人人皆可编码）。
9.Online支持在线增强开发，提供在线代码编辑器，支持代码高亮、代码提示等功能，支持多种语言（Java、SQL、JavaScript等）。
10.封装完善的用户、角色、菜单、组织机构、数据字典、在线定时任务等基础功能，支持访问授权、按钮权限、数据权限等功能。
11.前端UI提供丰富的组件库，支持各种常用组件，如表格、树形控件、下拉框、日期选择器等，满足各种复杂的业务需求 UI组件库文档。
12.提供APP配套框架，一份多代码多终端适配，一份代码多终端适配，小程序、H5、安卓、iOS、鸿蒙Next。
13.新版APP框架采用Uniapp、Vue3.0、Vite、Wot-design-uni、TypeScript等最新技术栈，包括二次封装组件、路由拦截、请求拦截等功能。实现了与JeecgBoot完美对接：目前已经实现登录、用户信息、通讯录、公告、移动首页、九宫格、聊天、Online表单、仪表盘等功能，提供了丰富的组件。
14.提供了一套成熟的AI应用平台功能，从AI模型、知识库到AI应用搭建，助力企业快速落地AI服务，加速智能化升级。
15.AI能力：目前JeecgBoot支持AI大模型chatgpt和deepseek，现在最新版默认使用deepseek，速度更快质量更高。目前提供了AI对话助手、AI知识库、AI应用、AI建表、AI报表等功能。
16.提供新行编辑表格JVXETable，轻松满足各种复杂ERP布局，拥有更高的性能、更灵活的扩展、更强大的功能。
17.平台首页风格，提供多种组合模式，支持自定义风格；支持门户设计，支持自定义首页。
18.常用共通封装，各种工具类（定时任务、短信接口、邮件发送、Excel导入导出等），基本满足80%项目需求。
19.简易Excel导入导出，支持单表导出和一对多表模式导出，生成的代码自带导入导出功能。
20.集成智能报表工具，报表打印、图像报表和数据导出非常方便，可极其方便地生成PDF、Excel、Word等报表。
21.采用前后分离技术，页面UI风格精美，针对常用组件做了封装：时间、行表格控件、截取显示控件、报表组件、编辑器等。
22.查询过滤器：查询功能自动生成，后台动态拼SQL追加查询条件；支持多种匹配方式（全匹配/模糊查询/包含查询/不匹配查询）。
23.数据权限（精细化数据权限控制，控制到行级、列表级、表单字段级，实现不同人看不同数据，不同人对同一个页面操作不同字段）。
24.接口安全机制，可细化控制接口授权，非常简便实现不同客户端只看自己数据等控制；也提供了基于AK和SK认证鉴权的OpenAPI功能。
25.活跃的社区支持；近年来，随着网络威胁的日益增加，团队在安全和漏洞管理方面积累了丰富的经验，能够为企业提供全面的安全解决方案。
26.权限控制采用RBAC（Role-Based Access Control，基于角色的访问控制）。
27.页面校验自动生成（必须输入、数字校验、金额校验、时间空间等）。
28.支持SaaS服务模式，提供SaaS多租户架构方案。
29.分布式文件服务，集成MinIO、阿里OSS等优秀的第三方，提供便捷的文件上传与管理，同时也支持本地存储。
30.主流数据库兼容，一套代码完全兼容MySQL、PostgreSQL、Oracle、SQL Server、MariaDB、达梦、人大金仓等主流数据库。
31.集成工作流Flowable，并实现了只需在页面配置流程转向，可极大简化BPM工作流的开发；用BPM的流程设计器画出了流程走向，一个工作流基本就完成了，只需写很少量的Java代码。
32.低代码能力：在线流程设计，采用开源Flowable流程引擎，实现在线画流程、自定义表单、表单挂靠、业务流转。
33.多数据源：极其简易的使用方式，在线配置数据源配置，便捷地从其他数据抓取数据。
34.提供单点登录CAS集成方案，项目中已经提供完善的对接代码。
35.低代码能力：表单设计器，支持用户自定义表单布局，支持单表、一对多表单，支持select、radio、checkbox、textarea、date、popup、列表、宏等控件。
36.专业接口对接机制，统一采用RESTful接口方式，集成Swagger-UI在线接口文档，JWT token安全验证，方便客户端对接。
37.高级组合查询功能，在线配置支持主子表关联查询，可保存查询历史。
38.提供各种系统监控，实时跟踪系统运行情况（监控Redis、Tomcat、JVM、服务器信息、请求追踪、SQL监控）。
39.消息中心（支持短信、邮件、微信推送等）；集成WebSocket消息通知机制。
40.支持多语言，提供国际化方案。
41.数据变更记录日志，可记录数据每次变更内容，通过版本对比功能查看历史变化。
42.提供简单易用的打印插件，支持谷歌、火狐、IE11+等各种浏览器。
43.后端采用Maven分模块开发方式；前端支持菜单动态路由。
44.提供丰富的示例代码，涵盖了常用的业务场景，便于学习和参考。

技术架构

前端

前端环境要求：Node.js要求Node 20+ 版本以上、pnpm 要求9+ 版本以上

( Vite 不再支持已结束生命周期（EOL）的 Node.js 18。现在需要使用 Node.js 20.19+ 或 22.12+)

依赖管理：node、npm、pnpm
前端IDE建议：IDEA、WebStorm、Vscode
采用 Vue3.0+TypeScript+Vite6+Ant-Design-Vue4等新技术方案，包括二次封装组件、utils、hooks、动态菜单、权限校验、按钮级别权限控制等功能
最新技术栈：Vue3.0 + TypeScript + Vite6 + ant-design-vue4 + pinia + echarts + unocss + vxe-table + qiankun + es6

后端

IDE建议： IDEA (必须安装lombok插件 )
语言：Java 默认jdk17(jdk21、jdk24)
依赖管理：Maven
基础框架：Spring Boot 3.5.5
微服务框架： Spring Cloud Alibaba 2023.0.3.3
持久层框架：MybatisPlus 3.5.12
报表工具： JimuReport 2.1.3
安全框架：Apache Shiro 2.0.4，Jwt 4.5.0
微服务技术栈：Spring Cloud Alibaba、Nacos、Gateway、Sentinel、Skywalking
数据库连接池：阿里巴巴Druid 1.2.24
AI大模型：支持 ChatGPT DeepSeek 千问等各种常规模式
日志打印：logback
缓存：Redis
其他：autopoi, fastjson，poi，Swagger-ui，quartz, lombok（简化代码）等。
默认提供MySQL5.7+数据库脚本

数据库支持

jeecgboot平台支持以下数据库，默认我们只提供mysql脚本，其他数据库可以参考转库文档自己转。

数据库	支持
MySQL	√
Oracle11g	√
Sqlserver2017	√
PostgreSQL	√
MariaDB	√
达梦	√
人大金仓	√
TiDB	√
kingbase8	√

微服务解决方案

1、服务注册和发现 Nacos √
2、统一配置中心 Nacos √
3、路由网关 gateway(三种加载方式) √
4、分布式 http feign √
5、熔断降级限流 Sentinel √
6、分布式文件 Minio、阿里OSS √
7、统一权限控制 JWT + Shiro √
8、服务监控 SpringBootAdmin√
9、链路跟踪 Skywalking 参考文档
10、消息中间件 RabbitMQ √
11、分布式任务 xxl-job √
12、分布式事务 Seata
13、轻量分布式日志 Loki+grafana套件
14、支持 docker-compose、k8s、jenkins
15、CAS 单点登录 √
16、路由限流 √

功能清单

├─AI应用平台
│  ├─AI模型管理
│  ├─AI应用管理
│  ├─AI知识库
│  ├─AI流程编排
│  ├─AI聊天助手(支持图片、文件)
│  ├─AI聊天助手支持嵌入第三方、支持移动端
│  ├─MCP插件管理
│  ├─提示词管理
│  ├─支持各种常见模型ChatGPT和DeepSeek、ollama等
├─AI应用门户
│  ├─ Chat2BI 图表生成智能体
│  ├─ AI绘图智能体
│  ├─ 看图说话
│  ├─ 图像识别
│  ├─ 帮我写作
├─工具箱
│  ├─OCR识别
│  ├─AI 海报
│  ├─AI 写作
│  ├─AI 简历
├─AI辅助功能
│  ├─AI建表（Online表单）
│  ├─AI生成报表（Online报表）
│  ├─AI生成大屏
├─系统管理
│  ├─用户管理
│  ├─角色管理
│  ├─菜单管理
│  ├─首页配置
│  ├─权限设置（支持按钮权限、数据权限）
│  ├─表单权限（控制字段禁用、隐藏）
│  ├─部门管理
│  ├─我的部门（二级管理员）
│  └─字典管理
│  └─分类字典
│  └─系统公告
│  └─职务管理
│  └─通讯录
│  ├─多数据源管理
│  ├─白名单管理
│  ├─第三方配置（对接钉钉和企业微信）
│  └─多租户管理（租户管理、租户角色、我的租户、租户默认套餐管理）
├─Online在线开发(低代码)
│  ├─Online在线表单
│  ├─Online代码生成器
│  ├─Online在线报表
│  ├─仪表盘设计器
│  ├─系统编码规则
│  ├─系统校验规则
│  ├─APP版本管理
├─数据可视化
│  ├─报表设计器(支持打印设计）
│  ├─大屏设和仪表盘设计
├─OpenAPI（基于AK和SK认证鉴权）
│  ├─接口管理
│  ├─接口授权
│  ├─接口文档
├─消息中心
│  ├─消息管理
│  ├─模板管理
├─代码生成器(低代码)
│  ├─代码生成器功能（一键生成前后端代码，生成后无需修改直接用，绝对是后端开发福音）
│  ├─代码生成器模板（提供4套模板，分别支持单表和一对多模型，不同风格选择）
│  ├─代码生成器模板（生成代码，自带excel导入导出）
│  ├─查询过滤器（查询逻辑无需编码，系统根据页面配置自动生成）
│  ├─高级查询器（弹窗自动组合查询条件）
│  ├─Excel导入导出工具集成（支持单表，一对多 导入导出）
│  ├─平台移动自适应支持
│  ├─提供新版uniapp3的代码生成器模板
├─系统监控
│  ├─Gateway路由网关
│  ├─基于AK和SK认证鉴权OpenAPI功能
│  ├─定时任务
│  ├─数据源管理
│  ├─性能扫描监控
│  │  ├─监控 Redis
│  │  ├─Tomcat
│  │  ├─jvm
│  │  ├─服务器信息
│  │  ├─请求追踪
│  │  ├─磁盘监控
│  ├─系统日志
│  ├─消息中心（支持短信、邮件、微信推送等等）
│  ├─数据日志（记录数据快照，可对比快照，查看数据变更情况）
│  ├─SQL监控
│  ├─在线用户
│─报表示例
│  ├─曲线图
│  └─饼状图
│  └─柱状图
│  └─折线图
│  └─面积图
│  └─雷达图
│  └─仪表图
│  └─进度条
│  └─排名列表
│  └─等等
│─大屏模板
│  ├─作战指挥中心大屏
│  └─物流服务中心大屏
│─常用示例
│  ├─自定义组件
│  ├─对象存储(对接阿里云)
│  ├─JVXETable示例（各种复杂ERP布局示例）
│  ├─单表模型例子
│  └─一对多模型例子
│  └─打印例子
│  └─一对多TAB例子
│  └─内嵌table例子
│  └─常用选择组件
│  └─异步树table
│  └─接口模拟测试
│  └─表格合计示例
│  └─异步树列表示例
│  └─一对多JEditable
│  └─JEditable组件示例
│  └─图片拖拽排序
│  └─图片翻页
│  └─图片预览
│  └─PDF预览
│  └─分屏功能
│─封装通用组件	
│  ├─行编辑表格JEditableTable
│  └─省略显示组件
│  └─时间控件
│  └─高级查询
│  └─用户选择组件
│  └─报表组件封装
│  └─字典组件
│  └─下拉多选组件
│  └─选人组件
│  └─选部门组件
│  └─通过部门选人组件
│  └─封装曲线、柱状图、饼状图、折线图等等报表的组件（经过封装，使用简单）
│  └─在线code编辑器
│  └─上传文件组件
│  └─验证码组件
│  └─树列表组件
│  └─表单禁用组件
│  └─等等
│─更多页面模板
│  ├─各种高级表单
│  ├─各种列表效果
│  └─结果页面
│  └─异常页面
│  └─个人页面
├─高级功能
│  ├─提供单点登录CAS集成方案
│  ├─提供APP发布方案
│  ├─集成Websocket消息通知机制
│  ├─支持electron桌面应用打包(支持windows、linux、macOS三大平台)
│  ├─docker容器支持
│  ├─提供移动APP框架及源码（Uniapp3版本）支持H5、小程序、APP、鸿蒙Next
│  ├─提供移动APP低代码设计(Online表单、仪表盘)

系统效果

AI模型与应用管理

AI流程编排

MCP和工具管理

AI知识库（支持各种文档格式，尤其markdown适配很好）

AI工具箱

AI聊天助手

AI绘图

AI写文章

PC端

系统交互

仪表盘设计器

报表设计器

手机端

PAD端

图表示例

在线接口文档

UNIAPP效果

大屏设计器

微服务架构图

Jeecg Boot 产品功能蓝图

系统功能架构图

捐赠

如果觉得还不错，请作者喝杯咖啡吧 ☺

免责声明

JeecgBoot 基于 Apache License 2.0 开源协议发布，在使用本软件前，请仔细阅读以下声明：

按"现状"提供
本软件及其相关文档按"现状"（AS IS）提供，不附带任何明示或暗示的担保，包括但不限于对适销性、特定用途适用性及非侵权性的担保。
使用风险自担
使用者应自行评估本软件是否满足其业务场景，并承担因下载、安装、使用、修改或二次开发本软件而产生的一切风险，包括但不限于数据丢失、业务中断、收益损失及其他任何形式的损害。
责任限制
在适用法律允许的最大范围内，JeecgBoot 的作者、贡献者及相关版权所有者对使用者或任何第三方因使用本软件而遭受的任何直接、间接、偶然、特殊、惩罚性或后果性损害不承担任何责任。
社区倡议
在遵守 Apache License 2.0 的前提下，我们真诚恳请基于本软件的衍生作品避免直接复刻、冒充 JeecgBoot 官方版本，或以与 JeecgBoot 高度相似的名称/品牌对外发布。

凡下载、复制、安装或以任何方式使用本软件的行为，即视为已阅读、理解并同意上述免责声明。

neo4j/neo4j

Graphs for Everyone

Neo4j: Graphs for Everyone

Neo4j is the world’s leading Graph Database. It is a high performance graph store with all the features expected of a mature and robust database, like a friendly query language and ACID transactions. The programmer works with a flexible network structure of nodes and relationships rather than static tables — yet enjoys all the benefits of enterprise-quality database. For many applications, Neo4j offers orders of magnitude performance benefits compared to relational DBs.

Learn more on the Neo4j website.

Using Neo4j

Neo4j is available both as a standalone server, or an embeddable component. You can download or try online.

Extending Neo4j

We encourage experimentation with Neo4j. You can build extensions to Neo4j, develop library or drivers atop the product, or make contributions directly to the product core. You’ll need to sign a Contributor License Agreement in order for us to accept your patches.

Dependencies

Neo4j is built using Apache Maven version 3.8.2 and a recent version of supported VM. Bash and Make are also required. Note that maven needs more memory than the standard configuration, this can be achieved with export MAVEN_OPTS="-Xmx2048m".

macOS users need to have Homebrew installed.

With brew on macOS

brew install maven

Please note that we do not support building Debian packages on macOS.

With apt-get on Ubuntu

sudo apt install maven openjdk-17-jdk

Be sure that the JAVA_HOME environment variable points to /usr/lib/jvm/java-17-openjdk-amd64 (you may have various java versions installed).

Building Neo4j

Before you start running the unit and integration tests in the Neo4j Maven project on a Linux-like system, you should ensure your limit on open files is set to a reasonable value. You can test it with ulimit -n. We recommend you have a limit of at least 40K.

A plain mvn clean install -T1C will only build the individual jar files.
Test execution is, of course, part of the build.
In case you just want the jars, without running tests, this is for you: mvn clean install -DskipTests -T1C.
You may need to increase the memory available to Maven: export MAVEN_OPTS="-Xmx2048m" (try this first if you get build errors).

Running Neo4j

After running a mvn clean install, cd into packaging/standalone/target and extract the version you want, then:

bin/neo4j-admin server start

in the extracted folder to start Neo4j on localhost:7474. On Windows you want to run:

bin\neo4j-admin server start

instead.

Neo4j Desktop

Neo4j Desktop is a convenient way for developers to work with local Neo4j databases.

To install Neo4j Desktop, go to Neo4j Download Center and follow the instructions.

Licensing

Neo4j Community Edition is an open source product licensed under GPLv3.

Neo4j Enterprise Edition includes additional closed-source components not available in this repository and requires a commercial license from Neo4j or one of its affiliates.

Trademark

Neo4j’s trademark policy is available at our trademark policy page.

kestra-io/kestra

Event Driven Orchestration & Scheduling Platform for Mission Critical Applications

Event-Driven Declarative Orchestration Platform

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 that makes both scheduled and event-driven workflows easy. By bringing Infrastructure as Code best practices to data, process, and microservice orchestration, you can build reliable workflows directly from the UI in just a few lines of YAML.

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!

TeamNewPipe/NewPipe

A libre lightweight streaming front-end for Android.

We are rewriting large chunks of the codebase, to bring about a modern and stable NewPipe! You can download nightly builds here.

Please work on the `refactor` branch if you want to contribute new features. The current codebase is in maintenance mode and will only receive bugfixes.

NewPipe

A libre lightweight streaming front-end for Android.

Screenshots • Supported Services • Description • Features • Installation and updates • Contribution • Donate • License

Website • Blog • FAQ • Press

Read this document in other languages: Deutsch, English, Español, Français, हिन्दी, Italiano, 한국어, Português Brasil, Polski, ਪੰਜਾਬੀ , 日本語, Română, Soomaali, Türkçe, 正體中文, অসমীয়া, Српски, العربية

Warning

THIS APP IS IN BETA, SO YOU MAY ENCOUNTER BUGS. IF YOU DO, OPEN AN ISSUE IN OUR GITHUB REPOSITORY BY FILLING OUT THE ISSUE TEMPLATE.

PUTTING NEWPIPE, OR ANY FORK OF IT, INTO THE GOOGLE PLAY STORE VIOLATES THEIR TERMS AND CONDITIONS.

Screenshots

Supported Services

NewPipe currently supports these services:

YouTube (website) and YouTube Music (website) (wiki)
PeerTube (website) and all its instances (open the website to know what that means!) (wiki)
Bandcamp (website) (wiki)
SoundCloud (website) (wiki)
media.ccc.de (website) (wiki)

As you can see, NewPipe supports multiple video and audio services. Though it started off with YouTube, other people have added more services over the years, making NewPipe more and more versatile!

Partially due to circumstance, and partially due to its popularity, YouTube is the best supported out of these services. If you use or are familiar with any of these other services, please help us improve support for them! We're looking for maintainers for SoundCloud and PeerTube.

If you intend to add a new service, please get in touch with us first! Our docs provide more information on how a new service can be added to the app and to the NewPipe Extractor.

Description

NewPipe works by fetching the required data from the official API (e.g. PeerTube) of the service you're using. If the official API is restricted (e.g. YouTube) for our purposes, or is proprietary, the app parses the website or uses an internal API instead. This means that you don't need an account on any service to use NewPipe.

Also, since they are free and open source software, neither the app nor the Extractor use any proprietary libraries or frameworks, such as Google Play Services. This means you can use NewPipe on devices or custom ROMs that do not have Google apps installed.

Features

Watch videos at resolutions up to 4K
Listen to audio in the background, only loading the audio stream to save data
Popup mode (floating player, aka Picture-in-Picture)
Watch live streams
Show/hide subtitles/closed captions
Search videos and audios (on YouTube, you can specify the content language as well)
Enqueue videos (and optionally save them as local playlists)
Show/hide general information about videos (such as description and tags)
Show/hide next/related videos
Show/hide comments
Search videos, audios, channels, playlists and albums
Browse videos and audios within a channel
Subscribe to channels (yes, without logging into any account!)
Get notifications about new videos from channels you're subscribed to
Create and edit channel groups (for easier browsing and management)
Browse video feeds generated from your channel groups
View and search your watch history
Search and watch playlists (these are remote playlists, which means they're fetched from the service you're browsing)
Create and edit local playlists (these are created and saved within the app, and have nothing to do with any service)
Download videos/audios/subtitles (closed captions)
Open in Kodi
Watch/Block age-restricted material

Installation and updates

You can install NewPipe using one of the following methods:

Add our custom repo to F-Droid and install it from there. The instructions are here: https://newpipe.net/FAQ/tutorials/install-add-fdroid-repo/
Download the APK from GitHub Releases, compare the signing key and install it.
Update via F-Droid. This is the slowest method of getting updates, as F-Droid must recognize changes, build the APK itself, sign it, and then push the update to users.
Build a debug APK yourself. This is the fastest way to get new features on your device, but is much more complicated, so we recommend using one of the other methods.
If you're interested in a specific feature or bugfix provided in a Pull Request in this repo, you can also download its APK from within the PR. Read the PR description for instructions. The great thing about PR-specific APKs is that they're installed side-by-side the official app, so you don't have to worry about losing your data or messing anything up.

We recommend method 1 for most users. APKs installed using method 1 or 2 are compatible with each other (meaning that if you installed NewPipe using either method 1 or 2, you can also update NewPipe using the other), but not with those installed using method 3. This is due to the same signing key (ours) being used for 1 and 2, but a different signing key (F-Droid's) being used for 3. Building a debug APK using method 4 excludes a key entirely. Signing keys help ensure that a user isn't tricked into installing a malicious update to an app. When using method 5, each APK is signed with a different random key supplied by GitHub Actions, so you cannot even update it. You will have to backup and restore the app data each time you wish to use a new APK.

In the meanwhile, if you want to switch sources for some reason (e.g. NewPipe's core functionality breaks and F-Droid doesn't have the latest update yet), we recommend following this procedure:

Back up your data via Settings > Backup and Restore > Export Database so you keep your history, subscriptions, and playlists
Uninstall NewPipe
Download the APK from the new source and install it
Import the data from step 1 via Settings > Backup and Restore > Import Database

Note

When you're importing a database into the official app, always make sure that it is the one you exported from the official app. If you import a database exported from an APK other than the official app, it may break things. Such an action is unsupported, and you should only do so when you're absolutely certain you know what you're doing.

APK Info

This is the SHA fingerprint of NewPipe's signing key to verify downloaded APKs which are signed by us. The fingerprint is also available on NewPipe's website. This is relevant for method 2.

CB:84:06:9B:D6:81:16:BA:FA:E5:EE:4E:E5:B0:8A:56:7A:A6:D8:98:40:4E:7C:B1:2F:9E:75:6D:F5:CF:5C:AB

Contribution

Whether you have ideas, translations, design changes, code cleaning, or even major code changes, help is always welcome. The app gets better and better with each contribution, no matter how big or small! If you'd like to get involved, check our contribution notes.

Donate

If you like NewPipe, you're welcome to send a donation. We prefer Liberapay, as it is both open-source and non-profit. For further info on donating to NewPipe, please visit our website.

Privacy Policy

The NewPipe project aims to provide a private, anonymous experience for using web-based media services. Therefore, the app does not collect any data without your consent. NewPipe's privacy policy explains in detail what data is sent and stored when you send a crash report, or leave a comment in our blog. You can find the document here.

License

NewPipe is Free Software: You can use, study, share, and improve it at will. Specifically you can redistribute 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.

opensearch-project/OpenSearch

🔎 Open source distributed and RESTful search engine.

Welcome!

OpenSearch is an open-source, enterprise-grade search and observability suite that brings order to unstructured data at scale.

Project Resources

Code of Conduct

The project's Code of Conduct outlines our expectations for all participants in our community, based on the OpenSearch Code of Conduct. Please contact conduct@opensearch.foundation with any additional questions or comments.

Security

If you discover a potential security issue in this project we ask that you notify OpenSearch Security directly via email to security@opensearch.org. Please do not create a public GitHub issue.

License

This project is licensed under the Apache v2.0 License.

Copyright

Trademark

OpenSearch is a registered trademark of LF Projects, LLC.

OpenSearch includes certain Apache-licensed Elasticsearch code from Elasticsearch B.V. and other source code. Elasticsearch B.V. is not the source of that other source code. ELASTICSEARCH is a registered trademark of Elasticsearch B.V.

thingsboard/thingsboard

Open-source IoT Platform - Device management, data collection, processing and visualization.

Open-source IoT platform for data collection, processing, visualization, and device management.

💡 Get started • 🌐 Website • 📚 Documentation • 📔 Blog • 🔗 LinkedIn

🚀 Installation options

Install ThingsBoard on-premises or use ThingsBoard Cloud.

💡 Getting started with ThingsBoard

Check out our Getting Started guide or watch the video to learn the basics of ThingsBoard and create your first dashboard! You will learn to:

Connect devices to ThingsBoard
Push data from devices to ThingsBoard
Build real-time dashboards
Create a Customer and assign the dashboard with them.
Define thresholds and trigger alarms
Set up notifications via email, SMS, mobile apps, or integrate with third-party services.

✨ Features

Provision and manage devices and assets Provision, monitor and control your IoT entities in secure way using rich server-side APIs. Define relations between your devices, assets, customers or any other entities. Read more ➜	Collect and visualize your data Collect and store telemetry data in scalable and fault-tolerant way. Visualize your data with built-in or custom widgets and flexible dashboards. Share dashboards with your customers. Read more ➜
SCADA Dashboards Monitor and control your industrial processes in real time with SCADA. Use SCADA symbols on dashboards to create and manage any workflow, offering full flexibility to design and oversee operations according to your requirements. Read more ➜	Process and React Define data processing rule chains. Transform and normalize your device data. Raise alarms on incoming telemetry events, attribute updates, device inactivity and user actions. Read more ➜

⚙️ Powerful IoT Rule Engine

ThingsBoard allows you to create complex Rule Chains to process data from your devices and match your application specific use cases.

Read more about Rule Engine ➜

📦 Real-Time IoT Dashboards

ThingsBoard is a scalable, user-friendly, and device-agnostic IoT platform that speeds up time-to-market with powerful built-in solution templates. It enables data collection and analysis from any devices, saving resources on routine tasks and letting you focus on your solution’s unique aspects. See more our Use Cases here.

Smart energy

SCADA swimming pool

Site fleet tracking

Smart farming

Smart metering

Check more of our use cases ➜

🫶 Support

To get support, please visit our GitHub issues page

📄 Licenses

This project is released under Apache 2.0 License

alibaba/spring-ai-alibaba

Agentic AI Framework for Java Developers

Spring AI Alibaba

A production-ready framework for building Agentic, Workflow, and Multi-agent applications.

Agent Framework Docs, Graph Docs, Spring AI, Examples.

Architecture

Spring AI Alibaba Admin is a one-stop Agent platform that supports visualized Agent development, observability, evaluation, and MCP management, etc. It also integrates with open-source low-code platforms like Dify, enabling rapid migration from DSL to Spring AI Alibaba project.

Spring AI Alibaba Agent Framework is an agent development framework that can quickly develop agents with built-in Context Engineering and Human In The Loop support. For scenarios requiring more complex process control, Agent Framework offers built-in workflows like SequentialAgent, ParallelAgent, RoutingAgent, LoopAgent.

Spring AI Alibaba Graph serves as the underlying runtime of the Agent Framework, providing essential capabilities such as persistence, workflow orchestration, and streaming required for long-running stateful agents. Compared to the Agent Framework, users can build more flexible multi-agent workflows based on the Graph API.

Core Features

Multi-Agent Orchestration: Compose multiple agents with built-in patterns including SequentialAgent, ParallelAgent, RoutingAgent, and LoopAgent for complex task execution.
Multimodal Support: ReactAgent with text and media input (image understanding). ReactAgent with tool based image or audio generation.
Voice Agent: WebSocket-based real-time voice agent that supports streaming audio or text input and responds with generated audio.
Context Engineering: Built-in best practices for context engineering policies to improve agent reliability and performance, including human-in-the-loop, context compaction, context editing, model & tool call limit, tool retry, planning, dynamic tool selection.
Graph-based Workflow: Graph based workflow runtime and api for conditional routing, nested graphs, parallel execution, and state management. Export workflows to PlantUML and Mermaid formats.
A2A Support: Agent-to-Agent communication support with Nacos integration, enabling distributed agent coordination and collaboration across services.
Rich Model, Tool and MCP Support: Leveraging core concepts of Spring AI, supports multiple LLM providers (DashScope, OpenAI, etc.), tool calling, and Model Context Protocol (MCP).
One-stop Agent Platform: Build agent in a visualized way, deploy agent without code or export as a standalone java project.

Getting Started

Prerequisites

Requires JDK 17+.
Choose your LLM provider and get the API-KEY.

Quickly Run a ChatBot

There's a ChatBot example provided by the community at examples/chatbot.

Download the code.

git clone --depth=1 https://github.com/alibaba/spring-ai-alibaba.git
cd spring-ai-alibaba

Start the ChatBot.

Before starting, set API-KEY first (visit Aliyun Bailian to get API-KEY):

# this example uses 'spring-ai-alibaba-starter-dashscope', visit https://java2ai.com to learn how to use OpenAI/DeepSeek.
export AI_DASHSCOPE_API_KEY=your-api-key

# Maven installation is optional when using mvnw.
./mvnw -pl examples/chatbot spring-boot:run

Chat with ChatBot.

Open the browser and visit http://localhost:8080/chatui/index.html to chat with the ChatBot.

Chatbot Code Explained

Add dependencies

<dependencies>
  <dependency>
    <groupId>com.alibaba.cloud.ai</groupId>
    <artifactId>spring-ai-alibaba-agent-framework</artifactId>
    <version>1.1.2.0</version>
  </dependency>
  <!-- Assume you are going to use DashScope Model. Refer to docs for how to choose model.-->
  <dependency>
    <groupId>com.alibaba.cloud.ai</groupId>
    <artifactId>spring-ai-alibaba-starter-dashscope</artifactId>
    <version>1.1.2.1</version>
  </dependency>
</dependencies>

Define Chatbot

For more details of how to write a Chatbot, please check the Quick Start on our official website.

📚 Documentation

Overview - High level overview of the framework
Quick Start - Get started with a simple agent
Agent Framework Tutorials - Step by step tutorials
Use Graph API to Build Complex Workflows - In-depth user guide for building multi-agent and workflows
Spring AI Basics - Ai Application basic concepts, including ChatModel, MCP, Tool, Messages, etc.
Chat Memory - Spring AI reference for chat memory repositories and usage

Project Structure

This project consists of several core components:

spring-ai-alibaba-agent-framework: A multi-agent framework designed for building intelligent agents with built-in context engineering best practices.
spring-ai-alibaba-graph: The underlying runtime for Agent Framework. We recommend developers to use Agent Framework but it's totally fine to use the Graph API directly.
spring-ai-alibaba-admin: A one-stop Agent platform that supports visualized Agent development, observability, evaluation, and MCP management, etc.
spring-ai-alibaba-studio: The embedded ui for quickly debugging agent in a visualized way.
spring-boot-starters: Starters integrating Agent Framework with Nacos to provide A2A and dynamic config features.

Spring AI Alibaba Ecosystem

Repository	Description	⭐
Spring AI Alibaba Graph	A low-level orchestration framework and runtime for building, managing, and deploying long-running, stateful agents.
Spring AI Alibaba Admin	Local visualization toolkit for the development of agent applications, supporting project management, runtime visualization, tracing, and agent evaluation.
Spring AI Extensions	Extended implementations for Spring AI core concepts, including DashScopeChatModel, MCP registry, etc.
Spring AI Alibaba Examples	Spring AI Alibaba Examples.
JManus	A Java implementation of Manus built with Spring AI Alibaba, currently used in many applications within Alibaba Group.
DataAgent	A natural language to SQL project based on Spring AI Alibaba, enabling you to query databases directly with natural language without writing complex SQL.
DeepResearch	Deep Research implemented based on spring-ai-alibaba-graph.

Contact Us

Dingtalk Group (钉钉群), search 94405033092 and join.

WeChat Group (微信公众号), scan the QR code below and follow us.

Resources

AI-Native Application Architecture White Paper：Co-authored by 40 frontline engineers and endorsed by 15 industry experts, this 200,000+ word white paper is the first comprehensive guide dedicated to the full DevOps lifecycle of AI-native applications. It systematically breaks down core concepts and key challenges, offering practical problem-solving approaches and architectural insights.

Star History

Made with ❤️ by the Spring AI Alibaba Team

spring-projects/spring-ai

An Application Framework for AI Engineering

Spring AI

Spring Boot Version Compatibility

Spring AI 2.x.x (main branch) - Spring Boot 4.x

Spring AI 1.1.x (1.1.x branch) - Spring Boot 3.5.x

The Spring AI project provides a Spring-friendly API and abstractions for developing AI applications.

Its goal is to apply to the AI domain Spring ecosystem design principles such as portability and modular design and promote using POJOs as the building blocks of an application to the AI domain.

At its core, Spring AI addresses the fundamental challenge of AI integration: Connecting your enterprise Data and APIs with the AI Models.

The project draws inspiration from notable Python projects, such as LangChain and LlamaIndex, but Spring AI is not a direct port of those projects. The project was founded with the belief that the next wave of Generative AI applications will not be only for Python developers but will be ubiquitous across many programming languages.

You can check out the blog post Why Spring AI for additional motivations.

This is a high level feature overview. You can find more details in the Reference Documentation

Support for all major AI Model providers such as Anthropic, OpenAI, Microsoft, Amazon, Google, and Ollama. Supported model types include:
- Chat Completion
- Embedding
- Text to Image
- Audio Transcription
- Text to Speech
- Moderation
- Latest Models: GPT-5, and other cutting-edge models for advanced AI applications.
Portable API support across AI providers for both synchronous and streaming options. Access to model-specific features is also available.
Structured Outputs - Mapping of AI Model output to POJOs.
Support for all major Vector Database providers such as Apache Cassandra, Azure Vector Search, Chroma, Elasticsearch, Milvus, MongoDB Atlas, MariaDB, Neo4j, Oracle, PostgreSQL/PGVector, Pinecone, Qdrant, Redis, and Weaviate.
Portable API across Vector Store providers, including a novel SQL-like metadata filter API.
Tools/Function Calling - permits the model to request the execution of client-side tools and functions, thereby accessing necessary real-time information as required.
Observability - Provides insights into AI-related operations.
Document injection ETL framework for Data Engineering.
AI Model Evaluation - Utilities to help evaluate generated content and protect against hallucinated response.
ChatClient API - Fluent API for communicating with AI Chat Models, idiomatically similar to the WebClient and RestClient APIs.
Advisors API - Encapsulates recurring Generative AI patterns, transforms data sent to and from Language Models (LLMs), and provides portability across various models and use cases.
Support for Chat Conversation Memory and Retrieval Augmented Generation (RAG).
Spring Boot Auto Configuration and Starters for all AI Models and Vector Stores - use the start.spring.io to select the Model or Vector-store of choice.

Getting Started

Please refer to the Getting Started Guide for instruction on adding your dependencies.

Project Resources

Awesome Spring AI - A curated list of awesome resources, tools, tutorials, and projects for building generative AI applications using Spring AI
Spring AI Examples contains example projects that explain specific features in more detail.
Spring AI Community - A community-driven organization for building Spring-based integrations with AI models, agents, vector databases, and more.

Breaking changes

Refer to the upgrade notes to see how to upgrade to 1.0.0.M1 or higher.

Cloning the repo

This repository contains large model files. To clone it you have to either:

Ignore the large files (won't affect the spring-ai behaviour) : GIT_LFS_SKIP_SMUDGE=1 git clone git@github.com:spring-projects/spring-ai.git.
Or install the Git Large File Storage before cloning the repo.

Building

The project targets and builds artifacts compatible with Java 17+, and requires a JDK with support for the -XDaddTypeAnnotationsToSymbol javac argument, like Liberica 17.0.19+, for nullability checks.

The recommended JDK is specified in the .sdkmanrc file, which can be installed and configured with the SDKMAN! tool:

sdk env install to install the related JDK locally
sdk env to use the related JDK

NOTE: Building Spring AI requires components that depend on your specific CPU architecture (PyTorch for example). MacOS can seamlessly run x86 Java applications on ARM processors using Rosetta, but this will fail when building this project because it tries to download architecture-specific native dependencies. (Note: this is only an issue for building the project, not for consuming the libraries). If you are unsure if you have the correct JDK distribution for your CPU, run the command java -XshowSettings:properties -version 2>&1 | grep os.arch from a fresh terminal to validate that it matches your machine.

To build with running unit tests

./mvnw clean package

To build including integration tests.

./mvnw clean verify -Pintegration-tests

Note that you should set API key environment variables for OpenAI or other model providers before running. If the API key isn't set for a specific model provider, the integration test is skipped.

To run a specific integration test allowing for up to two attempts to succeed. This is useful when a hosted service is not reliable or times out.

./mvnw -pl vector-stores/spring-ai-pgvector-store -am -Pintegration-tests -Dfailsafe.failIfNoSpecifiedTests=false -Dfailsafe.rerunFailingTestsCount=2 -Dit.test=PgVectorStoreIT verify

Integration Tests

There are many integration tests, so it often isn't realistic to run them all at once.

A quick pass through the most important pathways that runs integration tests for

OpenAI models
OpenAI autoconfiguration
PGVector
Chroma

can be done with the profile -Pci-fast-integration-tests and is used in the main CI build of this project.

A full integration test is done twice a day in the Spring AI Integration Test Repository

One way to run integration tests on part of the code is to first do a quick compile and install of the project

./mvnw clean install -DskipTests -Dmaven.javadoc.skip=true

Then run the integration test for a specific module using the -pl option

./mvnw verify -Pintegration-tests -pl spring-ai-spring-boot-testcontainers

Documentation

To build the docs

./mvnw -pl spring-ai-docs antora

The docs are then in the directory spring-ai-docs/target/antora/site/index.html

Formatting the Source Code

The code is formatted using the java-format plugin as part of the build. Correct formatting is enforced by CI.

Updating License Headers

To update the year on license headers using the license-maven-plugin

./mvnw license:update-file-header -Plicense

Javadocs

To check javadocs using the javadoc:javadoc

./mvnw javadoc:javadoc

Source Code Style

Spring AI source code checkstyle tries to follow the checkstyle guidelines used by the core Spring Framework project with some exceptions. The wiki pages Code Style and IntelliJ IDEA Editor Settings define the source file coding standards we use along with some IDEA editor settings we customize.

Run checkstyle manually:

./mvnw process-sources -P checkstyle-check

Contributing

Your contributions are always welcome! Please read the contribution guidelines first.

MojoLauncher/MojoLauncher

A Minecraft: Java Edition launcher, based on PojavLauncher

MojoLauncher

Readme на русском

MojoLauncher is a launcher, based on PojavLauncher, that allows you to play Minecraft: Java Edition on your Android device!
It can run almost every version of Minecraft, allowing you to use .jar only installers to install modloaders such as Forge and Fabric and mods like OptiFine.

Navigation

Introduction

MojoLauncher is a Minecraft: Java Edition launcher for Android based on PojavLauncher
This launcher can launch almost all available Minecraft versions ranging from rd-132211 to 1.21 snapshots (including Combat Test versions).
Modding via Forge and Fabric are also supported.

Getting MojoLauncher

You can get MojoLauncher via three methods:

You can get the prebuilt app from automatic builds.
You can get it from Google Play by clicking on this badge:
You can build from source.

Building

Build the launcher (it will automatically download all required components)

./gradlew :app_pojavlauncher:assembleDebug

(Replace ./gradlew with .\gradlew.bat if you are building on Windows).

Current roadmap

Known Issues

Some physical mice may have very slow mouse speed
On Holy GL4ES, large texture atlases may be distorted (resulting in stretched/blocky textures in modpacks)
Probably more, that's why we have a bug tracker 😉

License

MojoLauncher is licensed under GNU LGPLv3.

Contributing

Contributions are welcome! We welcome any type of contribution, not only code. For example, you can help the wiki shape up. You can help the translation too!

Any code change to this repository should be submitted as a pull request. The description should explain what the code does and give steps to execute it.

Credits & Third party components and their licenses (if available)

PojavLauncher: GNU LGPLv3 License
Boardwalk (JVM Launcher): Unknown License/Apache License 2.0 or GNU GPLv2.
Android Support Libraries: Apache License 2.0.
GL4ES: MIT License.
OpenJDK: GNU GPLv2 License.
LWJGL3: BSD-3 License.
Mesa 3D Graphics Library: MIT License.
pro-grade (Java sandboxing security manager): Apache License 2.0.
bhook (Used for exit code trapping): MIT license.
Authlib-Injector (Used for authorisation via ely.by): AGPL-3.0.
alsoft (Audio output library): GNU LIBRARY GENERAL PUBLIC LICENSE and modified PFFFT.
oboe: Apache License 2.0.
Thanks to Mineskin for providing Minecraft avatars.

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)

Warp, built for coding with multiple AI agents

CodePhiliaX/Chat2DB

AI-driven database tool and SQL client, The hottest GUI client, supporting MySQL, Oracle, PostgreSQL, DB2, SQL Server, DB2, SQLite, H2, ClickHouse, and more.

🚀 Zoer is Launching

Powered by Chat2DB Team - AI-powered app builder that creates professional applications in minutes, no coding required

New Open-Source Project from the Chat2DB Team: youClaw

If Chat2DB has been useful to you, we'd appreciate a quick star on youClaw. Early stars help new open-source projects get discovered, attract contributors, and keep us building in public.

1. Intelligent SQL Generation:
Chat2DB Pro supports AI-driven intelligent SQL development to help you write SQL queries faster.

2. Database Management:
Supports more than 10 databases, including MySQL, PostgreSQL, H2, Oracle, SQLServer, SQLite, MariaDB, ClickHouse, DM, Presto, DB2, OceanBase, Hive, KingBase, MongoDB, Redis, Snowflake, and more.

3. Intelligent Report Generation:
Chat2DB Pro supports AI-driven intelligent data reporting to help you generate dashboards faster.

4. Data Structure Synchronization:
Chat2DB Pro supports database table structure synchronization to help you sync database table structures faster.

Feature Comparison

Feature	Community Open Source	Local	Pro
Database Types	16+	Target 100+	Target 100+
Supported AI	Requires AI Configuration	AI ready on installation	AI ready on installation
AI Capabilities	Basic	Varied	Varied
Visual Table Editor	✅	✅	✅
SQL Console	✅	✅	✅
SQL Formatting	✅	✅	✅
Save Query Records	✅	✅	✅
Theme Color Settings	✅	✅	✅
Data Structure Sync	❌	✅	✅
Database Grouping	❌	✅	✅
Database Structure Import/Export	❌	✅	✅
Data Import/Export	❌	✅	✅
Data Migration	❌	✅	✅
Copy/Clear Table	❌	✅	✅
Open and Run SQL Files	❌	✅	✅
UML Diagram	❌	In Development	In Development
Generate Code	❌	✅	✅
Copy Results as Insert/Update	❌	✅	✅
Modify Query Results	❌	✅	✅
Intelligent SQL Editor	❌	✅	✅
AI Table Creation	❌	✅	✅
AI Data Sets	❌	✅	✅
Chat2Excel	❌	✅	✅
Intelligent Dashboard	❌	✅	✅
Editor Settings	❌	✅	✅
Custom Shortcuts	❌	✅	✅
Cross-device Usage	❌	❌	✅

Download and Installation

Chat2DB is a cross-platform application that supports Windows, MacOS, and Linux. You can download Chat2DB from the following links:

Community Edition Docker Installation

System Requirements

Before installing Chat2DB, ensure your system meets the following requirements:

Docker 19.03.0 or later
Docker Compose 1.25.0 or later
CPU >= 2 Cores
RAM >= 4 GiB

  docker rm chat2db
  
  docker run --name=chat2db -ti -p 10824:10824 -v ~/.chat2db-docker:/root/.chat2db  chat2db/chat2db:latest

  docker start chat2db

Code Debugging

Runtime Environment

Note: If local debugging is needed:

Java runtime: Open JDK 17
Node.js runtime: Node 16 Node.js.

Clone the repository locally

$ git clone git@github.com:chat2db/Chat2DB.git

Frontend Debugging

Node version must be 16 or higher  
Use yarn only, npm is not supported
$ cd Chat2DB/chat2db-client
$ yarn
$ yarn run start:web

Backend Debugging

$ cd ../chat2db-server
$ mvn clean install # Maven version 3.8 or higher is required
$ cd chat2db-server/chat2db-server-start/target/
$ java -jar -Dloader.path=./lib -Dchatgpt.apiKey=xxxxx chat2db-server-start.jar  # 需要安装java 17以上版本，启动应用 chatgpt.apiKey 需要输入ChatGPT的key,如果不输入无法使用AIGC功能

Standalone Deployment

# chat2db-client
$ npm run build:web:prod 
$ cp -r dist ../chat2db-server/chat2db-server-start/src/main/resources/static/front 
$ cp -r dist/index.html ../chat2db-server/chat2db-server-start/src/main/resources/thymeleaf

Contact Us

Acknowledgments

Thanks to everyone who has contributed to Chat2DB~~

Star History

License

The primary license used by this software is the Apache License 2.0, supplemented by the Chat2DB License.

camunda/camunda

Process Orchestration Framework

Camunda 8 orchestrates complex business processes that span people, systems, and devices

Camunda 8 delivers scalable, on-demand process automation as a service. Camunda 8 is combined with powerful execution engines for BPMN processes and DMN decisions, and paired with tools for collaborative modeling, operations, and analytics.

This repository contains the Orchestration cluster components of Camunda 8 and Optimize:

Zeebe - The cloud-native process engine of Camunda 8.
Tasklist - Complete tasks that require human input.
Operate - Manage, monitor, and troubleshoot your processes.
Identity - Manage integrated authentication and authorization.
Optimize - Improve your processes by identifying constraints in your system.

In addition, the Camunda 8 stack also includes:

Console - Configure and deploy clusters with Console.
Web Modeler - Web Application to model BPMN, DMN, & Forms and deploy or start new instances.
Desktop Modeler - Use Desktop Modeler as a desktop application for modeling BPMN, DMN, and Forms with your local process application project.
Connectors - Integrate with an external system by using a Connector.
Management Identity - Manage authentication, access, and authorization for components outside the Orchestration cluster (Console, Web Modeler, and Optimize)

Using Camunda 8, you can:

Define processes visually in BPMN 2.0
Choose your programming language
Deploy with Docker and Kubernetes
Build processes that react to messages from Kafka and other message queues
Scale horizontally to handle very high throughput
Fault tolerance (no relational database required)
Export process data for monitoring and analysis
Engage with an active community

Learn more at camunda.com.

Status

To learn more about what we're currently working on, check the GitHub issues and the latest commits.

Helpful Links

Documentation

This repository includes comprehensive documentation in the docs/ directory. The content is served via a Docusaurus site located in monorepo-docs-site/.

Running the Documentation Site

cd monorepo-docs-site
npm install
npm start

The documentation site will be available at http://localhost:3000/camunda/.

Adding Documentation

Add new markdown files to the docs/ directory
Update the sidebar configuration in monorepo-docs-site/sidebars.js to include your new documentation file in the appropriate array position. For example:

// in monorepo-docs-site/sidebars.js
module.exports = {
  docs: [
    'introduction',
    'getting-started',
    // add your new doc ID here
    'your-doc-id',
  ],
};

For more details, see the documentation site README.

Recommended Docs Entries for New Users

Contributing

Read the Contributions Guide.

Code of Conduct

This project adheres to the Camunda Code of Conduct. By participating, you are expected to uphold this code. Please report unacceptable behavior as soon as possible.

Release Lifecycle

Please refer to our Release Policy to learn about our release cadence, maintenance periods, etc.

License

Zeebe, Operate, and Tasklist source files are made available under the Camunda License Version 1.0 except for the parts listed below, which are made available under the Apache License, Version 2.0. See individual source files for details.

Available under the Apache License, Version 2.0:

Java Client (clients/java)
Camunda Spring Boot Starter (camunda-spring-boot-starter)
Exporter API (exporter-api)
Protocol (protocol)
Gateway Protocol Implementation (gateway-protocol-impl)
BPMN Model API (bpmn-model)

Clarification on gRPC Code Generation

The Zeebe Gateway Protocol (API) as published in the gateway-protocol is licensed under the Camunda License 1.0. Using gRPC tooling to generate stubs for the protocol does not constitute creating a derivative work under the Camunda License 1.0 and no licensing restrictions are imposed on the resulting stub code by the Camunda License 1.0.

apache/camel

Apache Camel is an open source integration framework that empowers you to quickly and easily integrate various systems consuming or producing data.

Apache Camel

Apache Camel is an Open Source integration framework that empowers you to quickly and easily integrate various systems consuming or producing data.

Introduction

Camel empowers you to define routing and mediation rules in a variety of domain-specific languages (DSL, such as Java, XML, Groovy and YAML). This means you get smart completion of routing rules in your IDE, whether in a Java or XML editor.

Apache Camel uses URIs to enable easier integration with all kinds of transport or messaging model including HTTP, ActiveMQ, JMS, JBI, SCA, MINA or CXF together with working with pluggable Data Format options. Apache Camel is a small library that has minimal dependencies for easy embedding in any Java application. Apache Camel lets you work with the same API regardless of the transport type, making it possible to interact with all the components provided out-of-the-box, with a good understanding of the API.

Apache Camel has powerful Bean Binding and integrated seamlessly with popular frameworks such as Spring, Quarkus, and CDI.

Apache Camel has extensive testing support allowing you to easily unit test your routes.

Components

Apache Camel comes alongside several artifacts with components, data formats, languages, and kinds. The up-to-date list is available online at the Camel website:

Components: https://camel.apache.org/components/latest/
Data Formats: https://camel.apache.org/components/latest/dataformats/
Languages: https://camel.apache.org/components/latest/languages/
Miscellaneous: https://camel.apache.org/components/latest/#_miscellaneous_components

Examples

Apache Camel comes with many examples. The up to date list is available online at GitHub:

Examples: https://github.com/apache/camel-examples/tree/main#welcome-to-the-apache-camel-examples

Getting Started

To help you get started, try the following links:

Getting Started

https://camel.apache.org/getting-started.html

The beginner examples are another powerful alternative pathway for getting started with Apache Camel.

Examples: https://github.com/apache/camel-examples/tree/main#welcome-to-the-apache-camel-examples

Building

https://camel.apache.org/camel-core/contributing/

Contributions

We welcome all kinds of contributions, the details of which are specified here:

https://github.com/apache/camel/blob/main/CONTRIBUTING.md

Please refer to the website for details of finding the issue tracker, email lists, GitHub, chat

Website: https://camel.apache.org/

GitHub (source): https://github.com/apache/camel

Issue tracker: https://issues.apache.org/jira/projects/CAMEL

Mailing-list: https://camel.apache.org/community/mailing-list/

Chat: https://camel.zulipchat.com/

StackOverflow: https://stackoverflow.com/questions/tagged/apache-camel

Twitter: https://twitter.com/ApacheCamel

Support

For additional help, support, we recommend referencing this page first:

https://camel.apache.org/community/support/

Getting Help

If you get stuck somewhere, please feel free to reach out to us on either StackOverflow, Chat, or the email mailing list.

Please help us make Apache Camel better — we appreciate any feedback you may have.

Enjoy!

The Camel riders!

Licensing

The terms for software licensing are detailed in the LICENSE.txt file,
located in the working directory.

iflytek/astron-agent

Enterprise-grade, commercial-friendly agentic workflow platform for building next-generation SuperAgents.

English | 简体中文

🔭 What is Astron Agent

Astron Agent is an enterprise-grade, commercial-friendly Agentic Workflow development platform that integrates AI workflow orchestration, model management, AI and MCP tool integration, RPA automation, and team collaboration features. The platform supports high-availability deployment, enabling organizations to rapidly build scalable, production-ready intelligent agent applications and establish their AI foundation for the future.

Why Choose Astron Agent?

Stable and Reliable: Built on the same core technology as the iFLYTEK Astron Agent Platform, providing enterprise-grade reliability with a fully available high-availability version open source.
Cross-System Integration: Natively integrates intelligent RPA, efficiently connecting internal and external enterprise systems, enabling seamless interaction between Agents and enterprise systems.
Enterprise-Grade Open Ecosystem: Deeply compatible with various industry models and tools, supporting custom extensions and flexibly adapting to diverse enterprise scenarios.
Business-Friendly: Released under the Apache 2.0 License, with no commercial restrictions, allowing free commercial use.

Key Features

Enterprise-Grade High Availability: Full-stack capabilities for development, building, optimization, and management. Supports one-click deployment with strong reliability.
Intelligent RPA Integration: Enables cross-system process automation, empowering Agents with controllable execution to achieve a complete loop “from decision to action.”
Ready-to-Use Tool Ecosystem: Integrates massive AI capabilities and tools from the iFLYTEK Open Platform, validated by millions of developers, supporting plug-and-play integration without extra development.
Flexible Large Model Support: Offers diverse access methods, from rapid API-based model access and validation to one-click deployment of enterprise-level MaaS (Model as a Service) on-premises clusters, meeting needs of all scales.

📰 News

🔄 Ongoing

📅 Past

Astron Hackathon @ 2025 iFLYTEK Global 1024 Developer Festival 🎤 @mklong
Astron Agent Zhengzhou Meetup 🎤 @lyj715824 @wowo-zZ
Astron on Campus @ Zhejiang University of Finance and Economics 🎤 @lyj715824
Astron Agent & RPA · Qingdao Meetup Brings Agentic AI! 🎤 @vsxd @doctorbruce @MaxwellJean
Astron Training Camp · Cohort #1 🎤 @lyj715824 @Thomas1024-Astron @abelzha
Astron Talk @ Chongqing Mini Tech Fest 🎤 @lyj715824
Astron Agent @ MWC Barcelona 2026
Astron Agent & RPA · Hefei Meetup 🎤 @lyj715824 @doctorbruce
Astron Industrial Intelligence Hackathon 🎤 @lyj715824 @horizon220222

🚀 Quick Start

We offer two deployment methods to meet different scenarios:

Option 1: Docker Compose (Recommended for Quick Start)

# Clone the repository
git clone https://github.com/iflytek/astron-agent.git

# Navigate to the Docker deployment directory
cd docker/astronAgent

# Copy environment configuration
cp .env.example .env

# Configure environment variables
vim .env

For environment variable configuration, please refer to the documentation:DEPLOYMENT_GUIDE_WITH_AUTH.md

# Start all services (including Casdoor)
docker compose -f docker-compose-with-auth.yaml up -d

📊 Service Access Addresses

After startup, you can access the services at the following addresses:

Authentication Service

Casdoor Admin Interface: http://localhost:8000

AstronAgent

Application Frontend (nginx proxy): http://localhost/

Note

Default Casdoor login credentials: username: admin, password: 123

Option 2: Helm (For Kubernetes Environments)

🚧 Note: Helm charts are currently under development. Stay tuned for updates!

# Coming soon
# helm repo add astron-agent https://iflytek.github.io/astron-agent
# helm install astron-agent astron-agent/astron-agent

📖 For complete deployment instructions and configuration details, see Deployment Guide

📖 Using Astron Cloud

Try Astron：Astron Cloud provides a ready-to-use environment for creating and managing Agents. Get quick access at https://agent.xfyun.cn.

Using Guide：For detailed usage instructions, please refer to Quick Start Guide.

📚 Documentation

🤝 Contributing

We welcome contributions of all kinds! Please see our Contributing Guide

🌟 Star History

📞 Support

💬 Community Discussion: GitHub Discussions
🐛 Bug Reports: Issues
👥 WeChat Work Group:

📄 Open Source License

This project is licensed under the Apache 2.0 License, allowing free use, modification, distribution, and commercial use without any restrictions.

skylot/jadx

Dex to Java decompiler

JADX

jadx - Dex to Java decompiler

Command line and GUI tools for producing Java source code from Android Dex and Apk files

Warning

Please note that in most cases jadx can't decompile all 100% of the code, so errors will occur.
Check Troubleshooting guide for workarounds.

Main features:

decompile Dalvik bytecode to Java code from APK, dex, aar, aab and zip files
decode AndroidManifest.xml and other resources from resources.arsc
deobfuscator included

jadx-gui features:

view decompiled code with highlighted syntax
jump to declaration
find usage
full text search
smali debugger, check wiki page for setup and usage

Jadx-gui key bindings can be found here

See these features in action here: jadx-gui features overview

Download

release from github:
latest unstable build

After download unpack zip file go to bin directory and run:

jadx - command line version
jadx-gui - UI version

On Windows run .bat files with double-click
Note: ensure you have installed Java 11 or later 64-bit version. For Windows, you can download it from oracle.com (select x64 Installer).

Install

Arch Linux
```
sudo pacman -S jadx
```
macOS
```
brew install jadx
```

Flathub

flatpak install flathub com.github.skylot.jadx

Use jadx as a library

You can use jadx in your java projects, check details on wiki page

Build from source

JDK 17 or higher must be installed:

git clone https://github.com/skylot/jadx.git
cd jadx
./gradlew dist

(on Windows, use gradlew.bat instead of ./gradlew)

Scripts for run jadx will be placed in build/jadx/bin and also packed to build/jadx-<version>.zip

Usage

jadx[-gui] [command] [options] <input files> (.apk, .dex, .jar, .class, .smali, .zip, .aar, .arsc, .aab, .xapk, .apkm, .jadx.kts)
commands (use '<command> --help' for command options):
  plugins	  - manage jadx plugins

options:
  -d, --output-dir                              - output directory
  -ds, --output-dir-src                         - output directory for sources
  -dr, --output-dir-res                         - output directory for resources
  -r, --no-res                                  - do not decode resources
  -s, --no-src                                  - do not decompile source code
  -j, --threads-count                           - processing threads count, default: 16
  --single-class                                - decompile a single class, full name, raw or alias
  --single-class-output                         - file or dir for write if decompile a single class
  --output-format                               - can be 'java' or 'json', default: java
  -e, --export-gradle                           - save as gradle project (set '--export-gradle-type' to 'auto')
  --export-gradle-type                          - Gradle project template for export:
                                                   'auto' - detect automatically
                                                   'android-app' - Android Application (apk)
                                                   'android-library' - Android Library (aar)
                                                   'simple-java' - simple Java
  -m, --decompilation-mode                      - code output mode:
                                                   'auto' - trying best options (default)
                                                   'restructure' - restore code structure (normal java code)
                                                   'simple' - simplified instructions (linear, with goto's)
                                                   'fallback' - raw instructions without modifications
  --show-bad-code                               - show inconsistent code (incorrectly decompiled)
  --no-xml-pretty-print                         - do not prettify XML
  --no-imports                                  - disable use of imports, always write entire package name
  --no-debug-info                               - disable debug info parsing and processing
  --add-debug-lines                             - add comments with debug line numbers if available
  --no-inline-anonymous                         - disable anonymous classes inline
  --no-inline-methods                           - disable methods inline
  --no-move-inner-classes                       - disable move inner classes into parent
  --no-inline-kotlin-lambda                     - disable inline for Kotlin lambdas
  --no-finally                                  - don't extract finally block
  --no-restore-switch-over-string               - don't restore switch over string
  --no-replace-consts                           - don't replace constant value with matching constant field
  --escape-unicode                              - escape non latin characters in strings (with \u)
  --respect-bytecode-access-modifiers           - don't change original access modifiers
  --mappings-path                               - deobfuscation mappings file or directory. Allowed formats: Tiny and Tiny v2 (both '.tiny'), Enigma (.mapping) or Enigma directory
  --mappings-mode                               - set mode for handling the deobfuscation mapping file:
                                                   'read' - just read, user can always save manually (default)
                                                   'read-and-autosave-every-change' - read and autosave after every change
                                                   'read-and-autosave-before-closing' - read and autosave before exiting the app or closing the project
                                                   'ignore' - don't read or save (can be used to skip loading mapping files referenced in the project file)
  --deobf                                       - activate deobfuscation
  --deobf-min                                   - min length of name, renamed if shorter, default: 3
  --deobf-max                                   - max length of name, renamed if longer, default: 64
  --deobf-whitelist                             - space separated list of classes (full name) and packages (ends with '.*') to exclude from deobfuscation, default: android.support.v4.* android.support.v7.* android.support.v4.os.* android.support.annotation.Px androidx.core.os.* androidx.annotation.Px
  --deobf-cfg-file                              - deobfuscation mappings file used for JADX auto-generated names (in the JOBF file format), default: same dir and name as input file with '.jobf' extension
  --deobf-cfg-file-mode                         - set mode for handling the JADX auto-generated names' deobfuscation map file:
                                                   'read' - read if found, don't save (default)
                                                   'read-or-save' - read if found, save otherwise (don't overwrite)
                                                   'overwrite' - don't read, always save
                                                   'ignore' - don't read and don't save
  --deobf-res-name-source                       - better name source for resources:
                                                   'auto' - automatically select best name (default)
                                                   'resources' - use resources names
                                                   'code' - use R class fields names
  --use-source-name-as-class-name-alias         - use source name as class name alias:
                                                   'always' - always use source name if it's available
                                                   'if-better' - use source name if it seems better than the current one
                                                   'never' - never use source name, even if it's available
  --source-name-repeat-limit                    - allow using source name if it appears less than a limit number, default: 10
  --use-kotlin-methods-for-var-names            - use kotlin intrinsic methods to rename variables, values: disable, apply, apply-and-hide, default: apply
  --use-headers-for-detect-resource-extensions  - Use headers for detect resource extensions if resource obfuscated
  --rename-flags                                - fix options (comma-separated list of):
                                                   'case' - fix case sensitivity issues (according to --fs-case-sensitive option),
                                                   'valid' - rename java identifiers to make them valid,
                                                   'printable' - remove non-printable chars from identifiers,
                                                  or single 'none' - to disable all renames
                                                  or single 'all' - to enable all (default)
  --integer-format                              - how integers are displayed:
                                                   'auto' - automatically select (default)
                                                   'decimal' - use decimal
                                                   'hexadecimal' - use hexadecimal
  --type-update-limit                           - type update limit count (per one instruction), default: 10
  --fs-case-sensitive                           - treat filesystem as case sensitive, false by default
  --cfg                                         - save methods control flow graph to dot file
  --raw-cfg                                     - save methods control flow graph (use raw instructions)
  -f, --fallback                                - set '--decompilation-mode' to 'fallback' (deprecated)
  --use-dx                                      - use dx/d8 to convert java bytecode
  --comments-level                              - set code comments level, values: error, warn, info, debug, user-only, none, default: info
  --log-level                                   - set log level, values: quiet, progress, error, warn, info, debug, default: progress
  -v, --verbose                                 - verbose output (set --log-level to DEBUG)
  -q, --quiet                                   - turn off output (set --log-level to QUIET)
  --disable-plugins                             - comma separated list of plugin ids to disable
  --config <config-ref>                         - load configuration from file, <config-ref> can be:
                                                   path to '.json' file
                                                   short name - uses file with this name from config directory
                                                   'none' - to disable config loading
  --save-config <config-ref>                    - save current options into configuration file and exit, <config-ref> can be:
                                                   empty - for default config
                                                   path to '.json' file
                                                   short name - file will be saved in config directory
  --print-files                                 - print files and directories used by jadx (config, cache, temp)
  --version                                     - print jadx version
  -h, --help                                    - print this help

Plugin options (-P<name>=<value>):
  dex-input: Load .dex and .apk files
    - dex-input.verify-checksum                 - verify dex file checksum before load, values: [yes, no], default: yes
  java-convert: Convert .class, .jar and .aar files to dex
    - java-convert.mode                         - convert mode, values: [dx, d8, both], default: both
    - java-convert.d8-desugar                   - use desugar in d8, values: [yes, no], default: no
  kotlin-metadata: Use kotlin.Metadata annotation for code generation
    - kotlin-metadata.class-alias               - rename class alias, values: [yes, no], default: yes
    - kotlin-metadata.method-args               - rename function arguments, values: [yes, no], default: yes
    - kotlin-metadata.fields                    - rename fields, values: [yes, no], default: yes
    - kotlin-metadata.companion                 - rename companion object, values: [yes, no], default: yes
    - kotlin-metadata.data-class                - add data class modifier, values: [yes, no], default: yes
    - kotlin-metadata.to-string                 - rename fields using toString, values: [yes, no], default: yes
    - kotlin-metadata.getters                   - rename simple getters to field names, values: [yes, no], default: yes
  kotlin-smap: Use kotlin.SourceDebugExtension annotation for rename class alias
    - kotlin-smap.class-alias-source-dbg        - rename class alias from SourceDebugExtension, values: [yes, no], default: no
  rename-mappings: various mappings support
    - rename-mappings.format                    - mapping format, values: [AUTO, TINY_FILE, TINY_2_FILE, ENIGMA_FILE, ENIGMA_DIR, PROGUARD_FILE, SRG_FILE, XSRG_FILE, JAM_FILE, CSRG_FILE, TSRG_FILE, TSRG_2_FILE, INTELLIJ_MIGRATION_MAP_FILE, RECAF_SIMPLE_FILE, JOBF_FILE], default: AUTO
    - rename-mappings.invert                    - invert mapping on load, values: [yes, no], default: no
  smali-input: Load .smali files
    - smali-input.api-level                     - Android API level, default: 27

Environment variables:
  JADX_DISABLE_XML_SECURITY - set to 'true' to disable all security checks for XML files
  JADX_DISABLE_ZIP_SECURITY - set to 'true' to disable all security checks for zip files
  JADX_ZIP_MAX_ENTRIES_COUNT - maximum allowed number of entries in zip files (default: 100 000)
  JADX_CONFIG_DIR - custom config directory, using system by default
  JADX_CACHE_DIR - custom cache directory, using system by default
  JADX_TMP_DIR - custom temp directory, using system by default

Examples:
  jadx -d out classes.dex
  jadx --rename-flags "none" classes.dex
  jadx --rename-flags "valid, printable" classes.dex
  jadx --log-level ERROR app.apk
  jadx -Pdex-input.verify-checksum=no app.apk

These options also work in jadx-gui running from command line and override options from preferences' dialog

Usage for plugins command

usage: plugins [options]
options:
  -i, --install <locationId>      - install plugin with locationId
  -j, --install-jar <path-to.jar> - install plugin from jar file
  -l, --list                      - list installed plugins
  -a, --available                 - list available plugins from jadx-plugins-list (aka marketplace)
  -u, --update                    - update installed plugins
  --uninstall <pluginId>          - uninstall plugin with pluginId
  --disable <pluginId>            - disable plugin with pluginId
  --enable <pluginId>             - enable plugin with pluginId
  --list-all                      - list all plugins including bundled and dropins
  --list-versions <locationId>    - fetch latest versions of plugin from locationId (will download all artefacts, limited to 10)
  -h, --help                      - print this help

Troubleshooting

Please check wiki page Troubleshooting Q&A

Contributing

To support this project you can:

Post thoughts about new features/optimizations that important to you
Submit decompilation issues, please read before proceed: Open issue
Open pull request, please follow these rules: Pull Request Process

Licensed under the Apache 2.0 License

alibaba/nacos

an easy-to-use dynamic service discovery, configuration and service management platform for building AI cloud native applications.

Nacos: Dynamic Naming and Configuration Service

What does it do

Nacos (official site: nacos.io) is an easy-to-use platform designed for dynamic service discovery and configuration and service management. It helps you to build cloud native applications and microservices platform easily.

Service is a first-class citizen in Nacos. Nacos supports almost all type of services，for example，Dubbo/gRPC service, Spring Cloud RESTFul service or Kubernetes service.

Nacos provides four major functions.

Service Discovery and Service Health Check

Nacos makes it simple for services to register themselves and to discover other services via a DNS or HTTP interface. Nacos also provides real-time health checks of services to prevent sending requests to unhealthy hosts or service instances.
Dynamic Configuration Management

Dynamic Configuration Service allows you to manage configurations of all services in a centralized and dynamic manner across all environments. Nacos eliminates the need to redeploy applications and services when configurations are updated, which makes configuration changes more efficient and agile.
Dynamic DNS Service

Nacos supports weighted routing, making it easier for you to implement mid-tier load balancing, flexible routing policies, flow control, and simple DNS resolution services in the production environment within your data center. It helps you to implement DNS-based service discovery easily and prevent applications from coupling to vendor-specific service discovery APIs.
Service and MetaData Management

Nacos provides an easy-to-use service dashboard to help you manage your services metadata, configuration, kubernetes DNS, service health and metrics statistics.

Quick Start

It is super easy to get started with your first project.

Deploying Nacos on cloud

You can deploy Nacos on cloud, which is the easiest and most convenient way to start Nacos.

Use the following Nacos deployment guide to see more information and deploy a stable and out-of-the-box Nacos server.

Start by the provided startup package

Step 1: Download the binary package

You can download the package from the latest stable release.

Take release nacos-server-1.0.0.zip for example:

unzip nacos-server-1.0.0.zip
cd nacos/bin

Step 2: Start Server

On the Linux/Unix/Mac platform, run the following command to start server with standalone mode:

sh startup.sh -m standalone

On the Windows platform, run the following command to start server with standalone mode. Alternatively, you can also double-click the startup.cmd to run NacosServer.

startup.cmd -m standalone

For more details, see quick-start.

Quick start for other open-source projects:

Documentation

You can view the full documentation from the Nacos website.

You can also read this online eBook from the NACOS ARCHITECTURE & PRINCIPLES.

All the latest and long-term notice can also be found here from GitHub notice issue.

Contributing

Contributors are welcomed to join Nacos project. Please check CONTRIBUTING about how to contribute to this project.

How can I contribute?

Take a look at issues with tags marked good first issue or contribution welcome.
Answer questions on issues.
Fix bugs reported on issues, and send us a pull request.
Review the existing pull request.
Improve the website, typically we need
- blog post
- translation on documentation
- use cases around the integration of Nacos in enterprise systems.

Other Related Project Repositories

nacos-spring-project provides the integration functionality for Spring.
nacos-group is the repository that hosts the eco tools for Nacos, such as SDK, synchronization tool, etc.
spring-cloud-alibaba provides the one-stop solution for application development over Alibaba middleware which includes Nacos.

Contact

Gitter: Nacos's IM tool for community messaging, collaboration and discovery.
Twitter: Follow along for latest nacos news on Twitter.
Weibo: Follow along for latest nacos news on Weibo (Twitter of China version).
Nacos Segmentfault: Get latest notice and prompt help from Segmentfault.
Email Group:
- users-nacos@googlegroups.com: Nacos usage general discussion.
- dev-nacos@googlegroups.com: Nacos developer discussion (APIs, feature design, etc).
- commits-nacos@googlegroups.com: Commits notice, very high frequency.
Join us from DingDing(Group 1: 21708933(full), Group 2: 30438813(full), Group 3: 31222241(full), Group 4: 12810027056).

DingDing Group QR Code

DingDing MCP Group QR Code

WeChat Group QR Code

Enterprise Service

If you need Nacos enterprise service support, or purchase cloud product services, you can join the discussion by scanning the following DingTalk group. It can also be directly activated and used through the microservice engine (MSE) provided by Alibaba Cloud. https://cn.aliyun.com/product/aliware/mse?spm=nacos-website.topbar.0.0.0

Download

Who is using

These are only part of the companies using Nacos, for reference only. If you are using Nacos, please add your company here to tell us your scenario to make Nacos better.

















郑州山水	知氏教育

quarkusio/quarkus

Quarkus: Supersonic Subatomic Java.

Quarkus - Supersonic Subatomic Java

Quarkus is a Cloud Native, (Linux) Container First framework for writing Java applications.

Container First: Minimal footprint Java applications optimal for running in containers.
Cloud Native: Embraces 12 factor architecture in environments like Kubernetes.
Versatile: From the smallest microservice to the largest monolith.
Fast startup: We do more at build time, we start fast.
JVM and native JVM for high throughput, native for constrained environments.
Unify imperative and reactive: Brings under one programming model non-blocking and imperative styles of development.
Standards-based: Based on the standards and frameworks you love and use (RESTEasy and JAX-RS, Hibernate ORM and JPA, Netty, Eclipse Vert.x, Eclipse MicroProfile, Apache Camel...).
Developer Joy: Development centric experience without compromise to bring your amazing apps to life in no time.

All under ONE framework.

Getting Started

Migration Guides

We collect all the migration notes in our migration guides.

Release Planning

Interested in when the next release is coming? Check our release planning document for details.

How to build Quarkus

The build instructions are available in the contribution guide.

halo-dev/halo

Halo 是一款强大易用的开源建站工具，从个人博客、知识库，到企业官网、在线商城，Halo 都能助您轻松实现，一站式满足您的多样化建站需求。

Halo [ˈheɪloʊ]，强大易用的开源建站工具。

官网文档社区 Gitee Telegram 频道

Halo 是什么？

Halo 是一款强大易用的开源建站工具，从个人博客、知识库，到企业官网、在线商城，Halo 都能助您轻松实现，一站式满足您的多样化建站需求。

快速开始

如果你的设备有 Docker 环境，可以使用以下命令快速启动一个 Halo 的体验环境：

docker run -d --name halo -p 8090:8090 -v ~/.halo2:/root/.halo2 halohub/halo:2.24

或者点击下方按钮使用 Gitpod 或 ClawCloud Run 启动一个体验环境：

以上方式仅作为体验使用，推荐使用开源 Linux 服务器运维管理面板 1Panel 进行部署（查看文档），轻松搞定反向代理、SSL 证书及升级备份任务。更多部署方式，请查看文档。

在线体验

环境地址：https://demo.halocms.site
后台地址：https://demo.halocms.site/console
用户名：demo
密码：P@ssw0rd123..

版本对比

Halo 社区版：开源免费，遵循 GPLv3 协议

适合个人开发者、技术爱好者、开源项目
零成本搭建博客、作品集、技术文档站
超过 100 款免费主题和插件

Halo 专业版：在社区版基础上，集成 10+ 高价值功能

移动端 APP：随时随地管理内容
AI 智能建站：快速生成专业站点
手机号验证登录：提升安全与用户体验
全站私有化部署：保障数据主权
付费主题/插件市场：专享精品主题和 SEO 优化、付费阅读、AI 助手等 10 款付费插件

Halo 商业版：在专业版基础上，集成在线商城重磅功能

一体化在线商城：商品管理、订单处理、支付对接全流程
为中国商家定制：无缝集成微信支付、支付宝等本土生态
品牌官网 + CMS + 线上店铺一站式落地，助力生意高效增长

关于三个版本的详细对比，请参考版本对比。

生态

可访问官方应用市场或 awesome-halo 仓库查看适用于 Halo 2.x 的主题和插件。

许可证

Halo 使用 GPL-v3.0 协议开源，请遵守开源协议。

贡献

参考 CONTRIBUTING。

状态

tronprotocol/java-tron

Java implementation of the Tron whitepaper

Java implementation of the TRON Protocol

What's TRON?

TRON is building the foundational infrastructure for the decentralized internet ecosystem with a focus on high-performance, scalability, and security.

TRON Protocol: High-throughput (2000+ TPS), scalable blockchain OS (DPoS consensus) powering the TRON ecosystem.
TRON Virtual Machine (TVM): EVM-compatible smart-contract engine for fast smart-contract execution.

Building the Source Code

Before building java-tron, make sure you have:

Hardware with at least 4 CPU cores, 16 GB RAM, 10 GB free disk space for a smooth compilation process.
Operating system: Linux or macOS (Windows is not supported).
Git and correct JDK (version 8 or 17) installed based on your CPU architecture.

There are two ways to install the required dependencies:

Option 1: Automated script (recommended for quick setup)

Use the provided install_dependencies.sh script:
```
chmod +x install_dependencies.sh
./install_dependencies.sh
```
Note: For production-grade stability with JDK 8 on x86_64 architecture, Oracle JDK 8 is strongly recommended (the script installs OpenJDK 8).
Option 2: Manual installation

Follow the Prerequisites and Installation Guide for step-by-step instructions.

Once all dependencies have been installed, download and compile java-tron by executing:

git clone https://github.com/tronprotocol/java-tron.git
cd java-tron
git checkout -t origin/master
./gradlew clean build -x test

The parameter -x test indicates skipping the execution of test cases.
If you encounter any error please refer to the Compiling java-tron Source Code documentation for troubleshooting steps.

Executables

The java-tron project comes with several runnable artifacts and helper scripts found in the project root and build directories.

Artifact/Script	Description
`FullNode.jar`	Main TRON node executable (generated in `build/libs/` after a successful build following the above guidance). Runs as a full node by default. `java -jar FullNode.jar --help` for command line options
`Toolkit.jar`	Node management utility (generated in `build/libs/`): partition, prune, copy, convert DBs; shadow-fork tool. Usage
`start.sh`	Quick start script (x86_64, JDK 8) to download/build/run `FullNode.jar`. See the tool guide.
`start.sh.simple`	Quick start script template (ARM64, JDK 17). See usage notes inside the script.

Running java-tron

Hardware Requirements for Mainnet

Deployment Tier	CPU Cores	Memory	High-performance SSD Storage	Network Downstream
FullNode (Minimum)	8	16 GB	200 GB (Lite)	≥ 5 MBit/sec
FullNode (Stable)	8	32 GB	200 GB (Lite) / 3.5 TB (Full)	≥ 5 MBit/sec
FullNode (Recommend)	16+	32 GB+	4 TB	≥ 50 MBit/sec
Super Representative	32+	64 GB+	4 TB	≥ 50 MBit/sec

Note: For test networks, where transaction volume is significantly lower, you may operate with reduced hardware specifications.

Launching a full node

A full node acts as a gateway to the TRON network, exposing comprehensive interfaces via HTTP and RPC APIs. Through these endpoints, clients may execute asset transfers, deploy smart contracts, and invoke on-chain logic. It must join a TRON network to participate in the network's consensus and transaction processing.

Network Types

The TRON network is mainly divided into:

Main Network (Mainnet)
The primary public blockchain where real value (TRX, TRC-20 tokens, etc.) is transacted, secured by a massive decentralized network.
Nile Test Network (Testnet)
A forward-looking testnet where new features and governance proposals are launched first for developers to experience. Consequently, its codebase is typically ahead of the Mainnet.
Shasta Testnet
Closely mirrors the Mainnet’s features and governance proposals. Its network parameters and software versions are kept in sync with the Mainnet, providing developers with a highly realistic environment for final testing.
Private Networks
Customized TRON networks set up by private entities for testing, development, or specific use cases.

Network selection is performed by specifying the appropriate configuration file upon full-node startup. Mainnet configuration: config.conf; Nile testnet configuration: config-nile.conf

1. Join the TRON main network

Launch a main-network full node with the built-in default configuration:

java -jar ./build/libs/FullNode.jar

For production deployments or long-running Mainnet nodes, please refer to the JVM Parameter Optimization for FullNode guide for the recommended Java command configuration.

Using the below command, you can monitor the blocks syncing progress:

tail -f ./logs/tron.log

Use TronScan, TRON's official block explorer, to view main network transactions, blocks, accounts, witness voting, and governance metrics, etc.

2. Join Nile test network

Utilize the -c flag to direct the node to the configuration file corresponding to the desired network. Since Nile Testnet may incorporate features not yet available on the Mainnet, it is strongly advised to compile the source code following the Building the Source Code instructions for the Nile Testnet.

java -jar ./build/libs/FullNode.jar -c config-nile.conf

Nile resources: explorer, faucet, wallet, developer docs, and network statistics at nileex.io.

3. Access Shasta test network

Shasta does not accept public node peers. Programmatic access is available via TronGrid endpoints; see TronGrid Service for details.

Shasta resources: explorer, faucet, wallet, developer docs, and network statistics at shasta.tronex.io.

4. Set up a private network

To set up a private network for testing or development, follow the Private Network guidance.

Running a super representative node

To operate the node as a Super Representative (SR), append the --witness parameter to the standard launch command. An SR node inherits every capability of a FullNode and additionally participates in block production. Refer to the Super Representative documentation for eligibility requirements.

Fill in the private key of your SR account into the localwitness list in the configuration file. Here is an example:

 localwitness = [
    <your_private_key>
 ]

Check Starting a Block Production Node for more details. You could also test the process by connecting to a testnet or setting up a private network.

Programmatically interfacing FullNode

Once the FullNode starts successfully, interaction with the TRON network is facilitated through a comprehensive suite of programmatic interfaces exposed by java-tron:

HTTP API: See the complete HTTP API reference and endpoint list.
gRPC: High-performance APIs suitable for service-to-service integration. See the supported gRPC reference.
JSON-RPC: Provides Ethereum-compatible JSON-RPC methods for logs, transactions and contract calls, etc. See the supported JSON-RPC methods.

Enable or disable each interface in the configuration file:

node {
  http {
    fullNodeEnable = true
    fullNodePort   = 8090
  }

  jsonrpc {
    httpFullNodeEnable = true
    httpFullNodePort   = 8545
  }

  rpc {
    enable = true
    port   = 9090
  }
}

When exposing any of these APIs to a public interface, ensure the node is protected with appropriate authentication, rate limiting, and network access controls in line with your security requirements.

Public hosted HTTP endpoints for both mainnet and testnet are provided by TronGrid. Please refer to the TRON Network HTTP Endpoints for the latest list. For supported methods and request formats, see the HTTP API reference above.

Community

TRON Developers & SRs is TRON's official Discord channel. Feel free to join this channel if you have any questions.

The Core Devs Community and TRON Official Developer Group are Telegram channels specifically designed for java-tron community developers to engage in technical discussions.

Contribution

Thank you for considering to help out with the source code! If you'd like to contribute to java-tron, please see the Contribution Guide for more details.

Resources

Medium — Official technical articles from the java-tron core development team.
Documentation and TRON Developer Hub — Primary documentation for java-tron developers.
TronScan — TRON mainnet blockchain explorer.
Nile Test Network — A stable test network for TRON development and testing.
Shasta Test Network — A stable test network mirroring mainnet features.
Wallet-cli — Command-line wallet for the TRON network.
TIP — TRON Improvement Proposals describing standards for the TRON network.
TP — TRON Protocols already implemented but not yet published as TIPs.

Integrity Check

After January 3, 2023, the release files will be signed using a GPG key pair, and the correctness of the signature will be verified using the following public key:
```
pub: 1254 F859 D2B1 BD9F 66E7 107D F859 BCB4 4A28 290B
uid: build@tron.network
```

License

java-tron is released under the LGPLv3 license.

netty/netty

Netty project - an event-driven asynchronous network application framework

Netty Project

Netty is an asynchronous event-driven network application framework for rapid development of maintainable high performance protocol servers & clients.

How to build

For the detailed information about building and developing Netty, please visit the developer guide. This page only gives very basic information.

You require the following to build Netty:

Latest stable OpenJDK 8
Latest stable Apache Maven
If you are on Linux or MacOS, you need additional development packages installed on your system, because you'll build the native transport.

Note that this is build-time requirement. JDK 5 (for 3.x) or 6 (for 4.0+ / 4.1+) is enough to run your Netty-based application.

Branches to look

Development of all versions takes place in each branch whose name is identical to <majorVersion>.<minorVersion>. For example, the development of 3.9 and 4.1 resides in the branch '3.9' and the branch '4.1' respectively.

Usage with JDK 9+

You can read the Modular Netty guide to learn more about using Netty with the Java Platform Module System, the guide contains a user section and a developer section for Netty contributors.

apache/dolphinscheduler

Apache DolphinScheduler is the modern data orchestration platform. Agile to create high performance workflow with low-code

Apache Dolphinscheduler

About

Apache DolphinScheduler is a modern data orchestration platform that empowers agile, low-code development of high-performance workflows. It is dedicated to handling complex task dependencies in data pipelines and provides a wide range of built-in job types out of the box.

Key features for DolphinScheduler are as follows:

Easy to deploy, providing four deployment modes including Standalone, Cluster, Docker, and Kubernetes.
Easy to use, workflows can be created and managed via Web UI, Python SDK or Open API
Highly reliable and high availability, with a decentralized, multi-master and multi-worker architecture and native support for horizontal scaling.
High performance, its performance is several times faster than other orchestration platforms, and it is capable of handling tens of millions of tasks per day
Cloud Native, DolphinScheduler supports orchestrating workflows across multiple clouds and data centers, and allows custom task types
Workflow Versioning, provides version control for both workflows and individual workflow instances, including tasks.
Flexible state control of workflows and tasks, supports pausing, stopping, and recovering them at any time.
Multi-tenancy support
Additional features, backfill support(Web UI native), permission control including project and data source etc.

QuickStart

For quick experience
- Want to start with standalone
- Want to start with Docker
For Kubernetes
- Start with Kubernetes
For Terraform
- Start with Terraform

User Interface Screenshots

Homepage: Project and workflow overview, including the latest workflow instance and task instance status statistics.
Workflow Definition: Create and manage workflows by drag and drop, easy to build and maintain complex workflows, support a wide range of tasks out of box.
Workflow Tree View: Abstract tree structure could provide a clearer understanding of task relationships
Data source: Supports multiple external data sources, provides unified data access capabilities for MySQL, PostgreSQL, Hive, Trino, etc.
Monitor: View the status of the master, worker and database in real time, including server resource usage and load, do a quick health check without logging in to the server.

Suggestions & Bug Reports

Follow this guide to report your suggestions or bugs.

Contributing

The community welcomes contributions from everyone. Please refer to this page to find out more details: How to contribute. Check out good first issues here if you are new to DolphinScheduler.

Community

Welcome to join the Apache DolphinScheduler community by:

Use GitHub Issues for questions, discussions, and bug reports
Follow the DolphinScheduler Twitter and get the latest news
Subscribe DolphinScheduler mail list, users@dolphinscheduler.apache.org for users and dev@dolphinscheduler.apache.org for developers

Landscapes

DolphinScheduler enriches the CNCF CLOUD NATIVE Landscape.

GitHub Java Weekly Trending

jeecgboot/JeecgBoot

JeecgBoot AI低代码平台

项目介绍

企业级AI低代码平台

🔥 AI Skills 重磅能力（自然语言编程）

AI Skills 技能清单

适用项目

版本说明

启动项目

技术文档

AI 应用平台介绍

为什么选择JeecgBoot?

技术架构

前端

后端

数据库支持

微服务解决方案

功能清单

系统效果

AI模型与应用管理

PC端

系统交互

仪表盘设计器

报表设计器

手机端

PAD端

图表示例

在线接口文档

UNIAPP效果

大屏设计器

微服务架构图

Jeecg Boot 产品功能蓝图

系统功能架构图

捐赠

免责声明

neo4j/neo4j

Neo4j: Graphs for Everyone

Using Neo4j

Extending Neo4j

Dependencies

With brew on macOS

With apt-get on Ubuntu

Building Neo4j

Running Neo4j

Neo4j Desktop

Licensing

Trademark

kestra-io/kestra

Event-Driven Declarative Orchestration Platform

🌟 What is Kestra?

🚀 Quick Start

Launch on AWS (CloudFormation)

Launch on Google Cloud (Terraform deployment)

Get Started Locally in 5 Minutes

Launch Kestra in Docker

Your First Hello World Flow

🧩 Plugin Ecosystem

📚 Key Concepts

🎨 Build Workflows Visually

🔧 Extensible and Developer-Friendly

Plugin Development

Infrastructure as Code

🌐 Join the Community

🤝 Contributing

📄 License

⭐️ Stay Updated

TeamNewPipe/NewPipe

We are rewriting large chunks of the codebase, to bring about a modern and stable NewPipe! You can download nightly builds here.

Please work on the refactor branch if you want to contribute new features. The current codebase is in maintenance mode and will only receive bugfixes.

NewPipe

A libre lightweight streaming front-end for Android.

Screenshots

Supported Services

Description

Features

Installation and updates

APK Info

Contribution

Donate

Please work on the `refactor` branch if you want to contribute new features. The current codebase is in maintenance mode and will only receive bugfixes.

Provision and manage
devices and assets

Collect and visualize
your data