@factiii/runner@0.12.1
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 package has no registry install lifecycle hook or demonstrated credential exfiltration, but runtime provisioning automatically installs persistent user-scoped Claude and Codex extensions and MCP configuration. This is a concrete first-party agent-extension lifecycle risk that warrants a warning rather than a publish block.
Decision evidence
public snapshot- Runtime workspace provisioning installs a Factiii plugin into user-scoped Claude and Codex configurations.
- The installed hook is designed to run during every Claude and Codex event and invokes a local shell script.
- Provisioning also removes and adds user-scoped MCP entries, changing AI-agent control configuration.
- The package can install index dependencies at runtime, expanding its supply-chain execution surface.
- package.json has no install, preinstall, or postinstall hook; prepublishOnly is publish-time only.
- Plugin changes occur after the user runs the runner and provisions or reattaches a workspace.
- The hook only publishes state to a discovered local Redis socket; no network transmission is shown there.
- The secret wrapper requests an owner-authorized command through a local socket and refuses callers without its session token.
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.1.
See all versions of @factiii/runner for other recorded verdicts.
- Review the evidence and your use of @factiii/runner@0.12.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.