@mushi-mushi/cli@0.35.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 3d ago · by lpm-firewall-aiThe flagged credential flows use the configured Mushi service endpoint, and the reviewed wizard report contains generic setup-test data. The manifest has no install lifecycle hook, and report sending is prompted unless explicitly enabled.
Decision evidence
public snapshot- The manifest lists only build, lint, test, and typecheck scripts; it has no install lifecycle hook.
- The init flow resolves its API endpoint from a command option, MUSHI_API_ENDPOINT, or saved config before acquiring and verifying credentials.
- Wizard funnel events go to that resolved endpoint, carry event metadata, and can be disabled with MUSHI_NO_TELEMETRY.
- The setup wizard asks before sending its generic test report unless the user explicitly sets sendTestReport or uses --yes.
Source & flagged code
10 flaggedPackage source references child process execution.
dist/chunk-WFZTXEP3.jsView on unpkg · L59Source appears to send environment or credential material to an external endpoint.
dist/index.jsView on unpkg · L109Findings
Affected versions and remediation
This report applies to @mushi-mushi/cli@0.35.5.
See all versions of @mushi-mushi/cli for other recorded verdicts.
- Review the evidence and your use of @mushi-mushi/cli@0.35.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.