@emgeebee/phone_cli@3.26.0
mats useful cli scripts
AI Security Review
scanned 3d ago · by lpm-firewall-aiNo clear malware behavior was identified, but normal octo execution can sync household energy cache data to the package backend whenever a docs token is configured, without an in-command consent prompt. Treat this undisclosed runtime data sync as suspicious telemetry and warn users.
Decision evidence
public snapshot- The docs API uses a token read from config.cal.token and targets the package’s API Gateway endpoint.
- When a configured token exists, cache loading can upload merged local cache data if it differs from the remote document.
- The octo command flushes its cache during normal command execution.
- The Octopus API request sends the configured Octopus token to the Octopus API.
- The manifest declares build and command scripts, with no install lifecycle script.
- The remote cache sync requires config.cal.token and concerns this tool’s cache data.
- Octopus credentials are sent to api.octopus.energy, their intended service.
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.26.0.
See all versions of @emgeebee/phone_cli for other recorded verdicts.
- Review the evidence and your use of @emgeebee/phone_cli@3.26.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.