Discofork
Repository brief

koalaman/shellcheck

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-31T09:57:24.116Z
1mo ago

koalaman/shellcheck

ShellCheck is a widely used GPLv3 static analysis tool for bash/sh shell scripts. It is active, with recent commits in March 2026, a large user base, and a substantial fork ecosystem, so forks are likely to be interesting if they target shell-script linting, editor integration, packaging, or CI support.

GitHub
Loading tags...
Stars39,191
Forks1,907
Default branchmaster
Last pushed2026-03-12T02:48:15Z
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 upstream unless your main need is the fork’s platform-specific Dockerfile hardening. This fork looks useful as a targeted security-maintenance snapshot, but it is too far behind upstream for most active ShellCheck users.

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.