← Back to Scanner

TradingView-Claw Security Audit Report

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

TradingView-Claw is an AI agent skill, created by helenigtxu and published at helenigtxu/TradingView-Claw. ClawSecure audited TradingView-Claw across 25 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 80/100 (Safe). The 3 findings concentrate in Code Injection, Permissions Manifest and ReDoS, including Potentially dangerous code pattern detected: system\( and Missing config.json - agent may not be properly configured. 1 was rated high or critical severity.

Is TradingView-Claw safe?

ClawSecure audited TradingView-Claw and assigned a security score of 80/100 (Safe), identifying 3 findings across Code Injection and Permissions Manifest. Review the findings below before installing.

What did ClawSecure find in TradingView-Claw?

ClawSecure identified 3 findings in TradingView-Claw, concentrated in Code Injection, Permissions Manifest and ReDoS. 1 was rated high or critical severity. The most severe include Potentially dangerous code pattern detected: system\( and Missing config.json - agent may not be properly configured.

How was TradingView-Claw audited?

ClawSecure ran TradingView-Claw through its 3-Layer Audit Protocol with full OWASP ASI Top 10 coverage, scanning 25 files from helenigtxu/TradingView-Claw.

What does a score of 80 mean?

ClawSecure assigned TradingView-Claw a security score of 80/100, placing it in the Safe range. Scores of 80 or above qualify for ClawSecure Verified status, though 1 finding was rated high or critical and warrants review. 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 TradingView-Claw

ClawSecure detected 3 security findings in TradingView-Claw, spanning Code Injection, Permissions Manifest and ReDoS.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for TradingView-Claw

Eliminate dynamic code execution
TradingView-Claw evaluates code at runtime (for example eval or dynamic exec). Remove dynamic evaluation of untrusted input, and where code generation is unavoidable, sandbox it and validate every input.
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.
Fix ReDoS-prone patterns
TradingView-Claw contains regular expressions vulnerable to catastrophic backtracking (ReDoS). Replace vulnerable patterns, bound input length, and prefer linear-time matching so a crafted input cannot hang the agent.
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→Beyond Static Scans: Why ClawSecure Verifies Agentic Intent→How to Secure an MCP Server: The 2026 Guide→

Related AI Agent Security Audits

clippyScore 90/100stock-market-apiScore 95/100gtsec-smart-stock-selection (1)Score 95/100gtsec-smart-stock-selectionScore 95/100gtsec-smart-stock-selectionScore 95/100

Scanned on March 11, 2026. TradingView-Claw 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