/jump to repo

Repos Recent Bookmarks Watched Notes Tags Discover Compare Stats GitHub

Repository brief

wagoodman/dive

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-30T13:07:29.338Z

3mo ago

wagoodman/dive

wagoodman/dive is a mature Go-based CLI/TUI for inspecting Docker/OCI image layers and finding wasted space. It is actively maintained, has a very large user base, and appears to be a strong candidate for forks focused on image analysis, workflow integration, or UI/UX changes.

Loading tags...

Stars53,670

Forks1,971

Default branchmain

Last pushed2025-12-15T17:20:36Z

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

Choose this fork if you want dive with small but practical maintenance and workflow improvements, especially Containerfile support and fresher tooling. Stick with upstream if you want the absolute latest mainline fixes and do not need the fork-specific updates.

Prefer upstream unless you need the 2022 snapshot exactly. This fork adds no evident user-facing value and is too stale to recommend for normal adoption.

Choose this fork if you want dive’s core image-layer analysis plus Apple Containers support and UI refinements; stick with upstream if you want the safest, most established Docker/OCI-centric default.

Prefer upstream unless you explicitly need this fork's release/distribution changes. The fork looks like a workflow-tailored snapshot, not a stronger general-purpose replacement for dive.

Prefer upstream. This fork offers no clear added capability and is materially behind, so it is only sensible if you explicitly want an old, frozen snapshot.

Choose this fork only if you need the old Go 1.11 Travis setup and are comfortable maintaining everything else yourself. For most adopters, upstream is the clear choice.

Choose upstream unless you explicitly need this older frozen snapshot. This fork offers no added features, is stale, and trails upstream by 128 commits, so it is a poor default choice for new adopters.

Choose this fork only if you specifically want an old, frozen baseline. For normal adoption, upstream wagoodman/dive is the better choice because this fork shows no added value and is materially behind.

Prefer upstream unless you explicitly need an old frozen snapshot; this fork adds no evident value and is materially behind on maintenance, fixes, and newer CLI/build support.

Choose upstream unless you specifically need this exact snapshot; this fork adds nothing and is already behind on fixes and maintenance.

Fork comparison

jauderho/dive

71/100

active

moderate

Choose this fork if you want dive with small but practical maintenance and workflow improvements, especially Containerfile support and fresher tooling. Stick with upstream if you want the absolute latest mainline fixes and do not need the fork-specific updates.

Likely purpose

A maintained downstream of dive that tracks upstream closely while adding recent dependency refreshes, build/runtime tweaks, and workflow support for users who want a current, patch-forward copy of the CLI/TUI rather than a radically different product.

Best for

Teams already using dive who want a lightly differentiated but actively maintained fork.; Users who want Containerfile-aware build-and-analyze workflows.; Adopters who care about updated dependencies, CI reliability, and release automation more than new product areas.; People who prefer a conservative fork that preserves the upstream UX and command model.

Additional features

Containerfile support for the `dive build` workflow.
Updated build and runtime plumbing across the CLI, UI, image resolution, and CI/export paths.
More recent dependency and tooling updates, including Docker CLI and GitHub Actions bumps.
Ongoing release and validation workflow maintenance for adopters who care about packaging and CI stability.
Changes agent workflow behavior, such as prompt handling, handoffs, worktrees, memory, or orchestration flow.

Missing features

It is 25 commits behind upstream, so users may miss the newest upstream bug fixes and maintenance changes not yet merged here.
Any upstream improvements after the merge base are not present here, which can matter if you want the latest release workflow or command-structure refinements from main.

Strengths

Active recent development through March 2026.
Stays close to upstream dive, so migration cost should be low.
Good fit for users who want a familiar image-inspection tool with incremental improvements rather than a forked redesign.
Useful if you value a fork that keeps dependencies and CI tooling fresher.

Risks

The fork is still behind upstream, so some fixes or edge-case improvements may be missing.
No evidence of major new platform support or a broad feature expansion, so adopters should not expect a substantially different product.
Because the changes are incremental, the fork’s long-term advantage depends on continued maintenance.