@lotics/cli@0.313.1
Lotics SDK and CLI for AI agents
AI Security Review
scanned 23d ago · by lpm-firewall-aiThe suspicious signals resolve to opt-in telemetry, a documentation index entry, and ordinary CLI deployment helpers. The default telemetry endpoint is the package's Lotics API, and no concrete attack behavior was established.
Decision evidence
public snapshot- The manifest exposes the CLI bundle and client library; its only lifecycle hook is a prepublish build.
- The flagged agent integration location is a documentation index entry pointing to AGENTS.md, not an agent configuration write.
- Telemetry is disabled unless LOTICS_TELEMETRY is set to 1.
- Telemetry records command metadata, error text, and argument hashes and shapes rather than argument values.
- When enabled, telemetry sends events with a bearer key to the configured API; the default API is api.lotics.ai.
- The CLI invokes telemetry setup at startup, but the setup function exits immediately when telemetry is disabled.
- Telemetry can send an API key to the configured API endpoint when explicitly enabled; the endpoint can be changed through LOTICS_API_URL.
- The CLI includes child-process helpers for user-invoked app deployment and build operations.
Source & flagged code
8 flaggedPackage source references child process execution.
dist/src/cli.jsView on unpkg · L46913Findings
Affected versions and remediation
This report applies to @lotics/cli@0.313.1.
See all versions of @lotics/cli for other recorded verdicts.
- Review the evidence and your use of @lotics/cli@0.313.1 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.