ClawAudit verdict

api-failover

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

Design guidance and configuration patterns for building LLM API failover routing; explicitly limits scope and does not claim autonomous takeover — local proxy deployment pattern with user-controlled config.

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

65
security
90
transparency
70
maintenance

Findings (4)

Pattern match high

HTTP request to bare IP address — common in malicious payloads

references/activation-checklist.md · code · http://127.0.0.1

Pattern match medium

subprocess execution — runs system commands from Python

scripts/activate_secondary.py · prose · downgraded · subprocess.run(

Pattern match low

Python os.environ.get — reads environment variable

scripts/discover_env.py · prose · downgraded · os.environ.get(

Pattern match low

Python urllib.request — network access

scripts/failover_proxy.py · prose · downgraded · urllib.request

Why the tier is capped

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