T08 · Insecure Dependencies
- Location
SKILL.md:5- Finding
Unpinned Dependency Installed from a Third-Party Homebrew Tap
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:5
Vulnerability Type: Unpinned third-party dependency and mutable supply-chain source
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 installation metadata directs Homebrew to install the
summarizeexecutable from the third-partysteipete/taptap. It does not pin an immutable package version, source commit, artifact digest, or verified signature.The executable and Homebrew formula are not included in the audited project, so their implementation and future changes cannot be verified from this package. Consequently, the effective installed code may change after this Skill has been reviewed. This creates a supply-chain trust boundary in which compromise of the tap, its maintainers, release infrastructure, or referenced artifacts could cause users to install altered code.
This finding does not establish that the current external package is malicious. The risk arises from relying on a mutable, externally controlled installation source without integrity pinning.
Attack Path
- An attacker compromises the third-party Homebrew tap, a maintainer account, its release infrastructure, or an artifact referenced by its formula.
- The attacker modifies the formula or distributed executable while retaining the expected package and binary names.
- A user or agent installs the dependency through the Skill metadata using
steipete/tap/summarize. - Homebrew retrieves and installs the modified dependency because the Skill does not constrain installation to an independently verified immutable version.
- The installed
summarizeexecutable runs under the installing user's account when the Skill processes a URL or local file.
...[truncated 1031 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin the dependency to a specific, reviewed release rather than relying on the latest mutable tap state.
- Verify downloaded artifacts using a cryptographic checksum obtained through a separately trusted channel.
- Prefer signed releases and validate the publisher's signature before installation.
- Record the exact audited formula revision, source commit, package version, and artifact digest in the Skill metadata or installation documentation.
- Prefer an official or project-controlled package source with documented release and provenance controls.
- Add automated dependency monitoring so changes to the formula, source URL, checksum, signing identity, or transitive dependencies trigger a new security review.
- Run the CLI with least privilege and isolate it from unrelated files and environment variables. Provide only the credentials and input files required for the current operation.
- Where practical, use short-lived, narrowly scoped API credentials and revoke or rotate them if dependency compromise is suspected.
