Adminlist Bundle Laravel Package

Product Decisions This Supports

• Build vs. buy for back-office CRUD: This bundle is a working specification for what an admin list screen needs — server-side filtering, CSV export, and inline editing on top of basic CRUD. Use its feature set to size internal build estimates rather than to shortlist a dependency.
• Feature scoping for admin tooling: If admin/ops screens are on the roadmap, treat filtering + export + in-place edit as the baseline bar. This package demonstrates the pattern; your team can decide which of the three are table stakes for v1 versus fast-follow.
• Export as a product requirement: CSV export is often requested by ops, finance, and support teams as an escape hatch from the UI. This package's inclusion of it is a useful signal that "export the current filtered view" is a distinct, non-trivial requirement worth speccing explicitly.
• Platform/stack fit decisions: The bundle is a Symfony bundle (Kunstmaan CMS ecosystem), not a Laravel package — which makes it relevant only if the decision at hand is "standardize on Kunstmaan/Symfony for content-driven admin." It should not enter a Laravel build-vs-buy comparison at all.
• Reference architecture for internal reviews: When engineering proposes hand-rolling admin CRUD, this is a concrete, MIT-licensed artifact to point at and ask, "which of these capabilities are we deliberately dropping, and why?"

When to Consider This Package

Consider it only when all of the following hold:

• You are already on a legacy Symfony 2.x codebase or the Kunstmaan CMS bundle family, and the admin lists you need are structurally similar to content entities (articles, taxonomy, dropdown values).
• You need list filtering, CSV export, and inline editing fast, and you accept that you will fork and own the code rather than consume it as a maintained dependency.
• The work is internal or low-risk, with no security or compliance exposure from unpatched third-party admin code.

Look elsewhere — or don't adopt — when:

• The stack is Laravel. This is not a Laravel package; the fit is zero without a rewrite. Use Filament, Laravel Nova, or a custom Livewire/Inertia table with an export action.
• The stack is modern Symfony. EasyAdmin or SonataAdmin give the same list/filter/export/inline-edit capabilities with active maintenance and current PHP support.
• Maintenance matters. Last release was 2014-08-07 — roughly a decade without updates. No PHP 8, no current Symfony, no security patches. That is a hard stop for anything customer-facing or audited.
• You need social proof. 20 stars and 0 dependents means no community validation, no third-party bug reports, and no ecosystem of answers. Your team will be the only users.
• Accessibility, i18n, or audit-logging requirements exist. There is no evidence these are addressed, and no upstream to file against.

How to Pitch It (Stakeholders)

Recommendation: do not adopt as a dependency; mine it as a design reference.

To executives: this is a small, MIT-licensed Symfony bundle that adds filtering, CSV export, and inline editing to admin content lists. It solves a real and recurring problem, but its last release was in 2014, it has essentially no adoption (20 stars, zero dependent projects), and it is not a Laravel package. Adopting it would create an unmaintained, single-owner component in our back office with no security patch path — a low-ceiling, open-ended maintenance liability. The total cost of ownership exceeds the cost of building the same three capabilities on our own stack.

To engineering: treat it as a requirements artifact. Review the feature set — server-side filters, export of the current filtered view, in-place editing — and confirm we are deliberately covering or cutting each one. If anyone wants to reuse the code, the only defensible path is a fork with an explicit owner, a supported Symfony/PHP version target, and a plan to replace it within two quarters. Otherwise, implement on EasyAdmin (Symfony) or Filament/Nova (Laravel), both of which are actively maintained and give us the same surface area.

Ask: one hour of engineering time to extract the feature checklist into our admin-tooling ticket; no procurement, no pilot, no dependency added.