Discofork
Repository brief

vbenjs/vue-vben-admin

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-30T19:54:27.016Z
1mo ago

vbenjs/vue-vben-admin

vbenjs/vue-vben-admin is a large, active MIT-licensed Vue 3 admin template and monorepo for building backend/admin frontends. It is positioned as a modern, fast starter with strong community adoption, with 31,925 stars and 8,690 forks, and it was updated on 2026-03-30.

GitHub
Loading tags...
Stars31,925
Forks8,690
Default branchmain
Last pushed2026-03-29T06:17:00Z
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 if you need osharp-specific admin functionality and are willing to own divergence. Choose upstream if you want a current, well-maintained starter with broader community momentum and less migration risk.

Choose this fork if your product is centered on media streaming operations and you want those workflows prebuilt. Choose upstream if you need the broadest, freshest general-purpose admin starter with lower merge risk.

Adopt only if you specifically need this older baseline or an existing internal mirror; otherwise upstream is the better choice because it is much more current and actively maintained.

Choose upstream unless you specifically want this fork's bespoke admin workflow and are prepared to maintain a large, stale codebase. The fork looks useful for a narrowly tailored product, but it is not a low-risk base for a new long-lived platform.

Choose this fork if you want a more productized Smart Boot admin platform with extra business modules and deployment-oriented customization. Choose upstream if you want the broader, more standard vben-admin starter with the full set of maintained variants and less migration risk.

Choose this fork if you want a closer-to-production full-stack admin starter with NestJS, Prisma, PostgreSQL, and JWT already wired in. Choose upstream if you want the most current Vue admin base and broader upstream documentation/support.

Choose upstream instead unless you specifically need a frozen copy. This fork adds no visible capabilities and is materially behind on fixes and improvements.

Prefer this fork only if you specifically need an Electron-centered Vben baseline and are comfortable with a stale, highly divergent codebase. If you want the broadest feature set and the lowest maintenance burden, upstream is the safer choice.

Choose this fork only if you want its specific customizations and are comfortable owning a long-lived, outdated branch. For new work or for keeping close to upstream, the upstream repository is the safer default.

Choose this fork if you want a specialized project-management-oriented admin system and are willing to accept significant divergence from upstream. Choose upstream instead if you need the broadest multi-app starter coverage, easier upstream syncing, or the removed `web-antdv-next` path.