Weave Code
Users Security Bundle Laravel Package
smartassert/users-security-bundle
Symfony bundle for adding user security to your application, offering a foundation for authentication, user management, and related security services. It provides reusable components and integration points to implement protected user flows with less boilerplate and configuration.
SmartAssert Users Security Bundle is a Symfony bundle that provides a complete user authentication and security layer for your applications. It handles user accounts, credential verification, and access control, letting you focus on building features instead of reinventing authentication.
- User management with registration, profiles, and password handling
- Authentication services and Symfony security integration
- Role-based access control for protecting routes and resources
- Configurable via bundle settings with sensible defaults
- Testable, service-oriented design for clean integration
Frequently asked questions about Users Security Bundle
- Is smartassert/users-security-bundle a Laravel package?
- No. It is a Symfony bundle that registers Symfony dependency-injection services and security integration, not Laravel service providers, guards, or middleware. Laravel cannot load the bundle natively. The only plausible reuse path for Laravel is extracting or depending on the underlying smartassert user-security domain library and writing thin Laravel adapters.
- Can I install smartassert/users-security-bundle in a Laravel app with Composer?
- Composer can install the package, but Laravel will not auto-discover or boot a Symfony bundle. You would have to manually wire any reusable domain services or bypass the bundle wrapper entirely. For production authentication, a small first-party Laravel adapter or a Laravel-native package is usually safer.
- Does this package support Laravel 10, 11, or 12?
- There is no evidence of claimed Laravel support. The package is a Symfony bundle with Symfony component constraints, so Laravel version compatibility is not guaranteed. You must verify PHP and Symfony constraints in composer.json and test any adapter yourself before relying on it.
- How do I integrate this bundle's authentication with Laravel guards?
- You cannot use the bundle's Symfony firewall factory directly in Laravel. A realistic approach is to use the underlying user-security domain library and write a custom Laravel guard, user provider, and middleware for token validation. Keep domain objects at the boundary and map them to Eloquent models rather than leaking them into controllers or Blade views.
- What does the UsersSecurityBundle actually register in Symfony?
- As a Symfony bundle it likely registers service definitions, configuration trees, compiler passes, and possibly a security firewall factory. Those are Symfony DI artifacts that Laravel's container does not load natively. Inspect the bundle class and services configuration to confirm exactly what is registered before planning any integration.
- Is it safe to use this low-adoption Symfony bundle for production auth?
- Authentication is security-critical, and this package has very low adoption and zero dependents, which means little third-party validation and no observable security-advisory surface. The release date and single-maintainer model also need confirmation. Only proceed if you can audit the small code surface, pin versions, and accept responsibility for security patches.
- Can I reuse the smartassert user-security domain library without Symfony?
- Possibly, if the domain layer avoids Symfony contracts such as UserInterface, PasswordAuthenticatedUserInterface, and event dispatchers. You need to verify composer.json and the source for framework coupling. If the domain is clean, implement Laravel-specific adapters for persistence, hashing, and token validation.
- Does this bundle implement password hashing itself or use PHP password_hash?
- The provided context does not confirm which approach the package uses. Inspect the code before committing: custom hashing increases migration cost and security review burden. If it delegates to PHP's native password_* functions, adapter work is simpler and safer.
- What are alternatives for Laravel user security and roles?
- Laravel's built-in auth, Sanctum, Fortify, and packages like spatie/laravel-permission cover typical application needs. For services authenticating with an external users service, a small custom guard plus a maintained SDK is usually safer than porting a Symfony bundle. Choose Symfony integration only when the target application is actually Symfony.
- How should I test a Laravel adapter for this Symfony bundle?
- Test the adapter contract rather than the bundle internals: user lookup, credential verification, token validation, and middleware behavior. Use integration tests against a real users-service stub or container, and run static analysis on the adapter. Pin the domain library version so upstream changes cannot silently break authentication.
Weaver
How can I help you explore Laravel packages today?