- How do I install filament-scanner-guard in a Laravel app?
- Install it with Composer using composer require jeffersongoncalves/filament-scanner-guard, then publish the package config and migrations and run php artisan migrate. Register the plugin in the relevant Filament PanelProvider so the guard applies to that panel. Check the repository README and composer.json for the exact publish tags and registration snippet for your Filament version.
- Which Laravel and Filament versions does filament-scanner-guard support?
- The package is built for Laravel applications that run a Filament admin panel, but you should verify the exact illuminate/*, filament/*, and PHP constraints in its composer.json before upgrading. The 1.2.0 testbench bump to ^11.0 is a dev dependency change and does not by itself prove runtime support for a newer Laravel or Filament line. Test the install against your target Laravel and Filament versions in staging rather than assuming compatibility.
- How does filament-scanner-guard detect and block vulnerability scanners?
- It adds a middleware-style request inspection layer that runs before Filament renders the panel, looking for suspicious scanner or device behaviour. Detected traffic can be logged and blocked according to your allow/deny configuration, with custom redirects for denied requests. It works alongside Filament's existing authentication and policies rather than replacing them.
- Does it work behind Cloudflare, load balancers, or reverse proxies?
- Correct client IP resolution is critical: if the package sees your CDN or load balancer IP instead of the real visitor IP, it can ban the wrong address and take the panel down. Confirm that it honours Laravel's TrustProxies configuration and the headers used by your proxy, such as X-Forwarded-For or Cloudflare headers. Test this in staging behind the same proxy or CDN setup you use in production.
- Can I allowlist IPs or avoid locking myself out of the Filament admin panel?
- The package supports configurable allow/deny behaviour and custom redirects, and you should confirm whether your version includes an explicit allowlist, admin self-exemption, and a detection-only or dry-run mode. Before enabling blocking in production, test with your own office and VPN IPs and keep a way to disable the guard from the server or config. An admin lockout is the main operational risk with request-blocking middleware.
- What does filament-scanner-guard retain after purge or unban in 1.2.0?
- Version 1.2.0 changed data-retention behaviour so the bans-per-day chart history survives purge or unban. Before upgrading, review the migration diff to see whether purged bans are soft-deleted, archived, or aggregated, and what request metadata is retained. If full IP addresses, user agents, or paths persist, treat that as a privacy, compliance, and storage-growth consideration.
- How is filament-scanner-guard different from Cloudflare or a WAF?
- Filament Scanner Guard is application-level protection inside your Laravel app, not an edge WAF. It can log and block suspicious scanner traffic before it reaches sensitive Filament routes, but it does not replace Cloudflare, AWS WAF, nginx rate limiting, or other infrastructure controls. Use it as an extra layer alongside your existing edge and network protections.
- Does filament-scanner-guard add a database query to every request?
- The package persists ban state in database tables and inspects requests on the way into Filament, so the lookup path and any caching or indexing matter for busy panels. Review the code and benchmark it against production-like traffic, especially if detection performs a database query on every request. Do not assume it is free under high request volume without measuring.
- Can I use it with multiple Filament panels or multi-tenant apps?
- The package is designed for multi-panel Filament apps with per-panel configuration, so you can apply different guard settings to different panels. Multi-tenancy scoping is not clearly guaranteed by the overview, so verify whether ban state is global or tenant-aware before relying on it in a multi-tenant application. Test each panel's middleware registration separately.
- Is filament-scanner-guard production-ready and actively maintained?
- It is a small, single-maintainer package at 1.x maturity, so adopt it with a fork option rather than as a strategic dependency. Expect limited production hardening around edge cases such as trusted proxies, IPv6, allowlists, admin lockout, and multi-tenant scoping, and check the actual test coverage. Pin the exact version, review diffs, and validate in staging before production rollout.