Fastfetch 2.70.0 Alters Disk‑Space Reporting, Potentially Disrupting Compliance Data Collection
What Happened — Fastfetch 2.70.0 (released Oct 14 2026) changed the Disk module’s output fields, removed QuickJS scripting, and adjusted how command‑line output and shell detection are handled. Configurations written for earlier versions may now return different values or fail outright.
Why It Matters for Trust & Control Assurance
- Continuous‑control‑assurance programs often ingest Fastfetch data to prove asset‑inventory, storage‑capacity, and system‑state controls; a shift in field semantics can create gaps in audit evidence.
- Inconsistent reporting may trigger false‑positive or false‑negative alerts in automated compliance dashboards, undermining the defensible audit trail.
- The removal of QuickJS and the switch to Lua require script migration, otherwise monitoring pipelines could break and leave controls undocumented.
Who Is Affected — Organizations that embed Fastfetch in CI/CD pipelines, endpoint‑inventory tools, or compliance‑automation scripts across technology, SaaS, and cloud‑infrastructure environments.
Recommended Actions
- Inventory all Fastfetch‑derived data feeds and map the new field definitions to your existing control evidence.
- Update scripts to use the new
{size-free}logic and migrate any QuickJS snippets to Lua. - Re‑run a control‑mapping validation run to confirm that storage‑capacity and system‑state controls still produce verifiable evidence.
Technical Notes — The Disk module now reports {size-free} based on the disk.useAvailable flag, drops {size-available}, and changes JSON keys (bytes.available/bytes.used removed). Windows quota handling was corrected, and the Shell module now reads the login shell from /etc/passwd. QuickJS support was removed; Lua is the new scripting engine. Source: Help Net Security