registry / @remcp/runtime / 0.2.157
@remcp/runtime@0.2.157
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-aiSource inspection found no install-time execution or self-dependency chain. Scanner flags correspond to on-demand screenshot support, paired-agent usage telemetry with configurable opt-out, and loopback-restricted browser access.
Static reason
One or more suspicious static signals were detected.
Trigger
A caller invokes the screenshot or browser tools, or the runtime records usage events while running.
Impact
The inspected behavior supports local runtime features and usage metrics; no concrete malicious action was established.
Mechanism
Screenshot capture uses a local desktop portal or OS utility; telemetry travels through the paired-agent MCP connection, and browser CDP endpoints must be loopback-only.
AI rationale
Source inspection found no install-time execution or self-dependency chain. Scanner flags correspond to on-demand screenshot support, paired-agent usage telemetry with configurable opt-out, and loopback-restricted browser access.
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json defines start, check, and test scripts, with no install lifecycle script; its runtime dependencies do not include the package itself.
- The screenshot helper is invoked as a runtime tool and captures through the desktop portal or local OS utilities.
- Telemetry is sent as an MCP notification to the paired ReMCP agent; event details are filtered to a fixed set of fields.
- Telemetry can be disabled through runtime configuration or an environment variable.
- The browser CDP endpoint is restricted to loopback hosts.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkWebSocket
HighEntropyStringsUrlStrings
Source & flagged code
5 flaggedsrc/screenshot-portal.mjsView file
249package = @remcp/runtime; repositoryIdentity = remcp; dependency = @jellybrick/dbus-next
L249: timeoutMs = DEFAULT_TIMEOUT_MS,
L250: loadDbus = () => import('@jellybrick/dbus-next'),
L251: } = {}) {
High
Copied Package Dependency Bridge
Package metadata claims a different repository identity while copied source loads a runtime dependency bridge.
src/screenshot-portal.mjsView on unpkg · L249src/helpers/wayland_eis_sender.pyView file
•path = src/helpers/wayland_eis_sender.py
kind = build_helper
sizeBytes = 15744
magicHex = [redacted]
Medium
Ships Build Helper
Package ships non-JavaScript build or shell helper files.
src/helpers/wayland_eis_sender.pyView on unpkgsrc/tools/files-screenshots.mjs#virtual:normalized:round1View file
Findings
2 High4 Medium6 Low
HighCopied Package Dependency Bridgesrc/screenshot-portal.mjs
HighSemantic Analysis Limitedsrc/tools/files-screenshots.mjs#virtual:normalized:round1
MediumNetwork
MediumEnvironment Vars
MediumShips Build Helpersrc/helpers/wayland_eis_sender.py
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowSuspicious Lifecycle Evidencepackage.json
LowSuspicious Lifecycle Evidencepackage.json
Affected versions and remediation
This report applies to @remcp/runtime@0.2.157.
See all versions of @remcp/runtime for other recorded verdicts.
- Review the evidence and your use of @remcp/runtime@0.2.157 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.