- Is rmzamora/admin-bundle a Laravel package?
- No. Despite being described as an admin bundle for Laravel, the repository is a fork of sonata-project/admin-bundle, a Symfony bundle built on Doctrine ORM, Twig, Symfony Form and Security, KnpMenu, and the SonataCore/Block/Doctrine dependency chain. It does not use Eloquent, Blade, service providers, or Laravel's container semantics. If you need Laravel admin scaffolding, this is the wrong artifact.
- Can I install rmzamora/admin-bundle in a Laravel application with Composer?
- You can add it to composer.json, but making it work means co-hosting a Symfony kernel alongside Laravel, which is not a viable production integration. Composer resolution will likely also fail or pin decade-old Symfony and PHP constraints that conflict with the Symfony 6/7 transitive packages pulled in by modern Illuminate releases. Run composer why-not rmzamora/admin-bundle in a clean container to confirm the conflict before spending any estimate on it.
- What PHP and Symfony versions does rmzamora/admin-bundle require?
- Compatibility is unverified because the fork ships no release notes or CI signals, but the upstream lineage points to PHP 7.x through 8.0 or 8.1, Symfony 4.4 or 5.x, Doctrine ORM 2, and Twig 2 or 3. Those constraints are older than what current Laravel applications require (PHP 8.2+, Symfony 6/7 transitives). Treat any version claim as a spike item, not a given.
- Is rmzamora/admin-bundle actively maintained?
- No. The repository is archived with zero stars, zero dependents, and a single maintainer, and there is no release cadence, issue triage, or published security process. Adopting it makes your team the de facto maintainer of every future Symfony, PHP, and Doctrine patch. The bus factor is one, and repo deletion or an account change breaks the supply chain with no fallback.
- Is it safe to run an abandoned admin panel in production?
- It is high risk. An admin panel is a privileged, write-capable surface and typically the highest-value target in an application, yet a fork receives no CVE backports and no upstream test-suite coverage signals. Divergence from the original Sonata code is silent, with no behavioral change log to review. If you must inspect it, vendor-pin an exact commit inside an isolated container and never let it reach a production composer.json.
- What are the best Laravel alternatives to rmzamora/admin-bundle?
- For Laravel, the maintained choices are Filament (open source), Laravel Nova (commercial), Backpack, and Orchid. All of them plug into Eloquent, Gate and Policy authorization, Blade, and Laravel's container without co-hosting another framework. If your host is actually Symfony, use the maintained upstream sonata-project/admin-bundle rather than this fork, which adds no differentiating capability over either path.
- Does rmzamora/admin-bundle integrate with Laravel authentication, gates, and policies?
- No. Authorization is handled by Symfony Security and the bundle's own admin roles, not Laravel's Auth guard, Gate, or Policy system. You would have to build a bridge layer yourself, and any bugs in that bridge sit directly in front of your most privileged screens. This is one of the clearest signs the artifact does not belong in a Laravel stack.
- How does this fork differ from upstream sonata-project/admin-bundle?
- The fork offers nothing meaningful over upstream, and everything to lose. It diverges without a documented diff against a named upstream tag, carries no additional features, and cannot track upstream fixes or security releases. Gate the evaluation on a security and legal review of the fork diff against a specific Sonata tag before considering code reuse.
- How should I evaluate or migrate a legacy Sonata admin panel?
- First confirm the framework target, since that single answer changes everything downstream. If the host is Symfony, migrate to upstream Sonata or another maintained panel; if the host is Laravel, do not migrate this in and instead build on Filament or Nova. Sequence it as gates: framework confirmation, a one-to-two day install spike in an isolated container, a fork-diff security review, then a documented build-versus-buy decision.
- Should I adopt rmzamora/admin-bundle for a new admin panel?
- No. The archived status, zero dependents, single-maintainer fork, and lack of security process make this a dead artifact, and the high opportunity score in the category reflects the value of admin tooling rather than this package. Close the evaluation with a written decision record and redirect to Filament, Nova, Backpack, or upstream Sonata depending on your framework. That decision record is the deliverable, not a working integration.