registry / @lotics/cli / 0.318.15
@lotics/cli@0.318.15
Lotics SDK and CLI for AI agents
AI Security Review
scanned 8d ago · by lpm-firewall-aiThe required manifest and CLI entrypoint review found opt-in telemetry sent to the Lotics API and user-invoked local tooling. The scanner’s network and subprocess signals do not establish malicious behavior.
Static reason
One or more suspicious static signals were detected.
Trigger
Telemetry activates only when LOTICS_TELEMETRY is set to 1; local app tooling runs when its related CLI operation is invoked.
Impact
No unconsented credential theft, host fingerprint disclosure, or command-output exfiltration was established from the inspected source.
Mechanism
The CLI records command metadata and posts queued events to the configured API; subprocess use is for tar and npm tooling.
AI rationale
The required manifest and CLI entrypoint review found opt-in telemetry sent to the Lotics API and user-invoked local tooling. The scanner’s network and subprocess signals do not establish malicious behavior.
Network endpoints1
api.lotics.ai
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exposes the built CLI and client; its prepublishOnly script runs a build, not an install hook.
- Telemetry is disabled unless LOTICS_TELEMETRY is set to 1, and its installer returns immediately otherwise.
- When enabled, telemetry sends CLI events to the configured API URL; the default is api.lotics.ai.
- The CLI subprocess matches are for tar and npm operations used by local app tooling.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsEvalFilesystemNetworkShell
HighEntropyStringsPossibleObfuscationUrlStrings
WildcardDependency
Source & flagged code
6 flaggeddist/src/cli.jsView file
1791// src/cli_dispatch.ts
L1792: import { spawn as spawn2 } from "node:child_process";
L1793:
High
1824// docs/cli_reference.md
L1825: var cli_reference_default = "# @lotics/cli \u2014 CLI Command Reference\n\nPer-command syntax, flags, contracts, and gotchas for the public `lotics` CLI. Start at [AGENTS.md](../AG...
L1826:
High
9// src/cli.ts
L10: import dns from "node:dns";
L11: import net from "node:net";
...
L111: import path from "node:path";
L112: function telemetryEnabled(env = process.env) {
L113: return env.LOTICS_TELEMETRY === "1";
...
L142: function sessionStorePath() {
L143: return path.join(os.homedir(), ".lotics", "session.json");
L144: }
...
L146: try {
L147: const parsed = JSON.parse(fs.readFileSync(file2, "utf-8"));
L148: if (typeof parsed !== "object" || parsed === null) return null;
High
Host Fingerprint Exfiltration
Source collects local host identity data and sends it to an external endpoint.
Findings
6 High3 Medium6 Low
HighChild Processdist/src/cli.js
HighShelldist/src/cli.js
HighHost Fingerprint Exfiltrationdist/src/cli.js
HighCredential Redirect Persistencedist/src/cli.js
HighCommand Output Exfiltrationdist/src/cli.js
HighTrigger Reachable Command Output Exfiltrationdist/src/cli.js
MediumNetwork
MediumEnvironment Vars
MediumWildcard Dependency
LowNon Install Lifecycle Scripts
LowScripts Present
LowEval
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @lotics/cli@0.318.15.
See all versions of @lotics/cli for other recorded verdicts.
- Review the evidence and your use of @lotics/cli@0.318.15 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.