Pear Exception Laravel Package

Product Decisions This Supports

This package remains obsolete and unsupported despite minor compatibility fixes. The sole update (PHP 8.1+ warning suppression) does not justify adoption for new projects. Modern Laravel/PHP applications should prioritize:

• PSR-compliant error handling (e.g., whoops, monolog).
• Native PHP exceptions or Laravel’s built-in App\Exceptions\Handler.
• Active maintenance (e.g., packages with recent commits, security patches, and Laravel version support).

Adoption would introduce technical debt, security risks (no license transparency), and compatibility issues with modern PHP/Laravel versions. Not recommended for roadmaps or build-vs-buy decisions unless maintaining a legacy PEAR-based system with no migration path.

When to Consider This Package

Only for:

• Legacy PEAR-based applications where migration is infeasible and PHP 8.1+ warnings are critical blockers.
• Short-term patches in deprecated systems (e.g., internal tools with no replacement planned).

Avoid for all other cases, including:

• New Laravel projects (use Illuminate\Foundation\Exceptions\Handler).
• Modern PHP applications (PSR-3/PSR-11 logging libraries).
• Systems requiring security audits or compliance (no license, no updates beyond trivial fixes).

How to Pitch It (Stakeholders)

To Executives: "This package is a relic with no strategic value. The single update (a PHP 8.1 warning fix) doesn’t offset risks: no maintenance, unclear licensing, and zero alignment with our modern stack. Investing in supported alternatives (e.g., Laravel’s native exception handling or PSR-compliant tools) will reduce costs, improve security, and future-proof our systems. Legacy systems should be deprecated, not propped up."

To Engineering: *"While the package now ‘works’ on PHP 8.1+, it’s a dead-end dependency. We should:

1. Replace it with Laravel’s App\Exceptions\Handler or whoops for new projects.
2. Deprecate it in legacy systems with a migration plan to PSR-compliant tools.
3. Block new integrations—this adds no value and introduces avoidable complexity. Focus on active, community-backed packages."*