registry / @lotics/cli / 0.316.17
@lotics/cli@0.316.17
Lotics SDK and CLI for AI agents
AI Security Review
scanned 13d ago · by lpm-firewall-aiThe manifest has no install-time hook; its publish hook only builds the package. The CLI’s telemetry requires explicit opt-in and uses the configured API endpoint, so the scanner signals do not establish malicious behavior.
Static reason
One or more suspicious static signals were detected.
Trigger
Telemetry requires LOTICS_TELEMETRY=1 and runs during CLI startup.
Impact
No unconsented credential redirection, host fingerprinting, or command-output exfiltration was established.
Mechanism
When enabled, the CLI may send command metadata and bounded failure text to the configured API URL.
AI rationale
The manifest has no install-time hook; its publish hook only builds the package. The CLI’s telemetry requires explicit opt-in and uses the configured API endpoint, so the scanner signals do not establish malicious behavior.
Decision evidence
public snapshotAI called this Clean at 96.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package exposes a CLI and client library; its only publish lifecycle hook builds the package.
- Telemetry is disabled unless LOTICS_TELEMETRY is explicitly set to 1.
- When enabled, telemetry records command metadata and a bounded stderr tail on failures, then posts events to the configured API URL.
- The API URL defaults to api.lotics.ai and can be set by the caller; flag and environment credentials use that URL.
Evidence against
- With telemetry enabled, failure text from stderr may be sent with telemetry; this is an explicit opt-in behavior.
Behavioral surface
ChildProcessCryptoEnvironmentVarsEvalFilesystemNetworkShell
HighEntropyStringsPossibleObfuscationUrlStrings
WildcardDependency
Source & flagged code
7 flaggeddist/src/cli.jsView file
1746// src/cli_dispatch.ts
L1747: import { spawn as spawn2 } from "node:child_process";
L1748:
High
1779// docs/cli_reference.md
L1780: 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...
L1781:
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
7 High4 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
HighRemote Agent Bridgedist/src/cli.js
HighTrigger Reachable Command Output Exfiltrationdist/src/cli.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
MediumWildcard Dependency
LowNon Install Lifecycle Scripts
LowScripts Present
LowEval
LowFilesystem
Affected versions and remediation
This report applies to @lotics/cli@0.316.17.
See all versions of @lotics/cli for other recorded verdicts.
- Review the evidence and your use of @lotics/cli@0.316.17 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.