@remcp/runtime@0.2.180
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-aiThe scanner flags resolve to the declared local runtime, its D-Bus screenshot support, and bounded telemetry through the paired MCP agent. Source inspection found no concrete attack behavior or install-time execution.
Decision evidence
public snapshot- package.json points to the runtime CLI and declares only start, check, and test scripts, with no install lifecycle hook.
- Telemetry is gated by the runtime setting and limits events to tool names, timings, outcomes, and coarse error classes sent through the paired ReMCP agent.
- The runtime forwards telemetry as an MCP notification, and its selected server transport uses standard input and output.
- The screenshot tool uses local capture helpers and the desktop screenshot portal; its D-Bus dependency matches that behavior.
- The file-write tool takes a path and content from the tool request and resolves the path through the runtime’s safety checks.
- The inspected runtime dependencies identify themselves as a D-Bus library and an MCP server SDK.
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.180.
See all versions of @remcp/runtime for other recorded verdicts.
- Review the evidence and your use of @remcp/runtime@0.2.180 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.