@remcp/runtime@0.2.171
First-party ReMCP local device runtime: filesystem, terminal, computer-use, browser, diagnostics and document tools over MCP.
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the inspected runtime behavior matches its declared local-device MCP purpose. Static hints about process helpers and a runtime dependency bridge did not establish an attack.
Decision evidence
public snapshot- package.json declares the stdio runtime entrypoint and has no install lifecycle hook; its dependencies support D-Bus screenshots and MCP serving.
- src/index.mjs starts the local MCP server. File writing uses caller-provided paths resolved through the runtime safety layer, and screenshots use the declared D-Bus dependency.
- The reviewed dependency entrypoints implement D-Bus and MCP functionality; no concrete malicious behavior was identified in the inspected source.
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.171.
See all versions of @remcp/runtime for other recorded verdicts.
- Review the evidence and your use of @remcp/runtime@0.2.171 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.