/jump to repo

Repos Recent Bookmarks Watched Notes Tags Discover Compare Stats GitHub

Repository brief

google/guava

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-30T12:50:43.949Z

3mo ago

google/guava

Google Guava is a large, actively maintained Java core libraries repository with very high adoption and fork/star counts. It targets JVM development, offers separate JRE and Android flavors, and is organized as a multi-module Maven project with extensive tests and integration support.

Loading tags...

Stars51,514

Forks11,156

Default branchmaster

Last pushed2026-03-23T21:06:48Z

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

Maintenance:

Magnitude:

Sort:

Selected

Prefer this fork only if you specifically need its Android/J2KT-oriented divergence or other fork-local changes. For most adopters, upstream Guava is the better choice because this fork is stale, heavily diverged, and likely missing years of maintenance.

Prefer this fork only if you specifically need its translation-target and code-quality adaptations. If you want a general-purpose Guava dependency, upstream is the safer choice because this fork is stale, heavily diverged, and likely missing newer upstream fixes and refinements.

Prefer this fork only if you want its specific compatibility and modernization changes and are willing to own a long-term divergence from upstream. If you mainly want a stable, well-maintained Guava dependency, upstream is the better default.

Prefer this fork only if you specifically need its older, locally curated changes and are prepared to carry merge debt. For most users, active upstream Guava is the safer choice because this fork is stale and materially behind.

Choose this fork only if primitive-collection performance or lambda-collector ergonomics are the priority and you can own the maintenance cost. If you want a stable, broadly compatible Guava dependency, upstream is the safer choice.

Prefer upstream unless you specifically need this exact historical snapshot; this fork currently behaves like a stale mirror rather than an enhanced alternative.

Prefer upstream `google/guava` unless you specifically need this exact snapshot. This fork adds no visible capabilities and is substantially behind, so it offers little adopter value beyond being a mirror.

Choose this fork only if you need its Android-oriented API exposure or existing local behavior. If you want a stable, low-maintenance dependency, upstream Guava is the safer choice because this fork is stale and materially behind.

Prefer this fork only if its Android/J2CL and internal-maintenance changes are specifically valuable to you. For most adopters, current upstream Guava is the safer default because this fork is stale and materially diverged.

Prefer upstream unless you specifically need this exact older revision; the fork adds nothing new and is 128 commits behind.

Fork comparison

deeptesh-rout/guava

38/100

stale

significant_divergence

Prefer this fork only if you specifically need its Android/J2KT-oriented divergence or other fork-local changes. For most adopters, upstream Guava is the better choice because this fork is stale, heavily diverged, and likely missing years of maintenance.

Likely purpose

To serve as a custom Guava branch for environments that need Android compatibility, J2KT-related changes, or fork-specific test/runtime behavior rather than the current upstream release train.

Best for

Teams maintaining an older Android or J2KT integration that depends on these fork-specific changes; Users who need to study or preserve a custom Guava branch rather than adopt the latest upstream; Projects that value a tailored fork over current upstream stability and release cadence

Additional features

J2KT compatibility work, including an explicit sequential executor implementation for j2kt super source
Android-specific library and test adjustments across `android/` and `guava-tests/`
Large-scale test modernization and compatibility edits in concurrency, cache, and futures test suites
Fork-specific release/build cleanup such as removing open-source release baggage and updating dependency versions
Adds or extends platform-specific client support, such as mobile, Android, iOS, or desktop packaging.
Changes agent workflow behavior, such as prompt handling, handoffs, worktrees, memory, or orchestration flow.

Missing features

Current upstream Guava maintenance after July 2024, including recent bug fixes and API polish
The current upstream release line and its latest JRE/Android flavor updates
Upstream changes in modules and tests added after the fork point, especially around concurrency, cache, and Android compatibility
The breadth of upstream’s active multi-module maintenance cadence
Some upstream behavior appears to be removed, disabled, or intentionally stripped down in this fork.
It trails upstream by 200 commits, so some recent upstream features and fixes are likely not present yet.

Strengths

Likely useful if you need a frozen, customized Guava base with extra compatibility work
Strong focus on Android and test behavior rather than just library code
Divergence suggests the fork may already include changes needed for a specific downstream toolchain or runtime

Risks

The fork is old enough that it may miss important upstream fixes and compatibility work
Large divergence makes rebasing or upgrading harder
Unknown behavior drift in core utilities and tests because the fork is far behind upstream
Low community traction compared with upstream