T08 · Insecure Dependencies
- Location
scripts/skill-install.sh:79- Finding
Resolved Skill Versions Are Ignored During Third-Party Installation
- Content
View full analysis
/dev/null && \ echo -e " ${GREEN}✅ $skill${NC}" || \ echo -e " ${YELLOW}⚠️ $skill (may need manual install)${NC}" elif command -v clawhub &> /dev/null; then clawhub install "$skill" 2>/dev/null && \ echo -e " ${GREEN}✅ $skill${NC}" || \ ``` ### Technical Analysis The installer obtains dependency names and version constraints from remote registry metadata and stores the resolved version in `TO_INSTALL`. However, the installation phase invokes: ```bash openclaw skill install "$skill" --yes clawhub install "$skill" ``` rather than installing an exact specification such as `"$skill@$version"`. Consequently, the versions displayed or collected during dependency resolution do not constrain the artifact ultimately selected by the package-management CLI. The c ...[truncated 2349 chars]- Remediation
View remediation
