@limai.io/cli@0.4.6
CLI and SDK for the LimAI data extraction platform
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe flagged execution and network behavior is consistent with development-checkout discovery, LimAI API operations, and a user-invoked CLI updater. The manifest has no install hook, and the inspected credential flow uses the configured API URL.
Decision evidence
public snapshot- The manifest describes a LimAI data extraction CLI and SDK, with `dist/index.js` as the library entry point and `dist/cli.js` as the command-line entry point.
- The only lifecycle script is `prepublishOnly: npm run build`; there is no install, preinstall, or postinstall hook.
- The library’s configuration code reads LimAI credentials and settings from the environment, `~/.limai/config.json`, or a LimAI monorepo checkout.
- The HTTP client sends the configured token as a bearer credential in requests to its configured API URL.
- The CLI’s npm install execution is inside the explicitly invoked `update` command.
- The package contains network, filesystem, and child-process capabilities, but the inspected paths tie them to API operations, configuration, development-checkout discovery, or the explicit updater.
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.6.
See all versions of @limai.io/cli for other recorded verdicts.
- Review the evidence and your use of @limai.io/cli@0.4.6 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.