Discofork
Repository brief

phaserjs/phaser

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-31T09:47:09.333Z
1mo ago

phaserjs/phaser

Phaser is a large, actively maintained open source HTML5 2D game framework for desktop and mobile browsers, with Canvas and WebGL rendering. It is very mature, with strong adoption signals: 39,255 stars, 7,123 forks, and a recent release at v3.90.0.

GitHub
Loading tags...
Stars39,255
Forks7,123
Default branchmaster
Last pushed2026-03-31T04:40:28Z
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
Selected

Prefer upstream unless you specifically need this exact snapshot; the fork adds no evident capabilities and is far behind current Phaser.

Choose this fork only if you are intentionally staying on legacy Phaser 2 and want its custom build outputs. For new work, or anything that needs current Phaser capabilities, upstream is the better choice.

Choose this fork only for legacy Phaser 2 work or archival needs; for any new game project, upstream Phaser is the better choice because this fork is very stale and substantially diverged.

Prefer upstream Phaser unless you specifically need this older snapshot; this fork adds no visible capabilities and mainly carries the risk of missing newer fixes and maintenance.

Choose this fork only if you need its legacy behavior or embedded Spine/asset workflow changes and are prepared to live on an old codebase. For new work, upstream Phaser is the safer default.

Prefer this fork only if you are maintaining legacy Phaser 2 assets or need its custom build shapes. For new work or anything that needs current Phaser 3 features, upstream is the safer default.

Prefer this fork only if you specifically need its local fixes and are willing to stay on an old, diverged Phaser branch. For new work or active maintenance, upstream Phaser is the safer choice.

Prefer this fork only if you are locked to its legacy behavior or its loader/resource patches. For new work, or if you want current Phaser features and fixes, upstream is the better choice.

Prefer this fork only if you need an old, frozen Phaser snapshot with bundled artifacts. For new work or active maintenance, upstream is the better choice.

Choose upstream Phaser unless you specifically need this mirror. This fork adds no visible capability and is simply a slightly outdated copy, so adopters should expect the upstream project to be the better default.