wildcrane-runner@0.6.0
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 5d ago · by lpm-firewall-aiThe flagged credential references belong to local provider configuration, and the reviewed cloud requests use the WildCrane session token. The launcher’s package update path verifies registry tarballs, and running local agent jobs is the package’s stated function.
Decision evidence
public snapshot- The package describes itself as a local runner that connects to WildCrane and runs its jobs using local AI coding tools.
- Provider API keys are configured for the selected local provider run; the source says the subscription run does not receive the key.
- Cloud requests use the WildCrane session token as a bearer token, consistent with the package’s cloud connection.
- The launcher fetches updates for this package from the npm registry and verifies the tarball’s SHA-512 integrity before installing it.
- The Claude Code harness uses --dangerously-skip-permissions so the local agent can run jobs without interactive approval; this is a powerful capability, but matches the package’s stated purpose.
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.0.
See all versions of wildcrane-runner for other recorded verdicts.
- Review the evidence and your use of wildcrane-runner@0.6.0 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.