- Is lasso/oauth2-client-bundle a Laravel package?
- No. It is a Symfony bundle that ships a Bundle subclass and DI extension, with no Laravel service provider, facade, config publishing, or package discovery. Using it in Laravel would require pulling in Symfony kernel, config, DI, and event dispatcher components. That is disproportionate for a single OAuth2 client.
- Can I install lasso/oauth2-client-bundle in Laravel 10 or 11?
- Almost certainly not. The last release was in 2014 and targets PHP 5.4-5.6 era code, while Laravel 10 and 11 require PHP 8.1 or newer. Composer resolution will likely fail, and even if forced, deprecated constructs may break at runtime. Treat it as incompatible.
- How do I install and configure lasso/oauth2-client-bundle?
- There is no Laravel installation path. In Symfony you would register the bundle and configure it through the DI extension and Configuration tree, but that contract does not exist in Laravel. There is no config publishing, facade, or service provider. Do not attempt a drop-in install.
- Does lasso/oauth2-client-bundle support OAuth2 authorization code flow with PKCE?
- The package predates PKCE (RFC 7636), state as a normative requirement, OpenID Connect, and modern redirect-URI hardening. Its grant flows may follow an older OAuth2 draft rather than RFC 6749 and 6750. Do not assume PKCE or OIDC support. Verify against the source if evaluating for reference only.
- Is lasso/oauth2-client-bundle safe for production credential handling?
- High risk. It has zero stars, zero dependents, no issue activity, and no commits since 2014, so there are no security patches. It likely pins abandoned Guzzle and Symfony 2.x branches with unpatched advisories, and composer audit will likely fail. A dormant repo is a poor trust anchor for OAuth2 credentials.
- What are alternatives to lasso/oauth2-client-bundle for Laravel?
- Use league/oauth2-client with a provider package, the de facto PHP standard, PSR-18 and PSR-17 based and actively maintained. Use laravel/socialite only for user-facing social login, and the Laravel HTTP client for simple token calls. laravel/passport is for issuing tokens, not consuming them. These fit Laravel idiomatically.
- How do I test OAuth2 integration if I port logic from this bundle?
- Port only non-obvious client or token behavior, then wrap it in a Laravel service provider and test with HTTP fakes. Use Illuminate\Support\Facades\Http::fake to stub token and userinfo endpoints. Cover refresh, error responses, and state validation. A plain authorization-code client rarely justifies porting this specific code.
- What Laravel versions and PHP versions does lasso/oauth2-client-bundle support?
- It was released in 2014, targeting PHP 5.4-5.6 era code with no scalar or return types and no strict_types. Laravel 10 and 11 require PHP 8.1 or newer, so it is a hard blocker before functional concerns. No modern Laravel version is supported.
- Is lasso/oauth2-client-bundle maintained or abandoned?
- Abandoned. The last release was 2014-07-08, with zero stars, zero dependents, and no issue activity. Twelve years without a commit means no security patches. The 0.2 score reflects unassessed, not assessed as adequate. Do not rely on it.
- Should I bridge Symfony components to use this bundle in Laravel?
- No. Bridging would pull symfony/http-kernel, symfony/config, symfony/dependency-injection, and symfony/event-dispatcher into vendor just to get one HTTP client wrapper. The cost is wildly disproportionate to value. Treat the repository as reference material at most, or use a maintained Laravel-native alternative.