@factiii/runner@0.12.0
Factiii Runner, run Board AI agents on a machine you control. Pairs with the Factiii web/mobile clients over WebRTC.
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe source establishes a real, user-scoped agent extension and update capability, requiring a warning. It lacks an npm registry install lifecycle hook and the inspected hooks are constrained to the runner context, so the source does not establish malicious install-hook abuse.
Decision evidence
public snapshot- The runner installs and updates a Factiii plugin in both Claude and Codex user scopes.
- It registers user-scoped MCP endpoints and bearer-token configuration for both agent CLIs.
- The bundled plugin executes status-reporting hooks on agent lifecycle events.
- A remotely approved update can globally install the latest package release and restart the runner.
- package.json has no npm install, preinstall, or postinstall hook; prepublishOnly is publish-time only.
- The behavior is reached through the explicit runner setup/start workflow, not package installation.
- The hook script exits unless it finds the runner's tmux pane and local Redis socket.
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.12.0.
See all versions of @factiii/runner for other recorded verdicts.
- Review the evidence and your use of @factiii/runner@0.12.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.