- What is Proviante Auth Bundle for Laravel?
- Proviante Auth Bundle is described as a Laravel/PHP authentication package that bundles login, registration, authorization, and account management into one installable solution. It is intended to provide configurable guards, middleware, and migrations to speed up secure application setup. The available evidence is limited, so treat the feature list as a starting hypothesis and verify it against the package code and configuration.
- How do I install proviante/auth-bundle in a Laravel application?
- Because the repository is hosted on a private GitLab instance, you will likely need to add a Composer repositories entry of type vcs or composer and distribute credentials to every developer machine and CI runner. After that, run composer require proviante/auth-bundle and check for service provider auto-discovery, publishable config, and migrations. Confirm the exact install steps in the package composer.json and README rather than assuming Packagist availability.
- Which Laravel versions does Proviante Auth Bundle support?
- The provided evidence does not list supported Laravel versions or illuminate/auth constraints. Check the package composer.json for Laravel framework and illuminate/auth version requirements, then compare them with your application's major version. Also confirm that the constraint admits your PHP version and that any lock file resolves cleanly in CI.
- Does Proviante Auth Bundle use Laravel's native authentication and hashing?
- This is not verified in the available evidence. Inspect the service provider and auth code to see whether it delegates to Laravel's AuthManager, Hash facade, and built-in rate limiting, or reimplements password hashing, token comparison, and session handling. For production use, prefer packages that delegate cryptographic operations to Laravel's built-in facilities rather than custom implementations.
- What guards and middleware does Proviante Auth Bundle provide?
- The package description mentions configurable guards and middleware, but the exact guard drivers, middleware aliases, and defaults are not documented in the evidence provided. Review the published config file and service provider registrations to identify what is added to your HTTP kernel and auth configuration. Test the middleware stack in a staging application before relying on it in production.
- Does Proviante Auth Bundle ship migrations that modify the users table?
- The package description says it includes migrations, but it is not clear whether they create new tables, alter an existing users table, or both. Inspect every migration before running it against an existing database, and take a backup or use a staging copy first. Published migrations against a live user table are a common source of irreversible production coupling.
- Is Proviante Auth Bundle safe for production use?
- The available assessment is built on a near-empty evidence set: a private GitLab host, no star count, no dependents, and no external adoption signal. Authentication code has a large blast radius, so a security review is non-negotiable before production exposure. Verify password hashing, token expiry, timing-safe comparison, rate limiting, session fixation handling, and supply-chain tracking yourself.
- How does Proviante Auth Bundle handle sessions, tokens, expiry, and revocation?
- The token and session model is not specified in the provided evidence. Determine whether it is Sanctum-style, Passport-style, custom, or cookie-only, and whether expiry, rotation, and revocation are implemented. Also check for hidden assumptions about session drivers, queues, or cookie settings that could surface late in integration.
- Can I use Proviante Auth Bundle with an existing Laravel user model?
- That is not confirmed by the available evidence. Auth packages often assume a specific user model shape, table name, or relationship structure, so inspect the configuration for a configurable model class and review any migrations for conflicts with your existing users table. Run an integration spike against a copy of your real schema before committing to the package.
- What are alternatives to Proviante Auth Bundle, and is it maintained?
- Laravel Breeze, Jetstream, Fortify, Sanctum, and Passport cover many common authentication and API-token needs, depending on your requirements. Maintenance of Proviante Auth Bundle is unclear from the evidence: it has a single author handle on a private host, no stars, no dependents, and no visible release cadence. Track its security posture internally and confirm maintainer ownership before making it a long-term dependency.