@lotics/cli@0.318.29
Lotics SDK and CLI for AI agents
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe flagged network and process behavior matches the CLI's documented functions: telemetry is off by default, and child processes support user-invoked build or upgrade operations. The inspected credential and telemetry flows do not show an unrelated destination or hidden automatic action.
Decision evidence
public snapshot- Runtime telemetry is off unless LOTICS_TELEMETRY=1 is set; the README describes the session recording and batching.
- When enabled, tool arguments contribute a hash and shape, not their values or file contents; the event includes command, exit status, duration, and failure message.
- Telemetry is posted to the configured Lotics API URL, with the API key sent to that same URL.
- The only lifecycle script is prepublishOnly, which runs the build.
- The CLI runs child processes for app build and install operations when those commands are invoked.
- The CLI offers a shell pipeline to download and run the official Lotics installer as an explicit upgrade action.
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.29.
See all versions of @lotics/cli for other recorded verdicts.
- Review the evidence and your use of @lotics/cli@0.318.29 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.