ClawAudit verdict
ragflow-runbook
End-to-end operational runbook for deploying and troubleshooting RAGFlow; uses user-configured env vars (RAGFLOW_BASE_URL, RAGFLOW_API_KEY) and all curl commands target the user's own RAGFlow instance, consistent with the documented ops-runbook purpose.
⚠ 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.
Permission integrity
credential_access
Findings (7)
Possible hardcoded credential
SKILL.md · code · API_KEY="${RAGFLOW_API_KEY}
References sudo — requests elevated privileges
SKILL.md · code · sudo
HTTP request to bare IP address — common in malicious payloads
SKILL.md · code · http://127.0.0.1
Changes file ownership
SKILL.md · code · chown
subprocess execution — runs system commands from Python
scripts/ragflow_alert.py · prose · downgraded · subprocess.run(
Python os.environ.get — reads environment variable
scripts/ragflow_alert.py · prose · downgraded · os.environ.get(
Python urllib.request — network access
scripts/ragflow_ping.py · prose · downgraded · urllib.request
Why the tier is capped
Execution sink present in raw bytes (Hard Floor: class B/D). Final tier capped at Caution — cannot be lifted by any downgrade, example-payload opt-in, or allowlist.
Permissions & capabilities
Requires 1 system binary.
credential_access Is this flag fair?
Thanks — recorded.