@factiii/runner@0.17.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 21d ago · by lpm-firewall-aiSource supports a warning for first-party agent extension installation and automatic updates, rather than the scanner's malicious verdict. The manifest lacks install hooks, and the inspected skill and tmux behavior does not establish an active attack.
Decision evidence
public snapshot- The manifest has no registry install hooks or runtime self-dependency; its lifecycle script is prepublishOnly.
- Runtime provisioning installs the Factiii plugin into Claude's user scope and adds it to Codex.
- The same provisioning flow updates the Claude plugin and runs again when an existing workspace is reattached, without a separate consent prompt in that flow.
- Plugin rendering uses the package's local plugin source rather than a fetched remote payload.
- The flagged Claude skill mutation links the workspace deploy skill during approval and deployment flows.
- The flagged tmux save script writes session layout to local resurrection backups.
- No concrete malicious install chain or covert credential theft was established.
- The agent changes serve the runner's own plugin and deployment integration.
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.17.1.
See all versions of @factiii/runner for other recorded verdicts.
- Review the evidence and your use of @factiii/runner@0.17.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.