- Is perform/user-bundle compatible with Laravel?
- No evidence suggests Laravel compatibility. The package name and -bundle suffix follow Symfony convention, and the description says it is a Symfony bundle. Inspect composer.json for illuminate/* dependencies and a Laravel service provider before assuming it works in Laravel.
- Does perform/user-bundle support Laravel 11 or Laravel 10?
- There is no published support matrix, and the package appears to be Symfony-oriented. Zero stars and zero dependents mean no observable Laravel installations. Treat Laravel 10 and 11 support as unconfirmed until you verify framework constraints and run a sandbox spike.
- How do I install perform/user-bundle?
- For a Symfony app, install via Composer with composer require perform/user-bundle and register the bundle in bundles.php if not auto-discovered. For Laravel, do not install it until you confirm the package type and dependencies; a Symfony bundle will not auto-register as an Illuminate service provider.
- Is perform/user-bundle a Symfony bundle or a Laravel package?
- The naming strongly indicates a Symfony bundle, and the overview explicitly calls it a Symfony bundle for user management. Laravel packages typically omit the -bundle suffix and use Illuminate\Support\ServiceProvider auto-discovery. Confirm via the composer.json type and require sections.
- Can I use perform/user-bundle alongside Laravel Sanctum or Fortify?
- That is unverified and risky because the package may assert ownership of user entities, forms, and services. Laravel already provides Sanctum, Fortify, Breeze, and Jetstream for authentication and identity. Audit whether it replaces, wraps, or conflicts with those first-party tools before attempting coexistence.
- Does perform/user-bundle own the users table?
- The description does not say, and that is the decisive integration question. A package that owns the users schema is a migration project, not a drop-in integration. Inspect published migrations and diff them against your existing users and profile tables.
- Is perform/user-bundle production-ready and secure?
- It has zero stars, zero dependents, and no visible CVE or disclosure process, so there is no community safety signal. User management touches password hashing, sessions, reset tokens, and privilege checks, where defects are security incidents. Require internal review, a test audit, and a rollback plan before production use.
- Who maintains perform/user-bundle and is it actively maintained?
- The repository shows a single-maintainer pattern and no evidence of ongoing releases from the provided context. Bus factor and long-term support are open questions. Check commit history, issue responses, and license terms before depending on it.
- What are the best Laravel alternatives to perform/user-bundle?
- For Laravel, the first-party stack is Sanctum for API tokens, Fortify for authentication backends, and Breeze or Jetstream for scaffolding. These are free, maintained, and security-reviewed. A third-party user package must beat them on a specific requirement to justify inclusion.
- How should I test perform/user-bundle before adopting it?
- Run a sandbox spike only after confirming it is Illuminate-native. Check service provider registration, config and migration publish tags, supported PHP and Laravel versions, and auth edge cases like expired tokens and concurrent sessions. Fork to an internal namespace and stage a reversible migration with dual-read validation.