registry / @remcp/runtime / 0.2.191
@remcp/runtime@0.2.191
First-party ReMCP local device runtime: filesystem, terminal, computer-use, browser, diagnostics and document tools over MCP.
AI Security Review
scanned 7d ago · by lpm-firewall-aiSource inspection found no install hook, unrelated network recipient, or unrequested account or control-surface action. The scanner flags correspond to the package's declared local runtime capabilities and SDK code, not demonstrated malicious behavior.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Starting the runtime; individual local operations are requested through MCP.
Impact
No package-directed attack impact was established from the inspected source.
Mechanism
The entry point starts an MCP stdio server. Runtime tools perform local file, screenshot, and system operations, while usage events are forwarded through the paired server.
AI rationale
Source inspection found no install hook, unrelated network recipient, or unrequested account or control-surface action. The scanner flags correspond to the package's declared local runtime capabilities and SDK code, not demonstrated malicious behavior.
Decision evidence
public snapshotAI called this Clean at 95.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest defines a CLI entry point, ordinary start/check/test scripts, and runtime dependencies; it has no install lifecycle hook.
- The runtime communicates over MCP stdio. The bundled SDK reads from standard input, writes to standard output, and forwards subscribed protocol notifications.
- Usage events are sent through the paired runtime server; event fields are restricted to tool names, timings, outcomes, and coarse error categories.
- The flagged tools perform local operations: screenshots use the desktop portal or available capture utilities, file writes use a supplied path, and system information reads host statistics.
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
3 High4 Medium5 Low
HighCopied Package Dependency Bridgesrc/screenshot-portal.mjs
HighSemantic Analysis Limitedsrc/tools/files-screenshots.mjs#virtual:normalized:round1
HighPrevious Version Dangerous Deltasrc/tools/system.mjs
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
Affected versions and remediation
This report applies to @remcp/runtime@0.2.191.
See all versions of @remcp/runtime for other recorded verdicts.
- Review the evidence and your use of @remcp/runtime@0.2.191 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.