@mushi-mushi/cli@0.30.6
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 19d ago · by lpm-firewall-aiThe package has no install lifecycle hook, and the inspected credential requests use the endpoint resolved for Mushi setup. MCP configuration changes are part of user-invoked connect setup or a separate wizard prompt, so the scanner hints do not establish malicious behavior.
Decision evidence
public snapshot- package.json defines a CLI entry point and only build, lint, test, and typecheck scripts; it has no install lifecycle hook.
- The setup wizard runs from a CLI command and resolves its API endpoint from an explicit option, environment variable, saved configuration, or the package’s Mushi Cloud default.
- The wizard sends its setup event with the SDK key to that resolved endpoint; the optional test report uses the same endpoint and requires confirmation unless the user selects the yes mode.
- Cursor MCP configuration is written to the project’s .cursor/mcp.json during connect setup; the wizard offers this step with a separate prompt.
- The cited init and main entrypoint locations check whether MCP configuration files exist; they do not mutate them.
Source & flagged code
8 flaggedPackage source references child process execution.
dist/chunk-YAF2NATT.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.6.
See all versions of @mushi-mushi/cli for other recorded verdicts.
- Review the evidence and your use of @mushi-mushi/cli@0.30.6 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.