@remcp/runtime@0.2.183
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 scanner flags resolve to ordinary runtime functionality: the package has no install hook, the dependency bridge loads a D-Bus client for local portal use, and the flagged MCP code filters and forwards protocol events. The inspected source does not establish a concrete attack.
Decision evidence
public snapshot- package.json exposes a CLI and lists runtime dependencies; its scripts contain no install lifecycle hook.
- The inspected dependency manifests contain no install lifecycle hooks, and the MCP server source implements filtered event subscriptions and stdio transport.
- Screenshot capture is invoked through the screenshot tool and uses the local desktop portal or platform screenshot commands.
- The D-Bus dependency exposes session-bus APIs used by the portal screenshot flow.
- File writes use a caller-supplied path resolved through the runtime's safe-path helper.
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.183.
See all versions of @remcp/runtime for other recorded verdicts.
- Review the evidence and your use of @remcp/runtime@0.2.183 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.