@limai.io/cli@0.4.8
CLI and SDK for the LimAI data extraction platform
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe flagged subprocess behavior is limited to git metadata discovery and an npm update command invoked by the user. Credential-bearing requests use the LimAI token and configured API URL, with no source evidence of automatic transmission to an unrelated host.
Decision evidence
public snapshot- The manifest has no install hook; its only lifecycle script is prepublishOnly, which runs the build.
- The SDK sends its supplied token as a bearer credential to the configured API base URL.
- The CLI reads its LimAI token and API URL from environment variables, local config, or its monorepo setup.
- The git commands discover the monorepo root and branch to locate local LimAI configuration.
- The CLI update check and npm install run inside the explicitly invoked update command.
- The CLI is described as a client for the LimAI data extraction platform, consistent with its API requests.
- The package entry points are a CLI and SDK; no install-time behavior is declared.
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.8.
See all versions of @limai.io/cli for other recorded verdicts.
- Review the evidence and your use of @limai.io/cli@0.4.8 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.