@lotics/cli@0.318.23
Lotics SDK and CLI for AI agents
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe suspicious scanner leads resolve to ordinary CLI behavior: an explicit update path, Lotics API requests, and opt-in disclosed telemetry. I found no automatic credential redirection or host-identity exfiltration in the inspected entry points.
Decision evidence
public snapshot- The manifest exposes a CLI and library entry point, with `prepublishOnly` running a build and no install-time script.
- Runtime telemetry is disabled unless `LOTICS_TELEMETRY=1` is set.
- Telemetry records command metadata and argument shape/hash rather than argument values; its documented behavior includes a failure message.
- The CLI sends requests to the Lotics API by default, or to the API URL the user configures.
- API-key setup prompts for a key and uses it with the selected API URL.
- The CLI includes a command string that pipes the official Lotics installer into a shell; it is part of the update flow, not an install hook.
Source & flagged code
6 flaggedSource collects local host identity data and sends it to an external endpoint.
Findings
Affected versions and remediation
This report applies to @lotics/cli@0.318.23.
See all versions of @lotics/cli for other recorded verdicts.
- Review the evidence and your use of @lotics/cli@0.318.23 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.