- What is TupleAuth and what problem does it solve in Laravel?
- TupleAuth is a Laravel authentication package that implements tuple-based credential checks, letting you verify users against composite credential sets inside Laravel's existing auth system. Its description also positions it as a fix for broken Laravel auth routes for developers who like Freek's controller simplification approach. The supplied metadata does not include source code or a README, so confirm the exact behavior against the repository before relying on it.
- How do I install edgrosvenor/tupleauth in a Laravel app?
- Install it with Composer using the package name edgrosvenor/tupleauth, and for evaluation pin the exact 0.1.3 tag rather than a floating constraint. The package is assumed to follow the standard Laravel package shape with a service provider, but the supplied metadata does not include a composer manifest or README, so verify auto-discovery and any manual provider registration step. After installing, check for publishable config or migrations and run your application's auth smoke path.
- Which Laravel versions does TupleAuth 0.1.3 support?
- The only release note for 0.1.3 says 'Allow for use in older Laravel apps', which indicates the Laravel constraint was widened but does not publish the exact supported matrix. Check the package's composer.json for the illuminate constraints and ask the maintainer which combinations are actually tested in CI. Do not assume every Laravel version inside the constraint range is covered.
- Is TupleAuth production ready?
- TupleAuth is at 0.1.3, which is pre-1.0 and pre-stability, so breaking changes are permitted on minor and patch releases under semver conventions. That makes it strongest for internal tooling, greenfield services, or non-critical auth paths, and weaker for customer-facing or load-bearing systems. If you adopt it, pin the exact version and plan to re-validate on each bump.
- Does TupleAuth work with older Laravel applications?
- Version 0.1.3 was released specifically to 'Allow for use in older Laravel apps', so that is the intended use case. The practical risk is that a widened Laravel constraint may not have been matched by a lower PHP floor or extended CI coverage. Verify the PHP minimum and the oldest Laravel and PHP pair your application needs before committing.
- How does TupleAuth integrate with Laravel's built-in auth system?
- The package is described as implementing tuple-based credential checks within Laravel's existing auth system rather than replacing it. That suggests it hooks into standard auth flows, but the supplied metadata does not include the service provider, config, or guard details. Confirm provider auto-discovery, any publishable config, and the exact guard or route wiring in a spike.
- How do I test TupleAuth before adopting it?
- Create a throwaway branch, require the exact 0.1.3 tag, and verify that the service provider registers. Publish and inspect any config or migrations, then run the package's documented smoke path plus your own login and credential-check tests. Repeat the spike on the oldest Laravel and PHP combination you intend to support, because compatibility shims often fail only there.
- What are the risks of the 0.1.3 compatibility widening?
- Relaxing Composer constraints expands the supported matrix, and if CI was not extended in lockstep, 'supported' can mean untested. Compatibility shims add version-conditional branches that are rarely exercised locally and can fail in production on the oldest supported version. A wider acceptable framework range can also resolve differently across applications, making bug reports harder to reproduce.
- Does TupleAuth have CI coverage for every supported Laravel version?
- The supplied metadata does not include CI configuration, so this cannot be confirmed from the release notes alone. Ask the maintainer which Laravel and PHP combinations actually run in CI and whether the 0.1.3 widening added those jobs. Treat any combination outside CI as unproven until you test it yourself.
- What is the upgrade path to TupleAuth 1.0 and will there be breaking changes?
- There is no published 1.0 plan in the supplied metadata, and the package is at 0.1.3. Under semver, 0.x releases may introduce breaking changes on minor or patch bumps, so assume the public API and configuration surface are fluid until 1.0. Ask the maintainer what 1.0 requires and how they will signal breaking changes.