@lotics/cli@0.311.2
Lotics SDK and CLI for AI agents
AI Security Review
scanned 27d ago · by lpm-firewall-aiThe manifest points to the inspected CLI and SDK entrypoints and has no automatic install hook. The flagged agent location is documentation data, while telemetry is opt-in and directed to the configured Lotics API service.
Decision evidence
public snapshot- package.json exposes the CLI entrypoint and SDK client; its only lifecycle script is prepublishOnly, which runs a build.
- The required flagged location is part of an embedded documentation index, not agent configuration logic.
- Telemetry is disabled unless LOTICS_TELEMETRY is set to 1; emitted events require an active telemetry session.
- The CLI sends telemetry to the configured Lotics API URL, which defaults to api.lotics.ai.
Source & flagged code
8 flaggedPackage source references child process execution.
dist/src/cli.jsView on unpkg · L46003Findings
Affected versions and remediation
This report applies to @lotics/cli@0.311.2.
See all versions of @lotics/cli for other recorded verdicts.
- Review the evidence and your use of @lotics/cli@0.311.2 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.