Skip to content

Security: bigeez/eez

Security

SECURITY.md

Security Policy

Reporting a Vulnerability

If you discover a security vulnerability in this project, please report it responsibly.

Email: Open a private security advisory via GitHub Security Advisories.

Do not open a public issue for security vulnerabilities.

Scope

This project connects to a locally running TradingView Desktop instance via Chrome DevTools Protocol on localhost:9222. Security concerns in scope include:

  • Code injection via crafted tool inputs
  • Unintended data exposure through tool outputs
  • Credential or session token leakage
  • Vulnerabilities in the MCP server or CLI that could be exploited locally

Out of Scope

  • TradingView's own security (report to TradingView directly)
  • Chrome DevTools Protocol security (report to Google/Chromium)
  • Claude Code or MCP SDK security (report to Anthropic)

Best Practices for Users

  • Only run TradingView with --remote-debugging-port=9222 on localhost
  • Do not expose port 9222 to your network or the internet
  • Do not pipe tv stream output to external services without reviewing the data
  • Keep your TradingView Desktop and Node.js installations up to date

There aren’t any published security advisories