@wonderwhy-er/desktop-commander@0.2.52
MCP server for terminal operations and file editing
AI Security Review
scanned 23d ago · by lpm-firewall-aiSource confirms explicit-user-command mutation of an AI-agent configuration, which the supplied policy classifies as warning-only capability risk. No block-eligible malicious behavior was established.
Decision evidence
public snapshot- The explicit setup command adds Desktop Commander to Claude's MCP configuration and writes the configuration file.
- Setup is activated by the setup CLI argument or direct execution of the setup script.
- Postinstall runs installation telemetry and ripgrep verification, rather than Claude configuration setup.
- Installation telemetry includes platform and installation context.
- The remote integration forwards requested tools and arguments to the local MCP client.
- No concrete malicious installation chain or credential theft was established.
- Runtime dependencies do not include the package itself.
- The inspected ripgrep resolver locates an existing binary and adjusts its executable permissions.
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.52.
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.52 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.