@lotics/cli@0.315.7
Lotics SDK and CLI for AI agents
AI Security Review
scanned 22d ago · by lpm-firewall-aiThe source shows no install-time attack behavior, and the agent-related hint resolves to a documentation catalog entry. The suspicious telemetry and process-launch signals correspond to explicit opt-in telemetry and CLI build operations.
Decision evidence
public snapshot- The manifest defines a CLI and SDK entrypoint and a prepublish-only build hook; it shows no install lifecycle hook.
- The flagged agent integration location is a documentation catalog entry, not an agent configuration write.
- Telemetry collection is gated on the explicit LOTICS_TELEMETRY=1 setting.
- Opted-in telemetry records CLI session and invocation metadata such as command, flags, exit status, duration, and version.
- The telemetry sender posts to the configured API base, which defaults to https://api.lotics.ai, at the CLI telemetry endpoint.
Source & flagged code
7 flaggedPackage source references child process execution.
dist/src/cli.jsView on unpkg · L46657Findings
Affected versions and remediation
This report applies to @lotics/cli@0.315.7.
See all versions of @lotics/cli for other recorded verdicts.
- Review the evidence and your use of @lotics/cli@0.315.7 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.