@vibeapi/cli@0.0.143
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 sends runtime telemetry by default without a disclosure found in the README, so this is suspicious under the telemetry rule. The reviewed event payload contains usage and runtime metadata, not an evident credential or user-input exfiltration flow.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A user runs the CLI; command events are queued and flushed during execution.
Impact
Reports CLI usage and environment version details without an apparent user opt-in.
Mechanism
The CLI sends usage events and package/runtime metadata to its telemetry API. Telemetry can be disabled through VIBECLI_TELEMETRY.
AI rationale
The package sends runtime telemetry by default without a disclosure found in the README, so this is suspicious under the telemetry rule. The reviewed event payload contains usage and runtime metadata, not an evident credential or user-input exfiltration flow.
Evidence
dist/lib/telemetry.jsdist/lib/command.jsdist/brand.json
Network endpoints6
www.vibeapi.cnwww.vibeapi.sihk.vibeapi.cnus13-www.vibeapi.cncf.vibeapi.cntoken.nfeyre.top
Decision evidence
public snapshotAI called this Suspicious at 91.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- Runtime telemetry is enabled by default; it can be disabled with the VIBECLI_TELEMETRY environment setting.
- Telemetry sends command events and package, OS, architecture, and runtime metadata to /api/platform/vibecode/telemetry.
- The CLI records command start and completion events during normal command execution.
- The manifest declares no install, preinstall, or postinstall lifecycle hook.
Evidence against
- The collected event fields are command and step names, status, duration, and masked error text; the reviewed code does not show prompts, command input, or credentials in the event payload.
- The default telemetry destinations are VibeAPI gateway domains, consistent with the package’s service.
Behavioral surface
ChildProcessEnvironmentVarsNetworkShell
HighEntropyStringsMinifiedUrlStrings
Source & flagged code
7 flaggeddist/lib/tools/desktop-process.jsView file
1import{spawnSync as e}from"child_process";import{logger as t}from"../../utils/logger.js";export const WINDOWS_PACKAGE_FAMILIES=["Claude_pzs8sxrjxfjjc","AnthropicPBC.Claude_fnn82j28...
High
Child Process
Package source references child process execution.
dist/lib/tools/desktop-process.jsView on unpkg · L1dist/lib/tools/tool-installs.jsView file
1import{spawnSync as t}from"child_process";import{existsSync as r,realpathSync as n,statSync as e}from"fs";import{delimiter as o,dirname as s,isAbsolute as i,join as a}from"path";im...
High
1import{spawnSync as t}from"child_process";import{existsSync as r,realpathSync as n,statSync as e}from"fs";import{delimiter as o,dirname as s,isAbsolute as i,join as a}from"path";im...
Findings
1 Critical5 High4 Medium4 Low
CriticalPrevious Version Dangerous Deltadist/lib/auto-update.js
HighChild Processdist/lib/tools/desktop-process.js
HighShelldist/lib/tools/tool-installs.js
HighSame File Env Network Executiondist/lib/tools/claude-desktop-cli.js
HighTrigger Reachable Persistencedist/lib/env-cleanup.js
HighRuntime Package Installdist/lib/tools/tool-installs.js
MediumNetwork
MediumEnvironment Vars
MediumInstall Persistencedist/lib/persistent-env.js
MediumStructural Risk Force Deep Review
LowScripts Present
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @vibeapi/cli@0.0.143.
See all versions of @vibeapi/cli for other recorded verdicts.
- Review the evidence and your use of @vibeapi/cli@0.0.143 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.