- What is Cortex/Auth used for in Laravel?
- Cortex/Auth is the authentication and authorization module for the Cortex platform on Laravel. It provides controllers, views, routes, and assets for login, registration, password management, roles, permissions, guards, and an out-of-the-box user dashboard. It is intended for traditional server-rendered Laravel applications that want a ready-made user management layer.
- Is Cortex/Auth compatible with Laravel 10 or 11?
- The package is archived and does not publish an active Laravel version support commitment, so compatibility with Laravel 10 or 11 must be proven in a disposable test app. Check PHP and Laravel constraints, Composer resolution, and the maintenance status of its underlying Rinvex auth dependency. Do not assume current Laravel support without a version-compatibility spike.
- How do I install cortex/auth with Composer?
- Installation would start with Composer requiring cortex/auth in a Laravel application that matches the package's supported stack. Expect to publish and reconcile config, routes, views, assets, and migrations, then verify middleware, guards, and session settings. Because the repository is archived, pin exact versions and test installation in isolation before touching an existing auth setup.
- Does Cortex/Auth work with Laravel Breeze, Jetstream, or Fortify?
- It is not designed to coexist automatically with Breeze, Jetstream, Fortify, or custom Laravel auth scaffolding. Its routes, views, middleware assumptions, and user schema may collide with existing scaffolding, so integration requires publishing assets and reconciling route and guard behavior. For modern Laravel apps, first-party auth scaffolding is usually the safer baseline.
- Does Cortex/Auth support APIs, SPAs, or headless authentication?
- Cortex/Auth is a Blade-era monolith add-on, not an API-first or headless auth package. The assessment flags it as a poor fit for API-first, SPA, mobile-backend, or multi-tenant systems without significant rework. Teams building token-based or headless auth should evaluate maintained Laravel auth packages instead.
- How does Cortex/Auth handle roles, permissions, and guards?
- The package advertises roles, permissions, and configurable guards as part of its user management layer. Those features come through its opinionated auth model and underlying Rinvex dependency, so confirm the exact guard providers, role and permission schema, and policy behavior before adopting it. Test authorization checks and middleware assumptions against your application's existing policies.
- Is Cortex/Auth maintained and safe for production?
- No. The repository is archived, has 12 stars and zero dependents, and carries high technical risk because archived packages receive no security patches or upstream fixes. The dependency chain is the largest concern, especially if the underlying Rinvex auth package is also stale. Legal reuse under MIT does not remove the need for a security review and an exit plan.
- Can I customize the Cortex/Auth views, routes, and dashboard?
- The package ships views, routes, controllers, and assets intended to be published and adapted in a Laravel app. Customization is possible, but the assessment warns that route collisions, view overrides, and auth middleware assumptions are likely. If you need deep changes, fork the repository, pin versions, and document an upgrade or replacement path.
- What dependencies does Cortex/Auth require?
- Cortex/Auth is a frontend layer for the Rinvex auth package on Laravel, bringing controllers, views, routes, and assets for user management. The assessment specifically calls out the maintenance status of rinvex/laravel-auth as a key risk, while the overview references rinvex/fort. Verify the actual Composer dependency graph, PHP and Laravel constraints, and security posture before installation.
- What are alternatives to Cortex/Auth for Laravel authentication?
- For modern Laravel applications, prefer actively maintained first-party scaffolding such as Breeze, Jetstream, or Fortify, or build the dashboard in-house on a maintained auth foundation. If you only need patterns, treat Cortex/Auth as a reference implementation rather than a dependency. The assessment recommends adopt, fork, reference-only, or reject only after a time-boxed compatibility spike.