@lotics/cli@0.313.3
Lotics SDK and CLI for AI agents
AI Security Review
scanned 23d ago · by lpm-firewall-aiThe manifest has no npm install hook, the flagged agent location indexes documentation, and telemetry is explicitly opt-in and sent to the configured API service. The inspected source does not establish credential theft, host fingerprint exfiltration, or another concrete attack.
Decision evidence
public snapshot- package.json points the executable to dist/src/cli.js and exports dist/src/client.js.
- The manifest’s lifecycle script is prepublishOnly, which runs the build; it has no npm install hook.
- The required agent-integration location indexes embedded CLI documentation and does not configure an agent.
- Telemetry collection requires LOTICS_TELEMETRY=1, and the startup installer checks that gate.
- Telemetry sends events to the configured API base URL, which defaults to api.lotics.ai; ordinary SDK requests use that same base URL with the supplied API key.
- Opt-in telemetry can include session and command details and failed-command error text.
Source & flagged code
8 flaggedPackage source references child process execution.
dist/src/cli.jsView on unpkg · L46599Findings
Affected versions and remediation
This report applies to @lotics/cli@0.313.3.
See all versions of @lotics/cli for other recorded verdicts.
- Review the evidence and your use of @lotics/cli@0.313.3 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.