@limai.io/cli@0.4.4
CLI and SDK for the LimAI data extraction platform
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe manifest identifies this as LimAI's CLI and SDK, and the inspected requests send LimAI authentication to the configured API URL. The scanner's process execution lead resolves to Git metadata checks; I found no install-time attack or unrelated exfiltration behavior.
Decision evidence
public snapshot- The manifest describes a LimAI data extraction CLI and SDK, with `dist/index.js` as its library entry point and `dist/cli.js` as its command.
- The HTTP client builds requests from the configured API URL and sends the LimAI bearer token; `VERCEL_BYPASS` is included as a Vercel protection header for those requests.
- The library's Git commands read repository metadata to detect a LimAI monorepo and derive local development URLs.
- The client forwards `VERCEL_BYPASS` with API requests, so that value reaches whichever API URL the user configures.
- The CLI and library use network requests and read configuration or environment variables during ordinary use.
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.4.
See all versions of @limai.io/cli for other recorded verdicts.
- Review the evidence and your use of @limai.io/cli@0.4.4 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.