stats README

The project's README from github.com/exelban/stats. As one markdown file: README.md.

Stats

Stats Stats

macOS system monitor in your menu bar

Installation

Manual

You can download the latest version here. This will download a file called Stats.dmg. Open it and move the app to the application folder.

Homebrew

To install it using Homebrew, open the Terminal app and type:

brew install stats

Uninstall

Run the uninstall script bundled with the app (requires administrator privileges to remove the SMC helper):

sh /Applications/Stats.app/Contents/Resources/Scripts/uninstall.sh

The script quits Stats and removes:

If the app has already been moved to the Trash, the script can be run directly from the repository:

curl -fsSL https://raw.githubusercontent.com/exelban/stats/master/Kit/scripts/uninstall.sh | sh

Legacy version

Legacy version for older systems could be found here.

Requirements

Stats is supported on macOS 12 (Monterey) and newer. Beta versions of macOS are not supported - only stable releases.

Features

Stats is an application that allows you to monitor your macOS system.

FAQs

How do you change the order of the menu bar icons?

macOS decides the order of the menu bar items not Stats - it may change after the first reboot after installing Stats.

To change the order of any menu bar icon - macOS Mojave (version 10.14) and up.

  1. Hold down ⌘ (command key).
  2. Drag the icon to the desired position on the menu bar.
  3. Release ⌘ (command key)

Stats icons do not appear in the menu bar

macOS 26 introduced a new privacy control under System Settings → Menu Bar. Apps must be explicitly allowed there to display menu bar items. If Stats is running with at least one module active and one widget enabled, but none of its icons show up in the menu bar, this is almost certainly the cause. More details you can find here.

Solution: open System Settings → Menu Bar and toggle Stats ON.

Desktop widgets not showing the data

Due to a problem with high data load in the system process (chronod) responsible for communication between the app and widgets, communication is disabled by default on the Stats side. To enable it, the macOS widgets option must be enabled in the Stats settings. More details you can find here.

Solution: open Stats Settings and toggle macOS widgets ON.

How to reduce energy impact or CPU usage of Stats?

Stats tries to be efficient as it's possible. But reading some data periodically is not a cheap task. Each module has its own "price". So, if you want to reduce energy impact from the Stats you need to disable some Stats modules. The most inefficient modules are Sensors and Bluetooth. Disabling these modules could reduce CPU usage and power efficiency by up to 50% in some cases.

Fan control

Fan control is in legacy mode. It does not receive any updates or fixes. It's not dropped from the app just because in the old Macs it works pretty acceptable. I'm open to accepting fixed or improvements (via PR) for this feature in case someone would like to help with that. But have no option and time to provide support for this feature.

Sensors show incorrect CPU/GPU core count

CPU/GPU sensors are simply thermal zones (sensors) on the CPU/GPU. They have no relation to the number of cores or specific cores. For example, a CPU is typically divided into two clusters: efficiency and performance. Each cluster contains multiple temperature sensors, and Stats simply displays these sensors. However, "CPU Efficient Core 1" does not represent the temperature of a single efficient core—it only indicates one of the temperature sensors within the efficiency core cluster. Additionally, with each new SoC, Apple changes the sensor keys. As a result, it takes time to determine which SMC values correspond to the appropriate sensors. If anyone knows how to accurately match the sensors for Apple Silicon, please contact me.

App crash – what to do?

First, ensure that you are using the latest version of Stats. There is a high chance that a fix preventing the crash has already been released. If you are already running the latest version, check the open issues. Only if none of the existing issues address your problem should you open a new issue.

Why my issue was closed without any response?

Most probably because it's a duplicated issue and there is an answer to the question, report, or proposition. Please use a search by closed issues to get an answer. So, if your issue was closed without any response, most probably it already has a response.

External API

Stats does not collect any telemetry or analytics. The only external requests it makes are to the following APIs:

Both of these APIs are used to check for updates. Additionally, an external request is required to obtain the public IP address. I do not want to use any third-party providers for retrieving the public IP address, so I use my own server for this purpose.

If you have concerns about these requests, you have a few options:

How to contribute to the project?

If you want to develop a new feature, or you've found something that doesn't work, the first step is to open an issue so the feature or problem can be discussed. Pull requests should only be opened for existing issues and after discussion; otherwise, they may be closed automatically. There are a few cases where this can be skipped: language changes, and contributors who have already made significant contributions and whose implementations align well with the project.

Open source, but not open contribution

Stats is an open-source project: the full source code is available under the MIT license, and you are free to read it, learn from it, fork it, and build your own version of the app.

However, it is not an open-contribution project. Stats is developed and maintained by a single person, and keeping the project stable and coherent takes priority over accepting every proposed change. Reviewing external code, testing it across different Macs and macOS versions, and maintaining it afterward often takes more time than writing it in the first place.

For that reason, unsolicited pull requests are generally not accepted and may be closed without review. If you want to change or add something, please open an issue first so it can be discussed. The exceptions are translations and language fixes, which are always welcome, and contributions from people who have already made significant contributions to the project.

The best ways to support the project are reporting bugs, improving translations, and proposing ideas through issues.

Supported languages

You can help by adding a new language or improving the existing translation.

License

MIT License

stats (exelban/stats)

Searching Database…

42.6K ·GitHub
这是什么?一款免费开源的 macOS 菜单栏系统监控工具:可以显示 CPU、GPU、内存、磁盘和网络的使用情况,还有电池电量、温度、蓝牙设备以及多时区时钟。
它是常驻菜单栏的,还是普通窗口应用?它是一个菜单栏应用——每个模块都在菜单栏里有自己的图标,点开下拉菜单就能看详细信息。也有桌面小组件,但默认是关闭的,需要在 Stats 的设置里手动开启。
风扇控制呢?完全支持吗?风扇控制目前处于遗留模式:不再有更新和修复,保留它只是因为在老 Mac 上还能勉强用。欢迎通过 pull request 提交修复和改进。
我的 Mac 能用吗?支持 macOS 12(Monterey)及更新版本,只支持正式版——macOS 测试版不在支持范围内。针对更老的系统,作者保留了旧版本。
它会把数据发到别处吗?没有任何遥测或数据统计。唯一的外部请求是检查更新,以及向作者自己的服务器请求一次,获取你的公网 IP 供网络模块使用——这两项都可以用防火墙软件屏蔽。
为什么在最新的 macOS 上菜单栏不显示图标?macOS 26 新增了一个隐私开关:应用必须在 系统设置 > Menu Bar 里被明确允许。打开这个设置,把 Stats 的开关打开即可。在此之前,Stats 虽然在运行,但不会显示任何图标。
那些传感器名称是指每个核心的温度吗?不是——它们是热区(thermal zone),不是核心:比如 'CPU Efficient Core 1' 指的是能效核心簇里的一个温度传感器。而且 Apple 每推出新的 SoC 都会更换 SMC 传感器键名,所以精确对应需要时间。
它会耗我的电池吗?每个模块都有开销,其中 Sensors 和 Bluetooth 的效率最低。在某些情况下,禁用它们最多能让 Stats 的 CPU 占用和功耗降低 50%。
它支持哪些语言?超过 35 种,包括英语、德语、法语、西班牙语、葡萄牙语、简体中文和繁体中文、日语、韩语、俄语、乌克兰语、波兰语和土耳其语——欢迎帮忙改进翻译。
Creator
exelban
Size
59.6 MB
Stars
42.6K
Age
7y
Commits · 90 Days