@remcp/runtime@0.2.178
First-party ReMCP local device runtime: filesystem, terminal, computer-use, browser, diagnostics and document tools over MCP.
AI Security Review
scanned 11d ago · by lpm-firewall-aiSource inspection found no install hook or concrete malicious behavior. The flagged runtime and dependency code supports local MCP, D-Bus, screenshot, and file operations; telemetry is filtered and routed through the paired agent.
Decision evidence
public snapshot- package.json lists no install lifecycle hooks; its executable starts the runtime entrypoint.
- The runtime starts an MCP server and forwards telemetry through that server’s paired notification channel.
- Telemetry events are restricted to tool names, timings, outcomes, and coarse error details; telemetry can be disabled by configuration.
- Screenshot capture is reached through a screenshot tool call and uses the desktop portal on Wayland; file writes use caller-provided paths and content.
- The inspected dependencies provide D-Bus and MCP server/stdio functionality; the flagged router forwards subscribed server events.
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.178.
See all versions of @remcp/runtime for other recorded verdicts.
- Review the evidence and your use of @remcp/runtime@0.2.178 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.