// the take
MoonShine is a Laravel admin panel built on Blade, Alpine.js and Tailwind rather than a bundled SPA — the usual CRUD-scaffolding tool for internal dashboards and back-office UIs. Version 4 splits the engine into separate Core/Crud/Contracts packages, aiming to decouple the admin logic from Laravel/Eloquent specifically. It's aimed at Laravel developers who want a no-JS-build admin panel they can theme quickly.
The v4 rewrite genuinely separates concerns into standalone composer packages (Core, Crud, Contracts, AssetManager, ColorManager) rather than one monolithic Laravel package, which is more architectural discipline than most PHP admin panels bother with. It has real CI hygiene — PHPStan static analysis, mutation testing, and test workflows running on every push, not just badges for show. Being Blade/Alpine/Tailwind-based instead of a bundled Vue/React SPA means no separate frontend build pipeline to maintain or keep in sync with the backend. There's a genuine ecosystem of installable add-ons (file manager, 2FA, visual editors) as separate packages instead of everything crammed into core.
The README is almost entirely marketing copy — AI-assistant pitches, emoji bullet lists, a self-flattering comparison table — with essentially no technical content; the real docs live in a separate, community-maintained repo whose completeness isn't verifiable from here. The headline claim that core is now framework-independent and 'works with Symfony/Yii' isn't backed by anything in this repo — there's only a Laravel integration package, so treat that claim as aspirational rather than shipped. Like any admin panel library, adopting it means your UI is coupled to its Blade component conventions and specific Tailwind build; migrating away later or bolting it onto an existing non-Tailwind design system is a real rewrite, not a config change. The 'AI admin developer' tools (Forty-Five, MoonVibe) and the 50+-item marketplace are separate products with licensing that isn't clearly spelled out alongside the MIT-licensed core, so some of what's advertised may not actually be free.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →