pmndrs/react-three-fiber

Prefer upstream unless you specifically need an old snapshot; this fork adds no visible capabilities and is 75 commits behind a still-active upstream.

Choose this fork only if you need its older, specialized testing/runtime changes. For most adopters, upstream is the better default because it is far more current, actively maintained, and already includes newer React compatibility and maintenance work.

Choose this fork only if you want an old, highly customized branch and are prepared to own the maintenance burden. For most adopters, upstream is the safer choice because this fork is stale and materially behind current support and tooling.

Prefer upstream unless you specifically need the 2019 behavior or the fork’s custom examples/assets. This fork is too stale and too divergent for most new adopters, and it would require significant effort to recover modern compatibility and maintenance.

Choose this fork only if you need its custom renderer/event behavior or its web plus React Native direction. If you want the most current, low-risk react-three-fiber, upstream is the better default because this fork is materially behind and significantly diverged.

Prefer upstream unless you specifically need a frozen snapshot; this fork adds no evident capabilities and is materially behind current upstream maintenance.

Prefer this fork only if you need its older compatibility work or specific API shape. If you want current react-three-fiber behavior, upstream is the better choice because this fork is stale and materially behind.

Choose this fork only if the custom-scene behavior is the point. For most adopters, upstream is the safer choice because this fork is old, behind, and likely missing newer compatibility and maintenance work.

Choose this fork only if Cesium.js support is the core requirement. For general React + 3D work, upstream react-three-fiber is the safer default because this fork is stale and likely missing many recent upstream improvements.