@limai.io/cli@0.4.11
CLI and SDK for the LimAI data extraction platform
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe flagged subprocess is used for local Git metadata discovery, and the npm install flow is reachable only through the explicit update command. Token use is part of authenticated requests to the configured LimAI API.
Decision evidence
public snapshot- The manifest exposes a JavaScript SDK and CLI; its only lifecycle hook is prepublishOnly, which runs the build.
- The SDK uses its configured API URL and sends its configured LimAI token as a bearer credential for API requests.
- The Git subprocess uses fixed rev-parse commands to inspect local repository metadata and proceeds only for a repository containing packages/cli.
- The npm registry check and global install are implemented inside the explicitly invoked limai update command.
- The package reads environment variables and local LimAI configuration for credentials and API settings.
- The CLI contains child-process execution, network access, and an npm install operation, but the inspected flows are tied to local repository detection, API use, or the explicit update command.
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.11.
See all versions of @limai.io/cli for other recorded verdicts.
- Review the evidence and your use of @limai.io/cli@0.4.11 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.