PEAR was historically promoted as a framework and distribution system for reusable PHP components. That historical relationship has become a liability for the PHP project. The current situation has several critical issues:
php.net domain.pear.php.net.php.net subdomain creates security risks.Attempts to find solutions with PEAR maintainers, directly and through official channels, did not lead to results. All this combined is a bad look, and a reputational risk for the PHP project. There were similar RFCs [4][5] in the past (last in 2025), but never brought to a vote. This RFC takes the concerns from earlier discussion into account: PHP internals cannot vote to stop independent maintainers from maintaining PEAR elsewhere. PHP internals can, however, decide what PHP bundles, what PHP domains serve, and what official websites endorse.
This RFC proposes to end the PHP project's explicit endorsement for the independent PEAR project, to unbundle PEAR from PHP sources, and for the time being provide a static PEAR archive to keep legacy CLI clients working. It is proposed to take the following four actions.
All relevant, public pages of the current PEAR website will be served as a static archive. The infrastructure team will decide technical details. The archive includes package details, downloads, manuals, and public bug reports. PEAR CLI endpoints will keep working to not break the PEAR CLI for legacy users.
The archive preview can be found under https://nicksdot.github.io/pear.
PHP source will no longer install or bundle the PEAR installer. This proposal aligns with the pre-existing PR [1] by Jakub, which intends to remove PEAR (and related integration). This RFC formalises that direction.
References to PEAR will be removed from official PHP websites. Composer should be mentioned as the community package manager -- this recommendation does not make Composer a PHP project and does not change Composer governance.
The PEAR mailing lists under news-web.php.net will be moved to the “Inactive Lists” section, where they will be accessible like other inactive non-PEAR and PEAR lists.
The goal is not to take over the governance of the independent PEAR package ecosystem. If an independent PEAR team wants to continue PEAR as an active project, they remain free to do so under domains they control.
Users will no longer receive PEAR bundled with PHP itself, but can install it manually. Users of the 6 packages that are still publishing on PEAR must switch to their Composer-installable versions.
8.7 for the php-src unbundling.
Members of the infrastructure team pointed out that providing the browsable archive should be temporary so as not to abruptly break legacy projects. At some point in the future the archive should be removed to avoid wasting project resources.
Requires 2/3 Yes.