registry / @remcp/runtime / 0.2.167
@remcp/runtime@0.2.167
First-party ReMCP local device runtime: filesystem, terminal, computer-use, browser, diagnostics and document tools over MCP.
AI Security Review
scanned 17d ago · by lpm-firewall-aiSource inspection found no lifecycle hook or concrete attack behavior. The flagged screenshot and telemetry code is consistent with the package’s local runtime functionality and paired-agent operation.
Static reason
One or more suspicious static signals were detected.
Trigger
The runtime starts when invoked; screenshot capture runs when its tool is called.
Impact
Screenshots are returned to the caller, and telemetry contains limited usage and runtime information; no malicious transfer or mutation was established.
Mechanism
Screenshot capture uses local backends or the desktop portal. Telemetry sanitizes event fields before forwarding them through an MCP notification.
AI rationale
Source inspection found no lifecycle hook or concrete attack behavior. The flagged screenshot and telemetry code is consistent with the package’s local runtime functionality and paired-agent operation.
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 declares start, check, and test scripts; no install lifecycle hook is declared.
- The runtime starts an MCP server, and telemetry is sent through its MCP notification channel.
- The screenshot tool uses local capture backends and is exposed as a runtime tool; its Wayland path calls the desktop screenshot portal and accepts a local file URI.
- Telemetry events are restricted to a whitelist of coarse fields and are sent with runtime metadata through the paired 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/index.mjs
Affected versions and remediation
This report applies to @remcp/runtime@0.2.167.
See all versions of @remcp/runtime for other recorded verdicts.
- Review the evidence and your use of @remcp/runtime@0.2.167 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.