Bootstrap Bundle Laravel Package

Product Decisions This Supports

• Clears up a category mismatch, not a feature decision. This is a Zikula CMS bundle (Symfony-based) that wired Bootstrap-era assets, form themes, and Twig helpers into Zikula modules — it is not a Laravel package. If the question on the table is "which Bootstrap integration do we standardize on for a Laravel app," this is out of scope; record it and close the ticket rather than opening an evaluation.
• Legacy estate triage. Its only real utility is as an input to a "keep or remove" decision inside an existing Zikula/Symfony application: is Bootstrap still delivered through this bundle, or through a standard asset pipeline?
• Build vs. buy resolves to build. The purchase price is $0 (MIT), but the total cost is an unowned dependency: archived, 0 stars, 0 dependents, last release 2017-07-19. The rational alternative is Symfony's native Bootstrap form themes plus your own asset build (npm + Vite/Encore) — less code, maintained upstream.
• Roadmap forcing function. If any roadmap item still assumes Bootstrap 3/4 theming in a Zikula-based admin or module UI, the archive status is the trigger to schedule a UI and asset-pipeline migration rather than a reason to keep the bundle.
• No input on greenfield features, design-system selection, or any Laravel/Livewire/Inertia work.

When to Consider This Package

Consider only if all of these hold:

• You maintain an existing Zikula (not Laravel) application on a PHP version the bundle actually supports.
• You already depend on it and need to understand its behavior for a migration plan or a security audit — i.e., you are reading it, not adding it.
• Reproducing its Bootstrap integration behavior in a legacy module costs more than a short, time-boxed pin.

Look elsewhere — do not adopt — when:

• Anything new is starting. An archived package with no maintainer, no security response path, and no release since 2017 offers no compatibility guarantee with current PHP or Symfony.
• You need a Laravel package. Use Laravel's Vite pipeline with Bootstrap installed from npm, or a maintained starter kit. There is no reason to reach for a CMS bundle here.
• You need Bootstrap 5+. This predates it.
• Supply chain or license review matters. MIT is fine; an unmaintained dependency with no upstream triage is a standing audit liability, not a one-time approval.
• You need docs, community support, or issue responsiveness. None exist.

If you must evaluate it anyway, the bar is: vendor the code, fork it under your organization, pin the exact commit, register it in your SBOM and CVE monitoring, and name an internal owner for the fork. No named owner means the answer is no.

How to Pitch It (Stakeholders)

Executives. This is a one-line decision, not a project. The package is an archived 2017 Zikula/Symfony Bootstrap integration with zero stars, zero dependents, and no release in roughly eight years — and it is not a Laravel package despite being surfaced in that context. Recommendation: do not adopt. Treat it as a legacy dependency to retire, not an option to weigh. License cost is zero; risk cost is high, because there is no one upstream to patch security issues, keep PHP compatibility, or answer a question.

Engineering. Keep it out of every composer.json. Where it is already present, we fork-or-remove: inventory which modules rely on its Twig helpers and form themes, replace them with Symfony's native Bootstrap form themes plus our standard asset build, and set a removal date. If a short pin is genuinely unavoidable, pin the commit, vendor it, and put it under dependency scanning with a named owner. There is no scenario in which this package is a forward-looking choice for a Laravel or modern Symfony product.