Starting the external repository's Docker Compose executes its container configuration locally
Source references: 1The Skill tells users to obtain an external GitHub repository and run docker compose up. Although it advises reading the Compose file and selecting a release tag, the supplied evidence does not contain the repository, images, mounts, entry scripts, or pinned image digests, so the executed contents cannot be verified in this review.
A Compose configuration can download and run container images, expose ports, and mount host directories. If an external tag, image, or configuration is compromised, local files, credentials, network services, or databases could be affected.
This is a conditional local-execution risk: Docker starts the external repository’s declared images and configuration only if the user chooses the project and runs the command. Advising the user to check out a release tag and inspect the Compose file reduces risk, but the supplied source lacks the Compose content, image digests, mounts, and entrypoints, so container access and behavior cannot be audited here. Users can require pinned commits and image digests and review ports, volumes, environment variables, and privileges first.
Get the repository from <https://github.com/autonnel/autonnel> (Apache-2.0), checkout a release tag, and read its `docker-compose.yml` - it declares the images andports that will run. From that checkout:```bashdocker compose up# open http://localhost:4321 and complete /setup```