ClawAudit verdict

openclaw-1ly-payments

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

The skill seems to be setting up an integration with 1ly payments, which involves installing packages and configuring environment variables. While the intent is legitimate, the handling of sensitive information like wallet keys and API keys could pose a risk if not managed securely.

⚠ 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
60
transparency
70
maintenance

Permission integrity

Installs packages at runtime — transitive dependencies are not auditable

package_install

Findings (1)

Pattern match high

Accesses OpenClaw config/secrets directly

SKILL.md · frontmatter · ~/.openclaw/openclaw.json

Permissions & capabilities

Requires 10 environment variables. (1 sensitive: ONELY_API_KEY). Requires 3 system binaries. (1 elevated: npm).

network_inpackage_install

Is this flag fair?

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