@limai.io/cli@0.4.12
CLI and SDK for the LimAI data extraction platform
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe inspected entry points fit the stated LimAI CLI and SDK purpose: the API client uses configured LimAI credentials, while the flagged update installation is triggered by an explicit command. No evidence showed automatic unrelated credential collection or command-output exfiltration.
Decision evidence
public snapshot- The manifest identifies the package as a LimAI CLI and SDK, with a library entry point and a separate CLI binary.
- The HTTP client sends its configured token in an Authorization header to the configured API URL.
- The CLI update check and npm install are inside the explicit `update` command action.
- No attack behavior was identified in the inspected entry points; the flagged process execution detects LimAI monorepo context using fixed Git commands.
- The only declared lifecycle hook is `prepublishOnly`, which runs the package build rather than install-time code.
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.12.
See all versions of @limai.io/cli for other recorded verdicts.
- Review the evidence and your use of @limai.io/cli@0.4.12 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.