ClawAudit verdict

openclaw-shield-1-0-3

45
๐ŸŸ  Risky
Significant concerns โ€” only install if you understand the risks

The installation step clones an external GitHub repo (github.com/pfaria32/OpenClaw-Shield-Security) and immediately runs its code, creating a supply-chain risk where the external repo could be modified to deliver malicious payloads; additionally, Telegram alerting sends data to an external service.

โš  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.

80
security
70
transparency
70
maintenance

Findings (2)

Pattern match medium

Accesses .ssh directory

SECURITY.md ยท prose ยท downgraded ยท .ssh/

Pattern match medium

Accesses cloud provider credentials

SECURITY.md ยท prose ยท downgraded ยท ~/.aws

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

No declared permissions โ€” minimal attack surface.

Is this flag fair?

Check another skill Browse the registry Auditing your own skills or configs? Use the API