Weave Code
User Bundle Laravel Package
integrated/user-bundle
Integrated User Bundle provides a ready-to-use user management layer for Symfony applications, covering user entities, registration, authentication, and profile workflows. It helps reduce boilerplate and integrate common account features cleanly into existing projects.
Integrated User Bundle
Frequently asked questions about User Bundle
- Is integrated/user-bundle a Laravel package or a Symfony bundle?
- It is packaged as a Symfony bundle, using the -Bundle convention, services.yaml configuration, and security firewalls. Laravel cannot boot it as a dependency because it has no Laravel service provider or Laravel-native configuration. Treat it as Symfony-targeted code, or at best harvest its domain logic and reimplement the framework glue natively.
- Can I install integrated/user-bundle in a Laravel application with Composer?
- You can add a VCS repository entry pointing at the Bitbucket Git URL and require the package by name, but installing it is not the same as it working. Laravel will not register the bundle or read its Symfony configuration. There are no tagged releases, so pin to a commit SHA if you only want to inspect the source.
- Which Laravel versions does integrated/user-bundle support?
- None are documented, and the bundle targets Symfony's DI container and security component rather than Laravel's Auth manager. There is no evidence of Laravel 10, 11, or 12 support. Assume no Laravel compatibility until the maintainers explicitly state otherwise.
- How do I install integrated/user-bundle without Packagist?
- Add a Composer VCS repository entry for the Bitbucket URL and require the package by name, using a commit SHA because no version tags exist. Every CI pipeline will then need credentials for that private remote. Vendoring the source is often a cleaner alternative for a one-off evaluation.
- Does integrated/user-bundle include a license for commercial use?
- No license metadata is published, which is a procurement blocker for SaaS or redistribution. Without an explicit license you have no granted rights to use, modify, or ship the code. Get written clarification from the maintainers before any commercial adoption.
- Is integrated/user-bundle safe to use in production for authentication?
- Risk is high because there are no version tags, no changelog, no adoption signal, and no stated owner for security patches. Authentication and PII handling demand a maintained dependency with a disclosure process. A timeboxed audit of the login, logout, password reset, and role enforcement paths is the minimum bar before production.
- Does integrated/user-bundle work with Eloquent or does it require Doctrine?
- Its storage adapters are Symfony-oriented and may pull in Doctrine, which would add a second persistence layer to an Eloquent application. Running dual ORMs is a permanent cognitive and maintenance tax that rarely pays for itself. Confirm the ORM dependency before estimating any integration work.
- Will integrated/user-bundle conflict with Laravel's built-in authentication?
- Likely yes. If the bundle ships its own guards, password hashing, or session handling, it will collide with Laravel's Auth manager and existing users table. Ask the maintainers whether it owns the guard or is designed to sit behind one. In most Laravel hosts it is safer to reuse its domain concepts and rebuild the glue natively.
- What are the alternatives to integrated/user-bundle for Laravel user management?
- Laravel Breeze, Jetstream, and Fortify cover registration, login, password reset, and role-based access with first-party maintenance. For Symfony hosts, maintained Symfony Security components and MakerBundle-generated user flows are the safer route. Use integrated/user-bundle only as a reference implementation for entity and role design.
- Does integrated/user-bundle have tests covering login, logout, and password reset?
- Test coverage is not publicly documented, and the authentication paths are exactly where you need confidence. Ask maintainers for coverage of login, logout, password reset, and role enforcement before committing. Run the suite yourself during a two-to-three day audit if repository access is granted.
Weaver
How can I help you explore Laravel packages today?