All Radar picks

X OPPORTUNITY RADAR / THE BRIEF

PHP Powers Much of the Web. Its Foundation Has One Full-Time Employee.

PHP’s latest security scramble exposed a familiar business model: critical infrastructure for everybody, maintenance money from whoever still feels guilty.

Information Overload
3 min readSources
An exhausted maintainer at a tiny desk braces a cracked platform loaded with glowing servers and browser windows while a torrent of bug reports and AI circuitry pours in from the left and a thin trickle of coins arrives from the right.
AI-generated conceptual illustration of the maintenance burden behind critical web infrastructure; it does not depict an actual PHP Foundation employee, office or system.

Reuters reports that the nonprofit supporting PHP has one full-time employee: executive director Elizabeth Barron. It also has 14 mostly part-time contractors and unpaid volunteer directors. That employee count is not the total PHP workforce: contractors include full-time developers. Reuters reports that PHP may underpin up to 70% of websites globally. W3Techs uses a narrower denominator: 69.2% of websites whose server-side programming language it identifies, as of October 25.[1][2][3][4]

That staffing arrangement would be cute if the software were maintaining a neighborhood message board. This week, two serious flaws in the three-decade-old language triggered a global patching scramble.

Cloudflare reported millions of hacking attempts. Barron told Reuters the foundation had no evidence that attackers exploited the flaws before disclosure or on systems that had been patched.[1]

So the immediate instruction remains boring and useful: patch. The institutional lesson is less comfortable.

The robots found more work for the humans

AI helped researchers find flaws that had sat in the code for roughly a decade. It also increased the amount of work landing on maintainers. Barron said PHP is receiving nearly twice as many proposed code changes as it did a year ago, without twice as many contributors to review them.[1]

Very efficient.

The foundation’s own 2025 impact report says 536 sponsors and individual contributors provided $730,534. After fees, the foundation received $645,191 and spent $784,376, a gap of roughly $139,000 that it described as a deliberate investment in technical headcount. The report also says foundation-funded developers authored about 42% of commits to PHP’s core during the year. The report said it remained solvent with healthy reserves.[2]

Those are maintenance, security fixes, releases, reviews and the slow work of keeping a language used across the commercial internet from becoming an archaeological site with payment processing.

Six-month grants for an always-on dependency

The PHP Foundation has been building capacity. In May it announced a six-month grant-funded full-time security role meant to help projects triage credible AI-assisted vulnerability reports while filtering the low-quality machine-made reports that waste maintainer time.[3]

That is sensible. Six-month grants are still a strange financing model for infrastructure that corporations expect to remain secure every hour of every year.

The biggest users of open-source software routinely treat maintenance as somebody else’s cost center. The dependency is free, the margins are private and the risk becomes communal right up until the patch window opens. Then everybody discovers supply-chain governance and starts speaking very seriously about resilience.

PHP’s crisis is specific. The incentive problem is not. AI can increase the rate of useful discovery, junk reports and proposed code changes at the same time. Every one of those outputs creates review work, and review work requires people with experience rather than a cheerful dashboard.

If major companies depend on PHP, they should fund the people who keep it useful and secure as part of their infrastructure budget. Donations are welcome. Dependence deserves something more durable.

Which large users should be expected to pay for the maintenance they rely on?

CORRECTIONS & UPDATES.

Correction ·
Clarified the website-usage denominator and distinguished the Foundation’s employee count from its contractor workforce. Added the reported reserve position and restored faithful full-resolution artwork delivery.

FOLLOW THE SOURCES.

Checked Oct 25, 2026. Numbered references point to the evidence behind factual passages. Commentary is our own.

  1. PHP Foundation ‘under-funded’ with one full-time staff member, director says — October 23, 2026 (opens in a new tab)ReutersBack to cited passage
  2. The PHP Foundation Impact and Transparency Report 2025 — May 27, 2026 (opens in a new tab)The PHP FoundationBack to cited passage
  3. Announcing the Ecosystem Security Team at The PHP Foundation — May 18, 2026 (opens in a new tab)The PHP FoundationBack to cited passage
  4. Usage statistics of PHP for websites — checked October 25, 2026 (opens in a new tab)W3TechsBack to cited passage
CybersecurityOpen sourceWeb infrastructureArtificial intelligenceSoftware supply chainFundingThe PHP Foundation
Back to the latest picks