homebrew-core VS homebrew-cask-versions

Is disabling the compromised repo the typical GitHub policy? My concern is there are monorepos used by package managers, like brew, that are a collection of thousands of projects [1]. These monorepos seem like a prime target for attack and if GitHub disables one because a malicious commit was merged then you've taken down an entire ecosystem.

[1] https://github.com/Homebrew/homebrew-core

> Correct. Though we do not appear to be affected, this revert was done out of an abundance of caution.

[1] https://github.com/Homebrew/homebrew-core/pull/167512

> right, but now you know even less about your setup when you some roadblock

This is the same with a binary though. And with homebrew, you can't follow patches or flags used or if they change.

- https://github.com/Homebrew/homebrew-core/blob/c964ad7fa53ad...

definitely be careful about using fortune in a corporate environment or public space if you don't know what dat files you are using or you might just get an extremely unwelcome surprise.

I was practicing a presentation and used to use "fortune" all the time. I forget exactly what it output but I remember being absolutely mortified about what could have happened if that had popped up during an internal company tech talk.

Kudos to brew for keeping unsuspecting people safe

https://github.com/Homebrew/homebrew-core/commit/3fb3c4c3e55...

I'm sorry to be asking this as I find it a bit silly, but it's blocking my PR [3], so could a few of you star the project on Github [1] to get my PR to run?

[1] https://github.com/laktak/chkbit-py

[2] https://brew.sh

[3] https://github.com/Homebrew/homebrew-core/pull/160018

https://github.com/Homebrew/homebrew-cask-versions/blob/master/Casks/safari-technology-preview.rb -> that would brew install safari-technology-preview then, remembered it right.

> If I just wanted to install google-chrome, sublime, and skype, I would use the app store.

None of those is available on the Mac App Store. I don’t understand the argument you’re trying to make.

> In contrast to how it used to be, Homebrew now seems designed for people that only want popular bleeding edge packages, and nobody else.

Homebrew Cask—which is what you’re referring to in the reminder of that paragraph—has always been focused on the latest versions of packages. The versions repo[1] is secondary with stricter rules for acceptance.

[1]: https://github.com/Homebrew/homebrew-cask-versions