@memnexus-ai/mx-agent-cli@0.1.243
CLI for creating and managing AI agent teams
AI Security Review
scanned 3mo ago · by lpm-firewall-aiSource inspection confirms explicit user-invoked Claude hook/config mutation, so it warrants a warning under the lifecycle policy. No credential theft, stealth persistence, remote code loading, or unconsented install-time mutation was found.
Decision evidence
public snapshot- dist/commands/start.js invokes config and hook deployment on mx-agent start
- dist/lib/claude.js overwrites .claude/settings.json and managed hooks
- dist/lib/claude.js caches/reconciles hooks under ~/.mx-agent
- dist/agent-config/hooks/*.sh execute as Claude tool hooks
- package.json has no install lifecycle hook
- mutation requires explicit mx-agent start
- network sync is explicit/configured and defaults to localhost
- child processes use argv arrays; no eval or remote payload loader found
Source & flagged code
6 flaggedPackage source references child process execution.
dist/lib/fleet-data.jsView on unpkg · L20Findings
Affected versions and remediation
This report applies to @memnexus-ai/mx-agent-cli@0.1.243.
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.243 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.