@lotics/cli@0.318.33
Lotics SDK and CLI for AI agents
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe flagged process execution is part of an explicit upgrade command, and the telemetry path is gated by LOTICS_TELEMETRY=1, disclosed in the README, and directed to the configured Lotics API. The package manifest declares no install-time hook that would run these behaviors automatically.
Decision evidence
public snapshot- The manifest exposes a CLI binary and a separate client library; its only lifecycle script is prepublishOnly, which builds the package.
- Telemetry collection is disabled unless LOTICS_TELEMETRY is set to "1".
- Telemetry records command metadata and, on failure, the printed error message; arguments contribute a hash and shape rather than values.
- Telemetry posts to the configured Lotics API URL, which defaults to api.lotics.ai; the README discloses the collection and its opt-in setting.
- The upgrade command runs a fixed installer command only when the user invokes the upgrade action.
- No install or postinstall hook is declared.
- The source examined contains no confirmed credential forwarding to an unrelated host or unrequested account action.
- The update check contacts registry.npmjs.org only to retrieve the latest package version.
Source & flagged code
7 flaggedThis package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/src/cli.jsView on unpkgFindings
Affected versions and remediation
This report applies to @lotics/cli@0.318.33.
See all versions of @lotics/cli for other recorded verdicts.
- Review the evidence and your use of @lotics/cli@0.318.33 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.