// the find
go-admin-team/go-admin
基于Gin + Vue + Element UI & Arco Design & Ant Design 的前后端分离权限管理系统脚手架（包含了：多租户的支持，基础用户管理功能，jwt鉴权，代码生成器，RBAC资源控制，表单构建，定时任务等）3分钟构建自己的中后台项目；项目文档》：https://www.go-admin.pro V2 Demo： https://vue2.go-admin.dev V3 Demo： https://vue3.go-admin.dev Antd PRO：https://antd.go-admin.pro
go-admin is a Go backend + Vue frontend admin panel scaffold that bundles together RBAC (via Casbin), JWT auth, a code generator, form builder, and scheduled jobs into one deployable starter. It targets Go developers who need to ship a standard enterprise admin UI without building the plumbing from scratch. The frontend ships as a separate repo in three flavors: Element UI v2, Arco Design v3, and Ant Design Pro.
The code generator is the real draw — it reads your DB schema and generates CRUD API handler, router, service, DTO, and frontend JS in one pass, which eliminates days of boilerplate for standard admin tables. Casbin RBAC is wired through middleware at the route level with data-scope filtering (org-tree row-level access) already implemented, which is a pattern most teams would have to build themselves. The cobra-based multi-command layout (server, migrate, version as subcommands) is cleaner than a monolithic main.go and makes migrations safe to run separately in CI. Directory layout is consistent across every domain module — each one follows the same apis/models/router/service/dto structure, which makes onboarding a team straightforward.
The README says 'TODO: unit test' and that's accurate — there is essentially no test coverage of the actual auth, RBAC, or business logic. You're adopting untested Casbin middleware and JWT handling in production. Pre-built minified JS bundles are checked into static/form-generator/ with no source provenance, which is a supply chain problem for anyone running this somewhere that cares about that. Multi-tenancy is listed as a feature but what's actually implemented is org-tree data scoping — if you need hard tenant isolation (separate schemas or row-level security), that feature is not here and you'll be refactoring against a design that didn't plan for it. The community, issue tracker, and video tutorials are primarily Chinese (hosted on Bilibili and WeChat groups), so debugging a production edge case as a non-Chinese speaker is slower than the star count suggests.