@vibeapi/api-helper@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-aiThe package’s core functionality appears consistent with its purpose, and I found no concrete malicious attack chain. However, it sends runtime telemetry by default without an evident disclosure in the inspected README, so this warrants a warning.
Decision evidence
public snapshot- Runtime telemetry is enabled unless VIBECLI_TELEMETRY is explicitly set to 0, false, or off.
- Telemetry events can include command, step, status, error text, and details; the accompanying payload includes an install ID, brand, OS release, architecture, and Node version.
- The CLI flushes telemetry after command execution, and its default sender posts events to the VibeAPI gateway.
- The package’s stated purpose is managing AI coding assistant tools, consistent with its process execution and install commands.
- The telemetry contains usage and runtime fields rather than an evident credential collection flow; error text is truncated and passed through secret and home-path masking.
- Telemetry can be disabled through the VIBECLI_TELEMETRY environment variable.
- The process execution and install functionality align with the package’s stated CLI purpose.
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/api-helper@0.0.142.
See all versions of @vibeapi/api-helper for other recorded verdicts.
- Review the evidence and your use of @vibeapi/api-helper@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.