Discofork
Repository brief

square/okhttp

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:47:53.092Z
3mo ago

square/okhttp

OkHttp is Square’s actively maintained HTTP client for JVM, Android, and GraalVM. It is widely used, with high fork and star counts, and the repo is currently active on the master branch. The project emphasizes efficient defaults, modern HTTP/TLS support, and a principled API with limited configurability.

GitHub
Loading tags...
Stars46,916
Forks9,278
Default branchmaster
Last pushed2026-03-30T06:28:41Z
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
Selected

Choose the fork only if you want a Chinese-annotated, educational snapshot of older OkHttp internals. Choose upstream if you need an actively maintained HTTP client, current fixes, and the full module set.

Prefer this fork only if you need its custom repo/workflow shape or must stay on its older baseline. If you want current OkHttp behavior, active maintenance, and the full upstream feature set, upstream is the safer choice.

Prefer this fork only if you are maintaining a legacy Java 1.6 or old Android application and need the fork-specific compatibility behavior. For new or actively maintained systems, upstream OkHttp is the better choice by a wide margin.

Prefer upstream unless you specifically need this frozen baseline; the fork adds no visible value and is already behind on fixes.

Prefer this fork only if you need its legacy behavior or custom internals and are willing to own the maintenance burden. For new work, upstream OkHttp is the better default because it is active and far more complete.

Prefer upstream unless you specifically need this older, divergent fork for legacy compatibility or to preserve its backported fixes. For new work, the fork’s age and drift make it a poor default choice.

Choose this fork only for legacy compatibility. If you can adopt modern OkHttp, upstream is the better default by a wide margin.

Choose upstream unless you specifically need the fork’s multiplatform/experimental HTTP/3 direction and are prepared to maintain a large diverged codebase. For general OkHttp adoption, this fork is too stale and too far from upstream to be the safer default.

Choose this fork only if you specifically need its legacy compatibility and backported fixes. For most adopters, upstream OkHttp is the safer choice because this fork is stale and materially behind current capabilities.

Prefer upstream unless you must keep a legacy 2017 OkHttp baseline or depend on the fork's early API/behavior changes; this fork is too stale for new adopters.

square/okhttp · Discofork