@lotics/cli@0.312.19
Lotics SDK and CLI for AI agents
AI Security Review
scanned 24d ago · by lpm-firewall-aiThe required agent-configuration hint points to a static documentation table, and the manifest has no install-time lifecycle hook; its `prepublishOnly` hook only builds. The suspicious signals inspected resolve to opt-in telemetry and normal API authentication, with no verified malicious transfer or execution behavior.
Decision evidence
public snapshot- package.json defines only a `prepublishOnly` hook, which runs the build.
- The required agent-configuration location is a documentation-source entry in a static table; it performs no configuration write.
- Telemetry collection is gated on `LOTICS_TELEMETRY=1` and requires an invocation with a session.
- Telemetry sends command names, flag names, exit status, and duration to the configured Lotics API endpoint.
- The CLI sends authenticated requests to the configured Lotics API, with `api.lotics.ai` as its default.
- The inspected source did not establish credential redirection, host-identity disclosure, or remote command execution.
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.19.
See all versions of @lotics/cli for other recorded verdicts.
- Review the evidence and your use of @lotics/cli@0.312.19 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.