registry / @cloop/runner / 0.2.7
@cloop/runner@0.2.7
Make your machine and your agents Cloop runners: device login, the runner daemon, the Cloop MCP server, and Claude Code hooks.
AI Security Review
scanned 16d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the flagged process execution is reachable through explicit product commands. The inspected runtime package invocation runs this package's own background service, while takeover resumes a selected session; the scanner signals do not establish malicious behavior.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The relevant handlers run through explicit install, connect, disconnect, or takeover commands.
Impact
These inspected behaviors do not establish covert credential transfer, unrequested account actions, or harmful mutation of a consumer project.
Mechanism
The package registers its MCP server, manages its own runner service and state, or resumes a selected agent session; the runtime npx path selects this package and version.
AI rationale
The manifest has no install lifecycle hook, and the flagged process execution is reachable through explicit product commands. The inspected runtime package invocation runs this package's own background service, while takeover resumes a selected session; the scanner signals do not establish malicious behavior.
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json defines a CLI binary and ordinary build scripts, with no lifecycle hook.
- dist/index.js loads the install handler only for the explicit install subcommand.
- dist/install-HTDTCELB.js registers the Cloop MCP server with Claude Code and prints optional hook configuration.
- dist/disconnect-VTIIRAIV.js gates box cleanup behind --yes and operates on the runner's service and state files.
- dist/index.js loads takeover only for the explicit takeover subcommand; dist/chunk-DLFNATEZ.js resumes the selected Claude Code or Codex session in its repository.
- dist/chunk-X7MNNKU3.js uses npx to run the same @cloop/runner version for its own background runner service when connecting.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkWebSocket
HighEntropyStringsUrlStrings
Source & flagged code
5 flaggeddist/install-HTDTCELB.jsView file
6// src/commands/install.ts
L7: import { execFileSync } from "child_process";
L8: import { existsSync } from "fs";
High
Child Process
Package source references child process execution.
dist/install-HTDTCELB.jsView on unpkg · L6dist/disconnect-VTIIRAIV.jsView file
30// src/commands/disconnect.ts
L31: import { execFileSync } from "child_process";
L32: import { existsSync, readFileSync, rmSync } from "fs";
L33: import { homedir } from "os";
L34: var DONE_LINE = "This computer is no longer a Cloop runner. To connect it again: npx -y @cloop/runner connect";
L35: function unitOrigin(contents) {
High
Runtime Package Install
Package source invokes a package manager install command at runtime.
dist/disconnect-VTIIRAIV.jsView on unpkg · L30dist/chunk-DLFNATEZ.jsView file
Findings
1 Critical2 High3 Medium6 Low
CriticalPrevious Version Dangerous Deltadist/chunk-DLFNATEZ.js
HighChild Processdist/install-HTDTCELB.js
HighRuntime Package Installdist/disconnect-VTIIRAIV.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowSuspicious Lifecycle Evidencepackage.json
LowAi Review Evidencedist/index.js
Affected versions and remediation
This report applies to @cloop/runner@0.2.7.
See all versions of @cloop/runner for other recorded verdicts.
- Review the evidence and your use of @cloop/runner@0.2.7 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.