@vibeapi/cli@0.0.142
CLI tool for managing AI coding assistants (Claude Code, Codex, OpenClaw, Hermes, AtomCode, Grok Build) with one unified config
AI Security Review
scanned 5d ago · by lpm-firewall-aiThis version sends runtime usage telemetry by default, and I found no documentation or consent prompt disclosing it. The collected event fields are usage and runtime metadata, so this warrants a warning rather than a malicious verdict.
Decision evidence
public snapshot- Telemetry is enabled by default; it can be disabled with the TELEMETRY environment variable.
- The CLI sends command, step, status, timing, and masked error data to the telemetry endpoint after a command runs.
- Telemetry includes install ID and runtime/platform metadata; the sender uses the configured API base URL.
- The manifest points to a CLI entry and declares no lifecycle scripts in the inspected section.
- The package entry point only re-exports modules; the telemetry trigger is the CLI command flow.
- No evidence found that telemetry sends credentials to a foreign host or that shell-profile persistence runs automatically.
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.142.
See all versions of @vibeapi/cli for other recorded verdicts.
- Review the evidence and your use of @vibeapi/cli@0.0.142 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.