google/guava

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.