Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message

Filament Footer Laravel Package

tapp/filament-footer

tapp/filament-footer is a lightweight Filament plugin that adds a customizable footer to your admin panel. Configure footer content and links in your panel provider to give your backend a polished, branded finish without custom layout work. Simple to install and ideal for Laravel Filament apps.

View on GitHub
Deep Wiki
Context7

Product Decisions This Supports

  • White-label / reseller readiness. A per-panel, configurable copyright line is the last mile of "this product is yours" for agency and multi-tenant Filament deployments. This package turns a recurring custom-Blade task into a config toggle, which supports decisions like "do we ship tenant-branded admin panels in Q3?"
  • Build vs. buy for cosmetic surface area. The honest answer here is "neither, really" — the plugin is roughly a PanelsRenderHook::FOOTER registration plus a config array. Its value is not engineering leverage; it's not spending design/QA cycles on a footer five times across panels (admin, tenant, vendor) that all need the same legal/copyright treatment.
  • Compliance and attribution requirements. Enterprises and OSS-adjacent products need a visible copyright/licence notice. This lets you satisfy that with a config change rather than a layout PR touching every panel's theme.
  • Roadmap signal, not roadmap content. Stars (5) and dependents (0) mean this is not a strategic dependency. Treat it as evidence of a category — "panel chrome/branding polish for Filament apps" — rather than a component to build a roadmap around. If branding is a selling point, the durable investment is a custom theme + one in-house render hook, not a third-party footer.
  • Use cases worth naming: agency handoffs (client name + year in footer), SaaS plans where branding is tiered, and internal tools where a support/legal line must appear consistently.

When to Consider This Package

Adopt when all of the following hold:

  • You are on Filament and want the footer without forking your theme or maintaining a local Blade partial.
  • You need it across multiple panels with slightly different text (the per-panel configurability is the main differentiator over a one-off hook).
  • The requirement is genuinely just a copyright/branding line — no links menu, no status indicator, no version badge, no legal-page routing.
  • You are comfortable with the risk profile: 5 stars, 0 dependents, effectively a single-maintainer package with a recent release (2026-07-04) but no ecosystem validation. Mitigate by pinning the version and reading the ~source; the blast radius of failure is a missing footer.

Look elsewhere (or write ~20 lines yourself) when:

  • You need anything beyond static text — dynamic environment badges, changelog links, support widgets. Compose your own render hook instead.
  • Your team already owns a custom Filament theme; adding a plugin to style one line is net-negative complexity.
  • You have strict dependency governance (approved-vendor lists, SBOM review, security scanning thresholds). A zero-dependent, low-adoption package will fail procurement for near-zero benefit.
  • You need guaranteed maintenance. There is no signal here — no dependents, no community — that this survives a Filament major version bump.

Default recommendation: prototype with it, but budget the half-hour to replace it with an in-house render hook if it becomes load-bearing. The migration cost is trivial today and only rises if you build config around it.

How to Pitch It (Stakeholders)

To executives: This is a five-minute, zero-cost cosmetic add-on that lets every admin panel carry the right client or company copyright line — useful for agency handoffs and white-label deals where "does it look like ours?" matters in the demo. It is not a platform dependency and carries no meaningful strategic or security risk; the worst case is a missing footer. Do not count it as branding capability on the roadmap — the real branding work is theming.

To engineering: It's a thin Filament plugin that registers a footer render hook with per-panel configurable text. Two caveats: adoption is essentially unproven (5 stars, no dependents, single maintainer), so pin the version and skim the source before merging. If your panels diverge at all — links, environment tags, version strings — skip it and register PanelsRenderHook::FOOTER with your own Blade view in the panel service provider. Same result, one less dependency, and you keep it when Filament ships its next major.

Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
3mdikram/worldmoneywords
snowsoft/config
itmosoft/laravel-subscriptions
larva/laravel-ai-qwen
diephp/sequences
users-au/socialite-provider
twidpay/twid-logger
mrnewport/laravel-plaid
mrnewport/laravel-repo
mrnewport/laravel-docsign
mrnewport/laravel-stow
mrnewport/laravel-flow
mrnewport/laravel-priceable
mrnewport/laravel-nestedterms
fredmeng/laravel-apidoc-generator
itstructure/laravel-multilingual-tools
pdustdar/elasticsearch
markupai/php-sdk
rlacerda83/lumem-microservice-shipment
uni-method/symfony-lib