T08 · Insecure Dependencies
- Location
SKILL.md:18- Finding
Unpinned and Unreviewable Third-Party Plugin Dependency
- Content
View full analysis
```bash > # 1. the plugin — the engine. THIS is the step most people miss > openclaw plugins install clawhub:openclaw-plugin-clawvault > > # 2. this skill — skip it if you are already reading this from an installed copy > openclaw skills install @davidtkeane/clawvault-memory > > openclaw gateway restart > ``` ``` The later installation guidance also states: ```markdown > **Same plugin, either source:** the ClawHub package above and > [github.com/davidtkeane/openclaw-plugin-clawvault](https://github.com/davidtkeane/openclaw-plugin-clawvault) > are the same code. ClawHub is easier — one command, dependency (`typebox`) and prebuilt > `dist/` included, no clone or `npm install`. Use GitHub if you want to read or build the > source yourself. ``` ### Technical Analysis The Skill's essential functionality is not implemented in the audited artifact. Instead, users are instructed to install a remotely hosted executable plugin and restart the OpenClaw gateway to activate it. The installation command does not pin an immutable version or integrity hash, and the referenced plugin source and prebuilt `dist/` file are absent from the audited project. The statement that the ClawHub package and GitHub repository contain the same code is not an integrity control. Without cryptographic verification or reproducible-build validation, reviewers cannot establish that the downloaded executable corresponds to the repository source or to the version originally reviewed. The Skill claims that the plugin makes no network calls and stores data locally, but that claim cannot be verified from the supplied files because the plugin implementation is not included. ### Attack Path 1. An attacker compromises the package publisher account, registry ent ...[truncated 1357 chars]- Remediation
View remediation
