@lotics/cli@0.312.2
Lotics SDK and CLI for AI agents
AI Security Review
scanned 25d ago · by lpm-firewall-aiSource inspection confirms an opt-in telemetry path that forwards the active API key to LOTICS_API_URL without a destination allowlist. This is conditional credential exposure, so the package warrants a warning rather than a publish block.
Decision evidence
public snapshot- Telemetry is disabled unless LOTICS_TELEMETRY is set to 1.
- When telemetry is enabled, its POST sends a Bearer API key with event data.
- The telemetry destination can be set through LOTICS_API_URL; the same configured URL is used for the authenticated telemetry request.
- The required agent integration location is a static documentation-source entry, not an agent configuration write.
- package.json defines only a prepublishOnly build hook, with no install-time execution hook.
- The CLI defaults its API destination to api.lotics.ai; the credential-bearing telemetry request requires the explicit telemetry opt-in.
Source & flagged code
8 flaggedPackage source references child process execution.
dist/src/cli.jsView on unpkg · L46522Findings
Affected versions and remediation
This report applies to @lotics/cli@0.312.2.
See all versions of @lotics/cli for other recorded verdicts.
- Review the evidence and your use of @lotics/cli@0.312.2 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.