@emgeebee/phone_cli@3.28.0
mats useful cli scripts
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe package silently syncs local Octopus cache data to its docs API when a shared config token is present, and this behavior is not disclosed in the README. The Octopus API credential flow itself appears consistent with the CLI’s advertised purpose, so the evidence supports a warning rather than a malicious verdict.
Decision evidence
public snapshot- The Octopus command reads `cal.token` from the shared config and uses it for a fixed AWS API docs service.
- When that token exists, the command loads local service cache data, merges it with remote data, and uploads changed cache contents.
- The same token is used when saving dirty cache data; this sync behavior is not described in the README.
- The `octo` command triggers cache loading when run and separately sends Octopus credentials to Octopus’s API.
- The package has no install lifecycle scripts.
- Octopus credentials are sent to the Octopus API for the advertised energy lookup feature.
- The cache sync requires an existing `cal.token`; no install-time or import-time upload was identified.
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.28.0.
See all versions of @emgeebee/phone_cli for other recorded verdicts.
- Review the evidence and your use of @emgeebee/phone_cli@3.28.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.