preactjs/preact

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.