@lotics/cli@0.318.16
Lotics SDK and CLI for AI agents
AI Security Review
scanned 8d ago · by lpm-firewall-aiThe manifest has no install-time lifecycle hook, and telemetry collection and sending are gated by an explicit environment opt-in. The default recipient is the package’s Lotics API, so the inspected behavior supports ordinary CLI telemetry rather than a confirmed attack.
Decision evidence
public snapshot- package.json lists `prepublishOnly` running the build; no install-time hook is listed.
- Telemetry collection and spool flushing both require `LOTICS_TELEMETRY=1`.
- Opt-in telemetry posts events to `/v1/cli/telemetry` at the configured API base, which defaults to `https://api.lotics.ai`; the SDK sends its key as normal bearer authentication.
- Telemetry events include command metadata and may include recent stderr text on failure.
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.16.
See all versions of @lotics/cli for other recorded verdicts.
- Review the evidence and your use of @lotics/cli@0.318.16 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.