registry / @remcp/runtime / 0.2.221
@remcp/runtime@0.2.221
First-party ReMCP local device runtime: filesystem, terminal, computer-use, browser, diagnostics and document tools over MCP.
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe reviewed source supports the package's purpose as a local MCP device runtime. It discloses opt-out metrics sent through the user's paired agent, and the flagged screenshot code is tied to a requested tool operation; no attack behavior was identified.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Usage metrics are recorded during runtime activity; screenshot capture requires a screenshot tool request.
Impact
No unrelated collector, credential theft, or unrequested account action was identified. Metrics are opt-out and sent through the user's paired account.
Mechanism
Whitelisted usage events travel through the paired agent, while the screenshot tool captures locally through the desktop portal or platform helper.
AI rationale
The reviewed source supports the package's purpose as a local MCP device runtime. It discloses opt-out metrics sent through the user's paired agent, and the flagged screenshot code is tied to a requested tool operation; no attack behavior was identified.
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package describes itself as a first-party local device runtime for filesystem, terminal, computer-use, browser, diagnostics and document tools.
- Usage metrics are disclosed as opt-out and sent through the authenticated paired agent to the user's ReMCP account.
- The telemetry event schema whitelists tool names, timings, outcomes and coarse error classes, excluding paths, commands, arguments and tool output.
- Telemetry is sent as an MCP notification to the running runtime's paired agent.
- Screenshot capture is implemented as a tool operation and uses the desktop portal when requested on Wayland.
Evidence against
- The telemetry payload also includes runtime and platform metadata, plus the runtime name, which defaults to the hostname; this is not fully enumerated in the short telemetry disclosure.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkWebSocket
Source & flagged code
5 flaggedsrc/screenshot-portal.mjsView file
259package = @remcp/runtime; repositoryIdentity = remcp; dependency = @jellybrick/dbus-next
L259: timeoutMs = DEFAULT_TIMEOUT_MS,
L260: loadDbus = () => import('@jellybrick/dbus-next'),
L261: } = {}) {
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 · L259src/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/files-screenshots.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
LowAi Review Evidencepackage.json
Affected versions and remediation
This report applies to @remcp/runtime@0.2.221.
See all versions of @remcp/runtime for other recorded verdicts.
- Review the evidence and your use of @remcp/runtime@0.2.221 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.