Weave Code
Admin Bundle Laravel Package
kunstmaan/admin-bundle
Kunstmaan AdminBundle provides the administrative interface for the Kunstmaan CMS, offering reusable UI components, CRUD screens, media and user management, and extensible Symfony tooling for building content-driven applications.
KunstmaanAdminBundle provides a complete, extensible admin interface for Symfony applications and the Kunstmaan CMS. It bundles dashboard widgets, navigation, CRUD screens, and content management tools so teams can build and manage sites from one back office.
- Dashboard with configurable widgets
- Page/node management and tree navigation
- Media library and file management
- CRUD and form scaffolding
- Extensible admin UI and modules
Frequently asked questions about Admin Bundle
- Is kunstmaan/admin-bundle a Laravel package?
- No. It is a Symfony 2 bundle and a subtree split of the KunstmaanBundlesCMS suite, built on Symfony's HTTP kernel, dependency injection, Doctrine ORM, and Twig. Laravel's container, Eloquent, Blade, and middleware pipeline share no extension points with it, so it cannot be loaded as a Laravel package. Treat it as a reference artifact rather than a candidate dependency for a Laravel codebase.
- Can I install kunstmaan/admin-bundle in a Laravel application with Composer?
- Composer may attempt resolution, but the bundle pins Symfony ~2.x, Twig 1.x, and Doctrine 2.x, so installation against a modern Laravel project will almost certainly fail dependency resolution. Forcing it with --ignore-platform-reqs is likely to fatal at runtime on PHP 8 due to removed functions and dynamic property deprecations. There is no adapter layer that makes a Symfony bundle loadable into Laravel; cross-framework use would be a reimplementation.
- What Laravel versions does kunstmaan/admin-bundle support?
- None. The package has no Laravel service provider, facade, config publishing, or Artisan integration, and its last release was 2014-08-01, long before modern Laravel versions. Any claim of Laravel version support would be inaccurate.
- Which Symfony and PHP versions does kunstmaan/admin-bundle require?
- It targets Symfony ~2.3+ and PHP 5.x, with Twig 1.x and Doctrine 2.x dependencies. It does not run on Symfony 5, 6, or 7, or on PHP 8, without a port. Symfony 2 reached end of life in 2018–2019 and PHP 5.6 in 2018.
- Is kunstmaan/admin-bundle abandoned or still maintained?
- It shows clear signs of abandonment: the last release was 2014-08-01, it has roughly 58 stars and zero dependents, and its composite score is 1.16. There is no visible maintained fork in the dependent graph. The MIT license permits forking, but that turns a dependency decision into an owned product.
- What are the production and security risks of using kunstmaan/admin-bundle?
- Every transitive dependency is an unpatched security surface, including EOL Symfony 2, Twig 1.x, and PHP 5.x. Running it on modern PHP will trigger runtime fatals and deprecation issues, and there is no upstream security patch stream. Adoption would require an owner and budget for permanent maintenance, which is usually unjustifiable.
- What Laravel alternatives to Kunstmaan AdminBundle should I use for admin panels and CRUD?
- For Laravel, evaluate maintained packages such as Filament, Laravel Nova, and Backpack, which cover CRUD generation, media management, and role-based admin permissions. On Symfony, EasyAdmin and SonataAdmin are the maintained equivalents. Map each required Kunstmaan capability to one of these and evaluate them directly.
- How do I migrate a Kunstmaan AdminBundle admin interface to Laravel?
- Discard and substitute is the lowest-cost path: extract the admin UX and data model requirements, then rebuild them with a maintained Laravel admin package. Forking and porting the bundle to modern Symfony or Laravel is realistically multi-month work with no upstream to rebase against. Pattern extraction keeps the useful concepts without inheriting legacy code.
- Can I fork kunstmaan/admin-bundle and port it to modern Symfony or PHP 8?
- The MIT license allows forking, but a port means re-targeting Symfony 5+ bundle registration and DI, Twig 3 syntax and autoescaping, Doctrine ORM 3, and PHP 8.1+ compatibility. Realistically this is multi-month work, and it converts a dependency decision into an owned product with no upstream. Do it only if a unique Kunstmaan UI capability is business-critical.
- How should I test or evaluate kunstmaan/admin-bundle before adopting it?
- Start with a short spike rather than reading the README: confirm the actual target framework, then attempt Composer resolution in a disposable branch. Expect failure and verify whether any internal or community fork already exists. If the target is Laravel, close the evaluation and pivot to maintained alternatives.
Weaver
How can I help you explore Laravel packages today?