Discofork
Repository brief

jesseduffield/lazydocker

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-30T12:55:21.505Z
3mo ago

jesseduffield/lazydocker

`jesseduffield/lazydocker` is an active, widely used Go-based terminal UI for managing Docker and Docker Compose. It has a large user base, strong recent activity, and a mature repo with docs, CI, release, and vendoring setup, which makes it a plausible fork candidate if you want to extend or specialize Docker workflow tooling rather than start from scratch.

GitHub
Loading tags...
Stars50,450
Forks1,592
Default branchmaster
Last pushed2026-03-15T22:26:04Z
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

Prefer this fork if your main need is packaging or installer customization and you are willing to manage upstream drift. Prefer upstream if you want the latest fixes, active project-support changes, and the least maintenance burden.

Prefer this fork only if you want a nearly untouched historical snapshot and are prepared to maintain it yourself. For most adopters, the active upstream is the better starting point because this fork is far behind and shows no meaningful feature development.

Prefer upstream unless you specifically need an unmodified, older baseline. This fork adds nothing concrete and is materially behind on maintenance and bug fixes.

Choose the upstream project unless you specifically want an old, unmaintained snapshot; this fork adds no visible value and is far behind current lazydocker development.

Choose the upstream project unless you specifically need an untouched, old snapshot. This fork offers no added functionality and is materially outdated.

Prefer upstream unless you specifically need the Linux install/update script or one of the small UI fixes; this fork is too stale for most adopters and is best treated as a narrow, personal customization.

Choose this fork only if you need a near-upstream snapshot to pin or extend yourself; otherwise upstream is the better default because this fork currently adds nothing visible and is already behind by three commits.

Choose this fork if Podman is the target runtime and you value live event updates plus Linux build compatibility. Stay with upstream if you need the broadest, most current Docker/Compose support.

Choose upstream unless you specifically need this older snapshot or plan to build your own fork from it. As-is, it adds no visible capability over upstream and lags on fixes and improvements.

Prefer upstream unless you specifically want a frozen copy to modify yourself. This fork does not show added capabilities and is already 20 commits behind, so it offers less safety and no clear user-facing advantage.