T08 · Insecure Dependencies
- Location
SKILL.md:12- Finding
Unpinned Third-Party Executable Dependencies
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 12–17 and 105–112
Vulnerability Type: Supply-chain risk from mutable, unverified dependencies
Risk Level: MediumVulnerable Code
yaml install: - kind: brew formula: runapi-ai/tap/runapi bins: - runapimarkdown ## Integrate with SDK Use this route only for application or production-code integration. Open the current RunAPI SDK reference below, select the package for the target language and `MiniMax H3`, and confirm its install command, client methods, request types, response types, and error classes before coding. Build the request from the same discovered product contract and apply the same deliverable verification and stop rules. Do not invoke `runapi` as a subprocess from production code. ## References - Model overview, pricing, and rate limits: https://runapi.ai/models/minimax-h3.md - Provider overview: https://runapi.ai/providers/minimax.md - Full model catalog: https://runapi.ai/models.md - SDK integration: https://github.com/runapi-ai/minimax-h3-sdkTechnical Analysis
The skill directs users or agents to install a command-line executable from the custom Homebrew tap
runapi-ai/tap/runapi. It also directs production integrations to select and install a package by consulting a mutable external SDK repository.Neither dependency path specifies an immutable version, commit hash, cryptographic checksum, signature-verification procedure, or reviewed lockfile. Consequently, the code installed at execution time may differ from the content that existed when the skill was audited. A compromise of the tap, formula, source repository, package publication account, or referenced SDK guidance could introduce attacker-controlled executable code.
This is a supply-chain weakness rather than evidence that the currently referenced dependencies are malicious.
Attack Path
- An attacker compromises the custom Homebrew tap, its backing repository, the SDK repositor ...[truncated 1145 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin the CLI to a reviewed, immutable release rather than an unconstrained formula state.
- Publish expected SHA-256 checksums or require signature verification for downloaded release artifacts.
- Pin SDK dependencies to reviewed exact versions or immutable commit hashes.
- Use language-native lockfiles with integrity metadata for production integrations.
- Document exact official package names and registries to reduce dependency-confusion and typosquatting exposure.
- Require review of dependency provenance, maintainers, release history, and transitive dependencies before installation.
- Use automated dependency scanning and controlled update procedures instead of dynamically accepting the latest external content.
- Where supported, install and execute dependencies in a least-privileged, isolated environment with narrowly scoped credentials.
