@lotics/cli@0.315.5
Lotics SDK and CLI for AI agents
AI Security Review
scanned 22d ago · by lpm-firewall-aiThe package has no install hook, and its apparent agent-configuration match is only an embedded reference entry. The network and credential handling inspected is tied to the configured Lotics API, with telemetry disabled by default; no concrete attack behavior was found.
Decision evidence
public snapshot- package.json lists prepublishOnly as a build command; it has no install lifecycle hook.
- The required agent-configuration match is an embedded reference-table entry naming documentation files and their readers.
- Telemetry requires LOTICS_TELEMETRY=1; its events contain command and flag names, argument shape and hash, and stderr text on failed commands.
- Authenticated requests use the configured API base URL, which defaults to https://api.lotics.ai; telemetry is posted to that API.
Source & flagged code
7 flaggedPackage source references child process execution.
dist/src/cli.jsView on unpkg · L46640Findings
Affected versions and remediation
This report applies to @lotics/cli@0.315.5.
See all versions of @lotics/cli for other recorded verdicts.
- Review the evidence and your use of @lotics/cli@0.315.5 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.