worktree-devproxy
Pass
Audited by Gen Agent Trust Hub on Jun 12, 2026
Risk Level: SAFECOMMAND_EXECUTIONREMOTE_CODE_EXECUTIONEXTERNAL_DOWNLOADS
Full Analysis
- [COMMAND_EXECUTION]: The skill utilizes shell scripts (
scripts/wt,scripts/devproxy-route) to automate system-level tasks. - The
scripts/wtutility executesdirenv allowanddirenv execinside newly created Git worktrees. This behavior automatically authorizes the execution of.envrcfiles found in the branch, bypassing standard manual security checks. - The scripts invoke
docker composeanddocker runto manage containerized services and perform file ownership adjustments on the host system. - A port-checking function in
SKILL.mduses/dev/tcp/bash syntax for network socket testing, which is a common method for determining port availability but involves low-level network interaction. - [REMOTE_CODE_EXECUTION]: The skill facilitates the execution of configuration and code found within external Git branches.
- The
wt newcommand creates a worktree and immediately runsdocker compose up --build, which executes thedocker-compose.ymland any build instructions (such as Dockerfiles) provided in the repository branch. - The automated
direnvintegration allows for the execution of arbitrary shell commands defined in the environment configuration of the repository being processed. - [EXTERNAL_DOWNLOADS]: The configuration references and downloads the
traefik:v3image from Docker Hub, which is a well-known container registry. - [PROMPT_INJECTION]: The skill's workflow creates an attack surface for indirect injection where untrusted repository data influences system execution.
- Ingestion points: Git branch contents, specifically
.envrc,docker-compose.yml, andDockerfilefiles processed during worktree creation inscripts/wt. - Boundary markers: Absent. The script explicitly automates the
direnv allowstep, which is designed as a manual security boundary for environment configurations. - Capability inventory: Subprocess execution of
docker,git, anddirenvwithin the host environment. - Sanitization: While branch names are sanitized to prevent directory traversal or basic shell injection in filenames, the actual contents of the configuration files within the branch are executed without validation or isolation.
Audit Metadata