@remcp/runtime@0.2.174
First-party ReMCP local device runtime: filesystem, terminal, computer-use, browser, diagnostics and document tools over MCP.
AI Security Review
scanned 13d ago · by lpm-firewall-aiSource inspection found no install hook or concrete malicious behavior. The flagged dependency code provides DBus and MCP transport functionality, while telemetry is disclosed, scoped to usage events, and delivered through the paired agent.
Decision evidence
public snapshot- package.json defines only start, check, and test scripts; it has no install lifecycle hook.
- Telemetry is disclosed, can be disabled, and records sanitized usage events without file paths, commands, arguments, or tool output.
- Telemetry is sent through the runtime’s paired-agent MCP notification; the inspected MCP event subscription and stdio transport are ordinary protocol handling.
- The screenshot dependency is loaded inside the portal screenshot function, and filesystem tools expose requested read and write operations through MCP.
- Inspected dependency manifests contain build, lint, and test scripts; their source exports DBus and MCP protocol functionality.
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.174.
See all versions of @remcp/runtime for other recorded verdicts.
- Review the evidence and your use of @remcp/runtime@0.2.174 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.