Listing Widget Laravel Package

Product Decisions This Supports

• Almost none for a Laravel codebase. Despite the "Laravel/PHP package" framing, this is a Symfony bundle (WidgetListingBundle) built for Victoire DCMS, a Symfony-based CMS. It is not a Laravel package, has no service provider, no Composer laravel auto-discovery, and no Laravel-facing API. If your stack is Laravel, this does not accelerate any roadmap item — it answers a question you aren't asking.
• Its only real use case is if you are running or extending a Victoire DCMS site and need a "listing" widget that renders paginated/filterable lists of content (e.g., articles, products, media) inside a CMS page. That is a narrow, legacy-ecosystem feature.
• Build vs. buy: effectively build. The package is unmaintained (last release May 2019), has 2 stars and 0 dependents, so there is no community to inherit fixes from. The cost of adopting is the cost of owning a forked, dead Symfony bundle — strictly worse than writing the listing logic yourself in whatever framework you're actually on.
• If you need a content listing feature in Laravel, the relevant decision is: use a first-class CMS/content package (e.g., a maintained headless CMS, or a Laravel content package with active releases) versus a light custom implementation. This bundle should not appear on that shortlist.
• Roadmap signal, not a build input: treat "listing widget" as a feature requirement to spec (pagination, filters, sort, caching, admin configuration), then source it from maintained tooling — not from this repository.

When to Consider This Package

Consider it only if all of the following are true:

• You are already on Symfony with Victoire DCMS (not Laravel), and this widget's content type matches your existing CMS entities.
• You need a listing widget now and accept that you will own maintenance: pinning versions, patching PHP 8 compatibility, and auditing transitive Symfony dependencies that are years out of date.
• The alternative is meaningfully more expensive than a fork — which is unlikely given how small the feature surface appears to be.

Look elsewhere if:

• Your stack is Laravel. This is the decisive disqualifier — wrong framework ecosystem entirely.
• You require active maintenance, security patches, or PHP 8.2+/Symfony 6+ support. Last release was 2019; expect dependency conflicts on modern PHP and Symfony versions.
• You need documentation, community support, or hiring-pool familiarity — 2 stars and 0 dependents means no one can help you, and no candidate will know this.
• The "listing" requirement is core to your product. Never build core functionality on an abandoned, zero-adoption dependency.
• You are evaluating this as a general CMS listing solution — it is Victoire-specific, not portable.

How to Pitch It (Stakeholders)

Executive summary: We reviewed friendsofvictoire/listing-widget and recommend not adopting it.

• What it is: A small UI widget from a Symfony CMS called Victoire DCMS, last released in May 2019. It is not a Laravel package, so it does not fit our stack.
• Health: Negligible adoption (2 stars, 0 dependent projects) and no releases in roughly six years. No maintainers actively supporting it, no security patching, and no community to fall back on.
• Risk: Adopting it means we inherit maintenance of an abandoned dependency — version pinning, PHP/Symfony upgrade conflicts, and potential security exposure — in exchange for a feature we could implement directly in days.
• Engineering position: Wrong ecosystem, unmaintained, and too small a feature surface to justify a fork. If the listing capability is on our roadmap, we should spec it as a first-class requirement and build it ourselves or source a maintained, actively released alternative.
• Ask: Close this evaluation. If a content-listing feature is prioritized, run a short build-vs-maintained-package comparison against current tooling instead.