ClawAudit verdict
safe-exec
safe-exec-bak
Backup variant of safe-exec with more complete metadata; explicitly declares no network calls, no monitoring, no external notifications, and all env vars serve the skip/confirm UX, not exfiltration.
⚠ Flagged for review — coarse, uncorroborated signal, not a confirmed exploit. Review the config yourself before installing.
Automated static analysis — not a human review. ClawAudit flags capabilities, not confirmed intent, and can produce false positives. Disagree with this verdict? Use Dispute below.
Findings (9)
Pipe-to-shell pattern (curl | sh) — supply chain attack vector
README_EN.md · code · curl | bash
Recursive delete from root or home — destructive command
SKILL.md · code · rm -rf /
Pipe to bash — executes piped content as shell commands
README_EN.md · code · | bash
Accesses shell history/config
README_EN.md · code · ~/.zshrc
Pipe-to-shell pattern (wget | sh)
README-detail.md · prose · downgraded · wget | sh
Pipe to sh — executes piped content as shell commands
README-detail.md · prose · downgraded · | sh
Pipe to python — executes piped content as Python code
scripts/safe-exec.sh · prose · downgraded · |python
References sudo — requests elevated privileges
README_EN.md · prose · downgraded · Sudo
Sets world-executable permissions
README_EN.md · code · chmod 777
Why the tier is capped
Execution sink present in raw bytes (Hard Floor: class A/B). Final tier capped at Caution — cannot be lifted by any downgrade, example-payload opt-in, or allowlist.
Permissions & capabilities
No declared permissions — minimal attack surface.
Is this flag fair?
Thanks — recorded.