T08 · Insecure Dependencies
- Location
install.sh:10- Finding
Unpinned Third-Party Dependency Is Downloaded and Immediately Executed
- Content
View full analysis
Checking Agent Reach ..." if command -v agent-reach &>/dev/null; then echo " agent-reach already installed, skipping." else echo " Installing agent-reach via pip ..." pip install agent-reach echo " Running agent-reach install ..." agent-reach install --env=auto fi ``` From `docs/install.md:12-17`: ```bash pip install agent-reach agent-reach install --env=auto ``` From `docs/install.md:30-34`: ```bash git clone git@github.com:yy4fun/ai-news-skills.git cd ai-news-skills ./install.sh ``` ### Technical Analysis The installer retrieves `agent-reach` from the active Python package index without an exact version constraint or integrity hash. It then immediately invokes the downloaded package through: ```bash agent-reach install --env=auto ``` The repository does not contain the dependency's source code, so the behavior of this command cannot be established from the audited artifact. The effective installation payload may change after this Skill has been reviewed. The Git installation instructions also clone the repository's current default branch instead of a reviewed commit SHA or signed release. This permits the code executed by `./install.sh` to differ from the audited revision. This behavior is related to the declared web-reading functionality, but it is not least-risk installation practice. Installing and executing mutable third-party code grants the dependency the same operating-system privileges as the user running the installer. The pre-scan's separate allegation of a `curl | bash` chain was not confirmed. The repository's `curl` pipelines pass remote content to local data parsers ra ...[truncated 1618 chars]- Remediation
View remediation
