@mushi-mushi/cli@0.30.4
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 21d ago · by lpm-firewall-aiThe package has no npm install hook, and the credential sends inspected are directed to the configured Mushi API, whose default is the package's service endpoint. Agent configuration changes occur through CLI setup/connect flows, and the wizard's additional connect step is prompted; no concrete attack behavior was found.
Decision evidence
public snapshot- package.json exposes a CLI and has no npm install lifecycle hook.
- The CLI uses a Mushi API endpoint by default; alternate endpoints come from CLI options, environment settings, or saved configuration.
- The setup flow sends SDK credentials to that endpoint; sending a test report requires confirmation or an explicit noninteractive option.
- Agent configuration checks and writes are part of setup or connect commands; the wizard's follow-on connect action asks before proceeding.
- Inspected child-process calls support package installation or upgrades and local key-permission handling; no malicious execution chain was found.
Source & flagged code
9 flaggedPackage source references child process execution.
dist/chunk-SV6HHYWE.jsView on unpkg · L54Source appears to send environment or credential material to an external endpoint.
dist/index.jsView on unpkg · L84Findings
Affected versions and remediation
This report applies to @mushi-mushi/cli@0.30.4.
See all versions of @mushi-mushi/cli for other recorded verdicts.
- Review the evidence and your use of @mushi-mushi/cli@0.30.4 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.