nansen-cli@2.2.0
AI-agent CLI for Nansen API analytics, DEX swaps, and cross-chain trading
AI Security Review
scanned 27d ago · by lpm-firewall-aiSource inspection found an install hook limited to gated onboarding and an MCP setup command that operates on supported client configuration files only when explicitly invoked. The network and credential-related findings align with CLI API, transfer, and MCP setup functions; no malicious behavior was identified.
Decision evidence
public snapshot- The postinstall hook skips local installs, prints tips without a TTY, and asks before optional skill installation or an account check.
- MCP configuration paths are limited to named client config files; MCP installation runs only through an explicit CLI subcommand and requires an API key.
- Doctor connectivity checks make an unauthenticated GET to the configured API base URL.
- Transfer RPC requests send JSON-RPC calls to the selected URL; this is consistent with the package's blockchain transfer functions.
- The package declares a postinstall hook, which merits inspection, but its observed actions are gated or informational.
Source & flagged code
7 flaggedPackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to nansen-cli@2.2.0.
See all versions of nansen-cli for other recorded verdicts.
- Review the evidence and your use of nansen-cli@2.2.0 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.