@remcp/runtime@0.2.159
First-party ReMCP local device runtime: filesystem, terminal, computer-use, browser, diagnostics and document tools over MCP.
AI Security Review
scanned 18d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the flagged screenshot code performs local capture through a user-invoked runtime tool. Telemetry is limited to whitelisted usage fields sent to the paired agent and can be disabled; the inspected source establishes no concrete attack surface.
Decision evidence
public snapshot- package.json defines start, check, and test scripts but no install lifecycle hook.
- Screenshot capture is exposed as a runtime tool and invokes the local portal or screenshot utility when requested.
- The portal helper uses the declared D-Bus dependency to request a screenshot from the local desktop portal.
- Telemetry events use whitelisted fields and are sent as MCP notifications to the paired agent.
- Telemetry can be disabled through runtime configuration or an environment setting.
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.159.
See all versions of @remcp/runtime for other recorded verdicts.
- Review the evidence and your use of @remcp/runtime@0.2.159 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.