@cloop/runner@0.2.1
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 28d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the inspected process execution is tied to explicit CLI commands for Cloop setup and removal. The scanner’s runtime install signal is not supported by the disconnect source; it contains no npm install invocation.
Decision evidence
public snapshot- package.json defines a CLI entry point and has no install lifecycle hook.
- The install command registers Cloop’s own MCP server with Claude Code when the user invokes it.
- Disconnect stops Cloop services and removes Cloop state after confirmation when required.
Source & flagged code
5 flaggedPackage source references child process execution.
dist/install-HTDTCELB.jsView on unpkg · L6The install command registers Cloop’s own MCP server with Claude Code when the user invokes it.
dist/install-HTDTCELB.jsView on unpkg · L24Findings
Affected versions and remediation
This report applies to @cloop/runner@0.2.1.
See all versions of @cloop/runner for other recorded verdicts.
- Review the evidence and your use of @cloop/runner@0.2.1 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.