@memnexus-ai/mx-agent-cli@0.1.301
CLI for creating and managing AI agent teams
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe token deletion is an unrequested side effect of generated container setup, and the script does not check whether the credential is actually stale. The surrounding setup is consistent with the CLI's project-scaffolding purpose, so this warrants a warning rather than a malicious verdict.
Decision evidence
public snapshot- The generated post-create script runs `npm config delete //registry.npmjs.org/:_authToken` without checking whether the token is stale.
- The generated devcontainer invokes that script automatically during container creation.
- The script is generated as part of the explicit `mx-agent new project` setup flow.
- The token removal is described as clearing stale npm auth that can block public package installs.
- Other setup actions install Node.js and Claude Code from their official hosts, consistent with the generated devcontainer's purpose.
Source & flagged code
8 flaggedPackage source references dynamic require/import behavior.
dist/index.jsView on unpkg · L70Source decodes numeric character arrays into a child-process package-runner command and executes it.
Findings
Affected versions and remediation
This report applies to @memnexus-ai/mx-agent-cli@0.1.301.
See all versions of @memnexus-ai/mx-agent-cli for other recorded verdicts.
- Review the evidence and your use of @memnexus-ai/mx-agent-cli@0.1.301 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.