- Can I use endroid/google-api-bundle in a Laravel application?
- No. endroid/google-api-bundle is a Symfony bundle that registers google/google-api-php-client through AppKernel::registerBundles and YAML service configuration. It has no Laravel service provider, facade, publishable config, or package-discovery entry, so Laravel will not auto-wire it. You would have to hand-wire Symfony container assumptions, which is more work than using the underlying Google SDK directly.
- How do I install endroid/google-api-bundle?
- You can install it with Composer using endroid/google-api-bundle, but installation is only the first step. The README requires enabling EndroidGoogleApiBundle in app/AppKernel.php and adding endroid_google_api settings to config.yml, which are Symfony 2.x/3.x application conventions. Those steps do not map to a Laravel application, and the package is archived with no release discipline.
- What does endroid/google-api-bundle actually do?
- Its functional contribution is small: it registers google/google-api-php-client as a container service and exposes it as endroid.google_api_client. You provide application_name and api_key in YAML, then retrieve the client and instantiate Google service classes such as Google_Service_Translate. It is dependency-injection sugar of roughly 50 to 150 lines, not a full Google API abstraction or auth implementation.
- Is endroid/google-api-bundle compatible with Laravel 10 or 11?
- No supported compatibility path exists. The bundle targets Symfony 2.x/3.x components and legacy PHP, PSR, and Guzzle constraints, and it has been archived, so there is no PHP 8 or Symfony 5/6 work, let alone Laravel 10/11 support. Attempting to install it in a modern Laravel lockfile is likely to force unrelated downgrades. The project should be treated as evaluated and rejected for Laravel.
- What should Laravel developers use instead of endroid/google-api-bundle?
- Use google/apiclient directly, or the specific google-cloud-* package when the workload is Cloud Storage, Pub/Sub, or FCM. Wrap the client in an application-owned service class resolved from Laravel's container and bind it through a service provider. For Google sign-in specifically, laravel/socialite is usually the better fit than the raw API client. The correct framing is 'we need Google API access,' not 'we need this bundle.'
- Does endroid/google-api-bundle handle OAuth2 or service-account authentication?
- No, not in any way that has been reviewed or maintained recently. The bundle only injects a configured google/google-api-php-client instance; OAuth2 refresh-token handling, service-account key custody, and scope management remain your responsibility and depend on the SDK version. Because the wrapper predates the google/apiclient rename and the current credential model, its auth assumptions are stale and security-critical paths are unpatched.
- Is endroid/google-api-bundle maintained or production-ready?
- No. The repository is archived, has 2 stars, 0 dependents, and a maturity rating best described as README-only, with no evidence of tests, CI, or production use. Archival also means no CVE response, no PHP 8 compatibility work, and no adaptation to Google API changes. A 0.02 assessment score is consistent with something that should not enter a dependency graph.
- Why is the repository URL abandroid/google-api-bundle when the README says endroid?
- That mismatch is a supply-chain flag, not a cosmetic detail. The Composer package is published as endroid/google-api-bundle while the repository resolves to a personal account, abandroid/google-api-bundle, and the README credits endroid. An archived personal mirror of an abandoned bundle is a known risk shape, and Composer installs whatever name it is published under. Provenance must be answered before any code review or install.
- Can I test endroid/google-api-bundle or rely on its tests?
- Do not rely on tests here because the context shows no evidence of tests, CI, release discipline, or production use. The package is archived with a README-only maturity rating, so any testing you do would be your own integration testing against an unmaintained Symfony bundle. For a Laravel app, that effort is better spent testing a thin wrapper around google/apiclient that you own.
- What are the main risks of adding endroid/google-api-bundle to a Laravel project?
- Three risks compound: abandonment means no security or compatibility fixes; the auth surface covers OAuth2 refresh tokens, service-account keys, and scopes that nobody has reviewed or patched in years; and version resolution against Symfony 2/3, hard PHP upper bounds, and legacy Guzzle pins can conflict with a modern Laravel lockfile. The hidden cost often appears weeks later as unrelated downgrades. The integration approach is a replacement design, not a migration.