@emgeebee/phone_cli@3.22.3
mats useful cli scripts
AI Security Review
scanned 4mo ago · by lpm-firewall-aiStatic source inspection shows a multi-command personal utility CLI with no install hooks and no unconsented lifecycle behavior; network, child_process, env, and file writes are package-aligned and user-invoked. The dangerous static labels are noisy because they match bundled libraries, local subcommand dispatch, and documented API clients rather than an attack chain.
Decision evidence
public snapshot- package.json has no npm lifecycle hooks; only bin entrypoints under dist/*.js.
- dist/phone_cli.js only dispatches allowlisted subcommands via node spawnSync to package-local scripts.
- dist/fuel.js network use is user-invoked fuel lookup: Fuel Finder API, postcodes.io, and package station-list API.
- dist/cmd.js exposes explicit home automation commands; POST/PUT are triggered only by CLI arguments.
- dist/octo.js reads user config tokens and writes package cache/config paths, not foreign agent or persistence surfaces.
- No AI-agent control-surface writes, install-time execution, shell startup hooks, or destructive file operations found.
Source & flagged code
5 flaggedSource gates dangerous network, credential, or execution behavior behind CI, host, platform, time, or geo fingerprint checks.
dist/fuel.jsView on unpkg · L38Findings
Affected versions and remediation
This report applies to @emgeebee/phone_cli@3.22.3.
See all versions of @emgeebee/phone_cli for other recorded verdicts.
- Review the evidence and your use of @emgeebee/phone_cli@3.22.3 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.