@limai.io/cli@0.4.14
CLI and SDK for the LimAI data extraction platform
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe routed execution and network capabilities fit the advertised LimAI CLI/SDK: requests use its configured API and token, while global installation occurs only within the explicit update command. The manifest has no install hook; its prepublishOnly script only builds the package.
Decision evidence
public snapshot- The manifest identifies a LimAI CLI/SDK, exports dist/index.js, and exposes dist/cli.js as the limai command.
- The only lifecycle hook is prepublishOnly running the package build; there is no install hook.
- The SDK sends its configured LimAI token as a bearer credential in requests built against the configured API URL.
- The npm registry check and global npm install are inside the explicit `limai update` command action.
- The package includes command execution and network APIs, but inspected uses support repository context discovery, API requests, and an explicit update feature.
- The CLI registers commands at startup, but no inspected evidence indicates an automatic install-time or import-time data transfer.
Source & flagged code
6 flaggedSource combines command execution, command-output handling, and outbound requests; review data flow before blocking.
dist/index.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @limai.io/cli@0.4.14.
See all versions of @limai.io/cli for other recorded verdicts.
- Review the evidence and your use of @limai.io/cli@0.4.14 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.