@lotics/cli@0.312.21
Lotics SDK and CLI for AI agents
AI Security Review
scanned 23d ago · by lpm-firewall-aiSource inspection found no confirmed malicious behavior. The agent-related location is a documentation registry entry, and the flagged telemetry path is opt-in and targets the configured API.
Decision evidence
public snapshot- package.json routes the CLI and SDK to their built entrypoints; its prepublishOnly script runs the build.
- The required agent-integration location registers AGENTS.md as a documentation source; it does not configure or install an agent extension.
- Telemetry collection and installation require LOTICS_TELEMETRY=1.
- When enabled, telemetry records CLI session and command metadata and flushes only after at least five events to the configured API; the default API is api.lotics.ai.
- SDK requests send the caller's API key to the configured API base URL as a bearer credential.
- The inspected source does not substantiate host fingerprint exfiltration, an unofficial credential redirect, or command-output exfiltration.
- The credentialed SDK request uses its configured service base URL; telemetry is opt-in and uses that same configured API target.
Source & flagged code
8 flaggedPackage source references child process execution.
dist/src/cli.jsView on unpkg · L46924Findings
Affected versions and remediation
This report applies to @lotics/cli@0.312.21.
See all versions of @lotics/cli for other recorded verdicts.
- Review the evidence and your use of @lotics/cli@0.312.21 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.