Automic VaultAutomic Vault

brew

Install tmux-mem-cpu-load with Homebrew, MacPorts, Nix

CPU, RAM memory, and load monitor for use with tmux. Version 3.8.3 via Homebrew; verified 2026-06-25.

install

Additional install commands

macOS

Homebrewverified · 100%
brew install tmux-mem-cpu-load

local Homebrew formula metadata

MacPortsverified · 94%
sudo port install tmux-mem-cpu-load

MacPorts ports tree · sysutils/tmux-mem-cpu-load/Portfile · source: api.github.com

Linux

Nixverified · 92%
nix profile install nixpkgs#tmux-mem-cpu-load

nixpkgs package indexes · pkgs/by-name/tm/tmux-mem-cpu-load/package.nix · source: api.github.com

overview

Package summary

CPU, RAM memory, and load monitor for use with tmux

Commands and aliases

  • tmux-mem-cpu-load

history

Project history and usage

tmux-mem-cpu-load is a small tmux status-line monitor that prints memory use, CPU load, and system load averages. Its history is best understood as part of the tmux customization ecosystem rather than as a standalone platform project.

Project history

The official README describes the project as a simple, lightweight program for system monitoring in tmux's status line. It is written mainly in C++ with platform-specific code for Linux, macOS, FreeBSD, OpenBSD, NetBSD, and Windows visible in the repository layout.

Adoption history

The README documents installation by tmux plugin manager, Homebrew, Gentoo, FreeBSD pkg, and zsh plugin tooling such as Antigen. The batch input adds MacPorts and Nix package names, showing the tool's adoption among users who manage tmux extras through package managers rather than hand-copying scripts.

How it is used

Users add tmux-mem-cpu-load to status-left or status-right in ~/.tmux.conf, often matching its interval to tmux's status-interval. Options support colors, powerline separators, vertical graphs, memory display modes, CPU display modes, and load-average count.

Why package nerds care

Package nerds care about this project because it is the kind of narrowly scoped tmux add-on that becomes valuable when it is packaged: once installed, it becomes just another executable in a reproducible dotfiles setup.

Timeline

  • Current: Official README documents use from ~/.tmux.conf and multiple installation paths.
  • 2026: GitHub repository page listed 10 releases, latest 3.8.3 on Jun 25, 2026.

Related projects

  • tmux provides the status line that tmux-mem-cpu-load targets.
  • tmux plugin manager, tmux-powerline, and zsh plugin managers are documented integration paths.

security posture

Risk level: green

narrow executable package without higher-risk signals.

Risk classifier

green risk · low confidence · appliance

Why

  • narrow executable package without higher-risk signals

Signals

  • metadata:no-higher-risk-signals

Install behavior

  • No Homebrew post-install hook is recorded in formula metadata.
  • Homebrew bottle metadata is available for 6 platform targets.
  • Build metadata lists 1 build dependencies.

Recommended review

Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.

local files

Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.

Configuration files

Config paths the tool may read or write during local use.

Unix
~/.tmux.conf

executables

Installed executables

CommandKindExposureNote
tmux-mem-cpu-loadcliglobal executable

freshness

Version and freshness

These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.

page generated2026-07-08
manager version3.8.3
manager updated2026-06-25
local dataok
upstreamcurrent
latest detectedv3.8.3

https://github.com/thewtex/tmux-mem-cpu-load

  • okNo freshness warnings were generated.

install metadata

Package metadata

Package keybrew:tmux-mem-cpu-load
Version3.8.3
Package managerHomebrew
Package manager pagehttps://formulae.brew.sh/formula/tmux-mem-cpu-load
Homepagehttps://github.com/thewtex/tmux-mem-cpu-load
Repositoryhttps://github.com/thewtex/tmux-mem-cpu-load
Upstream docshttps://github.com/thewtex/tmux-mem-cpu-load#readme
LicenseApache-2.0
Source archivehttps://github.com/thewtex/tmux-mem-cpu-load/archive/refs/tags/v3.8.3.tar.gz
Last updated2026-06-25T20:40:28Z
Pulseupdated
Build dependenciescmake
Bottleavailable (on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-installnot defined
Servicenone declared

registry facts

Source database details

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Nametmux-mem-cpu-load
Version Scheme0
Revision0
Head VersionHEAD
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • head
  • stable

source database matches

Other package-manager records

Matches are pulled from external package-manager indexes and kept separate from local Automic Vault package links.

Nix95%

tmux-mem-cpu-load

nix profile install nixpkgs#tmux-mem-cpu-load
  • normalized package name match
  • Matched by: Tmux Mem Cpu Load
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/tm/tmux-mem-cpu-load/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
MacPorts95%

tmux-mem-cpu-load

sudo port install tmux-mem-cpu-load
  • normalized package name match
  • Matched by: Tmux Mem Cpu Load
MacPorts ports tree · api.github.com · MacPorts ports tree: sysutils/tmux-mem-cpu-load/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1

source trail

Generated from repository data

This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.

Used sources

  • Geiger risk classifier
  • Nucleus package database
  • av.db category and tag curation
  • cross-ecosystem install command graph
  • curated configuration and credential file locations
  • curated package history
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment