Caveat verdict

ppq-private-mode

45
🟠 Risky
Significant risk patterns flagged — automated deep scan, not behavioral proof.

The setup step runs `openclaw plugins install https://github.com/PayPerQ/ppq-private-mode-proxy` which fetches and executes unpinned code from a third-party GitHub repository, creating supply-chain risk where a compromised repo would silently install malicious code alongside the user's API key.

⚠ Flagged for review — coarse, uncorroborated signal, not a confirmed exploit. Review the config yourself before installing.

Automated static analysis — not a human review. Caveat flags capabilities, not confirmed intent, and can produce false positives. Disagree with this verdict? Use Dispute below.

55
security
50
transparency
70
maintenance

Permission integrity

Code accesses API keys/tokens but declares no environment variables

credential_access

Findings (2)

Pattern match high

HTTP request to bare IP address — common in malicious payloads

SKILL.md · code · http://127.0.0.1

Pattern match medium

Accesses OpenClaw config/secrets directly

SKILL.md · prose · downgraded · ~/.openclaw/openclaw.json

Permissions & capabilities

No declared permissions — minimal attack surface.

credential_access

Is this flag fair?

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