@mushi-mushi/cli@0.30.2
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 27d ago · by lpm-firewall-aiSource confirms conditional forwarding of the saved API key to an unrestricted operator-configured HTTPS endpoint. The endpoint is explicitly configurable for self-hosted use, so this is a credential exposure risk rather than evidence of covert theft or malicious intent.
Decision evidence
public snapshot- The CLI accepts an API endpoint from environment configuration alongside the API key and project ID.
- Requests send the configured endpoint the API key in authentication headers.
- The endpoint check permits any HTTPS host, without restricting it to the Mushi service.
- Agent integration setup is exposed as an explicit CLI command; the inspected target locations do not show an install hook.
- The package has no preinstall, install, or postinstall lifecycle hook.
- Endpoint selection is configurable for self-hosted use, and the package also provides a default service endpoint.
- The inspected agent target locations concern setup or detection; they do not establish an automatic foreign agent configuration mutation.
Source & flagged code
8 flaggedPackage source references child process execution.
dist/chunk-AJ6TRLJX.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.2.
See all versions of @mushi-mushi/cli for other recorded verdicts.
- Review the evidence and your use of @mushi-mushi/cli@0.30.2 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.