Laminas Dependency Plugin Laravel Package

Product Decisions This Supports

• Legacy modernization roadmap: Quantifies and de-risks a Zend Framework → Laminas migration. If any service in your portfolio still requires zendframework/* or zfcampus/*, this plugin is the cheapest known lever to move that dependency graph forward without a rewrite sprint.
• Security/compliance posture: Zend Framework is end-of-life and no longer receives security patches. Adopting this plugin is a concrete, auditable action you can put in a compliance remediation plan ("EOL dependency elimination") rather than leaving the exposure open indefinitely.
• Build vs. buy: Buying (free, BSD-3) beats building a custom Composer rewrite script or a one-off sed migration. The plugin operates at dependency-resolution time, which means it keeps composer.json/composer.lock consistent — a homegrown script usually does not.
• Scope estimation for upgrade work: Use it as a discovery tool. Running it in a branch tells you which transitive Zend dependencies you actually have, which directly sizes the migration epic and informs whether PHP-version upgrades (7.x → 8.x) are blocked by Zend-era packages.
• Release-gating / risk acceptance: If a planned feature release touches a service with Zend dependencies, this is the cheapest way to unblock the release without deferring the feature to a migration quarter.
• Portfolio triage: Services with zero Zend dependencies need no decision. Services with many become candidates for "strangle and rebuild" rather than "migrate." The plugin's output is the input to that call.

When to Consider This Package

Adopt when:

• composer.json or composer.lock contains zendframework/* or zfcampus/* packages, directly or transitively.
• You need a time-boxed migration, not a permanent architecture. The plugin is explicitly a bridge; its job ends when the last Zend package is gone.
• You want the dependency swap to happen without hand-editing every composer.json in a monorepo or multi-service estate.
• You are already on, or moving to, the Laminas Project ecosystem and want the official path rather than a third-party fork.

Look elsewhere or deprioritize when:

• Greenfield work. New projects should depend on laminas/* directly; adding a migration shim to a new codebase is pure overhead.
• You expect API-level compatibility. This rewrites package names, not code. Zend\ → Laminas\ namespace changes, changed signatures, and removed classes still require manual refactoring and regression testing. Budget engineering time regardless.
• You need a long-lived dependency. This is transitional tooling with a narrow blast radius; expect low activity and eventual retirement. Do not build anything on top of it.
• Governance requires a supported, actively developed vendor dependency. 31 stars and a low opportunity score reflect a small, purpose-built tool, not a widely adopted platform. It is official Laminas Project output, which helps, but the bus factor is thin.

How to Pitch It (Stakeholders)

For executives: We have services running on Zend Framework, which reached end-of-life and no longer receives security fixes. That is an open compliance and incident-response exposure. The Laminas Dependency Plugin is a free, officially maintained Composer plugin that automatically swaps those packages for their maintained Laminas equivalents at install time. It is not the whole migration — application code still needs namespace and API updates — but it removes the mechanical dependency work, keeps our lockfiles consistent, and lets us size the remaining effort precisely. Cost is effectively zero; the return is a measurable reduction in EOL surface and a credible remediation story for audit.

For engineering: It's a Composer plugin, drop-in, no runtime footprint. It rewrites zendframework/* and zfcampus/* requirements to laminas/* during dependency resolution, so you don't hand-edit manifests across a monorepo. Treat it as scaffolding: adopt it in a branch, use it to enumerate what actually breaks, then remove it once the last Zend package is gone. Expect real work in Zend\ → Laminas\ namespace changes and any API drift — the plugin does not do that for you. Verify each service against its test suite before merging, and do not leave the plugin installed as a permanent dependency.

Positioning summary: Low cost, narrow scope, official provenance, transitional by design. Approve it as a migration accelerant, not as a platform commitment.