registry / @lotics/cli / 0.311.1
@lotics/cli@0.311.1
Lotics SDK and CLI for AI agents
AI Security Review
scanned 27d ago · by lpm-firewall-aiThe manifest has no npm install lifecycle hook or runtime self-dependency, and the flagged agent-integration location is a passive documentation index. The inspected telemetry is opt-in and the network default is the package's own API, so the scanner signals did not establish malicious behavior.
Static reason
One or more suspicious static signals were detected.
Trigger
Telemetry requires LOTICS_TELEMETRY=1; the documentation index location is passive data.
Impact
No confirmed unauthorized collection, agent configuration mutation, or command-output exfiltration was identified.
Mechanism
The inspected code constructs limited invocation metadata and uses the official Lotics API endpoint by default, with an explicit endpoint override.
AI rationale
The manifest has no npm install lifecycle hook or runtime self-dependency, and the flagged agent-integration location is a passive documentation index. The inspected telemetry is opt-in and the network default is the package's own API, so the scanner signals did not establish malicious behavior.
Network endpoints1
api.lotics.ai
Decision evidence
public snapshotAI called this Clean at 89.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json exposes the CLI entrypoint and SDK client; its only lifecycle script is prepublishOnly build, with no install hook or runtime self-dependency.
- The flagged agent-integration location is a documentation index entry pointing to this CLI's own guidance; it does not mutate agent configuration.
- Telemetry requires LOTICS_TELEMETRY=1, and its session metadata construction limits command labels and excludes arguments and resource IDs.
- Network configuration defaults to api.lotics.ai, with an explicit LOTICS_API_URL override.
Evidence against
- The CLI can spawn npm for its documented build or install operations, but the inspected code does not show an install-time trigger or a malicious command chain.
Behavioral surface
ChildProcessCryptoEnvironmentVarsEvalFilesystemNetworkShell
HighEntropyStringsPossibleObfuscation
Source & flagged code
8 flaggeddist/src/cli.jsView file
45969// src/cli_dispatch.ts
L45970: import { spawn as spawn2 } from "node:child_process";
L45971:
High
Child Process
Package source references child process execution.
dist/src/cli.jsView on unpkg · L4596945990// docs/cli_reference.md
L45991: 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...
L45992:
High
640loggedProperties[propertyName] = true;
L641: _logger2["default"].log("error", 'Handlebars: Access has been denied to resolve the property "' + propertyName + '" because it is not an "own property" of its parent.\nYou can add ...
L642: }
...
L928: },
L929: data: function data(value, depth) {
L930: while (value && depth--) {
...
L2907:
L2908: // ../../node_modules/handlebars/node_modules/source-map/lib/base64.js
L2909: var require_base64 = __commonJS({
...
L5680: (function() {
L5681: var reservedWords = "break else new var case finally return void catch for switch while continue function this with default if throw delete in try do instanceof typeof abstract enu...
L5682: var compilerWords = JavaScriptCompiler.RESERVED_WORDS = {};
Findings
8 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
HighSandbox Evasion Gated Capabilitydist/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
Affected versions and remediation
This report applies to @lotics/cli@0.311.1.
See all versions of @lotics/cli for other recorded verdicts.
- Review the evidence and your use of @lotics/cli@0.311.1 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.