wagoodman/dive

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.