@cloop/runner@0.2.10
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 inspected process execution is tied to explicit runner operations. The runtime npx path re-invokes this package at its current version when setting up a service; it does not establish a malicious install chain.
Decision evidence
public snapshot- package.json has no preinstall, install, or postinstall hook; its listed scripts are build, typecheck, dev, lint, format, and test.
- The local runner starts the selected harness with its configured arguments in the chosen repository.
- Disconnect revokes the runner device and removes the installed service and local files.
- The T3 helper limits the child environment to HOME, USER, and PATH.
- The takeover command opens the selected run in the configured harness after reporting the action.
- Service setup is explicit through the installService path; npx-based launch uses this package at the same version.
Source & flagged code
5 flaggedPackage source references child process execution.
dist/chunk-DHUZXAK2.jsView on unpkg · L23Package source invokes a package manager install command at runtime.
dist/disconnect-HGQW7TVG.jsView on unpkg · L31Findings
Affected versions and remediation
This report applies to @cloop/runner@0.2.10.
See all versions of @cloop/runner for other recorded verdicts.
- Review the evidence and your use of @cloop/runner@0.2.10 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.