In this thread Jared said it was a fact of life that Homebrew would not anlways show updates as rapidly as MacUpdater, and that he thought the overhead to do as MacUpdater does is part of the reason for its demise.
I dont know the answer to your question about un-adopting from Homebrew, but the AI summary for “unadopt Homebrew Updatest” says (amongst other methods) it is
brew uninstall --cask <cask_name>. I’m sure Jared would reply quickly to the question.
I have now moved over to using Updatest as my primary update tool. I have adopted all adoptable apps, except App Store apps as recommended. (Updatest announces these and takes you to the App Store, like MacUpdater did). I still update some apps from within the app, mainly when it announces it self in the app.
Before doing this I asked Jared about risk of getting bad updates. This was his reply:
“ As with anything, there’s always a level of risk. When you’re talking about Sparkle, Electron and Mac App Store there’s 0 risk to updating your apps, period. These sources are pulled from the app binary themselves.
GitHub and Brew have a very small chance of having issues. Malware on Brew? I’m not sure, but it’s maintained by either the developer themselves or the community and Homebrew has a reputation to uphold. There’s a variety of safety checks in Brew (sha hashsum, integrity checks) also by default Brew typically flags every update it does for Gatekeeper (on your Mac by default) to scan too I think.
Most of the sources in Updatest that it fetches require manual action (GitHub, Electron, Mac App Store (due to sudo from MAS CLI), Brew (Password only apps)). The only apps that Updatest can auto install itself are Sparkle and Brew (non password apps).
Updatest was designed with security/privacy first. If that helps at all. Happy to answer any follow up questions! ”