Filament Captcha Laravel Package

Product Decisions This Supports

• Hardening Filament authentication and account flows (login, registration, password reset) against bots, credential stuffing, and spam signups; supports security roadmap and reduces fraud/support burden.
• Opening public-facing Filament forms (contact, lead capture, support intake) without moderation overhead; supports growth/ops decisions to accept inbound submissions safely.
• Laravel/Filament upgrade planning: the 1.0.0 release’s “modernization Laravel 13” work supports a “stay on supported framework versions” decision and can unblock an upgrade if captcha compatibility was a constraint.
• Build vs buy: captcha is a commodity capability; adopting a focused package is cheaper than building/maintaining challenge infrastructure unless you need enterprise bot management, self-hosted/air-gapped challenge, or custom risk scoring.
• API stability and dependency budgeting: the 0.2.0 → 1.0.0 jump signals a semver stability commitment, supporting production use with lower expected integration churn.

When to Consider This Package

• You run Filament panels and expose login, registration, or public forms to untrusted traffic.
• You need a drop-in challenge on Filament form actions, not a full bot-management or fraud-scoring platform.
• You are planning or executing a Laravel/Filament upgrade and need the captcha layer to remain compatible.
• You can accept a small-team/community dependency with version pinning and release monitoring.
• Look elsewhere if you require enterprise SLA, on-prem/air-gapped captcha, invisible/risk-based scoring at scale, non-Filament forms as the primary surface, or procurement/security review that a single-maintainer package cannot satisfy.
• Look elsewhere if a specific captcha vendor is mandated (e.g., reCAPTCHA Enterprise, hCaptcha contract) and this package does not adequately wrap it; verify provider support before adoption.

How to Pitch It (Stakeholders)

Executive summary: a small, targeted dependency that adds bot protection to Filament-based admin and public forms. The 1.0.0 release marks a production-stable API and includes modernization for Laravel 13, reducing upgrade risk and signaling maintainer intent to track the framework. Cost and integration effort are low; building equivalent challenge infrastructure is not a differentiator. Engineering summary: adopt behind configuration, pin to ^1.0, add integration tests for login/registration flows, confirm captcha provider keys and fallback behavior, and monitor maintenance/security advisories. Primary risk is single-maintainer cadence and Filament/Laravel version lock; mitigate by keeping captcha optional and abstracting verification so the provider can be swapped.