@lotics/cli@0.318.34
Lotics SDK and CLI for AI agents
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe flagged CLI execution is part of app build tooling, and the manifest has no install-time hook. Telemetry is disabled by default and sends CLI metadata to the configured API endpoint, which defaults to the package's own service.
Decision evidence
public snapshot- The package exposes a CLI and client entry point; its only lifecycle script is prepublishOnly, which runs the build.
- Runtime telemetry is disabled unless LOTICS_TELEMETRY is set to "1".
- Telemetry events contain CLI session, command, flag names, version, duration and exit status metadata.
- Telemetry is posted to the configured API URL, which defaults to https://api.lotics.ai; the API key is sent as authorization to that same endpoint.
- The shell execution references are in the app toolchain's npm build path, with comments describing fixed CLI-written arguments.
- No install, preinstall or postinstall hook is declared.
- The inspected source shows no credential forwarding to an unrelated host or automatic host fingerprint collection.
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.34.
See all versions of @lotics/cli for other recorded verdicts.
- Review the evidence and your use of @lotics/cli@0.318.34 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.