@remcp/runtime@0.2.182
First-party ReMCP local device runtime: filesystem, terminal, computer-use, browser, diagnostics and document tools over MCP.
AI Security Review
scanned 10d ago · by lpm-firewall-aiThe manifest has no install hook, and the inspected runtime and dependency paths match local MCP, file, and desktop functions. Static signals such as shell and network APIs did not establish malicious behavior in these paths.
Decision evidence
public snapshot- The package manifest has no install lifecycle hook; it declares start, check, and test scripts and the two reviewed runtime dependencies.
- The desktop capture code uses the session D-Bus desktop portal, and the inspected D-Bus dependency exposes a session-bus client.
- The MCP server dependency is used with stdio transport, which reads process stdin and writes process stdout.
- Screenshot capture is exposed as a tool taking caller arguments; the portal result must be a local file URI before it is copied to the destination.
- File writes use caller-supplied path and content through the runtime safe-path resolver.
- The inspected SDK router filters subscribed events before forwarding notifications.
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.182.
See all versions of @remcp/runtime for other recorded verdicts.
- Review the evidence and your use of @remcp/runtime@0.2.182 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.