Discofork
Repository brief

pmndrs/react-three-fiber

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:51:32.876Z
1mo ago

pmndrs/react-three-fiber

pmndrs/react-three-fiber is a TypeScript-based React renderer for Three.js, intended for building 3D scenes declaratively in React. It is active, widely used, and well-established: 30,442 stars, 1,798 forks, and a recent push on 2026-03-21.

GitHub
Loading tags...
Stars30,442
Forks1,798
Default branchmaster
Last pushed2026-03-21T04:24:10Z
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 the fork's custom renderer changes. This fork looks like a materially diverged, stale codebase that may still be valuable for existing consumers, but it is a poor default choice for new adopters who want active maintenance and current React/Three.js support.

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.