← Back to Scanner

telegram-auto-topic Security Audit Report

🔭 Continuously monitored by ClawSecure Watchtower
Source:
SHA-256:

telegram-auto-topic is an AI agent skill, created by itstauq and published at itstauq/telegram-auto-topic. ClawSecure audited telegram-auto-topic across 5 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 80/100 (Safe). The 5 findings concentrate in Command Injection, Policy Violation and Permissions Manifest, including Variable $API (line 43) flows to `curl` at line 88. and Variable $API (line 43) flows to `curl` at line 109.. None were rated high or critical severity.

Is telegram-auto-topic safe?

ClawSecure audited telegram-auto-topic and assigned a security score of 80/100 (Safe), identifying 5 findings across Command Injection and Policy Violation. Review the findings below before installing.

What did ClawSecure find in telegram-auto-topic?

ClawSecure identified 5 findings in telegram-auto-topic, concentrated in Command Injection, Policy Violation and Permissions Manifest. The most severe include Variable $API (line 43) flows to `curl` at line 88. and Variable $API (line 43) flows to `curl` at line 109..

How was telegram-auto-topic audited?

ClawSecure ran telegram-auto-topic through its 3-Layer Audit Protocol with full OWASP ASI Top 10 coverage, scanning 5 files from itstauq/telegram-auto-topic.

What does a score of 80 mean?

ClawSecure assigned telegram-auto-topic a security score of 80/100, placing it in the Safe range. Scores of 80 or above qualify for ClawSecure Verified status; the 5 findings detected are lower-severity. ClawSecure derives this score with a weighted deduction model (critical -20, high -10, medium -5, low -2 from a base of 100).

Audit Findings for telegram-auto-topic

ClawSecure detected 5 security findings in telegram-auto-topic, spanning Command Injection, Policy Violation and Permissions Manifest.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for telegram-auto-topic

Harden command execution
telegram-auto-topic constructs or runs system commands. Validate that commands are built only from trusted inputs, never pass user-controlled strings directly to a shell, and restrict execution to an allow-list of expected commands.
Resolve policy violations
telegram-auto-topic trips ClawSecure policy checks. Review each flagged pattern against your security policy and remediate or document an accepted exception before production use.
Add a config.json permissions manifest
A config.json file declares what an agent component can access: file system, network, shell execution and more. Without it, users have no visibility into what the component can do before installing. This is the single most impactful security improvement for any AI agent skill.
Pin dependencies to exact versions
Unpinned dependencies allow supply-chain attacks where a compromised version is pulled in automatically. Use exact version numbers in package.json (for example 1.2.3 instead of ^1.2.3) to keep unauthorized code out of your dependency tree. ClawSecure checks every dependency against known CVE databases.

Related Security Research

Why Generic Scanners Fail at AI Agent Security→Understanding Our 3-Layer Audit Protocol→OWASP ASI Top 10 Explained: The Complete Guide to AI Agent Security Standards→

Related AI Agent Security Audits

Anthropic-Cybersecurity-SkillsScore 70/100imsgScore 95/100antigravity-awesome-skillsScore 75/100GitNexusScore 75/100wacliScore 95/100

Scanned on May 4, 2026. telegram-auto-topic is one of thousands of agents audited by ClawSecure from the community-curated awesome-openclaw-skills list and the openclaw/skills repository.

Start Your Free Scan