@lotics/cli@0.298.1
Lotics SDK and CLI for AI agents
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe inspected source resolves the scanner signals to package-aligned authentication, optional diagnostics, explicit upgrades, and app tooling. The indicated agent integration location is a documentation entry, and no concrete malicious behavior was found.
Decision evidence
public snapshot- package.json has only a publishing build hook, no registry-install hooks or runtime self-dependency.
- The flagged agent location in dist/src/cli.js indexes AGENTS.md as CLI documentation; it does not configure an agent.
- Telemetry requires LOTICS_TELEMETRY=1; inspected events contain command metadata and failure diagnostics.
- Authentication defaults to api.lotics.ai, with an explicit endpoint override; the client sends requests to its configured API.
- App dependency installation disables lifecycle scripts; inspected process launches support app builds and packaging.
- Shell-based self-upgrade is activated by the explicit upgrade command; the automatic update check only retrieves version metadata.
Source & flagged code
8 flaggedPackage source references child process execution.
dist/src/cli.jsView on unpkg · L43784Findings
Affected versions and remediation
This report applies to @lotics/cli@0.298.1.
See all versions of @lotics/cli for other recorded verdicts.
- Review the evidence and your use of @lotics/cli@0.298.1 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.