Discofork
Repository brief

YunaiV/ruoyi-vue-pro

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-31T09:59:34.539Z
1mo ago

YunaiV/ruoyi-vue-pro

YunaiV/ruoyi-vue-pro is a large, actively maintained open-source Java backend/admin platform with a Vue frontend and a broad feature set. It is positioned as a fully open RuoYi-Vue Pro edition with many enterprise modules, and it has very high adoption signals: 36k stars and 7.8k forks. For fork interest, it looks strongest if you want a broad, opinionated Spring Boot + MyBatis Plus + Vue codebase with many prebuilt business modules rather than a minimal starter.

GitHub
Loading tags...
Stars36,106
Forks7,789
Default branchmaster
Last pushed2026-03-08T02:13:57Z
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

10 of 10 fork briefs
Selected

Choose this fork only if you need its older snapshot or local deployment customizations. For new adoption, upstream is the safer choice because this fork is heavily out of date and likely missing many later fixes and modules.

Choose this fork only if the analyzer/full-market-stock workflow is the reason you are adopting it. If you want a general-purpose RuoYi-Vue Pro base, current upstream is a safer choice because this fork is far behind and likely missing a large amount of recent maintenance and feature work.

Prefer this fork only if its customization goals match yours and you are prepared to own a large upstream gap. For most adopters, upstream is the safer default; this fork is mainly attractive as a rebranding/custom-integration base.

Choose this fork only if the API-signing/protection changes are the main value and you are comfortable owning a large upstream gap. If you want an actively maintained enterprise admin platform, upstream is the safer default.

Prefer this fork only if its added payment, tenant, and IoT changes match your needs and you are comfortable maintaining a stale, highly divergent codebase; otherwise upstream is the safer choice.

Choose the upstream project if you want an actively maintained, broad enterprise platform. Choose this fork only if you specifically want its older generator/workflow-oriented changes and are willing to absorb major merge and upgrade debt.

Choose this fork only if you specifically need its older, customized baseline and are willing to maintain it yourself. For most adopters, upstream is the better choice because it is far more current and actively maintained.

Prefer this fork only if you specifically need an older, customized code line. For most adopters, upstream is the better choice because this fork is materially stale and diverged, with the main upside being local compatibility tweaks rather than a stronger overall platform.

Prefer upstream unless you specifically need the fork’s chat and deployment tweaks on an old pinned baseline. This fork is significantly behind and looks expensive to maintain or extend.

Choose this fork only if you want an older, customized starting point with demo-environment additions. For most adopters, upstream is the better choice because this fork is stale and materially behind current fixes and features.