← Back to Scanner

tradingview-screener Security Audit Report

πŸ”­ Continuously monitored by ClawSecure Watchtower
Source:
SHA-256:

tradingview-screener is an AI agent skill, created by lukebaze and published at openclaw/skills. ClawSecure audited tradingview-screener across 19 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 25/100 (High Risk). The 7 findings concentrate in Command Injection, Code Injection and Permissions Manifest, including eval() with Dynamic Input and eval() with Dynamic Input. 5 were rated high or critical severity.

Is tradingview-screener safe?

ClawSecure audited tradingview-screener and assigned a security score of 25/100 (High Risk), identifying 7 findings across Command Injection and Code Injection. Review the findings below before installing.

What did ClawSecure find in tradingview-screener?

ClawSecure identified 7 findings in tradingview-screener, concentrated in Command Injection, Code Injection and Permissions Manifest. 5 were rated high or critical severity. The most severe include eval() with Dynamic Input and eval() with Dynamic Input.

How was tradingview-screener audited?

ClawSecure ran tradingview-screener through its 3-Layer Audit Protocol with full OWASP ASI Top 10 coverage, scanning 19 files from openclaw/skills.

What does a score of 25 mean?

ClawSecure assigned tradingview-screener a security score of 25/100, placing it in the High Risk range. This is driven by 7 findings led by Command Injection that should be addressed before use. 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-screener

ClawSecure detected 7 security findings in tradingview-screener, spanning Command Injection, Code Injection, Permissions Manifest and Policy Violation.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for tradingview-screener

Harden command execution
tradingview-screener 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.
Eliminate dynamic code execution
tradingview-screener 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.

Related Security Research

Why Generic Scanners Fail at AI Agent Security→Understanding Our 3-Layer Audit Protocol→

Related AI Agent Security Audits

Better PolymarketScore 30/100Better PolymarketScore 30/100imap-idleScore 30/100polymarketScore 26/100shopping-expertScore 35/100

Scanned on April 4, 2026. tradingview-screener 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