@lotics/cli@0.312.13
Lotics SDK and CLI for AI agents
AI Security Review
scanned 25d ago · by lpm-firewall-aiSource inspection found no concrete malicious behavior. The suspicious scanner signals are consistent with documented CLI functions: opt-in telemetry to the configured API and subprocess use for explicit build or packaging work.
Decision evidence
public snapshot- package.json assigns `prepublishOnly` only to `npm run build`; the published CLI is exposed through `dist/src/cli.js`.
- The cited agent integration location labels `AGENTS.md` as CLI reference material; it contains no configuration mutation there.
- Telemetry is disabled unless `LOTICS_TELEMETRY` equals `1`, and its event submission uses the configured Lotics API endpoint.
- The inspected source did not establish host identity theft, credential redirection, or command output exfiltration.
- The CLI can spawn npm and tar for explicit build or packaging operations, and can submit opted-in telemetry authenticated to the configured API endpoint.
Source & flagged code
8 flaggedPackage source references child process execution.
dist/src/cli.jsView on unpkg · L46797Findings
Affected versions and remediation
This report applies to @lotics/cli@0.312.13.
See all versions of @lotics/cli for other recorded verdicts.
- Review the evidence and your use of @lotics/cli@0.312.13 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.