Is aropixel/admin-bundle a Laravel package?

No. aropixel/admin-bundle is a Symfony bundle built for Symfony 6.4, 7.x, and 8.x applications, and the repository describes it as a Symfony administration framework. It is distributed via Composer, but it does not ship Laravel service providers, Eloquent support, or a Laravel wrapper.

Can I use aropixel/admin-bundle in a Laravel application?

You can install it with Composer, but it is not designed for Laravel and there is no supported integration path. Its CRUD generator, forms, routing, templates, and asset pipeline assume Symfony concepts such as FormType, Twig, Doctrine, and AssetMapper. Making it work in Laravel would require substantial rewriting rather than normal configuration.

What Laravel versions are supported by aropixel/admin-bundle?

None are officially supported. The package targets Symfony 6.4, Symfony 7.x, Symfony 8.x, PHP 8.2+, Doctrine ORM 2 or 3, and ext-intl. Laravel version compatibility is therefore not applicable unless you build a custom port.

Does aropixel/admin-bundle have a Laravel service provider?

No. It is a Symfony bundle, so it registers through Symfony's bundle and extension mechanisms rather than a Laravel service provider. There is no documented Laravel package discovery, facade, config publishing, or middleware integration. Laravel developers would need to create their own bridge, which is not provided.

Can the make:crud generator create Eloquent CRUD in Laravel?

No. The make:crud generator is driven by Symfony FormType classes and emits Symfony/Doctrine-oriented CRUD code, entities, repositories, and metadata. It does not generate Eloquent models, Laravel controllers, Blade views, or Route::resource definitions. Porting the generator to Eloquent would be a rewrite, not a configuration change.

What are the requirements for aropixel/admin-bundle 3.0.0?

Version 3.0.0 requires PHP 8.2 or newer, Symfony 6.4, 7.x, or 8.x, Doctrine ORM 2 or 3, and ext-intl. It also uses Twig, Symfony UX Icons, Stimulus, Turbo, AssetMapper, and ImportMap on the frontend. These are Symfony-centric requirements, not Laravel requirements.

Is there an upgrade path from aropixel/admin-bundle 1.x or 2.x to 3.0.0?

No in-place upgrade path is provided. Version 3.0.0 is a full rewrite, so nothing carries over from the 1.x/2.x evaluation, and older tutorials, plugins, and issue threads are stale. You should treat it as a new package evaluation.

Can I reuse AropixelAdminBundle Stimulus and Turbo controllers with Laravel and Vite?

Partially. Stimulus and Turbo are framework-agnostic, and Laravel has viable adopters such as hotwired/turbo-laravel, so browser-side controllers can be reused with effort. However, the server-side Turbo Frames and Streams are rendered through Twig, and the bundle relies on AssetMapper and ImportMap rather than Laravel's default Vite pipeline. You would need to rewrite import resolution and server-rendered fragments.

How much Twig-to-Blade conversion is needed to use AropixelAdminBundle in Laravel?

Significant conversion is required. Version 3.0.0 adds a new admin UI theme and form widgets, increasing the Twig surface rather than reducing it. You would need TwigBridge or manual Blade conversions for templates, form themes, macros, and Turbo-rendered fragments. This is one of the largest integration costs for Laravel.

What Laravel admin panel alternatives should I evaluate instead of aropixel/admin-bundle?

For Laravel, evaluate Laravel-native or Laravel-first admin tools such as Filament, Laravel Nova, Backpack for Laravel, or Orchid, depending on your licensing and architecture needs. If you specifically want Aropixel's CRUD generator concepts, compare them with Laravel generators and Livewire/Blade component workflows. AropixelAdminBundle remains a good fit only for Symfony applications, not Laravel.

Weave Code

Weaver

Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.

Admin Bundle Laravel Package

aropixel/admin-bundle

Developer-friendly Symfony 6/7 admin framework for PHP 8.2+ that speeds up CRUD building with a make:crud generator driven by your own FormType, plus built-in modules for user roles, news, pages and navigation menus, while keeping full control of your code.

View on GitHub

Deep Wiki

Context7

🛠️ A developer-friendly administration framework for Symfony applications

Frequently asked questions about Admin Bundle

Is aropixel/admin-bundle a Laravel package?: No. aropixel/admin-bundle is a Symfony bundle built for Symfony 6.4, 7.x, and 8.x applications, and the repository describes it as a Symfony administration framework. It is distributed via Composer, but it does not ship Laravel service providers, Eloquent support, or a Laravel wrapper.
Can I use aropixel/admin-bundle in a Laravel application?: You can install it with Composer, but it is not designed for Laravel and there is no supported integration path. Its CRUD generator, forms, routing, templates, and asset pipeline assume Symfony concepts such as FormType, Twig, Doctrine, and AssetMapper. Making it work in Laravel would require substantial rewriting rather than normal configuration.
What Laravel versions are supported by aropixel/admin-bundle?: None are officially supported. The package targets Symfony 6.4, Symfony 7.x, Symfony 8.x, PHP 8.2+, Doctrine ORM 2 or 3, and ext-intl. Laravel version compatibility is therefore not applicable unless you build a custom port.
Does aropixel/admin-bundle have a Laravel service provider?: No. It is a Symfony bundle, so it registers through Symfony's bundle and extension mechanisms rather than a Laravel service provider. There is no documented Laravel package discovery, facade, config publishing, or middleware integration. Laravel developers would need to create their own bridge, which is not provided.
Can the make:crud generator create Eloquent CRUD in Laravel?: No. The make:crud generator is driven by Symfony FormType classes and emits Symfony/Doctrine-oriented CRUD code, entities, repositories, and metadata. It does not generate Eloquent models, Laravel controllers, Blade views, or Route::resource definitions. Porting the generator to Eloquent would be a rewrite, not a configuration change.
What are the requirements for aropixel/admin-bundle 3.0.0?: Version 3.0.0 requires PHP 8.2 or newer, Symfony 6.4, 7.x, or 8.x, Doctrine ORM 2 or 3, and ext-intl. It also uses Twig, Symfony UX Icons, Stimulus, Turbo, AssetMapper, and ImportMap on the frontend. These are Symfony-centric requirements, not Laravel requirements.
Is there an upgrade path from aropixel/admin-bundle 1.x or 2.x to 3.0.0?: No in-place upgrade path is provided. Version 3.0.0 is a full rewrite, so nothing carries over from the 1.x/2.x evaluation, and older tutorials, plugins, and issue threads are stale. You should treat it as a new package evaluation.
Can I reuse AropixelAdminBundle Stimulus and Turbo controllers with Laravel and Vite?: Partially. Stimulus and Turbo are framework-agnostic, and Laravel has viable adopters such as hotwired/turbo-laravel, so browser-side controllers can be reused with effort. However, the server-side Turbo Frames and Streams are rendered through Twig, and the bundle relies on AssetMapper and ImportMap rather than Laravel's default Vite pipeline. You would need to rewrite import resolution and server-rendered fragments.
How much Twig-to-Blade conversion is needed to use AropixelAdminBundle in Laravel?: Significant conversion is required. Version 3.0.0 adds a new admin UI theme and form widgets, increasing the Twig surface rather than reducing it. You would need TwigBridge or manual Blade conversions for templates, form themes, macros, and Turbo-rendered fragments. This is one of the largest integration costs for Laravel.
What Laravel admin panel alternatives should I evaluate instead of aropixel/admin-bundle?: For Laravel, evaluate Laravel-native or Laravel-first admin tools such as Filament, Laravel Nova, Backpack for Laravel, or Orchid, depending on your licensing and architecture needs. If you specifically want Aropixel's CRUD generator concepts, compare them with Laravel generators and Livewire/Blade component workflows. AropixelAdminBundle remains a good fit only for Symfony applications, not Laravel.

Popularity trends

Recorded values over time (once-a-day snapshots). Oct 8, 2026 – Nov 6, 2026

GitHub · stars

GitHub · forks

GitHub · watchers

Packagist · monthly downloads

View on GitHub

Stars

Favorites

Forks

Score

28.4

Score breakdown

Sum of components, capped 0–100. Halved if archived.

Stars

input: 3

+0.0
Forks

input: 4

+0.1
Open issues + PRs

input: 0

+0.0
Releases

input: 31

+9.3
Recency

input: 30

+18.4
Issue opportunity

input: 0

+0.0
Laravel News mentions

input: 0

+0.0
Dependents

input: 0

+0.0

Total 27.8

Opportunity

29.9

Opportunity score breakdown

Hidden gem signal × 0.65 + contribution need × 0.35, scaled by health factor.

Hidden gem

log(monthly_downloads / (stars + 1)) × 25

46.3
Contribution need

open_issues + open_prs: 0

0.0
Health factor

archived + recency + open issues

×0.99

Total 29.7

License

MIT

Last release

Oct 7, 2026

Watchers

Downloads

281/mo

Dependents

Open issues

Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.

Add packages to context

No packages found.

dbravoan/dbcms-admin-theme-dbcms

dbravoan/dbcms-theme-db-cyber

dbravoan/dbcms-blocks-basic

dbravoan/dbcms-module-content-audit

dbravoan/dbcms-module-ai-assistant

paygate-to/paygate-php

padosoft/askmydocs-connector-base

defstudio/supercharged-carbon

bernskioldmedia/laravel-matomo

bernskioldmedia/laravel-harvest

bernskiold/laravel-data-scrubber

bernskiold/laravel-currency-converter

bernskiold/laravel-campaign-monitor

bernskioldmedia/laravel-autotranslate

siberfx/telegram-bot

roy-sandip/laravel-view-extended

gregsphotography/site-builder-core

roy-sandip/laravel-view

anodyne/blade-fluentui-icons

webx-ui/module-catalog-collections