T08 · Insecure Dependencies
- Location
requirements.txt:1- Finding
Unbounded Development Dependency Installed as a Runtime Requirement
- Content
View full analysis
=7.0.0 ``` `SKILL.md:10-13`: ```yaml install: - id: python-deps kind: python requirements: "requirements.txt" ``` ### Technical Analysis The skill installation configuration automatically installs packages from `requirements.txt`. That file specifies `pytest` using only a minimum version and provides no upper version constraint, exact pin, package hash, or lockfile. `pytest` is used only by the test suite and is not imported by the runtime implementation in `scripts/prompt_optimizer.py`. Installing it as a skill runtime dependency therefore unnecessarily expands the dependency and build-time attack surface. Because the permitted version range is open-ended, installation may resolve to a future release that was not included in this audit. If a permitted package release or one of its transitive dependencies is compromised, malicious package installation or build logic could execute under the account installing the skill. This finding does not establish that the current `pytest` package is malicious; the risk arises from unconstrained future resolution and unnecessary runtime installation. ### Attack Path 1. A user or automation framework installs the skill. 2. The installation metadata in `SKILL.md` directs the package manager to process `requirements.txt`. 3. The package resolver selects any available `pytest` release satisfying `>=7.0.0`, including future unaudited releases and associated transitive dependencies. 4. If a selected release or dependency is compromised, malicious build or installation logic may execute during dependency installation. 5. That logic executes with the filesystem, network, and process privileges of the account performing the installation. This exploitation path is condition ...[truncated 662 chars]- Remediation
View remediation
