veggiemonk/awesome-docker

Prefer upstream if you want current Docker curation. Prefer this fork only if you specifically want the added browsing/validation tooling and are willing to own a stale, highly divergent codebase.

Prefer upstream unless you specifically want an old, custom fork with tooling experiments; this fork is too stale for most adopters who need current Docker resources.

Choose this fork only if you want the added TUI/maintenance workflow and are comfortable with an older, significantly diverged content base. If you want the latest Docker resource curation, upstream is the better default.

Prefer upstream if you need current Docker recommendations. Prefer this fork only if you specifically want an older snapshot plus custom browsing or publication tooling and can accept substantial staleness.

Prefer this fork if you want a more tool-driven, customizable Docker resource browser and can tolerate falling behind upstream curation. Prefer upstream if the priority is the latest maintained list and lower merge burden.

Prefer this fork only if you specifically want the tooling and browsing workflow it adds. For most adopters, upstream is the better choice because it is actively maintained and materially newer.

Prefer upstream unless you specifically want this older fork’s custom tooling or historical snapshot. For anyone seeking current Docker resources, this fork is too stale and too far behind to be the default choice.

Choose the upstream repo if you want current Docker resources. Choose this fork only if you specifically want the older, tool-enhanced browsing/maintenance workflow and are comfortable with a stale, materially diverged snapshot.

Prefer upstream for a current, actively maintained Docker reference and site experience. Prefer this fork only if you specifically want its older, more specialized curation and are comfortable maintaining the catalog yourself.