- Is th3mouk/cms-user-bundle a Laravel package?
- No. th3mouk/cms-user-bundle is a Symfony bundle and a renamed fork of sonata-project/user-bundle, built around Symfony kernel bundles, dependency injection, Doctrine mapped superclasses, and Sonata Admin. It has no Laravel service provider, facade, publishable config, or Laravel-style migrations. Treating it as a Laravel package is a stack mismatch.
- How do I install th3mouk/cms-user-bundle in Laravel?
- You should not install it in a Laravel application. Composer may download the code, but Laravel package discovery will not register it because there is no Laravel service provider or bootstrap file. Making it run would require bootstrapping Symfony's HttpKernel, EventDispatcher, Form component, and Sonata Admin alongside Laravel's kernel, which is a parallel framework for authentication. Use Laravel-native auth packages instead.
- Which Laravel versions does th3mouk/cms-user-bundle support?
- None. The package targets the Symfony and Sonata ecosystem, not Laravel, so it has no declared Laravel version constraints or compatibility layer. Its real constraints are Symfony and Sonata Admin versions, and the fork's pinned requirements may hold a host app to older, unsupported majors. For Laravel version compatibility, choose a maintained Laravel package.
- Can I use th3mouk/cms-user-bundle for user authentication in Laravel?
- No, not without running Symfony inside Laravel, which is not a sensible design for auth. The bundle's user model, roles, password handling, and admin impersonation are wired to Symfony services and Sonata Admin, not Laravel guards, Eloquent, or middleware. Laravel's built-in auth with spatie/laravel-permission and Filament or Nova covers admin-managed users, roles, and access without a second framework. Authentication is too sensitive for a coexistence hack.
- What is the difference between th3mouk/cms-user-bundle and sonata-project/user-bundle?
- Functionally, very little: th3mouk/cms-user-bundle is a renamed fork of sonata-project/user-bundle. The meaningful differences are the package name and any local patches the fork carries, which you must diff against upstream at the pinned version. It has zero stars, zero dependents, and no visible release cadence, while upstream has the community and maintenance history. In a real Symfony/Sonata app, depend on sonata-project/user-bundle directly unless the fork patches something you can prove you need.
- Does th3mouk/cms-user-bundle work with Symfony 6 or Symfony 7?
- There is no evidence of Symfony 6 or 7 support in the provided assessment. Symfony has moved through 5, 6, and 7, and Sonata Admin is on 4.x, while an unreleased fork tends to pin a host app to dead majors. Check the composer.json constraints and diff against upstream before assuming compatibility. If you are on a supported Symfony version, use the maintained upstream bundle.
- How do I configure th3mouk/cms-user-bundle?
- Configuration is Symfony-style, through bundle registration, dependency injection service definitions, and Sonata Admin wiring, not through a Laravel config file you can publish. There is no Laravel publishable config or environment-driven config in the Laravel idiom. In a legacy Symfony/Sonata app, follow the upstream sonata-project/user-bundle docs, because the fork's docs are not a reliable separate source. For Laravel configuration, this package has nothing to publish.
- Is th3mouk/cms-user-bundle safe for production?
- The assessment rates technical risk as high, especially for production authentication. The package has zero stars, zero dependents, no visible maintainers, no release cadence, and no evidence that security patches from upstream will flow to it. An unmaintained user and auth dependency is a high-severity supply-chain surface covering user tables, roles, password handling, and admin impersonation. Do not put it on a revenue-critical auth path.
- What are the best Laravel alternatives to th3mouk/cms-user-bundle for user management?
- For Laravel, use the built-in authentication scaffold plus spatie/laravel-permission for roles and permissions, and Filament or Laravel Nova for admin-managed users. Those packages are Laravel-native, maintained, and integrate with Eloquent, middleware, guards, and migrations. If you need audit trails, choose a maintained Laravel audit package rather than a Symfony/Sonata bundle. The functional need is covered without crossing frameworks.
- Is th3mouk/cms-user-bundle maintained?
- The signals say no: zero stars, zero dependents, score zero, and no evidence of issue triage or release cadence. It appears to be a personal or single-project fork, likely created to satisfy a composer.json name in one CMS build. If a legacy Symfony/Sonata app depends on it, diff it against upstream and plan a contingency to vendor and patch or migrate to sonata-project/user-bundle. For Laravel, close it as a false positive and deny-list it.