@lotics/cli@0.318.18
Lotics SDK and CLI for AI agents
AI Security Review
scanned 8d ago · by lpm-firewall-aiThe manifest points to ordinary CLI and client entrypoints, and its prepublishOnly hook runs the build. The flagged telemetry and process execution are explained by explicit opt-in reporting and CLI build helpers; inspected source did not establish malicious behavior.
Decision evidence
public snapshot- The package exposes the CLI at dist/src/cli.js and the client at dist/src/client.js.
- The prepublishOnly hook runs the build command.
- Telemetry is disabled unless LOTICS_TELEMETRY is set to 1.
- Telemetry uploads event batches to the configured Lotics API endpoint; authenticated CLI calls use the same API URL and key.
- The telemetry event contains command metadata and, on failure, a bounded stderr tail.
- The inspected process launches are for tar and npm build/install helpers, with fixed CLI-controlled arguments.
- The credentialed telemetry upload requires the opt-in gate and uses the configured Lotics API destination; no unrelated recipient or credential harvesting was found.
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.18.
See all versions of @lotics/cli for other recorded verdicts.
- Review the evidence and your use of @lotics/cli@0.318.18 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.