@lotics/cli@0.318.17
Lotics SDK and CLI for AI agents
AI Security Review
scanned 8d ago · by lpm-firewall-aiThe manifest’s prepublishOnly hook runs a build, and the runtime telemetry path is gated by an explicit environment setting. The reviewed authentication and telemetry requests target the configured Lotics API base, which defaults to api.lotics.ai; the suspicious scanner labels did not establish malicious behavior.
Decision evidence
public snapshot- package.json points the CLI and library entrypoints to dist/src/cli.js and dist/src/client.js; its prepublishOnly hook runs the build.
- Telemetry is disabled unless LOTICS_TELEMETRY is set to 1.
- When enabled, telemetry events include CLI session, command, flags, exit status, and duration.
- Authenticated requests use the configured API base URL, which defaults to api.lotics.ai; telemetry posts to that API’s CLI telemetry endpoint.
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.17.
See all versions of @lotics/cli for other recorded verdicts.
- Review the evidence and your use of @lotics/cli@0.318.17 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.