Caveat verdict

telegram-bot-manager

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

Telegram bot setup and troubleshooting guide for OpenClaw; network_out is to official api.telegram.org for bot validation, and the skill explicitly warns to never commit bot tokens to version control.

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

13
security
70
transparency
70
maintenance

Permission integrity

Makes network requests but does not declare curl/wget in required binaries

network_out

Findings (5)

Pattern match critical

Possible hardcoded credential

README.md · code · TOKEN="your-bot-token

Pattern match high

References sudo — requests elevated privileges

references/WEBHOOK_SETUP.md · code · sudo

Pattern match medium

References webhook/callback URL

references/WEBHOOK_SETUP.md · code · WEBHOOK_URL

Pattern match medium

subprocess execution — runs system commands from Python

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

Pattern match low

Python os.getenv — reads environment variable

scripts/test_bot.py · prose · downgraded · os.getenv(

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.

network_out

Is this flag fair?

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