Twig Spreadsheet Bundle Laravel Package

Product Decisions This Supports

• The "export to Excel" feature bet. This package is a worked example of template-driven spreadsheet generation: define an .xlsx/Twig template once, render it with application data. It supports the decision of whether to invest in user-facing exports for reports, invoices, statements, reconciliation sheets, or bulk data pulls in any B2B or finance-adjacent workflow.
• Report authoring: template-driven vs. code-driven. It validates a specific product model — letting finance/ops or implementation teams own the shape of a report (a Twig template) while engineering owns only the data plumbing. If your roadmap includes "customers can self-serve report layouts," this is the cheapest conceptual prototype of that idea.
• Build vs. buy vs. borrow. This is a "borrow" tier: a small open-source integration layer over PhpSpreadsheet. It's useful as a reference architecture when deciding whether to (a) hand-roll PhpSpreadsheet calls, (b) adopt a supported reporting library, or (c) push reporting to a BI tool like Metabase and stop owning it.
• Commodity vs. differentiator. Spreadsheet export is table stakes, not differentiation. It's a decision input for scoping: cap the investment, ship the 80% case (styled tabular export with formulas and number formats), and don't build a templating engine of your own.
• Scheduled/automated delivery. The pattern generalizes to a roadmap item — "email me this spreadsheet every Monday" — and shows how little code that requires once templating exists.

When to Consider This Package

Consider it only as a reference implementation or for an existing legacy Symfony 3/4 app on PHP 7.x that already runs PhpSpreadsheet and needs Twig-templated exports quickly. Even there, treat it as code to copy, not a dependency to install.

Signals that make adoption untenable for anything new:

• Last release April 2019, 1 GitHub star, 0 dependents — effectively abandoned, with no security response path, no PHP 8 compatibility, and no support for current Symfony versions.
• No community. No maintainer activity, no issue triage, no ecosystem of templates. The bus factor is one, and that one is gone.
• It is not a Laravel package. It's a Symfony bundle built around Twig. In a Laravel codebase it is a poor fit by construction — Laravel's Blade/Excel packages are the native option.
• Compliance. If you're SOC 2 / ISO 27001 scoped, an unmaintained dependency will fail dependency review or force an exception you'll re-litigate every audit cycle.

Look elsewhere for: new builds, anything on PHP 8.1+, anything customer-facing at scale, anything requiring an SLA. Reach for PhpSpreadsheet directly, Laravel Excel / OpenSpout on the Laravel side, or offload reporting to a BI layer.

How to Pitch It (Stakeholders)

For executives: The idea is proven and cheap; the artifact is stale. Report exports are expected in every B2B product we sell into, and this package demonstrates that a template-based approach gets us there with low engineering cost. But it hasn't been maintained since 2019 and has essentially no user base, so adopting it as a dependency imports upgrade and security risk in exchange for saving a sprint. Recommendation: fund a thin internal wrapper, borrowed from this design, rather than taking the dependency.

For engineering: Don't composer require it. Read it as a design reference for separating report layout (template) from data assembly (service), then implement ~200 lines against the current PhpSpreadsheet release, with tests and pinned versions. If we're on Laravel, use the maintained ecosystem packages instead — this bundle's Twig binding is Symfony-specific and won't transfer.

For design/ops stakeholders: The user-facing win is that finance and implementation teams can adjust report layouts without an engineering ticket. That's the capability worth buying; the specific library is not.

The headline: Validate the pattern, reject the package. Low score, low stars, and a five-year-old last release make this a "steal the idea" decision, not an adoption decision.