@mushi-mushi/cli@0.27.1
CLI for Mushi Mushi — `mushi init` wizard installs the right SDK for your framework, plus report triage and pipeline health commands
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThe scanner's credential-exfiltration and install-persistence claims are not supported: there are no lifecycle hooks, and authenticated network calls serve the configured Mushi API. The package nevertheless explicitly mutates AI-agent control-surface files, so policy calls for a warning rather than a block.
Decision evidence
public snapshot- Explicit `mushi setup` writes MCP entries for Cursor, Claude, Continue, or Zed.
- `mushi setup --with-rules` writes `.cursorrules` or `.claude/rules/mushi.md`.
- Explicit `mushi connect` writes `.env.local`, `.cursor/mcp.json`, and may amend `.gitignore`.
- Generated MCP entries can invoke `npx -y @mushi-mushi/mcp`.
- package.json has no preinstall, install, postinstall, or prepare lifecycle hook.
- All configuration mutations are reached through named CLI commands, not import/install time.
- API keys are sent as authentication headers only to the configured Mushi API endpoint.
- Source uses secure config permissions and warns/gitignores key-bearing MCP config.
Source & flagged code
5 flaggedSource appears to send environment or credential material to an external endpoint.
dist/index.jsView on unpkg · L65A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
dist/index.jsView on unpkg · L65Findings
Affected versions and remediation
This report applies to @mushi-mushi/cli@0.27.1.
See all versions of @mushi-mushi/cli for other recorded verdicts.
- Review the evidence and your use of @mushi-mushi/cli@0.27.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.