registry / @remcp/runtime / 0.2.67
@remcp/runtime@0.2.67
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 inspected source is consistent with the package’s local MCP runtime purpose. Scanner signals map to optional D-Bus integration, guarded loopback browser requests, and paired-agent telemetry; they do not establish malicious behavior.
Static reason
One or more suspicious static signals were detected.
Trigger
Running the remcp-runtime command or invoking its MCP tools.
Impact
No confirmed package-controlled attack surface was established from the inspected behavior.
Mechanism
The entrypoint starts the MCP server; browser requests validate loopback destinations, and telemetry uses a paired-agent sink with whitelisted event fields.
AI rationale
The inspected source is consistent with the package’s local MCP runtime purpose. Scanner signals map to optional D-Bus integration, guarded loopback browser requests, and paired-agent telemetry; they do not establish malicious behavior.
Network endpoints1
127.0.0.1:9222
Decision evidence
public snapshotAI called this Clean at 93.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json describes a first-party local device runtime and shows no preinstall, install, or postinstall hook.
- The Linux desktop module optionally loads the declared D-Bus dependency for session-bus access.
- Document archive handling rejects absolute paths and parent-directory traversal.
- Browser CDP endpoints are restricted to loopback hosts, including when configured through REMCP_CDP_URL.
- Telemetry code whitelists event fields and routes events through the paired ReMCP agent.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkWebSocket
HighEntropyStringsUrlStrings
Source & flagged code
5 flaggedsrc/extended/desktop-linux.mjsView file
1046package = @remcp/runtime; repositoryIdentity = remcp; dependency = @jellybrick/dbus-next
L1046: let dbus;
L1047: try { dbus = await import('@jellybrick/dbus-next'); } catch { return null; }
L1048: const bus = dbus.sessionBus();
High
Copied Package Dependency Bridge
Package metadata claims a different repository identity while copied source loads a runtime dependency bridge.
src/extended/desktop-linux.mjsView on unpkg · L1046src/helpers/wayland-eis-helper.pyView file
•path = src/helpers/wayland-eis-helper.py
kind = build_helper
sizeBytes = 20492
magicHex = [redacted]
Medium
Ships Build Helper
Package ships non-JavaScript build or shell helper files.
src/helpers/wayland-eis-helper.pyView on unpkgsrc/extended/documents.mjs#virtual:normalized:round1
Findings
2 High4 Medium6 Low
HighCopied Package Dependency Bridgesrc/extended/desktop-linux.mjs
HighSemantic Analysis Limitedsrc/extended/documents.mjs#virtual:normalized:round1
MediumNetwork
MediumEnvironment Vars
MediumShips Build Helpersrc/helpers/wayland-eis-helper.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.67.
See all versions of @remcp/runtime for other recorded verdicts.
- Review the evidence and your use of @remcp/runtime@0.2.67 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.