@memnexus-ai/mx-agent-cli@0.1.297
CLI for creating and managing AI agent teams
AI Security Review
scanned 20d ago · by lpm-firewall-aiThe flagged subprocess, network, and agent-configuration behavior is consistent with the CLI’s project and coordination functions, with user-command triggers and source-level scope checks. I found no concrete attack behavior supporting a block or warning.
Decision evidence
public snapshot- The manifest exposes a CLI and declares build-related lifecycle commands; it has no preinstall, install, or postinstall hook.
- Agent configuration writes are part of project setup and session commands; Codex deployment is scoped to a worktree, and guard proofs require existing hook trust.
- The coordination request reads the MemNexus key only after validating the URL. Its default host is under memnexus.ai, other hosts require a separate global allowlist entry, and redirects are rejected.
- The other flagged helpers perform project-scoped builds, behavioral-file checks, diagnostics, or PR metadata sync; inspected source did not establish malicious behavior.
Source & flagged code
10 flaggedPackage source references child process execution.
dist/lib/fleet-data.jsView on unpkg · L20Package source references shell execution.
dist/lib/vm-health.js#virtual:normalized:round1View on unpkg · L101Findings
Affected versions and remediation
This report applies to @memnexus-ai/mx-agent-cli@0.1.297.
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.297 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.