@lotics/cli@0.294.0
Lotics SDK and CLI for AI agents
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe scanner signals resolve to ordinary API authentication, opt-in diagnostics, and user-invoked build or upgrade operations. Direct inspection found no concrete malicious behavior or guarded agent configuration capability warranting a warning.
Decision evidence
public snapshot- The manifest exposes the CLI and SDK, has only a publishing build hook, and has no runtime self-dependency or registry-install hook.
- The flagged agent integration location is a documentation registry entry; it does not write agent configuration or install plugins.
- Diagnostics require LOTICS_TELEMETRY=1 and send command metadata and bounded error text to the active Lotics API.
- Authentication uses a caller-supplied or prompted API key with the selected Lotics server; the default is https://api.lotics.ai.
- Local npm execution supports explicit app creation and deployment; dependency installation disables lifecycle scripts.
- Shell-based self-upgrade runs only through the explicit upgrade command; automatic update checks retrieve version metadata.
Source & flagged code
8 flaggedPackage source references child process execution.
dist/src/cli.jsView on unpkg · L42429Findings
Affected versions and remediation
This report applies to @lotics/cli@0.294.0.
See all versions of @lotics/cli for other recorded verdicts.
- Review the evidence and your use of @lotics/cli@0.294.0 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.