@factiii/runner@0.23.2
Factiii Runner, run Board AI agents on a machine you control. Pairs with the Factiii web/mobile clients over WebRTC.
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe scanner's high-risk labels are not supported by the inspected behavior: package.json has no consumer install lifecycle hook, pairing requires browser approval and user token entry, and the inspected credential requests target their respective services. The agent integration and tmux save behavior are bounded setup and local session-state operations.
Decision evidence
public snapshot- package.json defines a prepublishOnly build and fetch hook, with no preinstall, install, or postinstall hook.
- The CLI pairs through a user-entered browser approval flow and saves the returned runner token in its configuration.
- The GitHub access token is sent to api.github.com for GitHub API requests.
- The agent integration helper creates a workspace-local Claude skill symlink; its caller first reads the workspace contract.
- The bundled tmux-resurrect save script records tmux session state and pane data locally.
- The CLI contains dynamic import via Function, but the inspected use imports modules and does not establish attack behavior.
- The manifest includes a prepublishOnly fetch step, which runs during publishing rather than consumer installation.
Source & flagged code
14 flagged · loading sourceSource appears to send environment or credential material to an external endpoint.
dist/cli.jsView on unpkg · L38A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
dist/cli.jsView on unpkg · L38Findings
Affected versions and remediation
This report applies to @factiii/runner@0.23.2.
See all versions of @factiii/runner for other recorded verdicts.
- Review the evidence and your use of @factiii/runner@0.23.2 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.