@lotics/cli@0.312.20
Lotics SDK and CLI for AI agents
AI Security Review
scanned 24d ago · by lpm-firewall-aiThe manifest has no install-time lifecycle hook, and the inspected flagged source does not establish the scanner's alleged exfiltration or agent-control behavior. The evidence supports a clean verdict.
Decision evidence
public snapshot- The manifest exposes the CLI entrypoint and lists only a prepublish build hook, with no install-time hook.
- The CLI defaults its API endpoint to api.lotics.ai; an override is explicitly read from LOTICS_API_URL.
- Telemetry is disabled unless LOTICS_TELEMETRY is set to 1.
- The flagged CLI location is a documentation catalog entry for AGENTS.md and cli_reference, not an agent configuration write.
- No inspected source established host-identity exfiltration, credential redirection, or an active remote agent bridge.
Source & flagged code
8 flaggedPackage source references child process execution.
dist/src/cli.jsView on unpkg · L46924Findings
Affected versions and remediation
This report applies to @lotics/cli@0.312.20.
See all versions of @lotics/cli for other recorded verdicts.
- Review the evidence and your use of @lotics/cli@0.312.20 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.