@lotics/cli@0.318.24
Lotics SDK and CLI for AI agents
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe manifest declares no install-time hook, and the flagged shell pipeline is printed as update advice rather than executed. Telemetry is off by default, documented, and sends to the configured Lotics API.
Decision evidence
public snapshot- The only lifecycle script is prepublishOnly, which runs the build; no install hook is declared.
- Telemetry is disabled unless LOTICS_TELEMETRY=1, and its documentation describes the recorded fields and excludes argument values, file contents, and record data.
- API credentials are sent as Bearer credentials to the configured API base URL, whose default is api.lotics.ai.
- The CLI checks the npm registry for its package version; the curl/PowerShell installer pipeline appears in update advice printed to stderr, not as executed code.
- The CLI contains process execution and shell-related code for app tooling, a version lookup, and commands that print installer advice.
- Opt-in telemetry can include the failure message printed by the CLI.
Source & flagged code
6 flaggedSource collects local host identity data and sends it to an external endpoint.
Findings
Affected versions and remediation
This report applies to @lotics/cli@0.318.24.
See all versions of @lotics/cli for other recorded verdicts.
- Review the evidence and your use of @lotics/cli@0.318.24 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.