Filter Widget Laravel Package

Product Decisions This Supports

• Build vs. buy for CMS filtering UI: Informs whether to reuse an existing filter widget for the Victoire DCMS editorial experience or build a bespoke filtering component. Given the package’s age and low adoption, this is likely a "build" signal for anything net-new.
• Symfony/Victoire roadmap scoping: Useful only if you are maintaining a Victoire-based site and evaluating whether to keep, fork, or replace legacy filter widgets during a CMS modernization effort.
• Legacy maintenance triage: Helps decide whether to patch an existing integration versus deprecate it — the 2016 last release and zero dependents make it a strong candidate for retirement rather than investment.
• Use cases it nominally supports: Content filtering within Victoire DCMS pages — e.g., filterable listings, taxonomy-style narrowing of editorial content — not general-purpose application filtering.
• Framework mismatch is itself a decision input: The package is a Symfony bundle (WidgetFilterBundle) for Victoire DCMS, not a Laravel package. If your stack is Laravel, this does not apply and the decision is closed.

When to Consider This Package

• You are actively running Victoire DCMS on Symfony and need a filtering widget that already fits that CMS’s widget model.
• You have a frozen or low-churn legacy codebase where matching the existing widget conventions matters more than modern maintenance.
• You are doing a short-term patch on a Victoire site and want to avoid writing a widget from scratch for a minor feature.
• You can tolerate unmaintained code: last release 2016, 3 stars, 0 dependents, and a low quality score (0.335) imply no community safety net, no security patching, and no Symfony-version currency.

Look elsewhere if:

• Your stack is Laravel — this package is the wrong ecosystem entirely.
• You need maintained, security-reviewed dependencies or current Symfony/LTS support.
• You are building new product surface area where filtering is a differentiator; a modern component (e.g., Symfony’s form/filter tooling, API Platform filters, or a custom implementation) is the better bet.
• You require documentation, support, or community answers — none are evidenced here.

How to Pitch It (Stakeholders)

For executives: This is a small, stale Symfony CMS add-on — not a strategic dependency. It has no meaningful adoption (3 stars, 0 dependents) and hasn’t shipped since 2016. It is not a Laravel package, so it’s out of scope for our Laravel work. Recommendation: do not adopt for new initiatives; treat it only as a legacy artifact if a Victoire site already depends on it, and plan to replace it during any modernization.

For engineering: A Victoire DCMS filter widget bundle with an unmaintained 2016 release. Safe to use only as a low-risk convenience inside an existing Victoire codebase; expect to own any fixes, framework-version compatibility, and security posture yourself. For anything new — or anything on Laravel — build or select a maintained alternative rather than inheriting this dependency.