- How do I install gerenuk/filament-utc-dts in a Laravel Filament panel?
- Install it with Composer, then register the plugin in the relevant PanelProvider using a single ->plugin(UtcDtsPlugin::make()) call. The package also requires an asset publish or build step as part of setup. The integration is additive and should take under a day including review.
- Which Laravel and Filament versions does this UTC clock plugin support?
- The technical evaluation flags Filament major-version support as an open question, so confirm the compatibility matrix in the package README and composer.json before adopting it. The repository shows a single release dated 2025-03-10, and Filament 4 readiness is not confirmed by the provided context. Pin the version explicitly and record it in your lockfile.
- Does the UTC time come from the browser clock or the server?
- The provided evaluation does not confirm whether the displayed time is derived from the browser clock, a server-rendered timestamp, or a remote API. This matters because a browser clock can drift and is user-manipulable, which weakens the indicator for audit or SLA use. Review the small code surface to verify the source before relying on it operationally.
- Does the package make external network requests or load remote assets?
- The evaluation lists this as a key question rather than a confirmed behavior: any package rendering into an authenticated admin surface should be reviewed for inline JS, external CDN calls, and outbound requests. A call to a third-party time API would raise data-egress and availability concerns. Because the code surface is tiny, the review is cheap.
- Can I customize the label, time format, or placement of the UTC clock?
- The package is described as having no config surface worth governing, so expect limited built-in configuration. Options such as label text, seconds precision, tooltip showing local time, and placement are worth verifying in the README. If the view is publishable, you can adjust presentation without forking.
- Is the Blade view publishable so I can override it without forking?
- The evaluation asks whether the view is publishable but does not confirm it. Publishing the Blade view is the cleanest way to customize rendering and avoid maintaining a fork. Check the service provider's publish configuration before making presentation changes.
- Does the plugin poll with Livewire or tick client-side, and what is the performance cost?
- The evaluation raises this as an open question: confirm whether it uses Livewire wire:poll or purely client-side ticking. A client-side tick avoids server load, while polling adds per-session cost at your concurrent-admin peak. Review the included JS and any Livewire usage to size the impact.
- Will it conflict with other Filament plugins that register topbar render hooks?
- It registers a render hook into the panel topbar, so conflicts are possible with other plugins targeting the same hook. The evaluation recommends checking that it survives Tailwind and asset rebuilds cleanly. Test alongside your existing topbar plugins in a staging panel before rollout.
- Are there automated tests and CI, and how actively is the package maintained?
- The provided context does not confirm automated tests or CI. Supply-side signals are weak: 5 stars, 0 dependents, a single release dated 2025-03-10, and a low opportunity score. Treat it as a one-maintainer package with little community validation, and plan for a possible fork or removal.
- Is there a data migration or rollback risk if I remove the plugin?
- No. The package carries no migrations, models, jobs, or domain coupling, so adoption is configuration-only. Rollback is symmetric and trivial: remove the plugin line, run composer remove, rebuild assets, and redeploy. There is no schema change, backfill, or state to unwind.