@lotics/cli@0.315.13
Lotics SDK and CLI for AI agents
AI Security Review
scanned 19d ago · by lpm-firewall-aiThe telemetry path has an effective opt-in, but it sends the API key to a destination that can be changed through LOTICS_API_URL. This supports a warning for conditional credential exposure, not a block.
Decision evidence
public snapshot- The CLI sends batched telemetry with its API key as a bearer credential.
- Telemetry collection and sending are gated on LOTICS_TELEMETRY=1.
- The default API destination is api.lotics.ai, but LOTICS_API_URL can replace it.
- The required agent-configuration location is a documentation catalog entry.
- The package exposes the CLI and client through declared entrypoints; the manifest has no install lifecycle hook.
- The inspected agent-configuration location only catalogs documentation and does not mutate agent settings.
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.13.
See all versions of @lotics/cli for other recorded verdicts.
- Review the evidence and your use of @lotics/cli@0.315.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.