@mushi-mushi/cli@0.34.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 8d ago · by lpm-firewall-aiSource inspection shows credential handling and reporting tied to the resolved API endpoint, with report transmission gated by user choice. The findings do not establish an unrelated credential recipient or a concrete attack.
Decision evidence
public snapshot- The manifest exposes a CLI entrypoint and the reviewed dependencies are prompt, command-parsing, and keyring packages.
- Setup selects the endpoint from the command option, environment, or saved configuration, then acquires and verifies credentials against that endpoint.
- Test reports send project credentials to the resolved API endpoint only after an explicit send option, --yes, or prompt confirmation; setup can also disable sending.
- The CLI’s default API endpoint is its service endpoint, and the CLI labels endpoint overrides as intended for self-hosting.
- No inspected source established credential forwarding to an unrelated recipient or an unconsented installation-time attack.
Source & flagged code
8 flaggedPackage source references child process execution.
dist/chunk-67WU4UYB.jsView on unpkg · L53Source appears to send environment or credential material to an external endpoint.
dist/index.jsView on unpkg · L87Findings
Affected versions and remediation
This report applies to @mushi-mushi/cli@0.34.1.
See all versions of @mushi-mushi/cli for other recorded verdicts.
- Review the evidence and your use of @mushi-mushi/cli@0.34.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.