Discofork
Repository brief

jeecgboot/JeecgBoot

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-30T11:57:02.279Z
3mo ago

jeecgboot/JeecgBoot

JeecgBoot is a large AI-driven low-code platform for Java, with both zero-code configuration and code-generation workflows. It includes a Spring Boot back end, Vue 3 front end, microservices support, online forms/reports/charts, workflow automation, AI chat and model features, and a plugin/MCP ecosystem. The repo is active, popular, and likely attractive if you want a mature enterprise low-code base rather than a small starter project.

GitHub
Loading tags...
Stars45,625
Forks15,857
Default branchmain
Last pushed2026-03-29T16:21:38Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

9 of 9 fork briefs
Selected

Choose this fork only if you need an older, customized JeecgBoot base and can tolerate falling far behind upstream; choose upstream if you want the current AI, workflow, and platform ecosystem.

Prefer upstream unless you explicitly need this frozen snapshot. This fork adds no visible capability and is too far behind to be a safe default for new adoption.

Prefer this fork only if you need the old JeecgBoot baseline and are prepared to own maintenance. If you want a current low-code platform with AI, Vue 3, and plugin/MCP support, upstream is the better choice.

Choose this fork only if you specifically want an older JeecgBoot baseline and do not need upstream’s newer AI and platform features; otherwise upstream is the better default because this fork shows no added capability and is materially behind.

Prefer the upstream project unless you specifically need this older customized snapshot. This fork is best for adopters who value its legacy customizations and database packaging more than current upstream capabilities and ongoing maintenance.

Choose this fork only if frontend load speed is the primary requirement and you are comfortable living on an old JeecgBoot base. If you need current platform features, active maintenance, or low merge overhead, upstream is the better choice.

Choose upstream unless you specifically need this fork’s legacy customizations or older runtime baseline. This fork looks like a frozen, highly customized branch with some useful enterprise fixes, but it is too far behind current JeecgBoot to be a good starting point for new adoption.

Prefer upstream unless you specifically need this fork’s legacy customizations. Choose the fork only if you are committed to maintaining an old snapshot and do not need the newer AI, plugin, and platform workflow features from upstream.

Choose this fork only if you specifically need its older customizations and are prepared to own long-term maintenance. For new adopters, upstream JeecgBoot is the better default because this fork is materially stale and likely lags on major platform capabilities.