registry / @lotics/cli / 0.315.0
@lotics/cli@0.315.0
Lotics SDK and CLI for AI agents
AI Security Review
scanned 23d ago · by lpm-firewall-aiSource inspection found no install-time attack behavior or agent control-surface mutation. The scanner’s agent-location hint points to documentation, and telemetry is explicitly opt-in and package-aligned.
Static reason
One or more suspicious static signals were detected.
Trigger
Telemetry requires the user to set LOTICS_TELEMETRY=1 and invoke the CLI.
Impact
No unconsented credential disclosure, agent configuration mutation, or other malicious effect was established.
Mechanism
The CLI buffers command metadata and posts events to its resolved API endpoint; the agent-related location is documentation metadata.
AI rationale
Source inspection found no install-time attack behavior or agent control-surface mutation. The scanner’s agent-location hint points to documentation, and telemetry is explicitly opt-in and package-aligned.
Decision evidence
public snapshotAI called this Clean at 97.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json exposes the CLI and SDK; its scripts show a prepublishOnly build hook, with no install lifecycle hook.
- The required agent integration location is a built-in CLI documentation index entry, not an agent configuration write.
- Telemetry is enabled only by LOTICS_TELEMETRY=1; when enabled, the CLI records command metadata and sends events to its resolved Lotics API endpoint.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsEvalFilesystemNetworkShell
HighEntropyStringsPossibleObfuscationUrlStrings
WildcardDependency
Source & flagged code
8 flaggeddist/src/cli.jsView file
46630// src/cli_dispatch.ts
L46631: import { spawn as spawn2 } from "node:child_process";
L46632:
High
Child Process
Package source references child process execution.
dist/src/cli.jsView on unpkg · L4663046651// docs/cli_reference.md
L46652: 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...
L46653:
High
661loggedProperties[propertyName] = true;
L662: _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 ...
L663: }
...
L955: },
L956: data: function data(value, depth) {
L957: while (value && depth--) {
...
L2968:
L2969: // ../../node_modules/handlebars/node_modules/source-map/lib/base64.js
L2970: var require_base64 = __commonJS({
...
L5756: (function() {
L5757: 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...
L5758: 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.315.0.
See all versions of @lotics/cli for other recorded verdicts.
- Review the evidence and your use of @lotics/cli@0.315.0 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.