@vibeapi/cli@0.0.145
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-aiTelemetry is enabled by default, and the CLI forwards switch arguments with only a narrow “key” filter, so inline credential-like values or identifying settings may be included. The package documents an opt-out and says the API key itself is not sent, but the source filter does not enforce that for other inline values; this warrants a warning rather than a malicious verdict.
Decision evidence
public snapshot- At CLI startup, the command event records switch arguments, excluding only arguments whose text contains “key”; inline values such as --token=… are not excluded by that filter.
- Telemetry copies event detail into the queued event without redacting it, then posts events to the configured gateway’s telemetry endpoint.
- Telemetry is enabled by default and can be disabled with VIBECLI_TELEMETRY=0, false, or off.
- The package documents that telemetry is best effort and says it does not send the API key itself or file contents.
- The manifest declares no lifecycle scripts. The telemetry flow is reached through the CLI entry point.
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.145.
See all versions of @vibeapi/cli for other recorded verdicts.
- Review the evidence and your use of @vibeapi/cli@0.0.145 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.