@lotics/cli@0.315.14
Lotics SDK and CLI for AI agents
AI Security Review
scanned 17d ago · by lpm-firewall-aiThe manifest exposes a CLI and SDK, with a publish hook limited to building the package. The inspected runtime behavior does not support the scanner’s claims of agent configuration abuse or credential redirection, so the package is clean.
Decision evidence
public snapshot- package.json exposes the CLI and SDK; its only publish lifecycle hook runs the build.
- The flagged agent-integration location is a catalog entry pointing to CLI documentation, not an agent configuration write.
- Telemetry collection requires LOTICS_TELEMETRY=1 and records command metadata and argument shapes rather than argument values.
- Telemetry is sent to the configured Lotics API telemetry endpoint using the resolved API key; the default API host is api.lotics.ai.
- The CLI initializes session tracking and telemetry at startup, but telemetry collection remains gated by the explicit environment setting.
- The scanner’s agent-configuration and credential-redirection claims are not supported by the inspected source locations; the flagged line is documentation metadata.
- No confirmed attack behavior was identified in the inspected entrypoint, telemetry, or credential-routing code.
Source & flagged code
7 flaggedPackage source references child process execution.
dist/src/cli.jsView on unpkg · L46888Findings
Affected versions and remediation
This report applies to @lotics/cli@0.315.14.
See all versions of @lotics/cli for other recorded verdicts.
- Review the evidence and your use of @lotics/cli@0.315.14 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.