Discofork
Repository brief

Homebrew/brew

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-30T11:50:08.850Z
3mo ago

Homebrew/brew

Homebrew/brew is the main Homebrew package manager repository for macOS and Linux. It is active, widely used, and heavily forked, with documentation, contribution, troubleshooting, and release workflow material in-repo. Forks are most interesting if you care about package management tooling, formula/cask ecosystem work, or maintenance of a large Ruby-based OSS project with active upstream development.

GitHub
Loading tags...
Stars47,289
Forks11,046
Default branchmain
Last pushed2026-03-30T05:08:14Z
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

9 of 9 fork briefs
Selected

Prefer this fork only if you need its local maintenance and typing work and are prepared to own divergence. For most adopters, upstream Homebrew is the safer choice because this fork is stale and far behind.

Choose this fork only if you want a source-only Homebrew derivative and are prepared to maintain it yourself. If you want current Homebrew behavior, fixes, and ecosystem compatibility, upstream is the safer choice.

Choose upstream unless you specifically need a legacy OS X-era fork with these historical bugfixes. This fork is not a good default for new users or active maintenance because it is deeply stale and far behind current Homebrew.

Prefer this fork only if you need its older, customized Homebrew maintenance baseline or its Sorbet/vendor-tooling work. If you want current Homebrew functionality and upstream fixes, upstream is the safer choice.

Prefer upstream unless you need a personal starting point; this fork adds no visible features and is far behind current Homebrew development.

Choose this fork only if you specifically need its publishing or signing-related additions. For normal Homebrew use or active core development, upstream is the better choice because this fork is far behind and appears to have diverged into niche workflow material.

Choose this fork only if you want the specific local additions and are comfortable with a stale, highly diverged Homebrew base. For normal adopters, upstream is the better choice because this fork is far behind and carries substantial maintenance risk.

Choose this fork only if you need its historical divergence or downstream maintenance patches. For most adopters, upstream Homebrew is the better default because this fork is stale and materially behind current development.

Choose this fork only if you specifically need its local patches and are willing to own a large, stale divergence from upstream. For most adopters, upstream Homebrew is the safer choice because this fork is far behind and likely missing many recent fixes and workflows.