T08 · Insecure Dependencies
- Location
SKILL.md:5- Finding
Unpinned Third-Party Homebrew Dependency
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 5
Vulnerability Type: Unpinned dependency from a third-party Homebrew tap
Risk Level: MediumVulnerable Code Snippet:
yaml metadata: {"clawdbot":{"emoji":"🧾","requires":{"bins":["summarize"]},"install":[{"id":"brew","kind":"brew","formula":"steipete/tap/summarize","bins":["summarize"],"label":"Install summarize (brew)"}]}}Technical Analysis
The skill declares
steipete/tap/summarizeas an installation source without specifying an immutable package version, repository commit, checksum, or cryptographic signature. The package implementation is not included in the audited artifact, which contains onlySKILL.mdand_meta.json. Consequently, the effective code installed and executed by users can change after this skill has been reviewed.This creates a supply-chain trust boundary: control of the third-party tap, its formula, or an associated release artifact could allow modified installation or runtime code to be distributed under the expected package name. The audit found no evidence that the current dependency is malicious; the vulnerability is the mutable and unverifiable dependency reference.
Attack Path
- An attacker compromises the third-party Homebrew tap, a maintainer account, the formula repository, or an artifact referenced by the formula.
- The attacker modifies the formula or its downloadable package to contain malicious installation or runtime behavior.
- A user or agent follows the skill metadata and installs
steipete/tap/summarize. - Homebrew retrieves the attacker-controlled version because the skill does not constrain installation to a reviewed immutable revision.
- Malicious code executes during installation or when the
summarizecommand is invoked. - The code accesses data available to the installing user, potentially including local documents submitted for summarization, environment-based API credentials ...[truncated 547 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin the dependency to a reviewed, immutable release and repository commit rather than a mutable formula reference.
- Verify downloaded artifacts using a published cryptographic checksum or signature.
- Record the authoritative source repository and expected package digest in the skill documentation.
- Review the Homebrew formula and all transitive installation sources before approving the skill.
- Prefer vendored or otherwise reproducibly built source when feasible, with a lock file or equivalent integrity metadata.
- Run the CLI with least privilege and restrict access to sensitive files and unrelated environment variables.
- Avoid exposing provider credentials globally; use narrowly scoped keys and rotate them if dependency compromise is suspected.
