@remcp/runtime@0.2.123
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 manifest has no install lifecycle hook, and inspected tool behavior is consistent with the package’s local runtime purpose. The browser debugging socket check limits targets to the configured loopback endpoint; the scanner hints do not establish malicious behavior.
Decision evidence
public snapshot- package.json defines start, check, and test scripts, with no install lifecycle hook.
- The Linux desktop module launches an application using the supplied app and arguments when its tool is invoked.
- The document module resolves a caller-supplied path before reading the document.
- Browser debugging socket targets must be loopback-only and match the configured endpoint.
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 launches an application using the supplied app and arguments when its tool is invoked.
src/extended/desktop-linux.mjsView on unpkg · L1627Findings
Affected versions and remediation
This report applies to @remcp/runtime@0.2.123.
See all versions of @remcp/runtime for other recorded verdicts.
- Review the evidence and your use of @remcp/runtime@0.2.123 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.