Weave Code
User Management Bundle Laravel Package
kunstmaan/user-management-bundle
Symfony bundle for user management in Kunstmaan applications, offering reusable user entities, registration, authentication integration, profile editing, password reset, and admin screens to help teams add and manage users with less boilerplate.
KunstmaanUserManagementBundle is a Symfony bundle that adds a ready-made user management layer to Kunstmaan-based applications. It provides the entities, admin screens, and services needed to create, edit, and organize users, while integrating cleanly with Symfony's security component for authentication and role handling.
- CRUD administration for users via the Kunstmaan admin interface
- Role and permission assignment built on Symfony security
- Configurable user entity and form types for project-specific fields
- Service-oriented architecture for extending or overriding behavior
- Twig templates and translations for quick UI integration
Frequently asked questions about User Management Bundle
- Can I use kunstmaan/user-management-bundle in a Laravel application?
- No. It is a Symfony bundle that requires the Symfony HttpKernel, dependency injection container, bundle registration, Doctrine ORM, Twig, EventDispatcher, and Symfony Security. Laravel has none of these primitives, and no adapter shim exists that makes a Symfony bundle run natively in Laravel. Embedding it would mean running a second framework kernel alongside Laravel, which is not a viable dependency.
- Does kunstmaan/user-management-bundle support Laravel 10 or 11 and PHP 8.2?
- No. The last release was 2014-04-22, and its Composer constraints target PHP 5.x and Symfony 2.x. A composer require against a modern PHP 8.2/8.3 and Laravel 10/11 matrix will almost certainly fail resolution. Forcing it with --ignore-platform-reqs is an automatic red flag in review.
- What features does kunstmaan/user-management-bundle actually provide?
- It provides user CRUD, groups, roles, permissions, and admin screens, plus back-office authentication and role-based access control integrated with Symfony Security. It was built for the Kunstmaan CMS distribution. The domain model and RBAC semantics are conceptually reusable, but the code is not.
- Is kunstmaan/user-management-bundle safe for production authentication?
- No. Vendoring abandoned 2014 authentication code into a 2025 application imports a decade of unpatched CVEs, obsolete password-hashing defaults such as MD5 or SHA1 with static salts, and session-handling and CSRF patterns that no longer reflect current guidance. This is a security-review blocker regardless of whether the functionality works.
- How do I install kunstmaan/user-management-bundle in a Laravel project?
- You cannot install it meaningfully in Laravel. Symfony usage requires bundle registration in AppKernel or bundles.php, services.yml or XML definitions, Doctrine entities and repositories, Twig, and security firewalls. There is no Laravel service provider, facade, or published config contract, and Composer resolution will likely fail before any of that matters.
- What are the best Laravel alternatives for user, group, role, and permission management?
- Use Laravel's first-party authentication scaffolding together with Gates and Policies, plus a maintained permission package for role and permission storage. The equivalent schema and RBAC semantics can be reimplemented natively in roughly one to two engineer-weeks. That compares favorably to the six to ten engineer-weeks estimated for a make-it-boot spike with a high probability of abandonment.
- Does kunstmaan/user-management-bundle have a REST or JSON API for SPAs and mobile apps?
- No. The admin UI is Twig-rendered and tightly coupled to Kunstmaan's backend node and CRUD abstractions. There is no headless JSON API, so it cannot serve an SPA, mobile client, or API-first product without a rewrite anyway.
- Why does kunstmaan/user-management-bundle use Doctrine instead of Eloquent?
- It is built for Symfony, so it uses Doctrine ORM entities and repositories following the Data Mapper pattern. Laravel uses Eloquent, an Active Record ORM, with a different container contract, its own Auth guard and provider abstraction, and Gates and Policies. There is no compatibility layer between these designs.
- Is kunstmaan/user-management-bundle actively maintained?
- No. It has 4 stars, 0 dependents, zero bus factor, and no downstream signal or issue activity, and its last release was in 2014. The Kunstmaan CMS lineage has moved on to a different generation of packages entirely. It will not receive PHP 8.x compatibility fixes, typed-property support, or PSR-4 and Symfony 5+ alignment.
- Can I fork kunstmaan/user-management-bundle and what is its license?
- The MIT license is clean and commercially permissive, so forking and modifying the code carries no legal friction. That is the one genuinely positive finding. However, you would inherit abandoned 2014 authentication code and make every future PHP upgrade a manual patching exercise against code nobody on your team wrote, so treat it as a reference implementation rather than a dependency.
Weaver
How can I help you explore Laravel packages today?