@remcp/runtime@0.2.101
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-aiSource inspection found no install-time attack behavior or concrete malicious chain. The scanner signals are consistent with the package’s local device runtime features and do not establish malicious behavior.
Decision evidence
public snapshot- package.json defines no install lifecycle hook; its scripts are for starting, checking, and testing.
- The Linux desktop module dynamically imports the declared D-Bus dependency for desktop integration.
- Document archive handling rejects absolute and parent-traversal paths.
- Telemetry limits event fields and sends buffered data through an injected sink.
Source & flagged code
5 flaggedPackage metadata claims a different repository identity while copied source loads a runtime dependency bridge.
src/extended/desktop-linux.mjsView on unpkg · L1205The Linux desktop module dynamically imports the declared D-Bus dependency for desktop integration.
src/extended/desktop-linux.mjsView on unpkg · L1205Findings
Affected versions and remediation
This report applies to @remcp/runtime@0.2.101.
See all versions of @remcp/runtime for other recorded verdicts.
- Review the evidence and your use of @remcp/runtime@0.2.101 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.