End PEAR Project Endorsement proposal
Accepted 40–0–0; not implemented. At 02:06 UTC on 2026-10-21 the author announced on the internals list that the RFC was accepted with 40 Yes, 0 No and 0 abstentions; its one question needed 2/3. When inspected at about 04:07 UTC that day, the RFC page header said Accepted (last modified 2026-10-21 02:02 UTC), the poll still read "Final result: 40 / 0 / 0" with "This poll has been closed", and the official RFC index collected at 04:01 UTC listed it as accepted. Nothing has been implemented or released.
Before that, the poll closed at its scheduled time (2026-10-19 13:15 UTC) with the same 40 / 0 / 0 result, but the page header still said Voting when re-inspected at about 16:05 UTC on 19 October and 04:05 UTC on 20 October, and an internals message at 03:52 UTC on 20 October (132881) noted that the results had not yet been officially announced. During that gap this wiki kept the status as voting.
On 2026-10-05 at 13:18 UTC the author announced on the internals list that voting had opened. The RFC page (version 1.0.0, then status Voting, last modified 2026-10-05 13:11 UTC) and the official RFC index both listed it as voting. There is one primary question, "Stop endorsing PEAR?", which needs a 2/3 majority. The poll was set to close on 2026-10-19 at 13:15 UTC. When the page was inspected at about 16:05 UTC on 5 October it showed 14 Yes, 0 No and 0 Abstain; at about 04:05 UTC on 6 October it showed 21 Yes, 0 No and 0 Abstain; at about 04:02 UTC on 7 October it showed 23 Yes, 0 No and 0 Abstain; at about 10:02 UTC on 7 October it showed 24 Yes, 0 No and 0 Abstain. Those are interim counts in an open poll, not a result.
What is proposed
The RFC would end the PHP project's endorsement of the independent PEAR project in four steps:
- Serve the public pages of
pear.php.net(package details, downloads, manuals, public bug reports) as a static archive. The browsable archive, including the endpoints legacy PEAR CLI clients use, would remain until 2027-12-31 and then be offered only as a download. - Stop installing or bundling the PEAR installer with PHP source, proposed for PHP 8.7. The RFC formalises an existing php-src pull request (#20124).
- Remove PEAR references from official PHP websites and mention Composer as the community package manager. The RFC says this does not make Composer a PHP project.
- Move the PEAR mailing lists to the inactive lists section.
Taking over governance of the PEAR package ecosystem is a stated non-goal; an independent team could continue PEAR under domains it controls.
Motivation stated by the RFC
The RFC says the PHP project has no access to PEAR's infrastructure although it is hosted on a
php.net subdomain, cannot guarantee the integrity of the content served there, and that the
site is unmaintained with broken features and spam. It cites PEAR metadata from 2026-06-22:
534 of 603 packages marked unmaintained, and 63 of the remaining 69 not updated for extended
periods. These figures are the RFC's own count and were not independently re-measured here.
Affected users
According to the RFC, users would no longer get PEAR bundled with PHP but could install it
manually, and users of the six packages still publishing on PEAR would need their
Composer-installable versions. During the discussion the author stated that the static archive
would keep serving installer resources (for example go-pear.phar and /rest/ paths) on the
same domain, so the switch need not wait for unbundling.
Archive integrity suggestions (20 October)
The RFC leaves the static archive's technical details to the infrastructure team. On 2026-10-20 Sebastian Bergmann
suggested on the internals list: a signed SHA-256 manifest of every file the
archive serves (tarballs, go-pear.phar, install-pear-nozlib.phar, REST metadata), kept also in the archive's Git
repository; checking the installer PHAR that php-src downloads against a pinned hash in every branch that still
supports --with-pear, with a plan for branches supported after 2027-12-31; announced brown-outs of the CLI endpoints
and go-pear.phar before the cut-off and a "tombstone" go-pear.phar that exits non-zero afterwards; and published
aggregate request counts without IP addresses. The message recalls that go-pear.phar was replaced with a malicious
copy in January 2019.
On php-src master, pear/Makefile.frag (checked
2026-10-20) downloads https://pear.php.net/install-pear-nozlib.phar during make install-pear when the PHAR is not
already in the source or build tree, then runs it; that file contains no hash check. Release branches were not
checked. The suggestions are proposals; no reply or decision had been collected.
History and discussion
Two earlier proposals were never brought to a vote: Deprecate PEAR/PECL & Replace with composer/pickle (2016, now Inactive in the index) and Deprecate PEAR and recommend Composer (2025, now Withdrawn). The RFC changelog for 2026-09-14 records support from a long-time PEAR Group member for sunsetting the website and removing PEAR from PHP source, and adds the archive timeline. The discussion thread continued on 2026-10-02. In the thread the author expected that a vote would not end before mid-October and that nothing would land before November. That was a plan stated before the vote opened.
The vote opened on 2026-10-05; the proposal and BC sections inspected that day match the summary above. The page's introduction also states that the PEAR web repository was recently archived. The RFC cites pear/pearweb, but that repository's archive state was not checked here.
Limitations: the RFC is accepted, but each of its four steps still needs implementation work, and the result announcement gave no timeline beyond the RFC's own dates. The php-src change it formalises, PR #20124, was re-checked on 2026-10-06. It is titled "PECL and PEAR removal", which is wider than this RFC's PEAR scope, and it is an open draft that has not been merged (last updated 2026-09-03). Nothing in released PHP has changed. Related: support windows.