@mushi-mushi/cli@0.30.1
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 22d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the inspected credential transfers go to the resolved Mushi API endpoint as part of setup. Test-report sending and wizard-triggered MCP wiring have user-facing guards; no concrete attack behavior was found.
Decision evidence
public snapshot- package.json lists build, lint, test, and typecheck scripts; it declares no npm lifecycle hook.
- The indicated index.js and init.js code only checks whether MCP configuration files exist.
- The setup flow obtains an SDK key and sends it with the project ID to its resolved Mushi API endpoint.
- The test-report send is prompted by default; it proceeds without that prompt only with an explicit send option or --yes.
- Cursor MCP configuration is written during connection setup; the setup wizard asks before launching that connection, with the prompt defaulting to no.
- The inspected child-process calls retrieve the Windows user for file ACL tightening or open a URL without a shell.
Source & flagged code
8 flaggedPackage source references child process execution.
dist/chunk-BES6PACT.jsView on unpkg · L54Source appears to send environment or credential material to an external endpoint.
dist/index.jsView on unpkg · L82Findings
Affected versions and remediation
This report applies to @mushi-mushi/cli@0.30.1.
See all versions of @mushi-mushi/cli for other recorded verdicts.
- Review the evidence and your use of @mushi-mushi/cli@0.30.1 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.