@remcp/runtime@0.2.102
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 findings are explained by package-aligned runtime functions, and the browser endpoint is loopback-restricted. The manifest shows no install lifecycle hook or runtime self-dependency, so the scanner signals do not establish malicious behavior.
Decision evidence
public snapshot- package.json defines start, check, and test scripts; it has no install lifecycle script, and its runtime dependencies do not include itself.
- The Linux display code conditionally imports the declared D-Bus dependency only in a Wayland session to query display state.
- Document archive entries are checked for absolute paths and traversal before extraction.
- Browser control accepts only HTTP(S) endpoints and restricts them to loopback hosts.
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 · L1205The Linux display code conditionally imports the declared D-Bus dependency only in a Wayland session to query display state.
src/extended/desktop-linux.mjsView on unpkg · L1203Findings
Affected versions and remediation
This report applies to @remcp/runtime@0.2.102.
See all versions of @remcp/runtime for other recorded verdicts.
- Review the evidence and your use of @remcp/runtime@0.2.102 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.