Weave Code
Auth Laravel Package
devdojo/auth
DevDojo Auth is a drop-in Laravel authentication package with prebuilt Blade components for login, registration, password reset, email verification, and two-factor auth, so you can add a complete, customizable auth UI in minutes.
DevDojo Auth is a drop-in authentication package for Laravel that gives you fully styled login, registration, and password-reset flows in minutes. It ships with customizable Blade components, built-in Tailwind CSS styling, and a simple config file, so you can match your app's design without writing repetitive boilerplate.
- Login, registration, password reset, and email verification out of the box
- Ready-to-use Blade components with clean Tailwind styling
- Social login (GitHub, Google, and more) via Laravel Socialite
- Two-factor authentication support
- Fully configurable routes, views, and redirects
Frequently asked questions about Auth
- How do I install DevDojo Auth in a Laravel application?
- Install it with Composer via composer require devdojo/auth, then rely on service-provider auto-discovery and publish the config, views, or migrations if the package offers those steps. After that you configure routes and mail, and confirm whether the package registers its own routes through the service provider or publishes them for you to own. Realistic effort is a few hours for a working spike and a few days for production hardening, because most of the cost is reconciling route names, middleware, and your design system rather than the install itself.
- Which Laravel and PHP versions does devdojo/auth support?
- The package targets a standard Laravel monolith with the default session guard and Eloquent user provider, but you should read the composer.json constraints to confirm the exact Laravel and PHP ranges before committing. Supported versions and a stated upgrade policy for new Laravel majors are flagged as open questions rather than guaranteed. If your app runs an older or very new Laravel release, verify compatibility first or plan to fork and own the code.
- Does DevDojo Auth replace Laravel's authentication or wrap it?
- It wraps Laravel's native authentication rather than replacing it: it rides on the Auth facade, the session guard, the Eloquent user provider, and the password broker, and it does not introduce new auth primitives. Its value is a ready-made, good-looking login flow, not a different security model. Still confirm during review that it does not override guards, the password broker, or hashing, since any of those would change the risk profile significantly.
- Can I customize the DevDojo Auth login and registration views?
- Yes, but the shipped screens are opinionated Blade and Tailwind, so customization usually means publishing and overriding the views. Once you republish them, treat those files as owned source rather than an upstream dependency, because heavy edits fork you from future package updates. Also check which Tailwind major version the views assume and whether they require a specific Vite or build setup that matches your app.
- Will DevDojo Auth conflict with Laravel Breeze, Fortify, or Jetstream?
- Yes, running two auth scaffolds side by side typically produces duplicate route names, competing middleware, and ambiguous view resolution. Pick one auth layer per application and remove or disable the other's routes and providers before installing DevDojo Auth. If your app already uses Breeze, Fortify, or Jetstream, this package is a poor fit unless you are deliberately replacing that scaffolding.
- What authentication features does DevDojo Auth include out of the box?
- The package ships registration, login, logout, password reset, email verification, and profile screens, which covers the common monolith auth flow. Features like remember me, two-factor authentication, social login, and account deletion are gaps you should verify in the source and be prepared to build yourself. Check the routes and controllers it actually ships so you know whether you get views only or the full set of routes, controllers, migrations, middleware, and notifications.
- Is devdojo/auth secure enough for production use?
- The package does not reinvent authentication, so conceptual risk is low, but it sits on the front door of every user account, so a security review is non-negotiable. Verify session regeneration on login and logout, login throttling via RateLimiter or ThrottleRequests, password reset token expiry and single-use semantics, email verification enforcement, remember-me handling, and CSRF coverage. The MIT license and small surface area are positives, but a convenience package can quietly omit these details, so audit before shipping.
- Can I use DevDojo Auth for an API or SPA with Sanctum?
- No, this is a session-based Blade and Tailwind scaffold for a standard Laravel monolith, so it is a poor fit for API-first apps, Sanctum token flows, or single-page frontends. It assumes the default App\Models\User model, the users table, the session guard, and the web middleware group. For an API or SPA you are better served by Sanctum plus your own controllers, or by Fortify for headless auth.
- How do I test authentication flows built with DevDojo Auth?
- First check whether the repository ships its own test suite, since the presence of tests is one of the key questions to answer before adopting it. In your app, write feature tests covering registration, login, failed login throttling, logout session invalidation, password reset, and email verification enforcement. Because the package publishes views and routes, assert on redirects and authenticated state rather than on rendered markup, which you are likely to customize.
- Is DevDojo Auth actively maintained, and what are the alternatives?
- The ecosystem signal is thin: roughly 622 GitHub stars but zero dependents and limited visible release history, so adopting it makes you an early adopter rather than a follower. DevDojo is a developer-education brand and packages are often companions to content, so set support expectations accordingly and confirm the maintainer bus factor plus a documented fork-and-own path. Laravel's own starter kits, Breeze, Fortify, and Jetstream cover the same job with a formal support commitment; DevDojo Auth differentiates on aesthetics and simplicity, not capability.
Weaver
How can I help you explore Laravel packages today?