PHP RFC: Deprecate PEAR and recommend Composer

• Version: 0.1
• Date: 2025-10-09
• Author: James Titcumb, asgrim@php.net
• Status: Withdrawn
• Implementation: n/a

The RFC proposes to deprecate PEAR, and to recommend Composer for installing PHP packages going forward.

Along similar lines to the PECL deprecation RFC, this RFC proposes to officially deprecate the PEAR installer.

The proposal is made of two key messaging changes:

• PEAR becomes formally deprecated as an installation method for PHP packages. This is in messaging only, and practically, the PEAR tool and website (https://pear.php.net/) will still function for the time being.
• Composer is adopted formally as the recommended installation method for PHP packages.

Where possible, messaging will be added to PEAR resources (such as the PEAR website, the tool itself, PHP documentation, etc.) that PEAR is deprecated and switching to Composer is recommended. A link to the Composer website (https://getcomposer.org/) is recommended to provide a call to action to the user.

There are no breakages. PEAR will continue to function.

Not applicable - if accepted, this will take effect immediately.

Composer has overhauled the way PHP packages are installed, and arguably is the de-facto tool for installing packages. PEAR is still however used, for example the top package on pear.php.net shows ~15 installs per day on average. However, there is an ongoing maintenance burden for the PEAR website.

This RFC specifically does NOT propose a timeline for removing the PEAR website or CLI tool. These will continue to operate as they do currently. A follow-up RFC should be made to propose a timeline for their eventual removal, and methods by which this will be communicated to as many people as possible.

Yes / No vote requiring 2/3 Yes votes to pass.

• PEAR website: https://pear.php.net/
• Composer website: https://getcomposer.org/