@remcp/runtime@0.2.48
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 hook or self-dependency chain, and the flagged behaviors examined align with local runtime functionality. The scanner’s structural hints do not establish an attack.
Decision evidence
public snapshot- package.json defines ordinary start, check, and test scripts, with no install lifecycle hook or self-dependency.
- src/index.mjs starts a local MCP server as the runtime’s CLI behavior.
- src/extended/browser.mjs restricts browser debugging endpoints to loopback hosts.
- src/extended/documents.mjs rejects absolute and traversal paths in archive entries.
- src/helpers/wayland-eis-helper.py uses the desktop portal RemoteDesktop interface for its stated input helper.
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 · L1028Package 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.48.
See all versions of @remcp/runtime for other recorded verdicts.
- Review the evidence and your use of @remcp/runtime@0.2.48 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.