registry / @lotics/cli / 0.311.4
@lotics/cli@0.311.4
Lotics SDK and CLI for AI agents
AI Security Review
scanned 27d ago · by lpm-firewall-aiThe manifest has no install-time hook; prepublishOnly only builds the package. The reviewed telemetry is explicitly gated and directed to the configured Lotics API, while the agent-integration hint points to documentation metadata rather than an agent configuration mutation.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Telemetry runs only when LOTICS_TELEMETRY is set to 1.
Impact
No malicious effect was established from the inspected behavior.
Mechanism
The CLI records invocation telemetry and posts it to the configured API URL; the inspected agent-related location only registers documentation sources.
AI rationale
The manifest has no install-time hook; prepublishOnly only builds the package. The reviewed telemetry is explicitly gated and directed to the configured Lotics API, while the agent-integration hint points to documentation metadata rather than an agent configuration mutation.
Evidence
package.jsondist/src/cli.js
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 a CLI and client; its only lifecycle script is prepublishOnly, which runs the build.
- Telemetry collection and sending require LOTICS_TELEMETRY=1; telemetry posts to the configured Lotics API URL.
- The agent-integration location is a documentation-source registry entry, not an agent configuration write.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsEvalFilesystemNetworkShell
HighEntropyStringsPossibleObfuscationUrlStrings
WildcardDependency
Source & flagged code
9 flaggeddist/src/cli.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = @lotics/cli@0.311.3
matchedIdentity = npm:QGxvdGljcy9jbGk:0.311.3
similarity = 0.500
summary = stored previous version shares package body but lacks this dangerous source file
Critical
Previous Version Dangerous Delta
This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/src/cli.jsView on unpkg46149// src/cli_dispatch.ts
L46150: import { spawn as spawn2 } from "node:child_process";
L46151:
High
Child Process
Package source references child process execution.
dist/src/cli.jsView on unpkg · L4614946170// docs/cli_reference.md
L46171: 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...
L46172:
High
Findings
1 Critical8 High4 Medium6 Low
CriticalPrevious Version Dangerous Deltadist/src/cli.js
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
Affected versions and remediation
This report applies to @lotics/cli@0.311.4.
See all versions of @lotics/cli for other recorded verdicts.
- Review the evidence and your use of @lotics/cli@0.311.4 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.