Discofork
Repository brief

preactjs/preact

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:44:15.933Z
1mo ago

preactjs/preact

Preact is an actively maintained, MIT-licensed, fast React alternative focused on a small footprint and modern API compatibility. It has strong adoption signals (38k+ stars, 2k+ forks) and recent upstream activity on `main`, with the repo positioned as the branch for the upcoming release and a separate `v10.x` branch for v10 patches.

GitHub
Loading tags...
Stars38,523
Forks2,029
Default branchmain
Last pushed2026-03-30T18:35:20Z
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

9 of 9 fork briefs
Selected

Choose this fork if your goal is education, source annotation, or onboarding into Preact internals. Do not choose it if you need an actively maintained, upstream-aligned framework release.

Prefer upstream unless you specifically need this legacy TypeScript fork’s historical changes. The fork looks stale and far behind, but it may still be useful for legacy compatibility work where matching older behavior matters more than receiving current upstream fixes.

Prefer upstream unless you specifically need this frozen snapshot. This fork does not add features, and it lags upstream by 105 commits, so it is a poor choice for production adoption.

Choose upstream unless you specifically need this older, customized branch. This fork appears better suited to legacy maintenance or experimentation than to new adoption.

Prefer upstream unless you specifically need this historical snapshot. This fork is too stale and too far diverged for normal adoption, but it may still be valuable as a legacy reference or for reproducing old behavior.

Choose this fork only if you need its exact older behavior or already depend on its local changes. If you want an actively maintained Preact line with current fixes and compatibility work, upstream is the better default.

Choose this fork only if you need its local typing/compatibility changes and can accept owning maintenance. If you want current Preact, active fixes, and lower upgrade risk, upstream is the safer choice.

Prefer this fork only if you need its older compatibility and benchmark-oriented changes. For most adopters, upstream Preact is the better choice because it is actively maintained and much newer.

Adopt this fork only if you specifically need its older, customized baseline. For most users, upstream Preact is the safer choice because this fork is materially stale and significantly diverged.