Ezie Ls Laravel Package

Product Decisions This Supports

• Build vs. buy for developer tooling on legacy stacks. This package is prior art for a Language Server Protocol implementation targeting the eZ Publish template language. It informs the decision of whether to build editor intelligence (completion, go-to-definition, diagnostics) in-house or license/buy, by showing the scope of an existing PHP-based attempt.
• Migration-window DX investment. If the roadmap includes retiring eZ Publish / eZ Platform templating, this quantifies what a "keep the legacy authors productive" workstream would cost versus freezing tooling and accepting slower edits during the migration.
• Static analysis and codemod strategy. The grammar/symbol-resolution approach here supports scoping a template analyzer or migration codemod, which feeds decisions about automated versus manual template conversion.
• OSS dependency and risk policy. A 2014 archival date, NOASSERTION license, 27 stars, and zero dependents make this a useful test case for a policy on unmaintained or license-ambiguous dependencies — a governance decision, not a feature decision.
• Reference architecture for PHP language servers. Supports an engineering spike on PHP-native LSP tooling by providing a concrete 2014-era baseline to compare against modern alternatives (Phpactor, php-parser, Psalm).
• Does not support: any new customer-facing feature, any Ibexa/eZ Platform (Twig) roadmap item, or any production dependency decision.

When to Consider This Package

Consider it when:

• You have a frozen legacy eZ Publish estate and need to understand what editor tooling for its template language looked like, as prior art before writing a modern replacement.
• You want a specification-grade reference for LSP plumbing (protocol lifecycle, document sync, symbol lookup) implemented in PHP, to de-risk a from-scratch estimate.
• You are reverse-engineering template grammar to bootstrap a parser, linter, or migration codemod, and need labeled examples of symbol resolution.
• You are cataloguing unmaintained OSS for an internal risk register and want a documented example of license and longevity failure modes.

Look elsewhere when:

• You need a working, installable LSP in a current editor (VS Code, Neovim, JetBrains) — use maintained alternatives or the editor's native PHP tooling.
• Your license policy requires unambiguous terms; NOASSERTION is a legal-review blocker for redistribution or hosted use.
• You target PHP 7.4+/8.x, need security response, or require Composer dependency resolution against a live registry — this released in 2014 and is archived.
• You are on eZ Platform or Ibexa with Twig templates — adopt Twig Language Server plus PHPStan/Ibexa bundles instead.
• You need community support or a maintained upstream: 27 stars, zero dependents, and a decade without releases are disqualifying signals.

How to Pitch It (Stakeholders)

For executives: "This is a 2014 archived component from eZ Systems that gave developers autocomplete and navigation for the older eZ Publish template language. It is not an adoption candidate — no release in over a decade, no dependents, and a license we cannot cleanly assert. Its value is as a free reference design: if we greenlight a legacy-tooling or template-migration initiative, reading it tells us roughly what a PHP language server costs to build and where the hard parts are. Recommendation: no dependency, and at most two engineering days of study if that initiative is approved."

For engineering: "Treat ezie-ls as a specification, not a library. Read the LSP wiring and template symbol-resolution logic, then reimplement on a modern stack (php-parser, Phpactor, or a Twig-based analyzer) under a license we can defend. Do not vendor it, do not add it to composer.json, and do not count on upstream fixes. If the goal is editor support for templates we still maintain, the honest options are a short internal build or a maintained third-party tool — this package is evidence for estimating the former, not a shortcut to it."