wildcrane-runner@0.6.6
WildCrane's Local Runner — connects this computer to WildCrane and runs its jobs on your local Claude Code, Codex, OpenCode or Cursor.
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe source behavior matches a local task runner: it connects to WildCrane, updates its own runner package with an integrity check, and supplies configured provider credentials to local harnesses. The bundled anonymous usage reporting is documented and has an opt-out; no credential exfiltration or unrelated execution was identified.
Decision evidence
public snapshot- The package describes a local runner that connects to WildCrane and runs jobs on the user's local AI coding tools.
- The launcher fetches its own package from npm and checks the tarball against the registry's SHA-512 integrity value before installation.
- Provider secrets are mapped into the selected local harness environment for a run.
- Cloud API calls use the signed-in session token with the configured WildCrane API.
- The bundled CLI describes usage reporting as anonymous, provides a telemetry off command, and sends batches to its first-party telemetry endpoint.
Source & flagged code
10 flaggedSource appears to send environment or credential material to an external endpoint.
dist/akb/dist/kanban.mjsView on unpkg · L58Package source references child process execution.
dist/akb/dist/kanban.mjsView on unpkg · L1168Findings
Affected versions and remediation
This report applies to wildcrane-runner@0.6.6.
See all versions of wildcrane-runner for other recorded verdicts.
- Review the evidence and your use of wildcrane-runner@0.6.6 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.