【低代码v2.0，一句话即可生成整个系统】企业级AI低代码平台，一键生成前后端代码甚至整个系统。 AI Skills 一句话画流程、设计表单、生成报表、大屏。内置 AI应用平台涵盖：AI聊天、知识库、流程编排、MCP插件等，兼容主流大模型。引领AI低代码「Skills 生成 → 在线配置 → 代码生成 → 手工合并->AI修改」开发模式，解决 Java 项目 90% 重复工作，提高效率又不失灵活。
C-Rank Grade: D (Risky) - 29/100
External PR Merge Rate: -
Response Time: -
First Timer Success: -
jeecgboot/JeecgBoot has a recorded first-timer success rate of 0.0%. Repositories ranked D typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in jeecgboot/JeecgBoot respond to incoming external pull requests in approximately 0.0 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 29.2 places jeecgboot/JeecgBoot in the D tier.
The external contributor pull request merge rate for jeecgboot/JeecgBoot is 0.0%, based on public PR activity from non-core contributors.
jeecgboot/JeecgBoot currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Responsive & active maintainer team in jeecgboot/JeecgBoot. Reviews pull requests with focus on project architectural goals.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/jeecgboot/JeecgBoot?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 01:00 UTC (01:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 00:00 to 04:00 UTC (00:00 - 04:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (81% approval). Large PRs (>500 lines) take ~115 hours (29% approval). Keep your diff compact for rapid review.
版本号： 3.8.3 分支： master 问题描述： 积木报表设置两级横向分组，一级分组标题无法设置分组合计 横向分组不像纵向分组那样，可以随意按照分组字段进行合计，纵向分组甚至还支持多个不同的分组字段分别进行合计 改成横向分组，分组小计设置没有合计选项， 不支持设置分组合计 错误截图： 友情提示： 未按格式要求发帖、描述过于简单的，会被直接删掉; 描述问题请图文并茂，方便我们理解并快速定位问题; 如果使用的不是master，请说明你使用的分支;
版本号： 2.1.5 分支： 问题描述： 积木报表设置两级横向分组，一级分组标题无法设置分组合计 错误截图： 友情提示： 未按格式要求发帖、描述过于简单的，会被直接删掉; 描述问题请图文并茂，方便我们理解并快速定位问题; 如果使用的不是master，请说明你使用的分支;
版本号： 3.9.5 分支： master 问题描述： 建议Chat2BI增加类似AI应用一样的发布功能，现在的Chat2BI所有操作和页面都在一起，这样无法进行权限管控，也无法独立在其他地方展示，现在要想使用只能在测试对话的界面使用，实话实说现在无法用在企业功能上，只是一个展示品 错误截图： 友情提示： 未按格式要求发帖、描述过于简单的，会被直接删掉; 描述问题请图文并茂，方便我们理解并快速定位问题; 如果使用的不是master，请说明你使用的分支;
版本号：3.9.5 分支： 问题描述： 积木报表在线填报表单中数据字典不能获取系统中已有数据字典、新增又提示编码已经存在 1、静态数据源：只支持选项（只有显示文本，没有值），应该增加文本值，同时增加json灵活配置（不需要一行行手动添加效率更高）； 2、数据字典：建议可以从系统数据字典中获取、只能编辑积木报表中新增的字典、系统字典可以只给调用权限； 3、API字典：系统管理中的字典API需要Token，此处不能调用； 4、表字典：表字典只能选择表，选择了数据字典表后无法通过SQL过滤，是不是加个过滤功能或自定义SQL（类似数据集）； 错误截图： 友情提示： 未按格式要求发帖、描述过于简单的，会被直接删掉; 描述问题请图文并茂，方便我们理解并快速定位问题; 如果使用的不是master，请说明你使用的分支;
版本号： 3.9.5 分支： 问题描述： AIGC AI流程设计和AI应用管理 增加LLM流程节点时模型列表，只有语言模型，AI应用编排里，AI模型列表也只有语言模型， 流程设计中，增加对图像模型的支持，AI应用管理 增加对图像模型的支持 错误截图： 友情提示： 未按格式要求发帖、描述过于简单的，会被直接删掉; 描述问题请图文并茂，方便我们理解并快速定位问题; 如果使用的不是master，请说明你使用的分支;
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to jeecgboot/JeecgBoot, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of jeecgboot/JeecgBoot acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 0.0% were successfully merged into the primary branch.
jeecgboot/JeecgBoot has a recorded first-timer success rate of 0.0%. Repositories ranked Risky typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 29.2 places jeecgboot/JeecgBoot in the Risky tier.
The external pull request merge rate is 0.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, jeecgboot/JeecgBoot currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for jeecgboot/JeecgBoot are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.