Omahub
← All plugins
E

Vitals

by Emmanuel Duchene

Processor, memory, graphics and thermal readings from the Omarchy bar.

GitHub

Security review

No obvious issues detected

Deterministic scan — not a security guarantee

None
Risk level
None
Analyzed commit
a4f5eb0
Scanned
1 month ago

No potentially dangerous behavior detected in the analyzed commit.

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
a4f5eb0
Reviewed
1 month ago

This plugin is a system monitor that reads from /proc and sysfs, writes only to user-specific state files with proper permissions, and executes no network or dangerous commands. The code is transparent and well-defended.

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/dotnetemmanuel/omarchy-vitals --enable
System #bar #quickshell #system

Vitals

A bar widget for Omarchy Quattro. The bar shows the processor temperature. Click it and a panel drops down with processor load, a bar per thread, memory, graphics use, video memory, the five busiest processes and the temperature readings.

The system monitor panel open below the bar

Install

omarchy plugin add https://github.com/dotnetemmanuel/omarchy-vitals --enable

The widget appears on the right of the bar. To place it yourself, run omarchy plugin enable io.github.dotnetemmanuel.vitals with a placement instead.

Remove

omarchy plugin remove io.github.dotnetemmanuel.vitals

That deletes the plugin folder. Nothing else is left behind: the only files it ever writes are its own sample counters under the runtime directory, and those are gone on the next reboot.

Using it

Left-click the bar entry to open or close the panel. Right-click it to open btop instead, which focuses an already running btop rather than starting a second one. With the panel open, r refreshes immediately, the arrow keys scroll, Tab moves to the next bar panel and Esc closes it.

Hovering a thread bar names that thread and its load. Process percentages use the same convention as top and btop, where 100% means one thread fully used, so a program spread over four threads can read 400%.

Anything the machine cannot report is drawn as -- rather than as a zero.

What it can read

Load, the per-thread bars, memory and the busiest processes come from /proc and work on any machine.

The rest is found by sensor name, so a reading appears when your hardware presents a sensor the plugin knows to look for.

Reading Covers
Processor temperature AMD Ryzen (k10temp, zenpower) and Intel (coretemp, x86_pkg_temp)
Graphics load AMD (amdgpu) and Intel (i915, xe)
Graphics temperature Cards whose driver reports one: amdgpu, radeon, nouveau, Intel Arc
Video memory Cards with memory of their own, so AMD and discrete Intel
Disk temperature NVMe drives, and SATA drives with drivetemp loaded
Fan speed ThinkPad, Asus, Dell and Apple laptops by name, then any other machine whose sensors report a fan at all

Two readings stay at -- on an ordinary Intel laptop, and that is the honest answer rather than a gap. Integrated graphics have no memory of their own, they borrow the system memory already shown above. And the graphics core on an Intel laptop has no temperature sensor separate from the processor it sits on, so the processor reading already covers it.

An Nvidia card stays at -- unless it is running on the open nouveau driver. The proprietary driver reports through nvidia-smi rather than through the kernel, and this plugin only reads the kernel.

Intel does not count how busy the graphics core is, it counts how long the core was asleep, so the load shown is the share of the gap between two readings that was not sleep. It matches what intel_gpu_top shows for overall busy time.

If a reading you expect stays at --, open an issue saying what sensors prints and I will add your hardware.

Requirements

Omarchy Quattro, and btop if you want the right-click shortcut. Everything else is bash and awk, already on any Omarchy install. The plugin reads only sysfs and /proc, needs no privileges, and makes no network connections.

License

MIT. See LICENSE.