Telemetry
The Kubb CLI collects anonymous usage data. This shows the team which plugins and features people use, and where the performance bottlenecks are.
IMPORTANT
Telemetry is enabled by default. Disable it any time with the DO_NOT_TRACK or KUBB_DISABLE_TELEMETRY environment variable.
What is collected
Each CLI command sends this anonymous data:
| Field | Description | Example |
|---|---|---|
command | CLI command that was run | "generate", "validate", "mcp" |
kubbVersion | Kubb CLI version | "5.0.0" |
nodeVersion | Node.js major version | "22" |
platform | Operating system | "linux", "darwin", "win32" |
ci | Whether running in CI | true |
plugins | Plugin names and their options (only for generate) | [{ "name": "@kubb/plugin-ts", "options": { "output": { "path": "types" } } }] |
duration | Command execution time in milliseconds | 1432 |
filesCreated | Number of files generated (only for generate) | 47 |
status | Whether the command succeeded or failed | "success" |
Commands that send telemetry
| Command | Description |
|---|---|
kubb generate | Sent after code generation completes or fails |
kubb validate | Sent after OpenAPI validation completes or fails |
kubb mcp | Sent after the MCP server starts or fails to start |
What is not collected
Kubb never sends:
- OpenAPI specification contents
- File paths or directory structures
- Secrets, API keys, or tokens
- Source code or generated code
- IP addresses or user identifiers
How to opt out
DO_NOT_TRACK (recommended)
DO_NOT_TRACK is a standard cross-tool opt-out convention. Many developer tools support it.
DO_NOT_TRACK=1 kubb generateAdd it to your shell profile (~/.bashrc, ~/.zshrc, etc.) to disable telemetry permanently:
export DO_NOT_TRACK=1KUBB_DISABLE_TELEMETRY
Kubb-specific opt-out flag:
KUBB_DISABLE_TELEMETRY=1 kubb generateOr permanently via your shell profile:
export KUBB_DISABLE_TELEMETRY=1Both environment variables accept "1" or "true" as values.
Data transmission
Telemetry is formatted as OpenTelemetry OTLP traces. Kubb sends them to https://otlp.kubb.dev/v1/traces at the end of each command. The request fires only when you are online. It times out after 5 seconds and fails silently if anything goes wrong.