Filament Grecaptcha Field Laravel Package

Product Decisions This Supports

• Build vs. buy for bot mitigation in admin/forms: This package wraps Google reCAPTCHA as a drop-in Filament form field. It supports the decision to buy/integrate rather than hand-roll a CAPTCHA component, since the integration surface (field rendering, validation rule, config publishing) is already solved and maintained.
• Admin panel hardening roadmap: If your product exposes public-facing or low-trust forms (registration, contact, support intake, lead capture) inside a Filament panel, this directly enables a "spam & abuse reduction" roadmap item without a custom frontend effort.
• Framework upgrade sequencing: The v0.0.12 release adds Filament 5.0, Laravel 13, and PHP 8.4 compatibility. This unblocks the decision to schedule a Filament 4→5 / Laravel 12→13 upgrade, and removes this package from the list of upgrade blockers to track.
• Vendor/dependency risk posture: The release is a compatibility patch with no new features or API changes. Signal for the roadmap: the package is being kept current with the ecosystem, but remains on a 0.0.x version line — plan for it as a low-ceremony utility dependency, not a strategic platform component.
• Compliance and privacy scoping: Because reCAPTCHA is a Google-hosted service, adoption forces a third-party data-processing review (user IP/behavior sent to Google). This is a product decision to make before rollout, particularly for EU/UK-facing surfaces and any regulated data flows.

When to Consider This Package

Adopt when:

• You run a Filament admin/app panel and need CAPTCHA on one or more forms with minimal code.
• Your team has already (or is willing to) standardize on Google reCAPTCHA v2/v3 — i.e., the vendor choice is settled and the only open question is the Laravel integration.
• You are on, or upgrading to, Filament 5 / Laravel 13 / PHP 8.4 — v0.0.12 explicitly targets this matrix, which is the main reason to pin to this version.
• You want configuration-driven keys and per-field validation rather than a bespoke validation rule maintained in-house.

Look elsewhere when:

• You need privacy-preserving or self-hosted CAPTCHA (hCaptcha, Turnstile, Friendly Captcha, ALTCHA). This package is Google-specific; choosing it forecloses that option without a swap.
• You are not on Filament. The value is the Filament field integration; outside Filament you'd use the underlying reCAPTCHA validation directly and skip this dependency.
• You need a stable, semantically-versioned dependency. 0.0.x means no API stability guarantee. For a large, long-lived platform, weigh whether a thin in-house field (typically a few dozen lines) is more predictable than tracking an early-stage package.
• Your threat model is advanced abuse (credential stuffing, headless-browser farms, API-level bots). reCAPTCHA on a form field is a baseline signal, not a full bot-management solution — pair it with rate limiting and server-side heuristics regardless.
• Filament 5 is not yet your target. If you're staying on Filament 4, confirm backwards compatibility before upgrading; the release bumps composer.json for Filament 5, which is the kind of change most likely to shift constraints.

Adoption caveats to verify before committing: whether the Filament 5 bump is additive (supports 4 and 5) or a hard constraint change; test coverage status; and whether the 0.0.11→0.0.12 diff includes anything beyond the two linked PRs.

How to Pitch It (Stakeholders)

For executives — the one-liner:

A small, free, community-maintained add-on that lets us put Google reCAPTCHA on our Filament admin forms in minutes instead of building it ourselves. The new release keeps it current with our planned Filament 5 / Laravel 13 / PHP 8.4 upgrade.

Why it matters commercially: spam and bot submissions on signup, contact, and support forms cost real money in support triage and pollute CRM and analytics data. This closes that gap with essentially zero engineering spend, and critically it does not block our platform upgrade — the latest version is already compatible with our target stack.

For engineering — the summary:

• Thin wrapper providing a Filament form field plus reCAPTCHA validation and publishable config. Keys are configuration-managed; per-form opt-in.
• v0.0.12 is a compatibility release, not a feature release: Filament 5 constraint update (#17) and Laravel 13 / PHP 8.4 support (#18). No breaking API changes signalled, but the composer.json change is the item to validate against our current Filament version.
• Cost of adoption: low — a dependency, a config publish, and a key pair per environment.
• Cost of exit: low — the integration is shallow; swapping to Turnstile or hCaptcha is a contained change limited to the field and its validation.
• Residual risks to accept explicitly: (1) 0.0.x versioning — no semver stability promise, so pin the version and read changelogs on upgrade; (2) single-maintainer / small-contributor base — mitigate by keeping the swap cheap rather than by avoiding the package; (3) third-party data flow to Google — requires a privacy review for EU-facing forms, which is a policy decision, not a technical one.

Recommendation: Approve for use on non-regulated forms where Google reCAPTCHA is already the accepted vendor. Pin to v0.0.12, treat as a replaceable utility, and gate any EU/regulated rollout on the privacy review.