| Version | Supported |
|---|---|
| 1.x.x | ✅ Current |
If you discover a security vulnerability, please report it responsibly:
- Do NOT open a public issue
- Email: oguzhnatly@gmail.com
- Include:
- Description of the vulnerability
- Steps to reproduce
- Potential impact
- Suggested fix (if any)
You will receive an acknowledgment within 48 hours and a detailed response within 7 days.
Fleet is a CLI tool that runs locally and interacts with:
- OpenClaw gateways on localhost (configurable ports)
- Systemd services (read-only status checks)
- GitHub API (via
ghCLI, uses your existing auth) - Linear API (optional, uses API key from environment variable)
- Configured endpoints (HTTP health checks only)
Fleet never stores credentials itself. It reads:
- API keys from environment variables (never from config files)
- Agent tokens from
~/.fleet/config.json(local file, user-controlled) - GitHub auth from
ghCLI's existing session
- Keep
~/.fleet/config.jsonreadable only by your user (chmod 600) - Use environment variables for API keys, not config files
- Rotate agent tokens periodically
- Review the config before sharing it (tokens may be present)
The following are in scope for security reports:
- Command injection via config values
- Credential exposure in logs or output
- Unauthorized access to local services
- Path traversal in file operations
The following are out of scope:
- Issues in OpenClaw itself (report to OpenClaw)
- Issues in
ghCLI (report to GitHub CLI) - Social engineering attacks