| Version | Supported |
|---|---|
| 0.7.x | ✅ Current release |
| < 0.7 | ❌ Not supported |
If you discover a security vulnerability in ValueClaw, please report it responsibly:
- DO NOT open a public GitHub issue for security vulnerabilities.
- Email the maintainer directly at: wangchen2007915@gmail.com
- Include a detailed description of the vulnerability, steps to reproduce, and potential impact.
- You will receive a response within 72 hours acknowledging the report.
- All API keys are stored in
value_claw.jsonwhich is gitignored by default. - The web dashboard masks sensitive values (API keys, tokens) in the config viewer.
- Never commit
value_claw.jsonto version control.
- The
run_commandtool executes shell commands within a sandboxed directory. - File write operations are restricted to the
~/.value_claw/sandbox. - Note:
read_filecurrently does not enforce sandbox restrictions — this is a known limitation being addressed.
- The web dashboard (port 7788) does not include authentication by default.
- If exposing to a network, use a reverse proxy (nginx/caddy) with authentication.
- Do not expose port 7788 to the public internet without additional security measures.
- All SEC EDGAR requests use a proper User-Agent header as required by SEC policy.
- Web scraping respects rate limits with built-in
time.sleep()delays. - No data is sent to third parties beyond the configured LLM provider and data APIs.
- Run ValueClaw on a trusted machine — it has access to your file system within
~/.value_claw/. - Use
allowedUsersin Telegram/Discord config to restrict bot access. - Regularly rotate API keys, especially LLM provider keys.
- Keep ValueClaw updated to the latest version for security patches.