Weave Code
Filament Captcha Field Laravel Package
yepsua/filament-captcha-field
yepsua/filament-captcha-field adds a ready-made CAPTCHA form field to Filament admin panels, helping you protect forms from bots and spam with minimal setup. Drop it into resources and custom forms to validate submissions and keep automated abuse out of your Laravel app.
Filament Captcha Field adds a ready-to-use captcha form component to any Filament form, protecting login, registration, and contact pages without hand-rolled markup or validation.
Add it like any other field — Filament handles rendering, server-side validation, and error messaging. The provider and API keys are managed through a config file, keeping forms clean and secrets out of your code.
- Works in resources, pages, and Livewire forms
- Built-in validation rule with localized errors
- Configurable provider, site key, and secret
- Dark mode and responsive rendering
- One-line fluent field definition
Frequently asked questions about Filament Captcha Field
- Which Laravel and Filament versions does yepsua/filament-captcha-field support?
- The last release was February 2023, which predates Filament v3 and v4, so the composer.json almost certainly constrains filament/forms to the 2.x line. Check the package's composer.json and run composer why-not with your target Filament version before planning adoption. Also confirm the PHP and livewire/livewire constraints match your application.
- How do I install yepsua/filament-captcha-field in a Laravel app?
- Install it with Composer, then publish any config or assets the service provider exposes and add the field to your Filament form schema. Because the package is old, verify the dependency constraints first so Composer does not resolve a Filament 2-only version into a modern stack. If installation conflicts, treat vendoring the field as the fallback.
- Which captcha providers does this package support?
- The available material does not clearly establish which providers are supported, so inspect the config file and the validation rule before assuming reCAPTCHA, hCaptcha, or Turnstile works. Provider support matters because each service has different token fields and verification endpoints. Confirm the package sends the token to the provider's API server-side rather than only rendering a client widget.
- How can I bypass or fake the captcha in tests?
- There is no documented fake or bypass driver in the available material, which can make feature tests and CI brittle if the field always calls a captcha provider. Check whether configuration allows disabling verification in testing or local environments. If not, plan a custom validation rule or a test-only bypass before relying on this field.
- Are the captcha widget assets loaded from a CDN or published locally?
- Inspect the Blade view and service provider to see whether widget JavaScript is published locally or loaded from a CDN. A captcha field executes third-party script on public pages, so review the asset source, integrity attributes, and your Content Security Policy. Local publishing is usually easier to audit and control than an unpinned CDN reference.
- What happens if the captcha provider API is unreachable?
- Captcha verification usually adds a synchronous HTTP call into the form submission path, so provider or network failure can affect every legitimate submission. The documented failure policy is not clear from the available material; confirm whether the package hard-fails, soft-fails, or logs and allows. Set an explicit timeout and choose a named failure policy before production use.
- Is yepsua/filament-captcha-field actively maintained?
- The package's last release was in February 2023, it has few stars and no dependents, and it has had no release for roughly two and a half years. Treat it as frozen rather than actively maintained and pin the exact version if you adopt it. For long-term use, vendor or fork the small field, view, and validation rule instead of depending on upstream fixes.
- Can I use this package for public-facing forms outside the Filament admin panel?
- This package only pays off if you already render Filament forms on unauthenticated pages, such as standalone form usage, registration, contact, or support intake in a public panel. If your captcha need is a plain Blade and controller form, a Filament form field is the wrong tool. Confirm your use case before adopting it.
- How do I migrate this captcha field to Filament 3 or 4?
- Run composer why-not against your target Filament version as the first gate; a conflict on filament/forms or livewire/livewire is likely. The realistic path on Filament 3 or 4 is to copy the Field class and Blade view into app/Filament/Forms/Components and adapt them to the current schema, asset registration, and Livewire APIs. The artifact is small, so this is usually a low-cost port rather than a rewrite.
- What are alternatives if yepsua/filament-captcha-field won't install on Filament 3 or 4?
- If the package will not install, vendor the field into your application or maintain a hard fork; both are realistic because the component is small. You can also use a maintained captcha package or a custom Filament field backed by a server-side validation rule. Whichever route you take, add an explicit HTTP timeout and a test bypass.
Weaver
How can I help you explore Laravel packages today?