1. Download (Free)
Get the official Linux CLI package. Core audit workflow is included.
Download FreeSystem
AuditWalk is local-first integrity software built around a strict workflow contract. The interface and modules are implementation layers of this contract — not separate products.
The canonical operator workflow is: Scan → Baseline Scan → PreFlight → Compare → Doctor → Repair. Scan and Baseline Scan are deliberately separate steps. A scan captures what's there — it makes no claim about whether that state is good. Baseline Scan is the operator's explicit sign-off: "I've reviewed this scan and I vouch for it as the trusted state." That separation is the safety boundary at the foundation of everything else.
Modules
Five modules execute in sequence. Each produces a typed artifact consumed by the next.
Scan Module
Captures filesystem state into a versioned artifact. Observation only — no claims about trust. Produces the scan_id used by Baseline Scan.
Baseline Module
The operator's trust gesture. Promotes a scan artifact to the authoritative trusted reference. Unlocks PreFlight and Compare. Never automatic — always explicit.
baseline set --scan-id <scan_id>PreFlight Module
Fast, scoped verification against the confirmed baseline. Targets specific areas — files, browser, agents, system — without re-scanning everything.
Findings Module
Full factual diff between current state and confirmed baseline. Evidence generation only — interpretation is handled by doctor.
Report Module
Renders outputs in Markdown, JSON, or PDF. Human-readable for review, machine-readable for pipelines.
auditwalk report render~/auditwalk-reports/State Machine
All UI controls are gated by state. The key gate is Baseline Scan — PreFlight, Compare, and all downstream commands are only available after a baseline has been explicitly reviewed by the operator.
Findings Contract
Every finding follows a strict structure so evidence and severity are machine-consistent across scans.
This is a display model — a simplified projection for documentation purposes. The canonical Finding record is defined in docs/architecture/auditwalk-engine-spec-v1.md §4.3.
{
"id": str,
"path": str,
"change_type": "added|removed|modified",
"category": "system|user|binary|config",
"severity": "clear|review|attention|critical",
"hash_before": str | None,
"hash_after": str | None,
"timestamp": datetime,
"notes": str
}
Default grouping by change_type. Sortable by path, severity, and timestamp.
Interface
Desktop application
A full-window interface for the complete scan lifecycle. Left-panel navigation through workflow stages, findings table with severity classification, baseline management, PreFlight controls, and one-click export. Runs locally — no cloud, no telemetry.
Dashboard dock tool
A persistent icon in your system dock that runs predefined scan schedules in the background. Amber while scanning, green when clear, red when findings require attention. Your system is being watched while you work.
Mobile companion
Tethered view of your desktop's scan status and findings on iPhone or Android. View findings, baseline status, and attention alerts in real time — all from your phone. Desktop remains the sole execution surface.
Mobile companion connects over local Wi-Fi using a QR-paired session. Remote access is not supported in v1.
The Linux CLI is available now and delivers the full audit workflow. The desktop GUI, dock tool, and mobile companion are in active development — included automatically with every active license when they ship.
Next Steps
Full audit workflow is available now: scan, baseline, preflight, compare, and doctor.