@vibeapi/api-helper@0.0.139
CLI tool for managing AI coding assistants (Claude Code, Codex, OpenClaw, Hermes, AtomCode, Grok Build) with one unified config
AI Security Review
scanned 8d ago · by lpm-firewall-aiStatic inspection confirms persistent environment changes on ordinary CLI command paths, creating a concrete risk of removing user settings. The evidence supports a warning for destructive capability, but does not establish a malicious attack or credential exfiltration.
Decision evidence
public snapshot- Ordinary non-configuration CLI commands can reach environment cleanup; the cleanup list includes Anthropic API keys and settings.
- The cleanup removes matching exports from shell startup files and deletes matching variables from the running process environment.
- Diagnostic reporting is invoked with the explicit report option; its request uses the configured base URL and API key.
- Claude plugin installation is exposed as a CLI adapter operation, and the installer checks installed plugins and supports an environment opt-out.
- The inspected source establishes persistent environment changes, but no unrelated credential recipient, data theft, or install-time trigger for those changes.
- Telemetry requests use the configured service base URL; the inspected source does not establish that the API key is sent to an unrelated recipient.
Source & flagged code
6 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.139.
See all versions of @vibeapi/api-helper for other recorded verdicts.
- Review the evidence and your use of @vibeapi/api-helper@0.0.139 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.