STATUS AND COMPATIBILITY

How much PHP does phpr actually run?

A measured snapshot against PHP 8.5.7, updated 12 July 2026. These percentages do not describe a stable release; they show actual progress.

2,429

Zend tests pass · 60% of runnable tests

517

core functions out of 654 · 79%

780

internal functions out of 2,143 · 36%

areas reported complete

Core language stdlib

79%

Strings, arrays, math, variables, date, output, hashing and regex: the surface ordinary applications use most.

36%

Most of the gap is concentrated in whole database, crypto, networking and media extensions not started yet.

COMPLETE AREAS

ctype · 100%json · 100%SimpleXML · 100%zlib · 100%bcmath · 100%tokenizer · 100% functionssession · 23/23PDO core · 100%

“Complete” means all expected internal functions for that area are present; official suites can still include SAPI cases or documented edge cases.

REAL SOFTWARE

These results matter more than a synthetic demo because they traverse many runtime surfaces at once.

Project	Measured status	What it validates
Composer	Runs	`require`, `install`, `diagnose`, HTTPS and autoloading
PHPUnit	11.5 / 13.2 / 13.3-dev	CLI, output buffering, Reflection, process isolation
Doctrine DBAL	3,769 / 0 / 0	PDO, SQLite, exceptions, metadata and SQLSTATE
Doctrine ORM	3,484 tests · 3 errors · 15 failures	Hydration, UnitOfWork, lazy proxies and Reflection
Symfony HttpFoundation	1,419 tests · 0 errors · 12 SAPI failures	Request/response, headers, cookies, files and processes
Monolog	Runs	Composer autoloading and real standard-library usage

CURRENT LIMITS

Major examples include PostgreSQL, MySQLi, sodium, GD, LDAP, ODBC, sockets, FTP, XMLWriter and other specialist surfaces.

The HTTP server remains under development. Tests requiring a real php -S server do not have full parity.

Hardening, security surface, packaging and load performance have not reached the level required to replace PHP in production.