@lotics/cli@0.312.16
Lotics SDK and CLI for AI agents
AI Security Review
scanned 24d ago · by lpm-firewall-aiThe flagged agent location is documentation metadata, while the inspected credential and network code serves authenticated requests to the configured Lotics API. Telemetry is opt-in, and the scanner hints do not establish malicious behavior.
Decision evidence
public snapshot- package.json exposes the CLI entrypoint and SDK client export, with only a build step under prepublishOnly.
- The flagged agent-related location is a bundled reference to AGENTS.md and the CLI reference; it does not configure an agent.
- Telemetry collection requires LOTICS_TELEMETRY=1; its requests use the selected Lotics API base URL.
- The CLI sends its API key as a bearer credential to its configured API client, consistent with normal authenticated requests.
- Sign-in requests send the supplied email to the selected Lotics API endpoint.
Source & flagged code
8 flaggedPackage source references child process execution.
dist/src/cli.jsView on unpkg · L46898Findings
Affected versions and remediation
This report applies to @lotics/cli@0.312.16.
See all versions of @lotics/cli for other recorded verdicts.
- Review the evidence and your use of @lotics/cli@0.312.16 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.