nansen-cli@1.42.0
AI-agent CLI for Nansen API analytics, DEX swaps, and cross-chain trading
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe lifecycle behavior is transparent and scoped to a first-party skill, with no concrete exfiltration or payload chain found. It nevertheless installs an agent extension from postinstall, so it warrants a warning rather than publication blocking.
Decision evidence
public snapshot- The install lifecycle runs a postinstall script.
- On an interactive global install, an empty answer accepts installation of an AI coding skill.
- The installer invokes npx to add the skill from the package's repository identifier.
- Local installs and non-interactive environments do not install the skill.
- The postinstall script prompts before the agent-skill action and uses argument-based spawning without a shell.
- No self-dependency, obfuscated payload, credential exfiltration, or broad project mutation was found in the inspected lifecycle code.
Source & flagged code
10 flaggedPackage defines install-time lifecycle scripts.
package.jsonView on unpkgA bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
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.42.0.
See all versions of nansen-cli for other recorded verdicts.
- Review the evidence and your use of nansen-cli@1.42.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.