@remcp/runtime@0.2.161
First-party ReMCP local device runtime: filesystem, terminal, computer-use, browser, diagnostics and document tools over MCP.
AI Security Review
scanned 18d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the flagged screenshot code is invoked at runtime for local capture. Inspected telemetry is limited to whitelisted usage details and sent through the paired runtime agent, so the static signals do not establish an attack.
Decision evidence
public snapshot- package.json defines start, check, and test scripts but no install lifecycle hook.
- The screenshot portal is loaded on demand and uses the declared D-Bus dependency.
- Screenshot capture is exposed as a runtime tool and runs when invoked.
- Telemetry sanitizes event details to whitelisted fields and sends them through the runtime server notification.
- Configuration allows telemetry to be disabled; source limits reported data to tool names, timings, and outcomes.
- Telemetry is enabled by default, but inspected source limits its fields and routes it through the paired runtime agent.
Source & flagged code
5 flaggedPackage metadata claims a different repository identity while copied source loads a runtime dependency bridge.
src/screenshot-portal.mjsView on unpkg · L249The screenshot portal is loaded on demand and uses the declared D-Bus dependency.
src/screenshot-portal.mjsView on unpkg · L248Findings
Affected versions and remediation
This report applies to @remcp/runtime@0.2.161.
See all versions of @remcp/runtime for other recorded verdicts.
- Review the evidence and your use of @remcp/runtime@0.2.161 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.