@remcp/runtime@0.2.75
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 source shows no install lifecycle trigger or runtime self-dependency, and the reviewed network and data handling are bounded to local browser control and paired-agent telemetry. The scanner signals are consistent with the package’s advertised local device runtime behavior.
Decision evidence
public snapshot- package.json exposes a CLI and ordinary runtime scripts, with no install lifecycle hook or self-dependency.
- The browser client restricts CDP endpoints to loopback hosts before making requests.
- Telemetry whitelists event fields and sends through the paired runtime agent.
- Document reads resolve paths through the runtime safe-path 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 · L1084package.json exposes a CLI and ordinary runtime scripts, with no install lifecycle hook or self-dependency.
src/extended/desktop-linux.mjsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @remcp/runtime@0.2.75.
See all versions of @remcp/runtime for other recorded verdicts.
- Review the evidence and your use of @remcp/runtime@0.2.75 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.