Filament Progress Column Laravel Package

Product Decisions This Supports

• Admin/internal tooling UX: filament-progress-column swaps raw numeric table cells (completion %, quota used, storage consumed, budget burn) for an at-a-glance progress bar. This is a cheap, high-visibility polish item for internal dashboards that stakeholders see weekly.
• Build vs. buy: A progress column is ~50–150 lines of custom Filament column code plus tests and maintenance. Adopting this package is effectively "buy" at zero cost (MIT), letting engineering spend that time on product surface instead of table rendering primitives.
• Roadmap unblocking (v2.1.0 specifically): This release adds Laravel 13 and Filament v5 support. If our platform upgrade roadmap includes either, this package is no longer a blocker — that's a scheduling input, not a feature decision.
• Concrete use cases: onboarding completion tracking, subscription/seat utilization, SLA or quota consumption, project milestone progress, credit/usage dashboards — any column where the magnitude relative to a target matters more than the exact figure.
• Risk posture: Single-purpose, low-surface dependency. It is a presentation-only column, so a failure mode is a degraded table cell, not data loss or outage. That keeps it in the "accept freely" tier of dependency review.

When to Consider This Package

Adopt when:

• The product already runs Filament (v3/v4, and now v5) — this is a Filament-native column, not a generic Laravel UI component.
• You need a percentage/progress representation inside a Filament table and want it declaratively, not via a custom view column.
• You are on, or planning, Laravel 13 or Filament v5 — v2.1.0 explicitly covers both.
• Dependency tolerance is high for small, presentation-layer packages and low for anything touching persistence, auth, or money movement.

Look elsewhere when:

• You are not on Filament; there is no meaningful use of this package outside it.
• You need real data visualization — charts, sparklines, trend-over-time, multi-segment bars. This renders a single value against a maximum, not a chart.
• You need strict, customizable accessibility semantics (ARIA progressbar roles, screen-reader text formatting) or design-system-grade theming beyond what the column exposes.
• You require a vendor with SLAs, or a package with a regular feature cadence. This is a small, single-maintainer project (bus factor of one) whose releases are largely compatibility bumps — plan to pin the version and accept that you may need to fork for bespoke behavior.
• Your upgrade policy forbids unpinned transitive churn during a framework migration; validate the Filament v5 / Laravel 13 combination in a branch before committing the roadmap to it.

Note on v2.1.0: This is a compatibility release — Laravel 13 and Filament v5 support, contributed by two first-time contributors. There are no new features, no API changes, and no deprecations. Upgrade risk is low; the meaningful signal is that the maintainer merges community compatibility PRs promptly, which reduces the risk of the package pinning you to an older framework.

How to Pitch It (Stakeholders)

For executives: This is a free, open-source add-on that makes internal dashboards easier to read — percentages and quota usage become visual bars instead of raw numbers, which reduces "what does this number mean?" back-and-forth. The new release is purely a compatibility update: it works with the latest Laravel and Filament versions, so it does not create an upgrade blocker for our platform roadmap. Cost is zero, effort to adopt is measured in hours, and the blast radius if it misbehaves is a single table cell — no customer data, no revenue path. Recommended decision: adopt for internal tooling, pin the version, and revisit only if we need richer visualization.

For engineering: Presentation-only Filament column, MIT licensed, no dependencies beyond Filament itself. v2.1.0 adds Laravel 13 and Filament v5 support with no API changes — a safe minor bump. Two caveats: it is a single-maintainer project, so pin the version and treat a fork as a routine contingency rather than an emergency; and it renders one value against one maximum, so if the requirement grows into charts or trend data, that's a different component, not a config change. Recommended integration: adopt behind a normal dependency review, add one smoke test on the column rendering in our Filament test suite, and confirm the Filament v5 path in a branch before we commit the broader upgrade.