nansen-cli@2.0.0
AI-agent CLI for Nansen API analytics, DEX swaps, and cross-chain trading
AI Security Review
scanned 1mo ago · by lpm-firewall-aiSource supports a warning for opt-in forwarding of an existing service credential to an unrestricted HTTPS recipient and guarded agent setup. It does not establish malicious behavior warranting a publication block.
Decision evidence
public snapshot- Credential resolution can select an existing API key from saved configuration.
- The active MCP command accepts a custom URL and enables saved-key forwarding through the explicit --send-api-key flag; HTTPS destinations have no service host allowlist.
- After server reachability succeeds, verification sends the selected key in an authenticated POST to that URL; redirects are refused.
- Explicit MCP install commands merge a Nansen server entry into agent configuration and back up existing files.
- Postinstall skill setup requires an affirmative response to a default-no prompt.
- No covert credential export or malicious intent was established.
- Local installs and noninteractive onboarding skip skill installation.
- Doctor platform checks support local diagnostics, and transfer operations use caller-supplied recipients.
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.0.0.
See all versions of nansen-cli for other recorded verdicts.
- Review the evidence and your use of nansen-cli@2.0.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.