@remcp/runtime@0.2.192
First-party ReMCP local device runtime: filesystem, terminal, computer-use, browser, diagnostics and document tools over MCP.
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe package has no install lifecycle hooks, and the flagged system capability is an explicitly invoked MCP tool with safeguards for the runtime and its parent agent. Default telemetry is disclosed, limited to usage details, and sent through the paired agent; no malicious behavior was identified.
Decision evidence
public snapshot- package.json has start, check, and test scripts, with no install lifecycle hook.
- Telemetry is announced at runtime startup, can be disabled, is limited to tool usage details, and travels through the paired ReMCP agent.
- Process termination is exposed as an MCP tool that takes a PID; its handler refuses to terminate the runtime or its parent agent.
- Screenshot portal code loads the declared D-Bus dependency when a screenshot is requested.
- Telemetry is enabled by default unless the user disables it.
- The kill_process tool can terminate arbitrary operating-system processes when called.
- The runtime uses filesystem and process capabilities as part of its documented local device tools.
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.192.
See all versions of @remcp/runtime for other recorded verdicts.
- Review the evidence and your use of @remcp/runtime@0.2.192 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.