Form Widget Laravel Package

Product Decisions This Supports

• Build vs. buy for form authoring in a CMS context. This package represents the "buy/reuse" option for letting non-technical editors compose custom forms (fields, validation, submissions) inside the Victoire CMS. It is the cheapest possible starting point if you are already on Victoire — and effectively a non-option otherwise.
• Roadmap scoping for editor-facing form tooling. Useful as a reference implementation for what a "form widget" surface looks like: field-type registry, per-form validation config, submission storage, and rendering hooks into a CMS block. Even if we don't adopt it, it's a legitimate spec artifact for a build decision.
• Platform/stack fit. This is a Symfony bundle for the Victoire CMS, not a Laravel package. For a Laravel product it supports a clear "do not adopt" decision and redirects the conversation to Laravel-native equivalents (Filament form builder, Livewire forms, or a hosted form service). If we maintain any Symfony/Victoire estate, that's the only context where adoption is even coherent.
• Maintenance/risk budgeting. Stars (4), zero dependents, and a last release of 2018-08-13 indicate an abandoned codebase. That supports a roadmap decision to not inherit a maintenance obligation, and to budget for a replacement path rather than a dependency.
• Opportunity triage. An opportunity score of 0.38 with negligible ecosystem traction means this should not consume roadmap capacity beyond a short evaluation note.

When to Consider This Package

Consider it only when all of the following hold:

• The product runs on Victoire CMS / Symfony, not Laravel — otherwise the integration cost exceeds any conceivable value.
• You need editor-authored custom forms embedded in CMS pages and would otherwise build that surface from scratch.
• You can pin and vendor the code, own the fork, and accept responsibility for security patches (CSRF, input validation, file uploads, spam/abuse controls, submission PII handling).
• The target runtime is verified compatible with the 2018-era Symfony/PHP versions it was written against — expect incompatibility with modern Symfony and PHP 8.x without meaningful porting work.
• A code and license review confirms acceptable terms and no known unpatched vulnerabilities.

Look elsewhere when:

• You are on Laravel. Use Laravel-native form tooling or a maintained form-builder package; do not bridge a dormant Symfony bundle.
• You need maintained dependencies. Zero dependents and an eight-year-old release is an unmanaged supply-chain risk in any customer-facing or regulated context.
• Forms touch PII, payments, or authentication. An unmaintained form handler is a poor place to absorb that risk.
• You need modern features — conditional logic, multi-step forms, webhook/CRM integrations, spam protection, accessibility conformance. None of that is evidenced here.
• The real need is a hosted form product (Typeform, Formbricks, Tally-class tools). That is usually cheaper than forking an abandoned bundle and gives you compliance and deliverability for free.

How to Pitch It (Stakeholders)

For executives (one line): We evaluated an open-source form-builder plugin for a CMS we don't run; it is unmaintained since 2018 with no ecosystem adoption, so we recommend against adoption and will evaluate a maintained or hosted alternative if form authoring becomes a priority.

For engineering: victoire/form-widget is a Symfony bundle for the Victoire CMS — not Laravel. It is four stars, zero dependents, and last released August 2018, meaning it targets an older Symfony/PHP baseline and carries unpatched security surface in exactly the wrong place (user-submitted data, file uploads, submission storage). Recommendation: do not add as a dependency. If we need this capability, either build a thin form-builder on our existing stack or buy a hosted form service; if someone insists on reuse, the only viable path is vendoring a fork with an owner and a security review, which is more expensive than building.

Ask: no roadmap capacity beyond a timeboxed evaluation note; revisit only if we take on a Victoire/Symfony estate or form authoring becomes a committed roadmap item.