deeptesh-rout/guava
stale
significant_divergence
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.
imagination76/guava
stale
significant_divergence
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.
riduwan45/guava
stale
significant_divergence
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.
Mhassanbughio/guava
stale
significant_divergence
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.
linlinisme/beyond-guava
stale
significant_divergence
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.
tanzinabd23/guava
stale
significant_divergence
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.
bdsazzad3/guava
stale
significant_divergence
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.
parvin528/guava
stale
significant_divergence
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.
karknowzdeveloper-png/guava
stale
significant_divergence
Prefer upstream unless you specifically need this exact older revision; the fork adds nothing new and is 128 commits behind.