@lotics/cli@0.315.12
Lotics SDK and CLI for AI agents
AI Security Review
scanned 21d ago · by lpm-firewall-aiInspected source does not support the scanner’s suspicious verdict: the agent hit is documentation metadata, telemetry is opt-in and package-aligned, and the manifest has no install hook. No concrete malicious behavior was identified.
Decision evidence
public snapshot- The agent marker is a documentation index entry for AGENTS.md; app scaffolding includes that file among generated project files.
- The manifest defines prepublishOnly as a build command and has no preinstall, install, or postinstall hook.
- Telemetry setup returns unless LOTICS_TELEMETRY is set to 1.
- Enabled telemetry records command metadata, argument hashes and shapes, and failed-command error text; it does not serialize raw arguments.
- Telemetry posts to the Lotics API base, which defaults to https://api.lotics.ai and can be explicitly overridden with LOTICS_API_URL.
- The sign-in request sends the entered email to the configured Lotics login endpoint, and authenticated requests use the supplied key as a Bearer credential.
Source & flagged code
7 flaggedPackage source references child process execution.
dist/src/cli.jsView on unpkg · L46888Findings
Affected versions and remediation
This report applies to @lotics/cli@0.315.12.
See all versions of @lotics/cli for other recorded verdicts.
- Review the evidence and your use of @lotics/cli@0.315.12 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.