@lotics/cli@0.318.14
Lotics SDK and CLI for AI agents
AI Security Review
scanned 8d ago · by lpm-firewall-aiInspected the manifest and bundled runtime paths highlighted by the scanner. The lifecycle, telemetry, API-host, and subprocess evidence is consistent with CLI functionality and does not establish credential theft or command-output exfiltration.
Decision evidence
public snapshot- package.json defines `prepublishOnly` as a build command; it has no install lifecycle hook.
- CLI telemetry is gated on `LOTICS_TELEMETRY=1`.
- Telemetry posts events to the CLI telemetry route using the configured API key.
- The default API host is Lotics, and an operator can configure `LOTICS_API_URL`.
- The app toolchain installs dependencies with `--ignore-scripts`.
- The scanner’s reported credential redirection and command-output exfiltration are not established by the inspected source: the visible network and subprocess paths support Lotics API requests, update checks, and user-invoked app build operations.
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.14.
See all versions of @lotics/cli for other recorded verdicts.
- Review the evidence and your use of @lotics/cli@0.318.14 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.