- Is baks-dev/auth-yandex compatible with Laravel?
- No. baks-dev/auth-yandex is a Symfony bundle, not a Laravel-native package, and it depends on Symfony console commands, Doctrine migrations, Symfony assets, and dependency injection. Using it in Laravel would require a significant adapter or fork and is a poor architectural fit. Laravel teams should prefer a Socialite-based Yandex provider or a thin custom OAuth2 integration.
- How do I install baks-dev/auth-yandex?
- Install it with composer require baks-dev/auth-yandex in a compatible Baks/Symfony application. Create a Yandex ID for site application, set the redirect URI to https://<DOMAIN>/auth/yandex, and add YANDEX_CLIENT_ID and YANDEX_CLIENT_SECRET to .env. Then run php bin/console baks:assets:install and apply Doctrine migrations with doctrine:migrations:diff followed by doctrine:migrations:migrate.
- What PHP version does baks-dev/auth-yandex require?
- The package requires PHP 8.4 or newer according to its README badge. The technical evaluation also ties it to a Symfony 7.4+ stack through baks-dev/core ^7.4. That PHP requirement may force framework upgrades or polyfills in older Laravel or Symfony applications.
- How do I set the Yandex ID redirect URI for baks-dev/auth-yandex?
- In the Yandex ID for site application settings, configure the redirect path as https://<DOMAIN>/auth/yandex. The package expects that callback route to complete the Yandex authorization flow. Ensure the domain and scheme exactly match your deployed application, including staging and production hosts.
- What database migrations does baks-dev/auth-yandex run?
- The package uses Doctrine ORM migrations, and the README instructs you to run doctrine:migrations:diff and doctrine:migrations:migrate. The exact schema is not documented in the excerpt, so inspect the generated migration before applying it. Mapping that schema to Laravel Eloquent would require review and translation, not a drop-in migration.
- How do I test the Yandex authorization flow in baks-dev/auth-yandex?
- The README shows php bin/phpunit --group=auth-yandex for the package test group. For real confidence, run an end-to-end flow with Yandex sandbox credentials covering success, denial, callback errors, token refresh, and edge cases. Public test coverage and security advisories are not documented, so independent verification is prudent.
- What Laravel package should I use for Yandex login instead?
- For Laravel, use Laravel Socialite with a Yandex provider such as socialiteproviders/yandex, or write a small custom Socialite driver. That keeps authentication in Laravel's session, CSRF, and guard systems and avoids bridging Symfony console, Doctrine, and asset pipelines. A native Socialite integration is usually lower risk and faster to maintain.
- Is baks-dev/auth-yandex production-ready and actively maintained?
- Treat it cautiously. The evaluation notes 0 stars, 0 dependents, sparse Russian-only documentation, and a suspicious last release date of 2026-05-07 that should be verified. There is no documented security advisory history or test coverage summary. Pin versions, review the OAuth2 code, and monitor baks-dev/core releases if you adopt it.
- Does baks-dev/auth-yandex support token refresh, revocation, or multi-tenant credentials?
- The README does not document token refresh, revocation, or per-tenant credential scoping. The core flow is standard Yandex OAuth2 authorization code exchange with user mapping, but storage and lifecycle details must be confirmed in the code and schema. Multi-tenant use would likely require custom work or a different integration.
- What does the baks:assets:install command do in baks-dev/auth-yandex?
- It installs the package configuration and file assets through the Symfony console, as shown by php bin/console baks:assets:install. In a Laravel application that step does not translate directly and should be replaced with Vite or Mix handling for any auth button or JavaScript assets. The evaluation suggests those assets are likely minimal, so reimplementation is low effort.