@langchain/langgraph-cli@1.5.7
The official command-line interface for LangGraph.js, providing tools to create, develop, and deploy LangGraph.js applications.
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe deploy credential finding is not supported: the key is used for the LangSmith backend, and the saved value is the deployment name. However, CLI commands send runtime telemetry by default, including the OS release, without disclosure in the reviewed source, so this warrants a warning.
Decision evidence
public snapshot- CLI command analytics posts events to a fixed Supabase endpoint.
- Events include OS release, runtime and CLI versions, command name, and selected command options.
- Analytics runs in a command’s preAction hook and is flushed when the CLI exits.
- An opt-out exists through LANGGRAPH_CLI_NO_ANALYTICS=1, but the reviewed source does not disclose the telemetry.
- The deploy command prompts for a LangSmith API key only when one is not already configured.
- The deployment client defaults to api.host.langchain.com; the host URL is also a command option.
- The deploy path persists the deployment name, not the API key.
Source & flagged code
6 flaggedManifest-reachable source sends a prompted API credential to a fixed unofficial gateway and persists the redirection.
dist/cli/deploy.mjsView on unpkgA bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
dist/cli/deploy.mjsView on unpkgFindings
Affected versions and remediation
This report applies to @langchain/langgraph-cli@1.5.7.
See all versions of @langchain/langgraph-cli for other recorded verdicts.
- Review the evidence and your use of @langchain/langgraph-cli@1.5.7 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.