square/retrofit

Choose this fork only if you need its legacy Retrofit 1.x compatibility and convenience features right now. For new work, or anything that needs active maintenance and current Retrofit capabilities, upstream is the better default.

Prefer upstream unless you specifically need this older frozen baseline; this fork adds no visible capabilities and is materially behind current Retrofit maintenance.

Choose this fork only if you need its decoupled internal architecture or must stay on an older customized Retrofit line. If you want current Retrofit capabilities, active maintenance, and full module/docs parity, upstream is the better default.

Choose this fork only for legacy compatibility or its specific 2016-era patches. For new work or active maintenance, upstream Retrofit is the better choice.

Choose this fork only if you need an old Retrofit-era API and its Android-specific conveniences; for new work, upstream is the better default because it is actively maintained and much richer in features.

Prefer upstream unless you specifically need this fork’s custom exception/request behavior and are willing to own a stale, highly diverged maintenance burden.

Prefer upstream unless you explicitly need the fork's legacy adapter/converter behavior or a specific historical bugfix. This fork looks useful as a niche customization base, not as a general-purpose Retrofit upgrade path.

Choose this fork only if you need its legacy behavior or existing downstream changes. For new work, upstream Retrofit is the better default because this fork is stale, heavily diverged, and likely missing modern maintenance and ecosystem support.