T08 · Insecure Dependencies
- Location
SKILL.md:14- Finding
Unpinned External Package Execution and Transitive Skill Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 14 and 21–39
Vulnerability Type: Unpinned third-party dependency execution
Risk Level: MediumVulnerable Code
yaml requires: bins: - agents-cli install: "uvx google-agents-cli setup"markdown > Requires: `agents-cli` and `uv` > One-time setup: `uvx google-agents-cli setup` > [Install uv](https://docs.astral.sh/uv/getting-started/installation/index.md) first if needed. ## Setup Run this once to install the CLI and all 7 specialized skills into the user's coding agent: uvx google-agents-cli setup After setup, the following skills become available and activate automatically based on the user's request: - `google-agents-cli-workflow` — full development lifecycle (always active) - `google-agents-cli-scaffold` — create new ADK projects, add CI/CD or deployment - `google-agents-cli-adk-code` — ADK Python API reference (agent types, tools, callbacks) - `google-agents-cli-eval` — run and debug agent evaluations - `google-agents-cli-deploy` — deploy to Agent Runtime, Cloud Run, or GKE - `google-agents-cli-publish` — register agents with Gemini Enterprise - `google-agents-cli-observability` — production tracing, logging, monitoringTechnical Analysis
The skill instructs the user to resolve and execute
google-agents-clithroughuvxwithout specifying an exact version, package hash, lockfile, or immutable source revision. The implementation executed by this command is not included in the audited project and can change independently after review.The command also installs seven additional skills into the user's coding-agent environment. Those transitive skills are absent from the project and therefore could not be inspected. Their documented automatic activation expands the trust boundary from the single reviewed file to mutable external package content and subsequently installed agent instruction ...[truncated 1623 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin
google-agents-clito a specific, reviewed release rather than resolving the latest available version. - Verify the package using trusted hashes, signed provenance, or an immutable source revision.
- Use a lockfile or equivalent reproducible dependency manifest covering transitive dependencies.
- Include the exact seven installed skill definitions in the review scope, or publish verifiable references to their pinned source revisions.
- Require explicit user confirmation before executing the external package and before installing or automatically activating additional skills.
- Run setup in a least-privileged, isolated environment without unnecessary credentials or access to sensitive project files.
- Document the files and configuration changed by setup, required network access, granted permissions, and a complete uninstall or rollback procedure.
- Pin
