Discofork
Repository brief

ReactiveX/RxJava

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-30T11:46:26.774Z
3mo ago

ReactiveX/RxJava

RxJava is a large, active JVM library for composing asynchronous and event-based programs with observable sequences. The repo is the 4.x line, recently updated on 2026-03-30, and appears highly mature and widely adopted, with 48,449 stars and 7,601 forks.

GitHub
Loading tags...
Stars48,449
Forks7,601
Default branch4.x
Last pushed2026-03-30T07:28:23Z
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

9 of 9 fork briefs
Selected

Choose this fork only if you need legacy RxJava 1.x compatibility and are willing to own a stale, highly diverged codebase. If you want active maintenance, modern JVM support, or upstream alignment, the main RxJava line is the better fit.

Choose this fork only if you explicitly need the older 2.x API and are willing to own a very stale codebase. For new work or active maintenance, upstream 4.x is the safer choice.

Choose this fork only if you specifically need a legacy RxJava 3 branch and are prepared to maintain it yourself. If you want current support, platform updates, or active upstream compatibility, upstream RxJava 4 is the better choice.

Choose this fork only if you must stay on the old RxJava 1.x API surface. For new work or active maintenance, upstream RxJava 4 is the better default because this fork is stale and materially behind.

Prefer upstream unless you explicitly need the older 3.x branch. This fork does not show added features, and its main value is legacy compatibility rather than active improvement.

Choose this fork only if you need a legacy RxJava 2.x-compatible line and can accept being materially behind upstream. For new work or active migration paths, upstream RxJava 4.x is the safer default.

Prefer upstream unless you specifically need an old RxJava 2.x snapshot. This fork is not a good default adoption target for new work; it is only attractive for legacy compatibility or historical backporting.

Prefer this fork only if you must stay on RxJava 1.x. For new work, or if you want current JVM support and active maintenance, upstream RxJava 4.x is the better choice.

Choose this fork only if you need the legacy API and its extra integrations; for new work or active maintenance, upstream is the better choice by a wide margin.