Homebrew gathers anonymous analytics using InfluxDB. You will be notified the first time you run
brew update or install Homebrew. Analytics are not enabled until after this notice is shown, to ensure that you can opt out without ever sending analytics data.
Homebrew is provided free of charge and run entirely by volunteers in their spare time. As a result, we do not have the resources to do detailed user studies of Homebrew users to decide on how best to design future features and prioritise current work. Anonymous analytics allow us to prioritise fixes and features based on how, where and when people use Homebrew. For example:
Homebrew’s anonymous analytics has a 365 day retention period in InfluxDB.
Homebrew’s analytics record some shared information for every event:
trueif the CI environment variable is set.
/opt/homebrew) or a custom one (e.g.
/home/mike/.brew). If your prefix is custom, it will be sent as
custom-prefixto preserve anonymity.
HOMEBREW_DEVELOPERenvironment variable is set.
devcmdrunis set, e.g.
trueif you have ever run one of Homebrew’s developer commands.
All analytics data previously sent to Google Analytics has been destroyed.
Homebrew’s analytics records the following different events:
installevent category and the Homebrew formula from a non-private GitHub tap you install plus any used options (e.g.
wget --HEAD) as the action. This allows us to identify which formulae where work should be prioritised, as well as how to handle possible deprecation or removal of any.
install_on_requestevent category and the Homebrew formula from a non-private GitHub tap you have requested to install (e.g. when explicitly named with a
brew install) plus options. This allows us to differentiate the formulae that users intend to install from those pulled in as dependencies.
cask_installevent category and the Homebrew cask from a non-private GitHub tap you install as the action. This allows us to identify which casks where work should be prioritised, as well as how to handle possible deprecation or removal of any.
build_errorevent category and the Homebrew formula plus options that failed to install as the action, e.g.
wget --HEAD. This allows us to identify formulae that may need fixing. The details or logs of the build error are not sent.
You can also view all the information that is sent by Homebrew’s analytics by setting
HOMEBREW_ANALYTICS_DEBUG=1 in your environment. Please note this will also stop any analytics from being sent.
It is impossible for the Homebrew developers to match any particular event to any particular user. We do not store or receive IP addresses.
Homebrew’s analytics are sent throughout Homebrew’s execution to InfluxDB over HTTPS.
Aggregates of analytics events are publicly available. A JSON API is also available. The majority of Homebrew maintainers are not granted more detailed analytics data beyond these public resources.
The code is viewable in
analytics.sh. They are done in a separate background process and fail fast to avoid delaying any execution. They will fail immediately and silently if you have no network connection.
Homebrew analytics helps us maintainers and leaving it on is appreciated. However, if you want to opt out of Homebrew’s analytics, you can set this variable in your environment:
Alternatively, this will prevent analytics from ever being sent:
brew analytics off