/jump to repo

Repos Recent Bookmarks Watched Notes Tags Discover Compare Stats GitHub

Repository brief

square/retrofit

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-30T16:00:11.994Z

1mo ago

square/retrofit

Square/retrofit is a widely used, actively maintained type-safe HTTP client for Android and the JVM. It has a large ecosystem footprint, with 43,907 stars and 7,357 forks, and recent commits show ongoing maintenance as of 2026-03-30.

Loading tags...

Stars43,907

Forks7,357

Default branchtrunk

Last pushed2026-03-30T09:51:45Z

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

9 of 9 fork briefs

Maintenance:

Magnitude:

Sort:

Selected

Choose this fork only if its custom request-building/processor behavior is the point; otherwise upstream Retrofit is the safer default because this fork is stale, highly diverged, and missing a lot of upstream maintenance and supporting infrastructure.

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.

Fork comparison

yongjhih/NotRetrofit

38/100

stale

significant_divergence

Choose this fork only if its custom request-building/processor behavior is the point; otherwise upstream Retrofit is the safer default because this fork is stale, highly diverged, and missing a lot of upstream maintenance and supporting infrastructure.

Likely purpose

Provide an alternate Retrofit-style client with extra request-builder ergonomics and processor-driven code generation, rather than tracking upstream Retrofit closely.

Best for

Teams maintaining legacy code that already depends on this fork's custom Retrofit behavior.; Developers who specifically want annotation-processor or builder-centric request generation.; Users willing to trade upstream freshness and ecosystem breadth for local behavioral changes.

Additional features

Supports `@QueryMap` and builder-style configuration for base URL and headers.
Includes a `retrofit-processor` module, suggesting annotation-processor/codegen-driven workflows.
Fixes callback success handling on the I/O thread and other request-execution edge cases.
Appears to keep custom Retrofit 1.x/2.x documentation and examples alongside the codebase.
Adds plugin, tool, or MCP-style extensibility beyond the upstream baseline.
Introduces more operational workflow surface such as server-side handling, auth, session control, or admin tooling.

Missing features

Follows upstream with a large lag: the fork is last pushed in 2016 while upstream remains actively maintained.
Appears to drop or heavily trim upstream's broader supported ecosystem, including current companion modules and documentation/site material.
Many tests and website assets are removed, which makes regression coverage and adoption confidence lower than upstream.
No evidence here that it tracks upstream's current build/tooling, release process, or current API surface.
Some upstream behavior appears to be removed, disabled, or intentionally stripped down in this fork.
Some upstream plugin, tool, or MCP-style integration paths may be reduced or disabled.

Strengths

May suit teams that want older Retrofit behavior with custom builder ergonomics.
Processor-based workflow may be useful if the adopter wants generated client glue rather than only runtime annotations.
Some user-facing request features were added early, such as query maps and builder-set headers/base URL.

Risks

Materially stale relative to upstream, so security fixes, bug fixes, and compatibility updates are unlikely to be current.
Large deletion footprint and missing tests increase the chance of regressions and undocumented behavior changes.
High divergence makes migration back to upstream Retrofit harder.
Upstream ecosystem expectations, including modern docs and companion modules, may not be preserved.

square/retrofit · Discofork