@lotics/cli@0.318.5
Lotics SDK and CLI for AI agents
AI Security Review
scanned 8d ago · by lpm-firewall-aiSource inspection found no install-time attack or fixed unofficial credential gateway. Telemetry is opt-in and uses the selected Lotics API endpoint; subprocess use is tied to CLI build operations.
Decision evidence
public snapshot- The package exposes its CLI through dist/src/cli.js and its client through dist/src/client.js; its only lifecycle hook is prepublishOnly, which runs the build.
- Telemetry requires LOTICS_TELEMETRY=1. When enabled, it posts CLI events to the selected API URL; the default is Lotics’ API.
- The authenticated telemetry caller supplies the same API URL and key used for the CLI context.
- The npm subprocess is used for CLI build operations, with arguments written by the CLI.
Source & flagged code
6 flaggedSource collects local host identity data and sends it to an external endpoint.
Findings
Affected versions and remediation
This report applies to @lotics/cli@0.318.5.
See all versions of @lotics/cli for other recorded verdicts.
- Review the evidence and your use of @lotics/cli@0.318.5 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.