Weave Code
Auth Laravel Package
laravelcollective/auth
Legacy Laravel Collective authentication scaffolding for Laravel apps, providing login, registration, password reset, routes, controllers, and views to help add session-based user authentication quickly.
The replacement for Laravel UI backend Auth components
Frequently asked questions about Auth
- What is laravelcollective/auth used for?
- laravelcollective/auth is legacy Laravel Collective authentication scaffolding intended as a replacement for Laravel UI backend auth components. It provides login, registration, password reset, routes, controllers, and views for session-based authentication. It is best treated as a compatibility or reference package for Laravel UI-era applications, not as a modern default auth dependency.
- How do I install laravelcollective/auth with Composer?
- The Composer package name is laravelcollective/auth, so installation would typically start with composer require laravelcollective/auth. However, the package has very low adoption and unclear version constraints, so verify the Packagist metadata and Composer constraints in an isolated branch first. Do not install it on a production auth path until license and Laravel compatibility are confirmed.
- Which Laravel and PHP versions does laravelcollective/auth support?
- The available context does not publish a clear Laravel or PHP compatibility matrix for laravelcollective/auth. You should inspect its composer.json constraints and test it against your exact Laravel and PHP versions before considering adoption. Treat unknown compatibility as a blocker for production use.
- Is laravelcollective/auth actively maintained?
- There is no clear maintenance signal in the provided context, and the package shows very low adoption with only 13 stars and a score of 0.155. Teams should expect to own patches, security reviews, and future Laravel upgrade compatibility if they adopt it. Monitor upstream activity and plan either a maintained fork or migration away.
- What license does laravelcollective/auth use?
- The license status is reported as NOASSERTION, meaning the actual license is unresolved in the available context. Legal review is required before any commercial use, distribution, or production dependency. Do not ship laravelcollective/auth until the license is clarified in writing.
- Does laravelcollective/auth conflict with laravel/ui, Fortify, Sanctum, or Passport?
- Because laravelcollective/auth targets Laravel UI backend auth components, it can conflict with overlapping auth routes, controllers, middleware, and session behavior. Fortify, Sanctum, and Passport use different auth models and should not be mixed without careful route and middleware testing. Run a branch-level proof of concept to identify route collisions and duplicate auth flows before adoption.
- What authentication features are included in laravelcollective/auth?
- Based on the package description, it provides backend auth scaffolding for login, registration, password reset, routes, controllers, and views. It is positioned as a backend replacement for Laravel UI auth components rather than a full frontend scaffold. Verify whether it also includes configuration, email verification, remember-me behavior, and views in your target version.
- Is laravelcollective/auth safe for production authentication?
- Authentication is security-critical, and laravelcollective/auth carries high risk due to low adoption, unclear maintenance, unresolved licensing, and unknown Laravel compatibility. It should not be used as a default dependency or on a critical production path without legal review, security audit, and automated auth flow tests. If upstream is unmaintained or the license remains unclear, do not ship it as a production dependency.
- What are the best alternatives to laravelcollective/auth for Laravel authentication?
- Laravel’s maintained paths are Fortify, Breeze, Jetstream, or native framework auth primitives, depending on whether you need backend-only, starter kit, or full application scaffolding. For API authentication, consider Sanctum or Passport instead of legacy session scaffolding. Greenfield and modern Laravel applications should generally avoid laravelcollective/auth unless they specifically need Laravel UI-era backend compatibility.
- How do I migrate from laravelcollective/auth to Laravel Breeze or Fortify?
- Inventory existing auth routes, controllers, middleware, views, password brokers, and mail flows before changing anything. Run a branch-level proof of concept comparing behavior against your current Laravel UI or laravelcollective/auth setup, and document exact deltas. Add automated tests for login, logout, registration, password reset, session invalidation, and route conflicts, then replace the package with a maintained Laravel auth path using a canary rollout and rollback plan.
Weaver
How can I help you explore Laravel packages today?