wildcrane-runner@0.3.1
WildCrane's Local Runner — connects this computer to WildCrane and runs its jobs on your local Codex or Claude Code.
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe flagged credential references concern provider configuration, and the shell commands appear as agent installation options rather than automatic execution. The CLI’s network activity supports its documented runner and update functions, with downloaded runner archives checked against registry integrity metadata.
Decision evidence
public snapshot- The manifest exposes a CLI and its prepare script runs the build; no install, preinstall, or postinstall hook is declared.
- The launcher checks downloaded runner tarballs against the registry’s SHA-512 integrity value before extracting them.
- The runner’s documented purpose is to connect to WildCrane and run tasks after the user starts it and signs in.
- Provider keys are configured for model endpoints; the flagged shell install commands appear as agent setup instructions, not automatic startup actions.
- Starting the CLI contacts WildCrane and checks for updates automatically.
- The bundled runner contains shell command strings that install AI agent tools when selected.
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.3.1.
See all versions of wildcrane-runner for other recorded verdicts.
- Review the evidence and your use of wildcrane-runner@0.3.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.