cyber-audit

When to Use

• Use when the user asks whether their machine or projects are affected by a CVE, breach, or package advisory.
• Use when a read-only local security exposure report is appropriate.

Hard rules

• Read-only. No installs, removes, upgrades, restarts, network calls, or file modifications outside ~/Documents/security-audits/.
• No sudo. Never.
• One report per invocation. Always end by writing the .md file (even if the verdict is "Not affected" — the audit trail matters).
• If a check requires a state-changing command, skip it and note "not checked (would require state change)" in the table. Do not run it.

Workflow