ClawAudit verdict
post-merge-rename
88
🟢 Trusted
Low risk — reviewed by ClawAudit, behavior matches stated purpose
The skill automates branch renaming post-merge, which seems to be a utility for maintaining clean git history.
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.
100
security
100
transparency
80
maintenance
No red flags detected in static analysis.
Checked: 115 threat patterns · AST capability extraction · cross-zone compound shapes · permission integrity.
Why the tier is capped
Execution sink present in raw bytes (Hard Floor: class B). Final tier capped at Caution — cannot be lifted by any downgrade, example-payload opt-in, or allowlist.
Permissions & capabilities
Requires 1 system binary.
Was this verdict right?
Thanks — recorded.