registry / @limai.io/cli / 0.4.16
@limai.io/cli@0.4.16
CLI and SDK for the LimAI data extraction platform
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe reviewed source matches a LimAI API SDK and CLI. Credential use is directed to the configured API, and the runtime package installation is limited to the explicit update command; no malicious behavior was identified.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
No malicious automatic trigger identified; package updates run only when the user invokes the update command.
Impact
No unauthorized credential disclosure or harmful action identified.
Mechanism
The SDK uses configured LimAI credentials for API requests. The CLI's update command checks the npm registry and installs this package.
AI rationale
The reviewed source matches a LimAI API SDK and CLI. Credential use is directed to the configured API, and the runtime package installation is limited to the explicit update command; no malicious behavior was identified.
Evidence
~/.limai/config.json
Network endpoints2
app.limai.ioregistry.npmjs.org
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 exports an SDK and CLI; its prepublishOnly script only builds the package.
- The SDK reads LimAI credentials from LimAI-specific environment variables or its own configuration and sends them as bearer authentication for API requests.
- The npm install command is part of the CLI's explicit update command, which updates this package from the npm registry.
- The CLI login flow uses LimAI's app host, and the SDK sends credentials to the configured LimAI API URL.
Evidence against
- The package includes process execution, network access, and file writes, but the reviewed execution is tied to Git development-setting discovery, API operations, user-requested login/configuration, and explicit updates.
- No automatic install-time data collection or unrelated credential destination was identified.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
Source & flagged code
7 flaggeddist/index.jsView file
1"use strict";var _e=Object.create;var ot=Object.defineProperty;var Ne=Object.getOwnPropertyDescriptor;var Le=Object.getOwnPropertyNames;var Me=Object.getPrototypeOf,Fe=Object.proto...
L2: `)===-1&&p.indexOf("\r")===-1){r.push(p);return}r.push(p);let c=r.join("");r.length=0;let m=w(c);m!==""&&r.push(m)}function w(p){let c=0;if(p.indexOf("\r")===-1){let m=p.indexOf(`
High
1"use strict";var _e=Object.create;var ot=Object.defineProperty;var Ne=Object.getOwnPropertyDescriptor;var Le=Object.getOwnPropertyNames;var Me=Object.getPrototypeOf,Fe=Object.proto...
L2: `)===-1&&p.indexOf("\r")===-1){r.push(p);return}r.push(p);let c=r.join("");r.length=0;let m=w(c);m!==""&&r.push(m)}function w(p){let c=0;if(p.indexOf("\r")===-1){let m=p.indexOf(`
High
Command Output Exfiltration
Source combines command execution, command-output handling, and outbound requests; review data flow before blocking.
dist/index.jsView on unpkg · L11Trigger-reachable command-output exfiltration chain: manifest.main -> dist/index.js
L1: "use strict";var _e=Object.create;var ot=Object.defineProperty;var Ne=Object.getOwnPropertyDescriptor;var Le=Object.getOwnPropertyNames;var Me=Object.getPrototypeOf,Fe=Object.proto...
L2: `)===-1&&p.indexOf("\r")===-1){r.push(p);return}r.push(p);let c=r.join("");r.length=0;let m=w(c);m!==""&&r.push(m)}function w(p){let c=0;if(p.indexOf("\r")===-1){let m=p.indexOf(`
Findings
2 Critical5 High3 Medium6 Low
CriticalSame File Env Network Executiondist/cli.js
CriticalTrigger Reachable Dangerous Capabilitydist/cli.js
HighChild Processdist/index.js
HighShelldist/cli.js
HighCommand Output Exfiltrationdist/index.js
HighTrigger Reachable Command Output Exfiltrationdist/index.js
HighRuntime Package Installdist/cli.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
Affected versions and remediation
This report applies to @limai.io/cli@0.4.16.
See all versions of @limai.io/cli for other recorded verdicts.
- Review the evidence and your use of @limai.io/cli@0.4.16 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.