Zend Paginator Laravel Package

Product Decisions This Supports

This package now partially supports PHP 7.3, expanding its compatibility scope but still lacks maintenance for modern PHP versions (8.x) and Laravel ecosystems. PMs should only consider it for:

• Legacy systems where migration is blocked by constraints (e.g., tightly coupled dependencies).
• Short-term patches in deprecated projects where no alternative exists.
• Non-critical internal tools with minimal security exposure, assuming risk acceptance.

For new projects, prioritize Laravel’s built-in paginator or KnpPaginator to avoid technical debt. If adopting this package, plan a migration roadmap within 12–18 months to a supported solution.

When to Consider This Package

Consider only if: ✅ The project is locked into PHP 7.3 (or lower) due to legacy constraints. ✅ No alternative paginator exists for the system (e.g., custom fork or unsupported framework). ✅ Security risks are acceptable (no active maintenance = no patches for CVEs). ✅ The team lacks bandwidth to migrate immediately.

Avoid if: ❌ Using PHP 8.x (no support). ❌ Building new Laravel projects (native paginator is superior). ❌ Security/compliance requires active maintenance (e.g., PCI, HIPAA). ❌ Long-term roadmap includes Laravel upgrades (conflicts guaranteed).

How to Pitch It (Stakeholders)

To Executives: "Zend Paginator 2.8.2 now supports PHP 7.3, but it remains unmaintained—posing security and compatibility risks for PHP 8.x and modern Laravel. While it may serve as a temporary fix for legacy systems, we recommend investing in a supported alternative (e.g., Laravel’s native paginator or KnpPaginator) to future-proof our stack. The cost of migration now is far lower than the risk of technical debt later."

To Engineering: "This update adds PHP 7.3 support, but no security fixes or PHP 8.x compatibility exist. If you’re stuck on PHP 7.3 with no migration path, this is a short-term band-aid—not a long-term solution. For new work, use Laravel’s built-in paginator or KnpPaginator. If adopting this, document the end-of-life risk and plan a migration timeline."