@emgeebee/phone_cli@3.29.1
mats useful cli scripts
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe package automatically syncs local Octopus cache data to a fixed backend when the octo command runs, without documenting that transfer. The token is user-configured for the package API, so this is an undisclosed runtime data-sync risk rather than clear credential theft.
Decision evidence
public snapshot- The Octopus CLI uses a fixed AWS API endpoint and reads its authorization token from config.cal.token.
- Running the octo command loads its cache automatically; when configured, it fetches remote cache data and compares it with local data.
- When the merged cache differs from the remote copy, the command uploads the cache contents to that endpoint.
- The token must already be present in the user's config, and the API uses it as its bearer token and API key.
- The upload is tied to an explicitly run CLI command, rather than occurring during installation or package import.
- The process execution finding is in bundled Commander code; the package launcher spawns only the selected CLI.
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.29.1.
See all versions of @emgeebee/phone_cli for other recorded verdicts.
- Review the evidence and your use of @emgeebee/phone_cli@3.29.1 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.