nansen-cli@1.39.0
AI-agent CLI for Nansen API analytics, DEX swaps, and cross-chain trading
AI Security Review
scanned 1mo ago · by lpm-firewall-aiInspected source establishes guarded first-party agent extension setup during postinstall, which the policy classifies as warning-only. The scanner's platform and dynamic-import signals do not independently establish malicious behavior.
Decision evidence
public snapshot- package.json automatically runs scripts/postinstall.js after installation.
- The install hook prompts to install a Nansen coding-agent skill, accepts an empty answer, and invokes npx skills add.
- The hook skips local npm installs and limits onboarding to interactive terminals.
- The platform check in src/doctor.js controls permission diagnostics; it does not establish sandbox evasion.
- src/x402.js dynamically imports the package's own wallet module for payment signing.
- No concrete malicious behavior was established in the inspected source.
- The agent skill setup is first-party and visibly prompted, which excludes the unconsented foreign-control-surface blocking rule.
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.39.0.
See all versions of nansen-cli for other recorded verdicts.
- Review the evidence and your use of nansen-cli@1.39.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.