HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
Homebrew
brew
Ruby2016–2026
Homebrew / brew

brew

đŸș The Package Manager for Everywhere

158Distinct people
201Mentions
0Explicit recommenders
50.3KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

đŸș The Package Manager for Everywhere

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 12:56:33 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year201 dated mentions

Observed mentions: 2016-04-04 18:36:42 UTC to 2026-09-13 13:02:51 UTC.

010203040502016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 47 mentions; 7 submissions, 40 comments20162017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 16 mentions; 0 submissions, 16 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 8 mentions; 0 submissions, 8 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 13 mentions; 0 submissions, 13 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 29 mentions; 6 submissions, 23 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 36 mentions; 3 submissions, 33 comments20212022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 9 mentions; 1 submissions, 8 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 15 mentions; 3 submissions, 12 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 9 mentions; 1 submissions, 8 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 10 mentions; 1 submissions, 9 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 9 mentions; 0 submissions, 9 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC47740
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC16016
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC808
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC13013
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC29623
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC36333
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC918
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC15312
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC918
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC1019
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC909

What Hacker News says

9 sources
The article is written by the primary contributor to homebrew and based off the author's interactions with users. Homebrew does indeed have both sponsors and donations... https://github.com/homebrew/brew#donations And I find it beyond credibility to believe that the primary contributor is not taking any money for his work on homebrew. Because while homebrew undoubtedly costs some money to host, a vast majority of the hosting is done using GitHub's public repositories.
In Entitlement in Open Source
There are two trends at work here: the most generic is the tendency for clickbait to drown out more substantial work. In this case, the provocative title isn't supported by the contents so it'll leave most readers disappointed. The second is that there are a lot of HN users who are active open source developers and that community has grown increasingly tired of whining by people who feel entitled to have their opinions shape projects without doing any work to help those projects. Starting with “Brew Is a Bad Neighbor”, he basically craps all over a huge amount of work which hundreds of developers have given him for free and can't even acknowledge things like them having given him the ability to do exactly what he wants – note the little snide parts like “(grudgingly?)” or the way the information presented in the default documentation is d
Read the rest
escribed as some kind of secret reveal. Note that he has _never_ attempted to contribute to either project: https://github.com/Homebrew/homebrew-core/issues?q=author%3A... https://github.com/Homebrew/brew/issues?q=author%3Apudquick It's perfectly fine not to contribute to projects you use, or to have strong opinions about how to architect things, but it'll definitely rub people the wrong way to not to contribute but have a “Why Wasn't I Consulted!?!” post. It's also common for people here to question things because they don't agree that a particular post is worth the community's time. Many of the comments here seem like meta-discussion to the submitter.
In Brew Is a Bad Neighbor
The question in that thread, and this later thread,[1] is how to know which keys are valid to sign a package. For example: I go to release a new version and I've lost my private key, so I roll a new one -- this will happen often across npm's 1.3 million packages. Do I then ... log in with my email and update the private key on my account and go about my business? What process does npm use to make sure my new key is valid? Can a person with control over my email address fake that process? How are key rotations communicated to people updating packages -- as an almost-always-false-positive red flag, or not at all, or some useful amount in between? If you don't get this part of the design right -- and no one suggests how to in those threads -- then you're just doing hashes with worse UX. And the more you look at it, the more you might start t
Read the rest
o think (as the npm devs seem to) that npm account security is the linchpin of the whole thing rather than signing. It's not just npm; that thread includes a PyPI core dev chipping in with the same view: "Lots of language repositories have implemented (a) [signing] and punted on (b) and (c) [some way to know which keys to trust] and essentially gained nothing. It's my belief that if npm does (a) without a solution for (b) and (c) they'll have gained nothing as well." It also has a link from a Homebrew issue thread deciding not to do signatures for the same reason -- they'd convey a false expectation without a solution for key verification.[2] [1] https://github.com/node-forward/discussions/issues/29 [2] https://github.com/Homebrew/brew/pull/4120#issuecomment-4068...
In NPM Vulnerability Discussion on Twitter
And to do that, as a package maintainer, you sometimes have to trace upstream’s build system because you need to intercept the file after the build system has patched it, but before they’re actually using it to run the tests. And then you try to inject the codesign command line into the upstream build system, and hope it’s going to work this time. And often enough, it just doesn’t work at all ([1] ballpark number of issues, [2] one example case where I can confirm that I was affected myself). Apple’s codesigning is hell. [1]: https://github.com/search?q=org%3AHomebrew+codesign&type=iss... [2]: https://github.com/Homebrew/brew/issues/7857#issuecomment-71...
In Richard Stallman – The state of the Free Software movement

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.