Security audit

ClawVC

Security checks for vulnerabilities and agentic risk

Overview

ClawVC appears to do what it claims: it uses Git to locally snapshot the OpenClaw workspace and can change OpenClaw settings to enable a read-only plan mode.

This looks internally consistent for a Git-based workspace version-control plugin. Before installing, be comfortable with it creating/using a Git repo in your workspace, committing all non-ignored files after agent turns, and editing ~/.openclaw/openclaw.json for plan mode. Add sensitive files to .gitignore because local Git history can retain secrets even after deletion. Also ensure git is installed, since the code depends on it even though the registry requirements section did not list it.

Static analysis

Detected: suspicious.dangerous_exec

Shell command execution detected (child_process).

Critical

Code: suspicious.dangerous_exec
Location: dist/git.js:9
Evidence: const { stdout } = await exec("git", [...GIT_IDENTITY, "-C", workspace, ...args], { maxBuffer: 1024 * 1024 });

Shell command execution detected (child_process).

Critical

Code: suspicious.dangerous_exec
Location: src/__tests__/commit.test.ts:61
Evidence: const { stdout } = await exec("git", ["-C", tmpDir, "log", "--oneline", "-1"]);

Shell command execution detected (child_process).

Critical

Code: suspicious.dangerous_exec
Location: src/__tests__/git.test.ts:33
Evidence: const { stdout } = await exec("git", ["-C", tmpDir, ...args]);

Shell command execution detected (child_process).

Critical

Code: suspicious.dangerous_exec
Location: src/git.ts:21
Evidence: const { stdout } = await exec(