@remcp/runtime@0.2.137
First-party ReMCP local device runtime: filesystem, terminal, computer-use, browser, diagnostics and document tools over MCP.
AI Security Review
scanned 27d ago · by lpm-firewall-aiThe inspected source supports a first-party local device runtime, with no install-time execution or concrete attack behavior identified. The scanner's dependency-bridge and helper-file signals do not establish malicious behavior in the inspected code.
Decision evidence
public snapshot- package.json defines a command-line entrypoint and ordinary start, check, and test scripts, with no install lifecycle hook.
- The Linux desktop module loads its declared D-Bus dependency only in a Wayland-specific display inventory path.
- Document reads resolve the requested path through the runtime's safe-path helper and dispatch by supported document type.
- The runtime instructions say to perform write, click, launch, or command side effects only when the user asked for them.
- Telemetry whitelists event fields and routes them only through the paired ReMCP agent.
Source & flagged code
5 flaggedPackage metadata claims a different repository identity while copied source loads a runtime dependency bridge.
src/extended/desktop-linux.mjsView on unpkg · L1368The Linux desktop module loads its declared D-Bus dependency only in a Wayland-specific display inventory path.
src/extended/desktop-linux.mjsView on unpkg · L1367Findings
Affected versions and remediation
This report applies to @remcp/runtime@0.2.137.
See all versions of @remcp/runtime for other recorded verdicts.
- Review the evidence and your use of @remcp/runtime@0.2.137 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.