@wonderwhy-er/desktop-commander@0.3.0
MCP server for terminal operations and file editing
AI Security Review
scanned 10d ago · by lpm-firewall-aiThe postinstall tracker automatically sends identifying project or workspace context without a visible consent gate. Its package-branded telemetry recipient and installation-attribution purpose do not establish the unrelated-collector behavior required for a block.
Decision evidence
public snapshot- The postinstall hook runs the installation tracker.
- The tracker collects GitHub repository and workflow names, and can collect a Gitpod workspace identifier.
- The installation event serializes the detected installation details and labels the event as npm lifecycle tracking.
- The tracker sends the installation payload to the package telemetry endpoint, with a fallback endpoint.
- The tracker makes an HTTPS request to the selected endpoint.
- The recipient is a package-branded telemetry service, and the reported information is installation context rather than credentials.
Source & flagged code
13 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 unpkgPackage source references child process execution.
dist/track-installation.jsFindings
Affected versions and remediation
This report applies to @wonderwhy-er/desktop-commander@0.3.0.
See all versions of @wonderwhy-er/desktop-commander for other recorded verdicts.
- Review the evidence and your use of @wonderwhy-er/desktop-commander@0.3.0 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.