@vibeapi/cli@0.0.166
CLI tool for managing AI coding assistants (Claude Code, Codex, OpenClaw, Hermes, AtomCode, Grok Build) with one unified config
AI Security Review
scanned 4h ago · by lpm-firewall-aiThe flagged process execution, downloads, and file writes support the package’s stated CLI functions and are invoked through tool-management operations. Runtime telemetry is disclosed, excludes API keys according to the privacy notice, and can be disabled.
Decision evidence
public snapshot- The manifest exposes a CLI entry point and its scripts list build, development, and maintenance tasks; no install lifecycle hook is declared.
- The CLI gathers command names, statuses, durations, and error messages; command arguments that look like keys are excluded.
- The English privacy notice says usage statistics are sent to VibeAPI, API keys are not included, and telemetry can be disabled with an environment variable.
- Telemetry posts events to the VibeAPI telemetry endpoint using the configured service base URL.
- Telemetry is enabled by default when the CLI runs, though it is disclosed and has an opt-out.
- The package includes shell and file operations for installing tools and configuring assistant environments; these serve the CLI’s stated purpose.
Source & flagged code
6 flaggedPackage source references child process execution.
dist/lib/tools/chatgpt-desktop.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @vibeapi/cli@0.0.166.
See all versions of @vibeapi/cli for other recorded verdicts.
- Review the evidence and your use of @vibeapi/cli@0.0.166 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.