@caishenai/cli@0.0.144
Configure Claude Code, Codex, Grok Build and other coding tools for 财神 AI with one command
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe CLI sends runtime telemetry by default, including command events and OS/runtime details, and the inspected documentation does not disclose this collection. Its opt-out and secret masking reduce risk, so this warrants a warning rather than a malicious verdict.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Automatically when the CLI runs a command; events are sent during execution or flushed when the command finishes.
Impact
The service receives usage events and OS/runtime details without disclosure found in the inspected package documentation.
Mechanism
The CLI records command events and posts them to `/api/platform/vibecode/telemetry` at the configured base URL. Telemetry is on by default, with an environment-variable opt-out.
AI rationale
The CLI sends runtime telemetry by default, including command events and OS/runtime details, and the inspected documentation does not disclose this collection. Its opt-out and secret masking reduce risk, so this warrants a warning rather than a malicious verdict.
Evidence
dist/lib/command.jsdist/lib/telemetry.jspackage.json
Decision evidence
public snapshotAI called this Suspicious at 87.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- CLI execution records command events and flushes telemetry at command completion.
- Telemetry sends install ID, CLI version, brand, OS details, Node version, and event data to `/api/platform/vibecode/telemetry` at the configured base URL.
- Telemetry is enabled by default; it can be disabled with `TELEMETRY=0`, `false`, or `off`.
- The package description says it configures coding tools; no telemetry disclosure was found in the inspected README search.
Evidence against
- The manifest declares no lifecycle scripts.
- Telemetry masks home paths and common token formats in error strings.
- The flagged Claude Desktop and process-management code serves the package’s stated tool-configuration purpose.
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 Medium3 Low
CriticalPrevious Version Dangerous Deltadist/lib/tools/claude-desktop.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
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to @caishenai/cli@0.0.144.
See all versions of @caishenai/cli for other recorded verdicts.
- Review the evidence and your use of @caishenai/cli@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.