- Does germey/geetest support Laravel 8, 9, 10, or 11?
- No. The package targets Laravel 5 and its last release was in 2020, before modern Laravel versions existed. Composer constraints and PHP assumptions will likely block installation on Laravel 8 and newer without a fork. For current Laravel versions, use the official Geetest SDK behind a thin internal adapter instead.
- How do I install germey/geetest in a Laravel 5 application?
- Install it with Composer, then register or auto-discover the service provider and publish the package configuration. Add your Geetest public and private keys to the published config, render the widget in your Blade form, and apply the package validation rule server-side. Verify the installed version's README because Laravel 5 provider and alias registration conventions vary by minor version.
- Which Geetest API version does germey/geetest target?
- The package wraps the Geetest slider verification flow of its era, which is closest to the v3-style challenge and validate endpoints. The repository does not clearly document a v4 or newer API target, so confirm the exact endpoints in the source before relying on it. Test against your Geetest account's current product configuration, because stale API assumptions are a real risk.
- Does germey/geetest enforce server-side validation by default?
- It provides server-side validation rules and helpers, but enforcement depends on you actually applying them to the request in your controller or form request. Rendering the widget alone does not protect the endpoint. Treat any flow without the server-side rule as unprotected and add explicit validation plus failure logging.
- Do I need to add the Geetest JavaScript manually?
- In most Laravel 5 setups you still need to include the Geetest client script and initialize the widget in your Blade view. The package's Blade helpers reduce boilerplate, but they are not a full asset pipeline. Confirm that the client script version matches the API version the package calls server-side.
- Is germey/geetest safe to use in production?
- Treat it as a tactical accelerator, not a strategic dependency. It has a single maintainer, no evident automated test suite, and a 2020 release targeting end-of-life Laravel 5, so budget for pinning, security review, and possibly an internal fork. Wrap it behind a CaptchaVerifier interface and roll it out to one low-risk flow first while monitoring failure rates.
- What PHP versions does germey/geetest support?
- Because it targets Laravel 5, expect support for PHP 5.5 through 7.x era runtimes rather than PHP 8. Check the package's composer.json constraints against your actual PHP version before planning integration. If you need PHP 8, plan on a fork or replacement rather than assuming it will work.
- What are good alternatives to germey/geetest for Laravel CAPTCHA?
- For modern Laravel, prefer the official Geetest SDK wrapped in your own service class, or a maintained CAPTCHA package that supports your Laravel version. If you must stay on Laravel 5, an internal fork of this package behind an interface is often safer than depending on upstream. Avoid spreading facade calls and package config across controllers so replacement stays cheap.
- How should I test Geetest CAPTCHA validation in Laravel feature tests?
- Put the package behind a CaptchaVerifier interface and swap in a fake implementation during tests so feature tests do not call Geetest. Add a small number of staging end-to-end tests that exercise the real widget and server-side validation. Also test the failure path, including what happens when Geetest is unavailable or returns an error.
- Who maintains germey/geetest and is it still actively updated?
- It is a single-maintainer package with roughly 156 stars and no release since 2020, so treat it as abandoned or minimally maintained. Upstream fixes for PHP 8, newer Laravel versions, or Geetest API changes are unlikely. Decide early who owns an internal fork if your application must remain on Laravel 5.