T08 · Insecure Dependencies
- Location
templates/team-summary.sh:52- Finding
Conflicting and unpinned npm installation instructions create a dependency-substitution risk
- Content
View full analysis
/dev/null; then echo -e "${RED}Error: agent-teams not found${NC}" >&2 echo "" >&2 echo "Install it with:" >&2 echo " bun install -g agent-teams" >&2 exit 1 fi ``` The same conflicting `bun install -g agent-teams` recommendation appears in `templates/monitor-channel.sh:171-178` and `templates/post-message.sh:155-162`. ### Technical Analysis The Skill manifest requests the npm package `agent-messenger`, but each runnable template tells users to install `agent-teams` globally. The Skill documentation expressly states that `agent-teams` is not the correct npm package name and may install the wrong package. This inconsistency creates a package-substitution or typosquatting opportunity. Neither installation path pins an exact package version or integrity digest. Consequently, the effective code can change after the Skill has been reviewed. npm-compatible package installations can also execute lifecycle scripts with the privileges of the invoking user. This is particularly dangerous here because the resulting CLI is expected to handle a reusable Microsoft Teams session token. The repository does not contain evid ...[truncated 1360 chars]- Remediation
View remediation
