@memnexus-ai/mx-agent-cli@0.1.300
CLI for creating and managing AI agent teams
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe startup report includes identifying machine and project fields and captured output, then ships to the configured observability API when a token is present. This appears tied to the package's dashboard feature, but runtime telemetry carrying identifying details warrants a warning.
Decision evidence
public snapshot- Startup reports include project, team, worktree, CLI version, and machine name.
- The start command captures output and schedules best-effort report shipping.
- With an observability token configured, reports are POSTed to the observability API.
- Shipping is part of the CLI's stated observability and dashboard behavior, and requires an observability token.
- The package exposes the behavior through an explicit CLI command; the flagged agent-configuration writes occur in the explicit project setup command.
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.300.
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.300 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.