@lotics/cli@0.311.6
Lotics SDK and CLI for AI agents
AI Security Review
scanned 24d ago · by lpm-firewall-aiInspected the package manifest, CLI entrypoint behavior, telemetry code, and flagged agent-related location. The static hints resolve to opt-in product telemetry and documentation indexing, with no confirmed attack behavior.
Decision evidence
public snapshot- package.json exposes the CLI entrypoint and SDK export; its only lifecycle script is prepublishOnly, which runs a build.
- The flagged location in dist/src/cli.js lists documentation sources; it does not configure an agent or mutate its files.
- Telemetry recording and exit handling are gated by LOTICS_TELEMETRY=1.
- Telemetry posts to the CLI API URL and uses the same API key the CLI uses for authenticated requests.
- The API URL defaults to api.lotics.ai; callers can explicitly set LOTICS_API_URL.
Source & flagged code
8 flaggedPackage source references child process execution.
dist/src/cli.jsView on unpkg · L46212Findings
Affected versions and remediation
This report applies to @lotics/cli@0.311.6.
See all versions of @lotics/cli for other recorded verdicts.
- Review the evidence and your use of @lotics/cli@0.311.6 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.