@remcp/runtime@0.2.150
First-party ReMCP local device runtime: filesystem, terminal, computer-use, browser, diagnostics and document tools over MCP.
AI Security Review
scanned 20d ago · by lpm-firewall-aiSource inspection found no install hook or unrelated credential transfer. The flagged DBus bridge is limited to optional Wayland display inventory, document reads are bounded, and telemetry uses a paired-agent path with restricted event fields.
Decision evidence
public snapshot- package.json defines ordinary start, check, and test scripts and no install lifecycle hook; the runtime dependencies are an MCP server and DBus library.
- The Linux desktop module loads DBus only in a Wayland display inventory function and returns if the optional import is unavailable.
- Document reads use bounded size limits and flags that avoid following symbolic links.
- The runtime describes local tools for a computer paired with ReMCP and directs side effects to occur only when the user asked for them.
- Telemetry fields are whitelisted to tool names, timings, outcomes, and coarse error classes, and are sent through the paired ReMCP agent.
- The entrypoint starts the MCP server and routes telemetry through its notification mechanism.
Source & flagged code
5 flaggedPackage metadata claims a different repository identity while copied source loads a runtime dependency bridge.
src/extended/desktop-linux.mjsView on unpkg · L1378The Linux desktop module loads DBus only in a Wayland display inventory function and returns if the optional import is unavailable.
src/extended/desktop-linux.mjsView on unpkg · L1376Findings
Affected versions and remediation
This report applies to @remcp/runtime@0.2.150.
See all versions of @remcp/runtime for other recorded verdicts.
- Review the evidence and your use of @remcp/runtime@0.2.150 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.