@lotics/cli@0.315.1
Lotics SDK and CLI for AI agents
AI Security Review
scanned 23d ago · by lpm-firewall-aiThe inspected manifest and entrypoint source do not support the scanner's attack claims. The agent-configuration hint points into documentation data, and telemetry is explicitly gated and defaults to the package's Lotics API endpoint.
Decision evidence
public snapshot- package.json exposes a CLI and a client library; its only lifecycle script is prepublishOnly, which runs the build.
- The flagged agent-configuration location is an embedded documentation index, not configuration mutation code.
- Telemetry is disabled unless LOTICS_TELEMETRY is set to 1, and installation of its exit handler uses the same guard.
- Telemetry targets https://api.lotics.ai by default; source records command metadata and argument shape, not argument values.
- The CLI source inspected does not establish credential theft, host fingerprint exfiltration, or remote command execution.
Source & flagged code
8 flaggedPackage source references child process execution.
dist/src/cli.jsView on unpkg · L46630Findings
Affected versions and remediation
This report applies to @lotics/cli@0.315.1.
See all versions of @lotics/cli for other recorded verdicts.
- Review the evidence and your use of @lotics/cli@0.315.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.