@remcp/runtime@0.2.203
First-party ReMCP local device runtime: filesystem, terminal, computer-use, browser, diagnostics and document tools over MCP.
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe package’s disclosed, opt-out telemetry sends tool usage through the paired ReMCP agent, but its payload also includes a runtime name that defaults to the machine hostname. That identifying detail makes the runtime telemetry suspicious.
Decision evidence
public snapshot- Runtime telemetry is enabled by default and can be disabled through configuration.
- Telemetry includes a runtime name that defaults to the machine hostname, alongside tool usage data.
- The runtime sends telemetry notifications to the paired ReMCP agent; no destination host is specified in this package.
- The package describes its telemetry and provides an opt-out.
- Telemetry events are limited to tool names, timings, outcomes and coarse error classes; they exclude paths, commands, arguments and tool output.
- The manifest has no lifecycle hooks, and the screenshot portal loads its D-Bus dependency only when capture is requested.
Source & flagged code
5 flaggedPackage metadata claims a different repository identity while copied source loads a runtime dependency bridge.
src/screenshot-portal.mjsView on unpkg · L249Package ships non-JavaScript build or shell helper files.
src/helpers/wayland_eis_sender.pyView on unpkgFindings
Affected versions and remediation
This report applies to @remcp/runtime@0.2.203.
See all versions of @remcp/runtime for other recorded verdicts.
- Review the evidence and your use of @remcp/runtime@0.2.203 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.