ClawAudit verdict

qr-code

openclaw-qr-code

45
🟠 Risky
Significant concerns — only install if you understand the risks

The recommended installation method pipes a remote shell script from GitHub via curl|bash, executing arbitrary remote code without verification; while the QR code functionality is benign, this installation pattern presents unsandboxed remote code execution risk.

⚠ 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.

25
security
70
transparency
70
maintenance

Permission integrity

Makes network requests but does not declare curl/wget in required binaries

network_out

Findings (2)

Pattern match critical

Pipe-to-shell pattern (curl | sh) — supply chain attack vector

SKILL.md · code · curl -s https://raw.githubusercontent.com/zouyawen/openclaw-qrcode/main/install.

Pattern match critical

Pipe to bash — executes piped content as shell commands

SKILL.md · code · | bash

Why the tier is capped

Execution sink present in raw bytes (Hard Floor: class A). 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.

network_outdata_encoding

Is this flag fair?

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