@emgeebee/phone_cli@3.22.0
mats useful cli scripts
AI Security Review
scanned 4mo ago · by lpm-firewall-aiSource inspection found risky primitives only in user-invoked, package-aligned CLI commands and no lifecycle hooks, persistence, exfiltration, agent hijack, or remote execution. Credential reads are for documented service API calls rather than broad harvesting.
Decision evidence
public snapshot- dist/cmd.js has user-invoked POST controls to http://api.emgeebee.buzz:1880 and WFH toggle endpoint.
- dist/octo.js reads Octopus token/account from ~/.phone_cli.json and sends Basic auth to api.octopus.energy.
- dist/fuel.js reads FUEL_FINDER_CLIENT_ID/SECRET and requests Fuel Finder OAuth tokens at runtime.
- package.json has no preinstall/install/postinstall lifecycle hooks.
- dist/phone_cli.js only dispatches allowlisted local dist/*.js subcommands via node spawnSync.
- No AI-agent control-surface writes, shell startup hooks, persistence, destructive actions, eval, or remote code execution found.
- Home/config/cache file writes are package-aligned: ~/.phone_cli.json and phone_cli/fuel cache paths.
- Network use is visible CLI functionality for weather, sports, rail, energy, fuel, docs/cache, and home shortcuts.
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.0.
See all versions of @emgeebee/phone_cli for other recorded verdicts.
- Review the evidence and your use of @emgeebee/phone_cli@3.22.0 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.