@lotics/cli@0.315.11
Lotics SDK and CLI for AI agents
AI Security Review
scanned 22d ago · by lpm-firewall-aiSource inspection found no install-time attack or unrelated credential recipient. The flagged agent location is embedded documentation, and the telemetry path is opt-in and aligned with the configured Lotics API.
Decision evidence
public snapshot- package.json exposes the `lotics` CLI and `LoticsClient` library entrypoints.
- The inspected lifecycle hook is `prepublishOnly`, which runs the build; no install hook is configured.
- The required agent-related location is part of the CLI’s embedded documentation index, not an agent settings mutation.
- Telemetry requires `LOTICS_TELEMETRY=1`; it records command metadata and may include stderr from failed invocations.
- Telemetry posts to the configured API URL using its API key; the default URL is `https://api.lotics.ai`.
- The client sends its API key to the `apiUrl` supplied in its options, with requests built against that base URL.
Source & flagged code
7 flaggedPackage source references child process execution.
dist/src/cli.jsView on unpkg · L46888Findings
Affected versions and remediation
This report applies to @lotics/cli@0.315.11.
See all versions of @lotics/cli for other recorded verdicts.
- Review the evidence and your use of @lotics/cli@0.315.11 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.