@wonderwhy-er/desktop-commander@0.3.1
MCP server for terminal operations and file editing
AI Security Review
scanned 22h ago · by lpm-firewall-aiThe manifest activates an install-time tracker that collects identifying project context and sends it to a package-selected collector without installer consent. This is an unconsented installation beacon, so the package should be blocked.
Decision evidence
public snapshot- package.json runs the installation tracker automatically from its postinstall hook.
- The tracker detects installation context, including CI repository and workflow names, and sends it without an installer consent check.
- The telemetry payload includes a client identifier and installation details; the tracker POSTs it to fixed Desktop Commander telemetry endpoints.
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.1.
See all versions of @wonderwhy-er/desktop-commander for other recorded verdicts.
- Avoid installing @wonderwhy-er/desktop-commander@0.3.1. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.