666ghj/BettaFish

Prefer upstream unless you specifically need a frozen copy. This fork does not add user-facing capabilities and is materially stale relative to upstream, so it is better as a baseline than as an adoption target.

Prefer upstream unless you specifically need a frozen snapshot. This fork adds no visible capabilities and is materially behind on maintenance and fixes.

Choose this fork only if you want a clean contribution branch; otherwise prefer upstream, since this fork adds nothing visible and is behind on recent fixes.

This fork is best treated as an outdated snapshot of BettaFish, not a differentiated alternative. If you want the current project and its recent fixes, upstream is the better choice; choose this fork only if you need a fixed base to modify yourself.

Choose this fork only if you specifically need this older snapshot; otherwise upstream is the better default because it is actively maintained and materially ahead.

Prefer upstream unless you specifically need this exact older snapshot; this fork appears to add no new capability and is materially behind on maintenance.

Prefer upstream unless you specifically need this snapshot as a private starting point; this fork adds no visible capabilities and is materially behind current upstream maintenance.

Prefer upstream unless you need this exact fork as a private starting point. It adds no visible product value yet appears materially behind on maintenance, so adopters should expect extra upgrade work and fewer recent fixes.

Prefer upstream unless you specifically need this older, near-vanilla snapshot. This fork adds no visible capabilities and is far enough behind that most adopters will be better served by the actively updated upstream.