@vibeapi/cli@0.0.147
CLI tool for managing AI coding assistants (Claude Code, Codex, OpenClaw, Hermes, AtomCode, Grok Build) with one unified config
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe CLI sends default-on runtime telemetry with a persistent install ID and command-event data, and the README does not disclose it. The telemetry has an opt-out and uses the configured gateway, so this is suspicious telemetry rather than evidence of malicious exfiltration.
Decision evidence
public snapshot- The `vibecli` binary runs the CLI, which records a command-start event during normal command execution.
- Runtime telemetry is enabled by default; `TELEMETRY=0`, `false`, or `off` disables it.
- Telemetry events include a session identifier, command, step, status, duration, optional error text, and details; the error text is truncated and some home paths and token patterns are masked.
- The CLI posts telemetry to `/api/platform/vibecode/telemetry` on its configured gateway, with an install ID and platform/runtime metadata.
- Telemetry can be disabled with the `TELEMETRY` environment variable.
- The code masks home-directory paths and common API-token patterns in error text before sending them.
- The telemetry request uses the configured service base URL and its API key when present; the source does not show credentials sent to an unrelated host.
Source & flagged code
7 flaggedPackage source references child process execution.
dist/lib/tools/desktop-process.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @vibeapi/cli@0.0.147.
See all versions of @vibeapi/cli for other recorded verdicts.
- Review the evidence and your use of @vibeapi/cli@0.0.147 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.