@remcp/runtime@0.2.186
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-aiSource inspection found no install hook or concrete attack behavior. The flagged dependency and runtime operations are consistent with desktop screenshot capture, MCP transport, and configured telemetry sent through the paired runtime connection.
Decision evidence
public snapshot- The manifest declares a CLI entry point and regular start, check, and test scripts; it has no install lifecycle hook.
- On Linux Wayland, the screenshot tool calls the desktop portal helper for a capture; that helper loads the declared D-Bus dependency for the request.
- The file write tool resolves the caller-supplied path before using its content.
- The bundled MCP listener forwards accepted subscription events as notifications, and the server package provides a stdio transport.
- Telemetry is sent as an MCP notification through the runtime server, uses whitelisted event fields, and can be disabled by configuration.
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.186.
See all versions of @remcp/runtime for other recorded verdicts.
- Review the evidence and your use of @remcp/runtime@0.2.186 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.