@lotics/cli@0.318.31
Lotics SDK and CLI for AI agents
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe manifest exposes a CLI and client, while the inspected credential and telemetry paths target the Lotics API and telemetry requires explicit opt-in. The flagged download-and-run string is printed for the user rather than executed automatically.
Decision evidence
public snapshot- The manifest exposes a CLI executable and a separate JavaScript client entry point.
- Telemetry is enabled only when LOTICS_TELEMETRY is set to "1".
- The CLI's default API host is api.lotics.ai, and its telemetry request uses the API key as a bearer credential.
- The flagged shell pipeline is returned as an update instruction for display.
- The manifest's prepublishOnly script is a build script, not an install hook.
- The inspected code did not show a fixed unofficial gateway receiving credentials or command output.
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.31.
See all versions of @lotics/cli for other recorded verdicts.
- Review the evidence and your use of @lotics/cli@0.318.31 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.