registry / @remcp/runtime / 0.2.160
@remcp/runtime@0.2.160
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 lifecycle hook or concrete attack behavior. The flagged screenshot and telemetry code supports the package’s local runtime functions, so the static signals do not warrant a warning.
Static reason
One or more suspicious static signals were detected.
Trigger
The runtime starts as a CLI, and its device capabilities activate when the paired agent invokes a tool.
Impact
No unauthorized credential transfer, installation-time mutation, or other concrete attack behavior was established.
Mechanism
Screenshot capture uses local desktop interfaces; telemetry is filtered and relayed through the paired agent.
AI rationale
Source inspection found no install lifecycle hook or concrete attack behavior. The flagged screenshot and telemetry code supports the package’s local runtime functions, so the static signals do not warrant a warning.
Decision evidence
public snapshotAI called this Clean at 92.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json exposes a CLI and start, check, and test scripts; it has no install lifecycle hook.
- The screenshot tool uses the desktop portal on Linux Wayland or local screenshot utilities when invoked.
- The portal requests a screenshot through session D-Bus and validates its returned request handle.
- Telemetry filters event fields, can be disabled, and is sent through the paired MCP agent.
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
LowAi Review Evidencesrc/tools/files-screenshots.mjs
Affected versions and remediation
This report applies to @remcp/runtime@0.2.160.
See all versions of @remcp/runtime for other recorded verdicts.
- Review the evidence and your use of @remcp/runtime@0.2.160 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.