nansen-cli@1.46.0
AI-agent CLI for Nansen API analytics, DEX swaps, and cross-chain trading
AI Security Review
scanned 1mo ago · by lpm-firewall-aiSource inspection supports a warning for conditional credential forwarding to an unrestricted custom HTTPS endpoint, not a finding of malware. Agent configuration changes and first-party skill onboarding are guarded or explicitly invoked and do not establish block-eligible install abuse.
Decision evidence
public snapshot- Authentication resolves the Nansen API key from local configuration or NANSEN_API_KEY.
- The active MCP verify command accepts a custom URL and enables saved-key forwarding through --send-api-key.
- Custom HTTPS destinations have no service allowlist; saved-key forwarding is withheld unless explicitly authorized.
- The authenticated verification call sends the resolved key in the NANSEN-API-KEY header to the selected URL.
- Explicit MCP install commands merge the Nansen server into agent configuration and back up existing files.
- Global interactive postinstall onboarding offers installation of the first-party Nansen skill through a declineable prompt.
- No covert credential theft or malicious payload execution was identified.
- Verification rejects public plain HTTP destinations and refuses redirects.
- Local and noninteractive npm installations skip skill installation; MCP configuration changes require explicit CLI commands.
- The update checker fetches registry version metadata and caches it rather than executing downloaded code.
Source & flagged code
8 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@1.46.0.
See all versions of nansen-cli for other recorded verdicts.
- Review the evidence and your use of nansen-cli@1.46.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.