@lotics/cli@0.305.1
Lotics SDK and CLI for AI agents
AI Security Review
scanned 29d ago · by lpm-firewall-aiThe manifest has no install-time execution hook, and the flagged agent location is documentation metadata. Inspected credential forwarding targets the configured Lotics API, while telemetry requires explicit opt-in; no concrete malicious behavior was established.
Decision evidence
public snapshot- The manifest’s only publish lifecycle hook is prepublishOnly, which runs the build; it defines no install-time hook.
- Telemetry is disabled unless LOTICS_TELEMETRY is set to 1, and its event builder records command metadata rather than raw arguments.
- The CLI defaults API traffic to api.lotics.ai and sends its bearer credential with requests to the selected API base URL.
- The flagged agent-integration location is an embedded documentation index entry, not an agent configuration write.
Source & flagged code
8 flaggedPackage source references child process execution.
dist/src/cli.jsView on unpkg · L44501Findings
Affected versions and remediation
This report applies to @lotics/cli@0.305.1.
See all versions of @lotics/cli for other recorded verdicts.
- Review the evidence and your use of @lotics/cli@0.305.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.