@lotics/cli@0.312.11
Lotics SDK and CLI for AI agents
AI Security Review
scanned 25d ago · by lpm-firewall-aiThe source does not establish malicious default behavior: telemetry is opt-in and defaults to the package-aligned Lotics API. Because an unrestricted LOTICS_API_URL override can receive the bearer API key during telemetry, this conditional credential-forwarding risk warrants a warning.
Decision evidence
public snapshot- The CLI entry point is dist/src/cli.js; the manifest has no install lifecycle hook, and prepublishOnly only builds.
- The required agent-integration location is a static documentation-source entry, not an agent configuration mutation.
- Telemetry is disabled unless LOTICS_TELEMETRY is set to 1.
- When telemetry flushes, it sends the API key as a bearer token to the telemetry endpoint at the selected API base URL.
- LOTICS_API_URL can override the default API host, and the CLI passes that selected URL and key to telemetry.
- Telemetry is explicitly opt-in and sends only after at least five queued events.
- The default API host is api.lotics.ai, matching the package's Lotics service. No unrelated recipient or covert default credential export was identified.
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.11.
See all versions of @lotics/cli for other recorded verdicts.
- Review the evidence and your use of @lotics/cli@0.312.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.