@remcp/runtime@0.2.65
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-aiSource inspection found no install lifecycle hook or concrete malicious behavior. The flagged source is consistent with the package’s local device runtime, and its browser endpoint is restricted to loopback.
Decision evidence
public snapshot- package.json defines start, check, and test scripts but no install lifecycle hook; it identifies the package’s first-party repository.
- src/extended/documents.mjs exposes document editing through caller-supplied paths and operations, resolving paths before editing.
- src/extended/browser.mjs limits the browser debugging endpoint to loopback hosts.
- src/extended/desktop-linux.mjs imports local device and Wayland helpers; the inspected source shows no runtime dependency bridge.
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 · L1046Package ships non-JavaScript build or shell helper files.
src/helpers/wayland-eis-helper.pyView on unpkgFindings
Affected versions and remediation
This report applies to @remcp/runtime@0.2.65.
See all versions of @remcp/runtime for other recorded verdicts.
- Review the evidence and your use of @remcp/runtime@0.2.65 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.