Omahub
← All plugins
B

Quadrant

by Bernard Visagie

Unified system monitor for the Quattro bar: CPU, GPU, memory, drives and network in one slot, with a tabbed panel that names your hardware, keeps an hour of history and shows the processes behind the numbers.

GitHub

Security review

Potentially dangerous behavior detected · 12 findings

Deterministic scan — not a security guarantee

High
Risk level
High
Analyzed commit
0b0d497
Scanned
1 day ago

Automated analysis only — not a security guarantee.

AI advisory review

No obvious issues detected

Language-model assessment · ~deepseek/deepseek-v4-flash-latest — advisory only

None
AI risk level
None
Recommendation
install
Model
~deepseek/deepseek-v4-flash-latest
Analyzed commit
0b0d497
Reviewed
1 day ago

The deterministic scan's high findings are all in test fixtures and test assertions (df-hostile.txt, df-basic.txt, settings.test.js, identity.test.js) that use strings like `rm -rf /` as hostile input to verify sanitization; they are not executed by the plugin. The package-manager and sudo findings are in the GitHub Actions CI workflow and README documentation, not in the plugin's runtime path. The plugin's runtime code reads system metrics and writes only to XDG runtime/state directories; no destructive or hidden behavior was found.

How this check works

This review combines the deterministic scan (the rule-based results above) with an independent look at the plugin's code by a language model. The model reads a trimmed sample of the repository's files, the manifest, and the README, then gives a plain-language risk level and a recommendation: install (no notable danger), review (look closer first), or avoid (clearly dangerous).

It runs on the same analyzed commit as the deterministic scan and is strictly advisory — it is not a security guarantee and never blocks a plugin by itself. A human moderator still reviews plugins before they are listed.

AI advisory only — automated analysis, not a security guarantee.

Install
$ omarchy plugin add https://github.com/BVisagie/omarchy-quadrant --enable
System #bar #quickshell #system

Quadrant

<p align="center"> <img src="preview.png" alt="Quadrant CPU, GPU, and Memory panels in dark, light, and monochrome Omarchy themes" width="1000"> </p> <p align="center"><em>CPU, GPU, and Memory — one plugin, your Omarchy palette.</em></p>

A unified system monitor for the Omarchy Quattro bar: CPU, GPU, memory, drives and network in one compact bar slot and one tabbed panel. Each tab identifies the hardware it measures, shows live usage and history, and lists the processes behind the numbers.

  • CPU topology and per-core load, RAM composition and pressure, GPU usage, drive throughput and mount capacity, and network traffic.
  • Last-minute graphs and an hour of saved history, shared across monitors.
  • Per-process CPU, memory, disk I/O, TCP traffic, and GPU metrics where available; see measurement sources and limits.
  • Independent bar segments, keyboard navigation, device pickers, and an inline settings view that follows the active Omarchy theme.
<p align="center"> <img src="docs/screenshots/bar.png" alt="Quadrant CPU, GPU, memory, and network segments beside Omarchy’s clock and weather" width="486"> </p>

See the tab and settings screenshots.

Requirements

Supports Omarchy 4.0.3 and later, with Quattro's plugin service and settings APIs. Requires bash ≥ 5, jq, python3, ss and ip (iproute2), coreutils (df, timeout, and filesystem utilities), and awk (mawk or gawk). The sampler needs a writable $XDG_RUNTIME_DIR, as provided by a normal desktop session.

nvidia-smi is needed for NVIDIA monitoring. lspci (pciutils) is optional and supplies AMD/Intel model names. Right-clicking the widget opens btop through Omarchy's terminal launcher.

Install

Quadrant is a third-party plugin and runs unsandboxed with your user permissions. Review the repository before enabling it.

From the Omarchy menu

  1. Open the Omarchy menu.

  2. Choose Setup → Plugins → Add.

  3. Enter:

    https://github.com/BVisagie/omarchy-quadrant.git

  4. Read and accept Omarchy's plugin warning, then choose whether to enable Quadrant.

From a terminal

omarchy plugin add https://github.com/BVisagie/omarchy-quadrant.git

Without --enable, Omarchy asks whether to enable the plugin after cloning and validating it. Choosing no lets you inspect the installed checkout at ~/.config/omarchy/plugins/dev.bvisagie.quadrant/ first. Enable it later with:

omarchy plugin enable dev.bvisagie.quadrant

The widget starts in the right bar section (barWidget.defaultSection). Move it with omarchy bar move dev.bvisagie.quadrant --section center.

Update

omarchy plugin update dev.bvisagie.quadrant

Omarchy shows the incoming diff and asks for confirmation, then fast-forwards the installed checkout and validates it. An invalid update is rolled back.

Uninstall

From the Omarchy menu, choose Setup → Plugins → Remove, then select Quadrant. Or from a terminal:

omarchy plugin remove dev.bvisagie.quadrant

Omarchy disables Quadrant before removing its git checkout. Saved graph history remains under $XDG_STATE_HOME/dev.bvisagie.quadrant/ (normally ~/.local/state/dev.bvisagie.quadrant/). See stored data and cleanup for the history file and temporary sampler state. Installation and removal do not require sudo or pkexec.

Getting started

Click a bar segment to open its tab; clicking the same segment again closes the panel. Click elsewhere in the slot to reopen the last-used tab. Use ← / → to switch tabs, uppercase H to switch all graphs between the last minute and last hour, S or the gear to open settings, and Esc to close settings or the panel.

The default bar shows CPU, dedicated GPU, memory, and network. Without a dedicated GPU, Drives fills the GPU slot; integrated graphics appear on the CPU tab. Use each tab's in bar switch to change what appears.

Documentation

Guide Contents
Usage Bar and panel controls, graphs, process rows, IPC, screenshots
Settings Every setting, defaults, validation, and CLI examples
Measurements Data sources, calculations, hardware support, and attribution limits
Security User permissions, process data, stored files, and helper behavior
Development Architecture, checks, rendering, and the manual test matrix
Changelog Release history

License

MIT — see LICENSE.