@mushi-mushi/cli@0.30.5
Mushi CLI: SDK setup, MCP wiring, bug triage. The bug mediator for AI-built apps: plain-English diagnosis + a ready fix, in your editor.
AI Security Review
scanned 20d ago · by lpm-firewall-aiThe inspected source supports normal CLI setup and authentication behavior, with no install hook or concrete attack chain. Scanner flags for credentials, subprocesses, and MCP configuration are explained by package-aligned API requests, local profile handling, and project-scoped setup.
Decision evidence
public snapshot- package.json declares a CLI entrypoint and build, lint, test, and typecheck scripts; it declares no install lifecycle hook.
- The agent-related code writes project-level MCP configuration or checks whether standard project MCP files exist.
- The flagged helper uses whoami to obtain the local account name for profile handling.
- Wizard API requests use the configured endpoint, which defaults to Mushi's API; test-report sending is prompted or enabled with --yes.
Source & flagged code
9 flaggedPackage source references child process execution.
dist/chunk-HVNXKTTL.jsView on unpkg · L22Source appears to send environment or credential material to an external endpoint.
dist/index.jsView on unpkg · L84Findings
Affected versions and remediation
This report applies to @mushi-mushi/cli@0.30.5.
See all versions of @mushi-mushi/cli for other recorded verdicts.
- Review the evidence and your use of @mushi-mushi/cli@0.30.5 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.