@vibeapi/api-helper@0.0.144
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 CLI sends runtime telemetry by default, including command events and platform/runtime identifiers, without a README disclosure found in the package. The opt-out and limited event collection reduce the risk, so this is suspicious telemetry rather than a confirmed data-exfiltration attack.
Decision evidence
public snapshot- Runtime telemetry is enabled by default; setting TELEMETRY to 0, false, or off disables it. Telemetry headers include an install ID and platform/runtime identifiers.
- CLI use records command events and sends pending telemetry before exit; events can include command details and masked error messages.
- Telemetry batches are posted to /api/platform/vibecode/telemetry using the configured API base URL.
- The manifest has no install, preinstall, or postinstall hook.
- The package is a CLI for managing AI coding assistants, and the observed telemetry is tied to CLI command use.
- Command-start telemetry filters out non-flag arguments and flags whose names contain “key”; the code also masks home paths and common token formats in errors.
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.144.
See all versions of @vibeapi/api-helper for other recorded verdicts.
- Review the evidence and your use of @vibeapi/api-helper@0.0.144 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.