Weave Code
Administrator Laravel Package
frozennode/administrator
Frozennode Administrator is a Laravel admin package that generates configurable CRUD interfaces for Eloquent models, with built-in authentication, relationships, filters, sorting, and customizable fields and actions.
Frozennode/Administrator is a configuration-driven admin interface builder for Laravel. It generates full CRUD panels for your Eloquent models from simple config files—no boilerplate views or controllers required. Describe your model's fields, columns, and relationships, and Administrator produces a polished, searchable backend.
- Declarative model configs for fields, validation, and relationships
- Rich field types including text, image, enum, and relationships
- Built-in filtering, sorting, and pagination
- Authentication hooks with customizable permissions
- Extensible custom actions and buttons per model
Frequently asked questions about Administrator
- Does frozennode/administrator work with Laravel 10 or 11?
- No. The last release was in 2016, so it targets Laravel 5.x-era projects and is not compatible with modern Laravel 9–11 or PHP 8.1+. Running it on current Laravel requires significant patching and is not recommended. Confirm your framework constraints with a time-boxed Composer spike before committing.
- How do I install frozennode/administrator?
- Installation is only feasible inside its historical Laravel/PHP support window, using Composer in a legacy Laravel 5.x project. You then publish the package config and define admin screens per Eloquent model. Greenfield installations on modern Laravel are low-feasibility, so validate dependencies in an isolated branch or container first.
- Is frozennode/administrator still maintained?
- No, it is effectively unmaintained. There have been no releases since 2016, no upstream security patches, and documentation and issues are historical. High GitHub stars reflect past popularity, not current production suitability. Your team would own all fixes and upgrades if you adopt it.
- What Laravel and PHP versions does frozennode/administrator support?
- It was built for the Laravel 5.x era and likely PHP 5.6/7.0, not modern Laravel 9–11 or PHP 8.1+. Treat those as historical constraints rather than a current support matrix. Verify exact versions with a dependency spike in a pinned container before any commitment.
- Can I build CRUD admin panels from Eloquent models with frozennode/administrator?
- Yes, that is its core purpose: config-driven CRUD screens from Eloquent models with relationships, filters, validation, and permissions. You configure screens rather than write frontend code. However, the approach creates config and convention lock-in and only makes sense for a legacy internal admin.
- Is frozennode/administrator secure for production admin panels?
- High risk. The package is unmaintained, so there are no security patches, and admin surfaces are high-privilege. Review authentication, CSRF, mass assignment, validation, file uploads, and query/filter behavior before production. Keep the admin internal-only behind SSO or VPN and define who owns patching and exit planning.
- What are the alternatives to frozennode/administrator for Laravel admin panels?
- For modern Laravel, maintained tools such as Filament, Laravel Nova, and Backpack are common alternatives. For simple needs, a thin custom admin or route-by-route replacement may be safer. Do not treat frozennode/administrator as a strategic platform foundation; use it only as a legacy accelerator.
- Can frozennode/administrator handle relationships, filters, and validation?
- The package supports relationships, filters, validation, and permissions through configuration, which is why it was popular for quick back-office screens. The trade-off is convention lock-in and dated behavior that needs security review. Test relationship handling and filter behavior carefully on a representative model.
- How do I migrate away from frozennode/administrator?
- Use a strangler approach: replace route-by-route, validate data parity, dual-run where needed, then decommission. First inventory admin entities and workflows, then migrate the capability to a maintained admin tool or thin custom admin rather than migrating the package itself. Define a replacement trigger and exit plan before production.
- Does frozennode/administrator support permissions and authentication?
- It supports config-driven permissions and works with Blade/session-based auth typical of legacy Laravel monoliths. It does not fit modern SSO-first or API-headless architectures without additional work. For high-privilege admin access, put it behind SSO/VPN and review authorization requirements.
Weaver
How can I help you explore Laravel packages today?