- Is rz/admin-bundle actually a Laravel package?
- No. Despite the description claiming it is a Laravel package, rz/admin-bundle is a Symfony 2.x-era bundle from the rzproject CMS family. Laravel has no bundle or kernel model and no equivalent registration mechanism, so this cannot be installed as a Laravel package. Treat the Laravel categorization as an error to correct before evaluation.
- Can I install rz/admin-bundle with Composer in a Laravel project?
- There is no viable integration path. Expect composer require to fail on constraint resolution before you ever reach a runtime error because the package targets an end-of-life framework generation and abandoned PHP constraints. Do not attempt to pin around it, since that drags the entire application onto an EOL runtime. Adoption would mean owning a fork, not adding a dependency.
- Which Laravel versions are supported by rz/admin-bundle?
- None. It is not a Laravel package and has no Laravel version compatibility. Even inside its native Symfony home, the rzproject family targets an EOL framework generation and will not boot on any currently supported Symfony release. There is no adapter that makes it a drop-in for Laravel.
- Does rz/admin-bundle include authentication and role-based admin access?
- The description claims built-in authentication and role-based access for admin users, but the package is a Symfony bundle, not a Laravel authentication integration. An admin bundle is by definition the highest-privilege surface in an application, covering auth-adjacent routing, CRUD over arbitrary entities, and file handling. With the repository archived, there will be no CVE response or PHP 8.x support, so it is not suitable for production auth paths.
- Can rz/admin-bundle scaffold CRUD screens for Eloquent models?
- No. It claims CRUD scaffolding for Eloquent resources with search, filters, and pagination, but Eloquent is Laravel-specific and this bundle has no Laravel adapter. It also carries undocumented ORM and entity assumptions that surface as silent data-layer bugs rather than clean errors. Use a maintained Laravel admin tool instead.
- Is rz/admin-bundle maintained and safe to depend on?
- No. The repository is archived with zero stars and zero dependents, so there is no production evidence, issue history, or fork to inherit maintenance. Transitive risk cannot even be estimated because there is no dependency graph and no one to ask. Archiving is a permanent statement that no dependency refresh, PHP 8.x fix, or security response will arrive.
- What Laravel admin panel alternatives should I use instead of rz/admin-bundle?
- For Laravel, evaluate maintained incumbents such as Filament, Nova, Backpack, or Voyager. For Symfony, use EasyAdmin or SonataAdmin. The correct move is to redirect the underlying requirement to a maintained equivalent in your actual stack rather than integrating this package. If a specific interaction pattern in this bundle is genuinely superior, write a design note and implement it internally.
- Does rz/admin-bundle work with Laravel middleware and policies?
- No. Compatibility with standard Laravel middleware and policies is claimed, but a Symfony bundle has no Laravel middleware or policy integration. Laravel's authorization layer does not map onto Symfony's bundle, kernel, and service-container model. Architecture fit is zero on both sides of the stack question.
- Is rz/admin-bundle suitable for production admin panels?
- No. Shipping an unmaintained admin layer is a standing audit finding because admin surfaces control auth-adjacent routing, CRUD over arbitrary entities, and file handling. Technical risk is high and unbounded with no CVE response, PHP 8.x support, or dependency refresh. If the work touches regulated data or production auth paths, the answer is no regardless of the rest.
- How do I migrate an existing application from rz/admin-bundle?
- There is no migration path because the package has zero consumers, zero migration burden, no changelog, and no versioning discipline to reason about. Treat the repository as read-only input to a short timeboxed spike, extract any entity, CRUD, or UX ideas worth keeping, and then discard the code. Redirect the underlying requirement to a maintained equivalent in your team's actual stack.