T08 · Insecure Dependencies
- Location
scripts/publish-skill-repo.sh:121- Finding
Unpinned ClawHub CLI Executes with Access to a Publishing Token
- Content
View full analysis
> "$GITHUB_OUTPUT" echo "version=$VERSION" >> "$GITHUB_OUTPUT" echo "slug=$REPO_NAME" >> "$GITHUB_OUTPUT" echo "name=$REPO_NAME" >> "$GITHUB_OUTPUT" - name: Validate required files shell: bash run: | test -f SKILL.md || (echo "SKILL.md not found" && exit 1) - name: Login to ClawHub run: clawhub login --token "$CLAWHUB_TOKEN" ``` ### Technical Analysis The generated GitHub Actions workflow installs `clawhub` without specifying an exact version: ```bash npm install -g clawhub ``` Consequently, every tagged build resolves and executes whatever package version is published under that npm package name at build time. The dependency is not protected by an exact version, a committed lockfile, or an integrity hash. The workflow also places `CLAWHUB_TOKEN` in the job-wide environment. Processes executed by any step in the job can therefore inherit the publishing credential. Although npm lifecycle scripts normally run during installation, the installed CLI is also explicitly executed later. A compromised package release, compromised maintainer account, or malicious transitive dependency could run arbitrary code in the CI runner and a ...[truncated 1284 chars]- Remediation
View remediation
