- How do I install smorken/auth in a Laravel application?
- The package is hosted on Bitbucket rather than Packagist, so you need to add a VCS repository entry in composer.json and require it pinned to a branch or commit. Laravel service provider auto-discovery should register it, and you can publish the config and views if you need customization. Check the declared Laravel and PHP constraints in composer.json before installing.
- Which Laravel versions does smorken/auth support?
- The provided package overview does not state a verified Laravel or PHP version range. Inspect composer.json and test the package against your application's Laravel version before relying on it. This matters because Laravel auth internals have changed across major releases, especially around guards, password brokers, and recommended starter kits.
- Does smorken/auth replace Laravel Auth, Fortify, Breeze, or Sanctum?
- It is described as a helper that integrates with Laravel's native guards, middleware, and Eloquent user provider, not as a replacement for the framework's auth system. It should decorate framework contracts rather than introduce a parallel auth model. If you already use Fortify, Breeze, Jetstream, Sanctum, Passport, or an external identity provider, evaluate overlap carefully before adding it.
- Can I customize the login, registration, and password reset views and routes?
- Yes, the package advertises publishable config and views for customization, along with configurable routes, views, and guards. You can publish those assets and adapt them inside your application. Keep customizations maintainable and retest the flows after any package update.
- Does smorken/auth work with Laravel middleware and guards?
- Yes, native Laravel middleware and guard integration are core parts of its stated design. It also uses Eloquent-backed user authentication. Make sure any custom guard or provider configuration still follows Laravel's contracts so you do not create inconsistent security behavior.
- Is smorken/auth safe to use in production?
- Authentication is security-critical, and this package has little visible external scrutiny, no Packagist metadata, and a single-maintainer risk profile. That does not automatically make it unsafe, but it raises the trust cost of depending on it. For production, audit the guard wiring, check the license and test coverage, and have a fork or maintenance plan if upstream goes dark.
- How do I test smorken/auth authentication flows?
- The available context does not confirm whether the package ships a verified test suite. You should add application-level integration tests for login, registration, password reset, and route protection. If the repository includes tests, run them against a currently supported Laravel release in your CI pipeline.
- Is smorken/auth available on Packagist?
- No, the assessment states that it is Bitbucket-hosted rather than on Packagist or GitHub. That means you cannot rely on normal Packagist metadata, advisories, or dependency tooling. Install it through a Composer VCS repository entry pinned to a branch or commit for reproducible builds.
- What license does smorken/auth use?
- The license is not confirmed in the provided package information. Check the repository for a LICENSE file before using it commercially or redistributing it. Redistribution and audit obligations remain unknown until you verify the license.
- What alternatives to smorken/auth should I consider?
- Laravel's native auth features, Fortify, Breeze, Jetstream, Sanctum, Passport, or an external identity provider are the main alternatives depending on your use case. These options generally have stronger maintenance visibility and security reporting. Choose smorken/auth only if it strictly decorates Laravel's auth contracts and provides clear value beyond those framework-native options.