registry / @limai.io/cli / 0.4.7
@limai.io/cli@0.4.7
CLI and SDK for the LimAI data extraction platform
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe flagged command and network behavior matches the package's documented CLI and SDK purpose: fixed Git metadata queries, LimAI API requests using LimAI credentials, and an explicitly invoked update command. The manifest has no install hook that would run those actions automatically.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
API requests occur when users invoke CLI or SDK operations; updating requires invoking the update command.
Impact
No unrelated credential collection, command-output exfiltration, or install-time contact was identified.
Mechanism
The package sends its configured LimAI token to the configured API and uses fixed git commands to inspect workspace metadata.
AI rationale
The flagged command and network behavior matches the package's documented CLI and SDK purpose: fixed Git metadata queries, LimAI API requests using LimAI credentials, and an explicitly invoked update command. The manifest has no install hook that would run those actions automatically.
Network endpoints4
app.limai.ioregistry.npmjs.org${workspace-prefix}tables.localhost${workspace-prefix}ws.localhost
Decision evidence
public snapshotAI called this Clean at 95.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The only lifecycle script is prepublishOnly, which runs the package build; there is no install hook.
- The SDK reads LimAI-specific token and API settings from its config, environment variables, or workspace context.
- The HTTP client sends the configured token as a bearer token with API requests.
- Shell execution is limited to fixed git rev-parse queries for workspace and branch metadata.
- The npm install command belongs to the CLI's explicit update command.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStringsMinifiedUrlStrings
NoLicense
Source & flagged code
6 flaggeddist/index.jsView file
1"use strict";var _e=Object.create;var ot=Object.defineProperty;var Le=Object.getOwnPropertyDescriptor;var Ne=Object.getOwnPropertyNames;var Me=Object.getPrototypeOf,Fe=Object.proto...
L2: `)===-1&&l.indexOf("\r")===-1){i.push(l);return}i.push(l);let o=i.join("");i.length=0;let d=m(o);d!==""&&i.push(d)}function m(l){let o=0;if(l.indexOf("\r")===-1){let d=l.indexOf(`
High
1"use strict";var _e=Object.create;var ot=Object.defineProperty;var Le=Object.getOwnPropertyDescriptor;var Ne=Object.getOwnPropertyNames;var Me=Object.getPrototypeOf,Fe=Object.proto...
L2: `)===-1&&l.indexOf("\r")===-1){i.push(l);return}i.push(l);let o=i.join("");i.length=0;let d=m(o);d!==""&&i.push(d)}function m(l){let o=0;if(l.indexOf("\r")===-1){let d=l.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 Le=Object.getOwnPropertyDescriptor;var Ne=Object.getOwnPropertyNames;var Me=Object.getPrototypeOf,Fe=Object.proto...
L2: `)===-1&&l.indexOf("\r")===-1){i.push(l);return}i.push(l);let o=i.join("");i.length=0;let d=m(o);d!==""&&i.push(d)}function m(l){let o=0;if(l.indexOf("\r")===-1){let d=l.indexOf(`
Findings
2 Critical4 High3 Medium6 Low
CriticalSame File Env Network Executiondist/cli.js
CriticalTrigger Reachable Dangerous Capabilitydist/cli.js
HighChild Processdist/index.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
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to @limai.io/cli@0.4.7.
See all versions of @limai.io/cli for other recorded verdicts.
- Review the evidence and your use of @limai.io/cli@0.4.7 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.