@mushi-mushi/cli@0.31.0
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 15d ago · by lpm-firewall-aiSource review did not confirm malicious behavior: credential sends use the configured Mushi API endpoint, and agent configuration changes occur through setup flows. Scanner hints about credential redirection and exfiltration were not supported by the inspected source.
Decision evidence
public snapshot- The manifest defines a CLI entrypoint and no install lifecycle hook; its scripts are build, lint, test, and typecheck.
- The CLI’s default API endpoint is Mushi’s configured service, and endpoint selection accepts an explicit value or MUSHI_API_ENDPOINT.
- Wizard requests send the SDK key to that endpoint; the wizard telemetry call is skipped when MUSHI_NO_TELEMETRY is set.
- MCP configuration writes occur during explicit setup flows and use project-level Cursor configuration; the inspected agent integration locations do not establish unconsented lifecycle mutation.
- The inspected runtime dependencies expose prompt, command-line, and keyring functionality, and their manifests declare no install scripts.
Source & flagged code
8 flaggedSource appears to send environment or credential material to an external endpoint.
dist/index.jsView on unpkg · L84A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
dist/index.jsView on unpkg · L84Findings
Affected versions and remediation
This report applies to @mushi-mushi/cli@0.31.0.
See all versions of @mushi-mushi/cli for other recorded verdicts.
- Review the evidence and your use of @mushi-mushi/cli@0.31.0 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.