This repository ships the official Routeplane developer tooling — the TypeScript SDK
(@routeplane/sdk), the CLI (@routeplane/cli), and the MCP server
(@routeplane/mcp-server). All three handle gateway credentials, and the MCP server runs
as a local process that mediates tool calls, so we treat security reports here as the
highest-priority class of issue.
Email security@routeplane.ai.
Please include:
- The package and version affected (
@routeplane/sdk,@routeplane/cli, or@routeplane/mcp-server, plus the version frompackage.jsonornpm ls). - A description of the issue and the component affected (file or exported symbol if known).
- Reproduction steps or a proof of concept.
- Your assessment of impact, if you have one.
You can also use GitHub's private vulnerability reporting on this repository if you prefer not to use email. Please do not open a public issue for anything you believe is a vulnerability.
Never include a real gateway key, provider API key, or customer data in a report. Redact them; we can reproduce from the shape of the request.
- Acknowledgement within 72 hours of your report reaching us.
- An initial assessment (accepted / needs-more-info / not-a-vulnerability) within 7 days.
- We ask for a standard 90-day coordinated disclosure window while we develop, test, and release a fix. We will agree a disclosure date with you and credit you in the release notes (or keep you anonymous — your choice).
- If we ship a fix sooner, we will coordinate earlier disclosure rather than sitting on the window.
In scope: the three published packages in this repository and the CI workflows that build them. We are particularly interested in:
- Credential handling — a gateway key leaking into logs, error messages, telemetry, a crash dump, or a file written with loose permissions.
- The MCP server as a trust boundary — it mediates tool calls for an agent. Anything that lets a tool result influence which tool runs next, escape the configured server set, or reach a host it was not configured for.
- Request construction — header or URL injection through SDK parameters, or anything that causes a request to be sent to a host other than the configured gateway.
- Dependency and supply-chain issues in what we publish.
Out of scope: the Routeplane gateway itself (report those to the same address — they are handled outside this repo's process), third-party LLM providers, issues that require an already compromised developer machine, and findings that depend on a maliciously modified local config file.
We do not run a paid bug bounty program. We are a small team and we would rather say so plainly than promise rewards we cannot pay consistently. We credit reporters in release notes, and we fix confirmed reports fast.
Security fixes land on the latest published version of each package. During the 0.x series we do not backport to older versions — upgrade to the newest release to receive fixes.