bumptech/glide

Prefer this fork only if you specifically need its legacy custom behavior and are prepared to maintain a large delta yourself. For most adopters, upstream Glide is the safer choice because this fork is stale and materially behind.

Prefer upstream unless you specifically need this older frozen state. This fork adds no visible capabilities, is stale, and is significantly behind upstream maintenance.

Choose this fork only if you need an old, stable Glide snapshot and accept missing recent fixes and build modernization. For most adopters, upstream is the safer choice.

Prefer upstream unless you specifically need the older 2024-era snapshot; this fork adds no visible functionality and lags materially behind on maintenance and fixes.

Prefer upstream unless you specifically need this older frozen revision; this fork adds no visible functionality and is behind on maintenance, fixes, and build modernization.

Prefer upstream unless you specifically need this fork’s legacy API or patched behavior. This fork is only attractive for projects locked to older Glide semantics; otherwise its age and divergence make it a maintenance burden.

Prefer upstream Glide unless you need this fork's older generated-API behavior or are already dependent on it. For new adoption, the fork is too stale and too far behind upstream to be the safer choice.

Prefer this fork if you want Compose/KTX/KSP-oriented Glide workflows and are comfortable owning a stale, highly divergent codebase. Prefer upstream if you want the broadest compatibility, active maintenance, and the lowest integration risk.

Prefer this fork if you need the added Compose/KTX/KSP and cache-workflow changes and are comfortable maintaining a stale, diverged codebase. Prefer upstream if you want the latest maintained Glide, lower maintenance risk, and broader compatibility with current releases.