/jump to repo

Repos Recent Bookmarks Watched Notes Tags Discover Compare Stats GitHub

Repository brief

bumptech/glide

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-30T20:01:20.863Z

1mo ago

bumptech/glide

Glide is a mature Android image-loading and caching library focused on smooth scrolling and efficient media handling. It is actively maintained, widely forked and starred, and the repo shows ongoing work on build modernization and cache behavior.

Loading tags...

Stars35,029

Forks6,183

Default branchmaster

Last pushed2026-03-30T17:20:10Z

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

Maintenance:

Magnitude:

Sort:

Selected

Prefer this fork only if you specifically need its older Airbnb-tuned Glide behavior. For new adopters, upstream Glide is the safer default because this fork is stale and materially behind current maintenance.

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.

Fork comparison

airbnb/glide

38/100

stale

significant_divergence

Prefer this fork only if you specifically need its older Airbnb-tuned Glide behavior. For new adopters, upstream Glide is the safer default because this fork is stale and materially behind current maintenance.

Likely purpose

Adopt Glide as a customized internal image pipeline for an Android app, with request-behavior and cache/disk-cache changes tuned for app-specific performance and rendering needs.

Best for

Teams already depending on this exact older Airbnb Glide behavior.; Android apps that need bespoke image-cache and request-lifecycle tuning more than upstream parity.; Maintainers willing to own a long-lived fork and backport upstream fixes manually.

Additional features

Custom disk-cache experimentation via the `sqljournaldiskcache` integration path.
Request-behavior adjustments such as disabling cross-fade by default, padding-aware targeting, and allowing some main-thread access when work is already complete.
Concurrency and scheduling tweaks around decode priority and request clearing to reduce jank and deadlock risk.
Adds or extends platform-specific client support, such as mobile, Android, iOS, or desktop packaging.
Changes agent workflow behavior, such as prompt handling, handoffs, worktrees, memory, or orchestration flow.
Adds performance-oriented execution paths, caching, or faster runtime modes.

Missing features

It is far behind current upstream Glide, so it likely lacks many newer upstream bug fixes, build modernizations, and cache behavior improvements.
Modern upstream maintenance work such as Gradle/Kotlin DSL cleanup and newer tooling support is absent or hard to use here.
The fork appears to carry a large amount of historical divergence, making newer upstream APIs, tests, and integrations harder to adopt directly.
Some upstream behavior appears to be removed, disabled, or intentionally stripped down in this fork.
It trails upstream by 200 commits, so some recent upstream features and fixes are likely not present yet.

Strengths

Useful if you need the forked request and cache behavior exactly as shipped.
Could suit teams maintaining an older Android stack that prefers conservative Glide behavior.
The fork shows deliberate changes around scrolling smoothness, cache behavior, and request lifecycle correctness.

Risks

Very stale activity: the fork was last pushed in 2016.
Large divergence from upstream increases merge and security-maintenance risk.
Many upstream improvements are likely missing, so adopters may inherit outdated behavior and tooling.