Open-source project
exelban/stats avatar
exelban/stats

Stats: A menu bar system monitor for macOS with a clear maintenance boundary

GitHub describes it as macOS system monitor in your menu bar. The repository metadata lists Swift as its primary language. The metadata lists the MIT license. This article stays within the project description and details documented in the GitHub repository README.

43,415 stars1,633 forksSwiftMIT

At a glance

What is it?
Stats puts CPU, GPU, memory, disk, network, battery, sensors, and Bluetooth data in the macOS menu bar. It is a mature Swift project under the MIT license, but its fan control is explicitly unmaintained and its widget support is disabled by default.
Who is it for?
Use Stats if you want a free, open-source menu bar monitor on macOS 12 or newer and you are comfortable with the project's single-maintainer pace. Avoid it if you need active fan control, because that feature is in legacy mode with no updates or fixes.
Can I use it commercially?
Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository received new commits within the last day.
What is it written in?
Mainly Swift, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • exelban/stats43,415 ★ · +2,247
Star history
Repository2026-08-132026-11-15
exelban/stats41.2k43.4k

2,247 Stars in the last 94 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

What Stats actually solves and who it is for

Stats solves a narrow problem: putting a set of live system readings into the macOS menu bar without opening Activity Monitor or a terminal. The README lists CPU utilization, GPU utilization, memory usage, disk utilization, network usage, battery level, fan control, sensor information, Bluetooth devices, and a multi-time-zone clock. That is the full feature set. It is for users who want glanceable data at the top of the screen, not a deep profiling tool. The target audience is macOS users on Monterey or newer who prefer open-source software and who are willing to read a FAQ before filing an issue. The project does not pretend to be an enterprise monitoring suite. The README's tone makes that clear: it gives troubleshooting steps, not a sales pitch.

How the data flows: modules, SMC helper, and the menu bar

The architecture is visible from the FAQ. Stats reads system data through modules, each with its own update cost. The most expensive modules are Sensors and Bluetooth, and the README advises disabling them to cut CPU usage and power consumption by up to 50% in some cases. The app also installs a privileged helper for SMC access. That helper is the reason the uninstall script requires administrator privileges. The app itself does not collect telemetry. The only external requests go to api.mac-stats.com for update checks and public IP retrieval, with api.github.com as a fallback for update checks. The README is explicit that blocking those servers means no updates and no public IP in the network module. That is a clear data-flow statement: local SMC reads, a single helper daemon, and two external endpoints.

Getting it running: Homebrew, DMG, and the uninstall script

Installation is straightforward. The README gives a DMG download and a Homebrew path for desktop use, plus a headless SSH installer. First, download Stats.dmg from the releases page, open it, and drag the app to the Applications folder. Second, use Homebrew with the command brew install stats. The Homebrew path is the one most engineers will choose because it makes updates predictable. Uninstall is also scripted. You run sh /Applications/Stats.app/Contents/Resources/Scripts/uninstall.sh, which needs administrator privileges to remove the SMC helper. The requirements are clear: macOS 12 (Monterey) and newer, with no beta macOS support.

The macOS 26 menu bar privacy toggle and the widget workaround

The README documents two failure modes that are easy to misdiagnose. On macOS 26, a new privacy control under System Settings → Menu Bar requires apps to be explicitly allowed to display menu bar items. If Stats is running with at least one module active and one widget enabled, but no icons appear, the cause is almost certainly that toggle. The fix is to open System Settings → Menu Bar and turn Stats ON. The second issue is with desktop widgets. Due to a problem in the system process chronod, which handles app-to-widget communication, Stats disables widget communication by default. You must enable the macOS widgets option in Stats settings to see data in widgets. Both of these are concrete, documented constraints. They are the kind of edge cases that would otherwise send a user down a rabbit hole of reinstalls and reboots. The README's directness here is a strength, even if the existence of such toggles is a minor annoyance.

Sensor readings are not what they appear to be

A critical limitation is how sensor data is presented. The README states that CPU and GPU sensors are simply thermal zones, not per-core readings. A label like 'CPU Efficient Core 1' does not mean that specific core's temperature; it means one temperature sensor within the efficiency cluster. The number of displayed sensors has no relation to the number of cores. On Apple Silicon, the sensor keys change with each SoC, so matching SMC values to physical sensors takes time. The author explicitly asks for help from anyone who knows how to map sensors accurately. This is a genuine caveat for anyone who plans to use Stats for thermal debugging. If you need per-core temperatures, Stats will mislead you. The documentation is honest about this, but the naming in the UI could easily fool a new user. That is a design trade-off worth knowing before you rely on the numbers.

Fan control is legacy, and that changes the calculus

The fan control feature is in legacy mode. The README says it does not receive updates or fixes, and it is kept only because it works acceptably on older Macs. The author is open to pull requests but will not support it. This is a significant boundary. If you are considering Stats specifically for fan control on a modern Mac, you should look elsewhere. The feature may work, but it will not be patched for new hardware or macOS versions. The rest of the app is actively maintained, with releases v3.0.22 to v3.0.24 between 2026-10-18 and 2026-11-01, so the project as a whole is not abandoned. But the fan control is a separate, frozen island within it. That distinction matters for engineers who evaluate dependencies based on maintenance status. The README's phrasing is unusually clear: 'It's not dropped from the app just because in the old Macs it works pretty acceptable.' That is a maintenance posture, and it is a good one, but it means you cannot treat fan control as a supported feature.

Alternatives and the trade-off in approach

The main alternative is iStat Menus, a commercial menu bar monitor that is not open source. Stats has an incomplete sensor mapping on Apple Silicon and a legacy fan control, which are areas where a commercial product may do better. The difference in approach is fundamental: Stats is a volunteer project that prioritizes transparency about its limits, while iStat Menus is a paid product. For a user who needs maintained fan control, iStat Menus may be the safer choice. For a user who wants a free, open-source monitor with a clean uninstall script and no telemetry, Stats is the better fit. The choice comes down to whether you need breadth or depth.

Maintenance cost and license implications

The project is under the MIT license, which means you can use, modify, and redistribute it freely, with attribution. There is no copyleft obligation, so you could embed parts of it in a proprietary tool. The maintenance cost for a user is low: the app updates through the same channels, and the uninstall script handles removal cleanly. The last push was 2026-11-01, with three releases (v3.0.22 to v3.0.24) between 2026-10-18 and 2026-11-01, so the project is active. But the fan control feature has no maintainer, and the sensor mapping depends on the author's time and community help. If you rely on Stats for daily monitoring, you should watch the release feed and be ready to update, because macOS changes can break the SMC helper or the menu bar integration, as the macOS 26 privacy toggle demonstrates.

Editorial conclusion

Use Stats if you want a free, open-source menu bar monitor on macOS 12 or newer and you are comfortable with the project's single-maintainer pace. Avoid it if you need active fan control, because that feature is in legacy mode with no updates or fixes. Avoid it if you expect out-of-the-box desktop widgets, because the macOS widgets option is off by default due to a known system bug. Before adopting, verify that you can enable the Menu Bar privacy toggle on macOS 26, confirm that the SMC helper installs without administrator friction, and check the open issues for any crash reports matching your hardware. The project is honest about its limits; the README states plainly that fan control is legacy and sensors are thermal zones, not core-specific readings. That candor is a strong signal for engineers weighing a long-term dependency.

Frequently asked questions

How do I install Stats on a Mac?

Download Stats.dmg from the releases page and move the app to the application folder, or run `brew install stats` in the Terminal. Over SSH the project provides `curl -fsSL https://cdn.mac-stats.com/install.sh | bash`, which installs the app, enables the Remote module and prints an authorization URL.

Why do the Stats icons not appear in the menu bar?

macOS 26 added a privacy control under System Settings, Menu Bar, and apps must be allowed there to display menu bar items. Open System Settings, then Menu Bar, and toggle Stats on. This is the cause when Stats is running with a module and a widget active but shows no icon at all.

Does Stats collect any data or telemetry?

No telemetry and no analytics. It calls https://api.mac-stats.com for update checks and to retrieve the public IP address, with https://api.github.com as a fallback for update checks, and the README says blocking both means no updates and no public IP in the network module.

Why does the Stats Wi-Fi network name show as Unknown?

macOS requires Location Services permission to read the Wi-Fi network name, and the name can show as Unknown with no permission popup when access is off. Enable Location Services under System Settings, Privacy & Security, toggle Stats on, then quit and reopen the app.

Can I control the fan speed from Stats?

Fan control is in legacy mode. The README says it receives no updates or fixes, and it is kept only because it works acceptably on older Macs, with the author open to a pull request but without time to support it.

How do I reduce the CPU and energy impact of Stats?

Disable the modules you do not need, because each module has its own cost. The README names Sensors and Bluetooth as the most inefficient and says turning them off could cut CPU usage and power draw by up to 50% in some cases.

Official sources

  1. Official documentation
  2. Official README
  3. Project repository
  4. Release notes
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/exelban-stats.svg)](https://hysenlabs.com/projects/exelban-stats)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/exelban-stats.svg)](https://hysenlabs.com/projects/exelban-stats)

Was this useful?