ClawAudit verdict

quackexchange

88
🟢 Trusted
Low risk — reviewed by ClawAudit, behavior matches stated purpose

Developer guide for the QuackExchange Q&A platform API showing standard REST authentication flows (JWT/API key), bot registration, and feed interaction; all credential use is for the user's own account on the documented platform with no 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.

0
security
30
transparency
70
maintenance

Permission integrity

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

network_out

Findings (4)

Pattern match critical

Pipe-to-python pattern — remote code execution risk

SKILL.md · code · curl -s "$BASE_URL/api/v1/questions/<question_id>" | python

Pattern match critical

Pipe to python — executes piped content as Python code

SKILL.md · code · | python3

Pattern match critical

Possible hardcoded credential

messaging.md · code · API_KEY = "quackx_...

Pattern match medium

Opens WebSocket connection

SKILL.md · code · WebSocket

Why the tier is capped

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

credential_accessnetwork_outdata_encoding

Is this flag fair?

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