T08 · Insecure Dependencies
Warning
- Location
- plugin-install.md:5
- Finding
- Unpinned Executable Companion Plugin Creates a Supply-Chain Risk<. Source: https://github.com/GrahamMcBain/fly-coworker . ``` ### Technical Analysis The companion plugin is installed by a registry package name without an immutable version, commit identifier, or cryptographic digest. Although `plugin-install.md` states that the workflow reuses companion version `v0.3.0`, the actual installation command does not constrain resolution to that version. Consequently, the package installed at runtime may differ from the version described or previously reviewed. The companion's executable source is not included in this artifact, so its behavior cannot be verified through this repository alone. This dependency is security-sensitive because the documented workflow grants it access to OpenClaw dashboard and session actions. It also participates in an authenticated `chat.send` handoff to the owning conversation. Registry review ...[truncated 1690 chars]
- Remediation
- <![CDATA[ ## Remediation Suggestions 1. Pin the companion to an explicit immutable version in every installation example, such as a registry version that exactly corresponds to the reviewed release. 2. Prefer verification by a cryptographic package digest or signed provenance statement in addition to a semantic version. 3. Document the expected package identifier, version, digest, publisher identity, and source commit. 4. Make installation fail closed when the resolved artifact does not match the documented integrity value. 5. Link to the exact audited source revision rather than only the repository's mutable default branch. 6. Keep the registry capability review enabled and document the minimum capabilities required by the companion. 7. Ensure the plugin cannot obtain unrelated filesystem, shell, network, or conversation permissions. 8. Update `README.md`, `plugin-install.md`, and `SKILL.md` together so all installation and recovery paths use the same pinned artifact. 9. Consider including the companion source in the audited distribution or conducting and publishing a separate audit of the exact companion release. ]]>
