@lotics/cli@0.313.4
Lotics SDK and CLI for AI agents
AI Security Review
scanned 23d ago · by lpm-firewall-aiThe inspected source ties the scanner's agent configuration hint to a read-only documentation catalog and gates telemetry behind an explicit opt-in. Credential-bearing client requests target the API base URL supplied by the caller, so the reviewed behavior does not establish malicious credential forwarding or another concrete attack.
Decision evidence
public snapshot- package.json routes the CLI to dist/src/cli.js and the library export to dist/src/client.js; the listed lifecycle hook is prepublishOnly, which runs a build.
- The indicated AGENTS.md location is a documentation catalog entry; docsCommand reads the catalog for CLI documentation rather than changing agent configuration.
- CLI telemetry requires LOTICS_TELEMETRY=1, and the entrypoint passes through that gate before telemetry setup.
- Telemetry posts to the configured API's telemetry endpoint; source inspection found no unrelated fixed telemetry recipient.
- The client takes its API key and API URL from caller options and uses that base URL for requests, sending the key as a bearer credential to that configured API.
- The package does contain network requests and credential-bearing API calls, but inspected code ties them to the configured service API and gates telemetry behind explicit opt-in.
Source & flagged code
8 flaggedPackage source references child process execution.
dist/src/cli.jsView on unpkg · L46629Findings
Affected versions and remediation
This report applies to @lotics/cli@0.313.4.
See all versions of @lotics/cli for other recorded verdicts.
- Review the evidence and your use of @lotics/cli@0.313.4 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.