koalaman/shellcheck

Choose this fork only if you need the 2014-era codebase and its local customizations. For normal shell-script linting, upstream ShellCheck is a much better choice because this fork is highly stale and materially diverged.

Choose this fork only if you specifically need its added checks or output format and can accept being far behind upstream; most adopters should prefer current ShellCheck.

Prefer upstream. This fork adds no visible capabilities and is materially behind, so adopters should only choose it if they explicitly need an unmodified 2022 snapshot.

Prefer upstream unless you specifically need this fork’s custom analysis/parsing work. The fork looks experiment-driven and materially outdated, so adopters should expect missing recent fixes and higher maintenance risk.

Prefer upstream ShellCheck unless you already know you need this fork's unpublished history. The available evidence shows divergence, but not concrete user-facing improvements.

Prefer this fork only if you specifically need its fork-branded site or license changes; otherwise upstream is the better choice because it is more current and better maintained.

Prefer upstream ShellCheck for normal use; this fork offers no added capabilities and is behind recent upstream maintenance, so it is only attractive as a clean baseline for your own changes.

Choose upstream instead unless you specifically need this fork as a starting point or pinned baseline; it adds no visible features and is materially behind current ShellCheck.

Prefer upstream unless you specifically want an unmodified snapshot. This fork adds no new capabilities and is far enough behind that it likely misses current fixes, CI compatibility work, and rule updates.