@mushi-mushi/cli@0.35.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 7d ago · by lpm-firewall-aiThe flagged credential and secret-scanning behavior resolves to product-aligned Mushi API and diagnostic flows. There is no install hook or source evidence of an unrelated credential recipient, covert collection, or other concrete attack.
Decision evidence
public snapshot- package.json exposes a CLI and lists build, lint, test, and typecheck scripts; it has no install lifecycle hook.
- Login and setup use the configured Mushi endpoint for supplied or saved Mushi credentials, and verify credentials against that service.
- The default API endpoint is the package’s Mushi Cloud endpoint; endpoint overrides support self-hosted deployments.
- Setup sends an opt-out funnel event to that endpoint; its synthetic test report is prompted or explicitly enabled with --yes.
- Radar scans locally by default. Explicit --push sends results and selected build configuration to Mushi; bundle findings carry file, line, and key type rather than matched secret values.
- Inspected dependencies provide prompts, command parsing, and optional OS keychain storage.
Source & flagged code
11 flaggedPackage source references child process execution.
dist/chunk-T36WTCFM.jsView on unpkg · L224Source 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.0.
See all versions of @mushi-mushi/cli for other recorded verdicts.
- Review the evidence and your use of @mushi-mushi/cli@0.35.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.