DartEnv/dart-env
stale
significant_divergence
Selected Choose this fork only if Dart support is the main requirement. For general Gym adoption, upstream is newer and the fork is materially stale, so Gymnasium or modern Gym-compatible alternatives are the safer default.
NotAnyMike/gym
stale
significant_divergence
Choose this fork if your goal is the more complex CarRacing variant and related experimentation. Choose upstream Gym or Gymnasium if you need a maintained, broadly compatible RL toolkit with the full general-purpose API surface.
RobotLocomotion/gym
slowing
significant_divergence
Prefer this fork if your priority is RobotLocomotion/Drake simulation support and you want those environments embedded in a Gym-compatible package. Prefer upstream Gym or Gymnasium if you want broad compatibility, active maintenance, and minimal divergence.
EmbersArc/gym
stale
significant_divergence
Prefer this fork only if you already rely on its legacy customizations and are willing to own maintenance. For most adopters, upstream Gymnasium or current upstream-compatible alternatives are safer because this fork is both stale and materially diverged.
gdb/gym
stale
significant_divergence
Prefer this fork only if you need its legacy demonstration/replay and scoreboard-oriented changes. For most adopters, upstream or Gymnasium is the safer choice because this fork is old, materially divergent, and missing later RL environment and vectorization work.
tianheyu927/gym
stale
significant_divergence
Adopt this fork only if you specifically need its older customized behavior or scoreboard/headless setup. For most users, upstream Gymnasium or a current Gym-compatible stack is the safer choice because this fork is stale and materially diverged.
Arain-sh/gym
stale
significant_divergence
Choose this fork only if you need a legacy Gym snapshot with local runtime tweaks and are prepared to own the maintenance burden. If you want current Gym behavior, broader compatibility, or easier long-term support, upstream Gymnasium is the better path.
MingtaoGuo/gym
stale
significant_divergence
Prefer this fork only if you need its legacy behavior or custom rendering/workflow changes and can accept substantial staleness. For new projects or active maintenance, upstream Gymnasium or a current fork is the safer default.
ry/gym
stale
significant_divergence
Prefer this fork only if you explicitly need legacy Gym behavior or are maintaining code tied to this old snapshot. For new work, upstream Gymnasium or a current Gym-compatible stack is the safer choice.
hardmaru/gym
stale
significant_divergence
Choose this fork only if you need legacy Gym behavior or its custom headless/runtime changes. For new work, upstream Gymnasium or current Gym is the safer default because this fork is stale and materially behind upstream.