/jump to repo

Repos Recent Bookmarks Watched Notes Tags Discover Compare Stats GitHub

Repository brief

php/php-src

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis

cached 2026-03-30T15:39:24.347Z

1mo ago

php/php-src

php/php-src is the upstream source repository for the PHP interpreter. It is very active, widely used, and heavily forked, with 39,960 stars, 8,022 forks, and commits landing on 2026-03-30. The tree includes core engine code, extensions, tests, build tooling, docs, and Windows support, so forks can differ across runtime behavior, extensions, portability, and packaging.

Loading tags...

Stars39,960

Forks8,022

Default branchmaster

Last pushed2026-03-30T13:48:13Z

Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs

Maintenance:

Magnitude:

Sort:

Selected

Choose this fork only if you specifically need its `jit-dynasm`-oriented runtime changes and can own a large maintenance burden. For most adopters, upstream PHP is the safer and far more current base.

Prefer this fork only if you need a long-lived custom PHP source base and can absorb the maintenance cost. If you want current upstream PHP behavior, this fork is too far behind.

Prefer this fork only if you specifically need its historical downstream runtime/JIT behavior and are prepared to own a very stale codebase. For most adopters, upstream PHP is the safer choice.

Choose this fork if you want a customized PHP engine and are comfortable owning a large downstream patch set. Choose upstream if you want current fixes, lower maintenance risk, and maximum compatibility.

Adopt this only if you specifically want an almost-upstream PHP source tree and are comfortable inheriting upstream lag; it does not currently show any fork-specific value add.

Choose this fork only if you specifically need its custom engine and library changes and are prepared to maintain a heavily divergent PHP tree. For most adopters, upstream PHP is the safer choice because this fork is stale, far behind, and likely to require substantial maintenance work.

Prefer this fork only if its downstream changes are specifically useful to you and you can maintain a large rebase gap. If you mainly want a current PHP interpreter, upstream is the safer choice.

Prefer this fork only if you specifically need one or more of its local patches and are prepared to maintain a large downstream delta. If you want current PHP behavior, security fixes, and low maintenance overhead, upstream is the better default.

Choose this fork only if your goal is Docker-oriented PHP packaging and you are comfortable inheriting an old, heavily diverged codebase. For anything that needs current PHP runtime behavior or active upstream maintenance, upstream php/php-src is the better choice.

Prefer this fork only if you need its specific downstream patches or generated-data changes and are willing to own a stale, heavily diverged PHP tree. If you want current PHP behavior, security posture, and easier maintenance, upstream is the better default.

Fork comparison

zendtech/php-src

38/100

stale

significant_divergence

Choose this fork only if you specifically need its `jit-dynasm`-oriented runtime changes and can own a large maintenance burden. For most adopters, upstream PHP is the safer and far more current base.

Likely purpose

Experimenting with PHP engine internals and JIT/runtime behavior, likely for users who want a custom interpreter branch rather than current upstream compatibility.

Best for

Runtime or VM engineers who want to study or extend PHP execution internals.; Teams already committed to this exact fork and prepared to maintain a private PHP distribution.; Users who value experimental engine changes more than staying current with upstream PHP.

Additional features

Alternative `jit-dynasm` default branch for runtime/JIT experimentation.
Large local changes in core execution code (`Zend/zend_vm_execute.h`) suggest customized interpreter behavior.
Fork-specific updates to bundled runtime data and parsers, including fileinfo, date/timezone handling, and mbstring tables.
Build and CLI behavior tweaks reflected in commits around phpdbg and readline defaults.
Expands API, schema, or SDK surface area for downstream integrations and generated clients.
Adds performance-oriented execution paths, caching, or faster runtime modes.

Missing features

Falls far behind upstream: last push was in 2019 while upstream is active in 2026, so it misses years of PHP fixes, features, and security updates.
Likely lacks many upstream extension, test, and platform updates that landed after the fork point.
Upstream bug fixes in areas like stream filters, iconv, URI parsing, and INI handling are not present unless manually backported.
A revert of bison location tracking and phpdbg/readline build changes suggests upstream behavior may be harder to rely on for standard toolchains.
Some upstream behavior appears to be removed, disabled, or intentionally stripped down in this fork.
It trails upstream by 1143 commits, so some recent upstream features and fixes are likely not present yet.

Strengths

Potentially useful if you specifically need the `jit-dynasm` line of development.
May contain custom performance or engine changes not available upstream.
Could be attractive to teams maintaining an old PHP runtime baseline with controlled local patches.

Risks

Very large divergence from upstream makes rebasing, security patching, and support expensive.
The fork is materially outdated, so compatibility and CVE exposure are major concerns.
The scope of changes across core, extensions, and generated tables raises the chance of subtle runtime regressions.