- How do I install filament-check-whois-widget in a Laravel app?
- Install it with Composer using composer require jeffersongoncalves/filament-check-whois-widget, then register the package service provider or Filament plugin on the panel where you want the widget to appear. Optionally publish the package config and Blade views if you need to customise the widget markup. There are no database migrations or persistence layers involved, so installation is additive to an existing Filament panel.
- Which Laravel and Filament versions does this package support?
- The package is built for Filament v3 panels and is described as a drop-in widget for existing Filament dashboards. The 1.1.0 release bumps dev tooling such as orchestra/testbench v10 and nunomaduro/collision v8, which hints at a Laravel 12-era test matrix, but that is not proof of the runtime constraint. Check the declared illuminate/support and filament/filament requirements in composer.json against your app's pinned versions before upgrading.
- Does the widget work outside Filament, for example in a plain Laravel dashboard?
- No. This is a Filament widget, so it assumes you already have a Filament panel, dashboard, and widget registration working. A non-Filament Laravel application would need its own controller or Blade view wrapping the underlying WHOIS lookup. Non-Laravel PHP projects are not supported at all.
- How do I add the WHOIS lookup widget to a Filament resource or page?
- Register the package's widget class in your panel's widget list or in a page's getHeaderWidgets or getFooterWidgets method, following normal Filament widget conventions. Configuration is intentionally minimal, so the widget should appear with its WHOIS query form and result display once the plugin is registered. You can publish views if you need to adjust the layout to match a custom admin theme.
- Are the 16 new locale files in 1.1.0 auto-loaded or do I need to run vendor:publish?
- The 1.1.0 changelog adds locale files for ar, az, de, fa, fr, hi, it, ja, nl, pl, pt, ru, tr, uk, uz, and zh_CN, but it does not document whether they are auto-discovered. If the service provider calls loadTranslationsFrom, the translations are available immediately after Composer install. If they are publishable instead, run vendor:publish with the package's translation tag, for example --tag=filament-check-whois-widget-translations, and verify the tag name in the package source.
- Do RTL locales such as Arabic, Farsi, Azerbaijani and Uzbek render right-to-left in the widget?
- The 1.1.0 release adds translation strings, but the evaluation notes do not confirm whether the Blade view handles RTL direction or sets dir=rtl. Treat these as string-only translations until you test them in an RTL-configured Filament panel. If layout is left-aligned, you will need to add direction handling in the published Blade view or theme CSS.
- Does every widget render hit the WHOIS network, and can I cache results?
- WHOIS lookups use the plaintext TCP/43 protocol, are rate-limited, and have no SLA, so hitting the network on each render is a real production concern. The package overview does not document a configurable timeout, retry policy, or cache TTL, so inspect the config file and the WHOIS client wrapper before relying on it. For production panels, wrap or cache lookups and set sensible timeouts rather than assuming the widget handles this.
- What are the production risks of relying on WHOIS data in an admin panel?
- Your results are bounded by upstream registrar and RIR behaviour, including rate limits, timeouts, and increasingly redacted output under GDPR and ICANN policies. WHOIS is unauthenticated and plaintext, so treat the widget as a convenience for support teams rather than an authoritative ownership check. It is suitable as a cosmetic dashboard helper but not as a load-bearing dependency in critical workflows.
- How is the package maintained, and is it safe for long-term use?
- The 1.1.0 release is largely a localisation and housekeeping release, with the substantive change being added locale files and the rest being Renovate and Dependabot bumps, CI standardisation, and README or FUNDING updates. The maintainer removed the Renovate config and self-merged several CI and documentation pull requests, which reads as a single-maintainer project on automated upkeep. That is acceptable for a cosmetic Filament widget but risky for a critical dependency, so pin the version if your panel is customer-facing.
- What is the upgrade path from 1.0.2 to 1.1.0, and are there breaking changes?
- There are no documented breaking changes, new APIs, config surface changes, or deprecations in 1.1.0, so treat it as a minor-version bump. Run composer update jeffersongoncalves/filament-check-whois-widget, clear cached config and views, and republish translations if the locale files are publishable rather than auto-loaded. Pin to ^1.1 if you want the new translations, or pin exactly if you need to control when locale strings change in a customer-facing panel.