Caveat verdict

wechat-rpa

wechat-message

🟢 Trusted

No high-risk patterns surfaced by the deep scan — automated capability review, not behavioral proof.

Uses desktop UI automation to operate WeChat on behalf of the user for sending and receiving messages; CHAT_API_KEY guards the auto-reply endpoint and no data is sent to undisclosed external hosts.

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

security

transparency

maintenance

Permission integrity

Installs packages at runtime — transitive dependencies are not auditable

package_install

Findings (4)

Pattern match critical

Possible hardcoded credential

SKILL.md · code · API_KEY="YOUR_API_KEY

Pattern match high

HTTP request to bare IP address — common in malicious payloads

SKILL.md · code · http://127.0.0.1

Pattern match medium

subprocess execution — runs system commands from Python

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

Pattern match medium

subprocess with shell=True — command injection vector

scripts/wechat.py · prose · downgraded · subprocess.Popen( [wechat_path],

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.

package_installcredential_access

Is this flag fair?

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