@remcp/runtime@0.2.155
First-party ReMCP local device runtime: filesystem, terminal, computer-use, browser, diagnostics and document tools over MCP.
AI Security Review
scanned 19d ago · by lpm-firewall-aiThe manifest and inspected entrypoint show a runtime package without an install hook. Its default-on usage metrics are opt-out, filtered to bounded event fields, and sent through the paired-agent channel; no concrete unrelated data transfer or hidden install-time behavior was identified.
Decision evidence
public snapshot- The manifest exposes src/index.mjs as the CLI and lists no install lifecycle hook; its dependencies support MCP and D-Bus functionality.
- The entrypoint starts a stdio MCP server and routes telemetry through an MCP notification.
- Telemetry uses a fixed event-field allowlist, is enabled by default with an opt-out, and travels through the paired-agent channel.
- Screenshot capture is a runtime tool; its portal helper accepts only a local file URI and copies the screenshot locally.
- The browser CDP client defaults to 127.0.0.1.
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.155.
See all versions of @remcp/runtime for other recorded verdicts.
- Review the evidence and your use of @remcp/runtime@0.2.155 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.