@lotics/cli@0.318.27
Lotics SDK and CLI for AI agents
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe source does not show malicious behavior. Telemetry is disabled by default, its collected fields and failure messages are documented, and the shell-based installer is only run by the explicit upgrade command.
Decision evidence
public snapshot- The manifest’s `prepublishOnly` script runs a build; it declares no install-time hook.
- Telemetry is off unless `LOTICS_TELEMETRY=1` is set.
- Opt-in telemetry records command metadata and, on failure, the printed error; arguments contribute a hash and shape, not their values.
- Telemetry posts to the configured Lotics API’s `/v1/cli/telemetry` endpoint; the default API host is `api.lotics.ai`.
- The installer pipeline is invoked through the explicit `upgrade` command and points to Lotics’ own installer host.
- The CLI contains subprocess execution and a download-and-run command, but the latter is part of an explicit upgrade flow.
- Failure messages can include subprocess output, but the package documents that failed-command messages are recorded when telemetry is enabled.
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.27.
See all versions of @lotics/cli for other recorded verdicts.
- Review the evidence and your use of @lotics/cli@0.318.27 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.