Laminas Progressbar Laravel Package

Product Decisions This Supports

• Build vs. buy vs. use what's already installed: This release is not a feature release — it archives and abandons laminas-progressbar. The decision it supports is not adopting it, and migrating off it if already in the dependency graph. Laravel already ships symfony/console, which provides ProgressBar and Laravel's own $this->output->createProgressBar() helper inside Artisan commands, so the "buy" cost of a replacement is effectively zero.
• Roadmap / feature scoping: Any roadmap item that assumed CLI progress feedback "comes free from a maintained library" should be re-scoped to Symfony Console's progress bar or a lightweight in-house wrapper. No new capability is unlocked by this release; there is nothing to plan around.
• Dependency hygiene and maintenance-risk triage: An archived upstream means no security patches, no PHP-version compatibility fixes, and no Symfony/Laravel compatibility updates. This is a standing liability line item, not a one-off upgrade task — treat it as tech debt with a deadline.
• Upgrade sequencing: If the package is a direct dependency, pin and schedule removal before the next PHP minor or framework major upgrade, since it is the most likely blocker in that upgrade. If it is transitive, check whether the pulling dependency already offers an alternative.
• Support and SLA commitments: If any customer-facing or internal tooling depends on this bar's output behavior, PM should confirm with engineering whether replacing it changes user-visible output (format, ETA, redraw behavior) and whether that needs release notes or a demo.

When to Consider This Package

• Do not adopt for new work. The 2.14.1 release is a documentation-only patch whose sole change is the archival/abandonment PR. There is no maintained path forward.
• Only relevant if it is already in the codebase: then the correct "consideration" is a removal plan — inventory usages, replace with symfony/console's ProgressBar (or Laravel's createProgressBar()), and drop the requirement.
• Look elsewhere — specifically here: Laravel's built-in Artisan output helpers and symfony/console ProgressBar cover the overwhelmingly common cases (determinate bars, iteration counts, ETA, message overlays, multi-bar for parallel work). For richer TUI needs, evaluate actively maintained options such as symfony/console's newer helper components or a TUI library with recent releases and an open security channel.
• Adoption criteria this package now fails: active maintenance, recent compatibility releases, a responsive security process, and a documented support horizon. All four are absent post-archive.
• Edge case worth checking: if the abandonment is a namespace-level migration (Laminas consolidating components), confirm with engineering whether a successor package is named before deciding between "replace with Symfony" and "follow upstream to the successor." The release notes as published do not name one.

How to Pitch It (Stakeholders)

For executives: The progress-bar library we were evaluating (or already use) has been formally abandoned upstream in release 2.14.1. That means no bug fixes, no security patches, and no compatibility updates going forward. The good news is the replacement costs essentially nothing — Laravel already includes Symfony Console, which has a first-class progress bar, so this is a small engineering task rather than a procurement or rebuild decision. Recommendation: no new adoption, and fund a short migration ticket to remove the dependency before our next framework or PHP upgrade.

For engineering: laminas-progressbar 2.14.1 contains one change — PR #45, archiving and abandoning the package. Zero issues closed, one contributor, no functional changes. Plan: grep for Laminas\ProgressBar usages, replace with $this->output->createProgressBar() in Artisan commands or Symfony\Component\Console\Helper\ProgressBar outside them, verify output parity for anything user-visible (CI logs, installers, customer-facing CLIs), then remove the Composer requirement. Flag it as the likely blocker in the next PHP/framework upgrade if left in place.