Discofork
Repository brief

ant-design/ant-design-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:49:14.983Z
1mo ago

ant-design/ant-design-pro

ant-design/ant-design-pro is a large, active, non-archived open-source enterprise UI starter built on React and Ant Design. It has very high adoption signals for a forkable upstream: 38,042 stars, 8,233 forks, and recent commits on 2026-03-31. The repo is positioned as an out-of-box UI solution for enterprise applications, with multilingual docs, template pages, mock data, tests, and a CLI-based project creation flow.

GitHub
Loading tags...
Stars38,042
Forks8,233
Default branchmaster
Last pushed2026-03-31T07:19:23Z
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 its custom admin workflows are already aligned with your needs; otherwise upstream Ant Design Pro is the safer base because this fork is materially stale and appears to have dropped some upstream scaffolding.

Choose this fork only if you need its custom legacy modifications or want to build on an old snapshot. If you want a current, well-maintained Ant Design Pro base, upstream is the better default.

Prefer upstream unless you specifically need this older frozen snapshot. The fork adds no visible product value and is far behind active maintenance.

Prefer this fork only if your real target is a Rails-backed app with Ant Design UI. If you want the actively maintained upstream enterprise React starter, the fork is materially behind and has diverged into a different product direction.

Choose this fork only if you specifically need its older custom admin workflow. If you want an actively maintained starter with current upstream capabilities, upstream is the safer default.

Choose this fork only if you need the specific legacy customizations it already contains. For a new project or anything that values maintenance, upstream is the safer choice.

Prefer this fork only if you need its legacy customizations and are prepared to own a long-lived, stale divergence. For new work or active maintenance, upstream is the safer default.

Prefer this fork only if the CRM-specific framing is the real requirement. If you want an actively maintained enterprise starter, upstream is the safer choice.

Choose this fork only if its custom business modules are the point. If you want an actively maintained starter or plan to keep up with upstream, the fork is a poor base because it is old, divergent, and missing recent upstream maintenance.

Choose this fork only if you want its legacy customizations and can tolerate major upstream drift. For a new or actively maintained enterprise starter, upstream is the safer choice.