@cloop/runner@0.3.24
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 4d ago · by lpm-firewall-aiThe automatic connection report includes identifying hostname data, which makes this undisclosed telemetry suspicious under the review rules. The report goes to Cloop’s own service during an explicit connect command, and the inspected source does not show credential or file-content exfiltration.
Decision evidence
public snapshot- Connect reports include the shortened machine hostname along with platform, runtime, harness and setup outcome details.
- Every connect attempt sends the report automatically, including attempts that fail.
- The report is posted to the configured Cloop origin.
- The report is sent to the package's own Cloop service and is limited to connection diagnostics; no credentials or file contents appear in the reported fields.
- The send is triggered by the explicit `cloop connect` command, not package installation or ordinary import.
- The manifest declares no lifecycle scripts.
Source & flagged code
5 flaggedPackage source references child process execution.
dist/chunk-UVB722OW.jsView on unpkg · L15Connect reports include the shortened machine hostname along with platform, runtime, harness and setup outcome details.
dist/chunk-UVB722OW.jsView on unpkg · L51Findings
Affected versions and remediation
This report applies to @cloop/runner@0.3.24.
See all versions of @cloop/runner for other recorded verdicts.
- Review the evidence and your use of @cloop/runner@0.3.24 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.