wildcrane-runner@0.6.3
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 4d ago · by lpm-firewall-aiThe package's entry point starts a local WildCrane runner, whose cloud calls use its own configured service and session token. The flagged environment and shell behavior is consistent with passing selected credentials to local agent processes or installing an agent from its official host; no malicious credential exfiltration was identified.
Decision evidence
public snapshot- The package describes a local runner that connects a computer to WildCrane and runs jobs using local coding agents.
- The bin entry imports the launcher, which starts the runner when the command is invoked; no install hook is shown beyond prepare running the build script.
- The launcher checks for a runner version using the configured WildCrane API and a machine ID.
- Cloud API calls require a WildCrane access token and send it as a bearer token to the configured API.
- Agent API keys are passed to the selected local agent in the environment for that run.
- The Cursor install command targets cursor.com and is part of the agent harness configuration.
Source & flagged code
9 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.3.
See all versions of wildcrane-runner for other recorded verdicts.
- Review the evidence and your use of wildcrane-runner@0.6.3 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.