@wonderwhy-er/desktop-commander@0.2.48
MCP server for terminal operations and file editing
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe package has automatic installation telemetry that collects more process context than necessary, plus an explicit Claude configuration writer that can select a future registry release. Source inspection found no automatic install-time Claude configuration mutation or self-dependency lifecycle chain.
Decision evidence
public snapshot- The automatic postinstall hook runs installation tracking and makes a network request.
- The tracker reads the parent process command line and can include it in installation telemetry.
- The explicit setup command writes an MCP entry into Claude Desktop configuration and can configure npx to run the package selected by a tag or latest.
- The postinstall hook does not invoke the Claude configuration writer.
- Claude configuration changes occur only through the setup command path.
- No runtime dependency on this package's own name is declared.
Source & flagged code
8 flagged · loading sourceInstall-time lifecycle script matches a deterministic static-gate block pattern.
package.jsonView on unpkgPackage defines install-time lifecycle scripts.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to @wonderwhy-er/desktop-commander@0.2.48.
See all versions of @wonderwhy-er/desktop-commander for other recorded verdicts.
- Review the evidence and your use of @wonderwhy-er/desktop-commander@0.2.48 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.