Running the external Docker Compose executes containers not audited in the supplied Skill
Source references: 2The instructions tell the user to obtain Autonnel from GitHub and run that repository's `docker-compose.yml`. Compose can pull and execute images, expose ports, and mount host paths or grant permissions as configured. The supplied evidence does not include that file, its image definitions, or installation scripts, so their behavior cannot be verified here. Reading the file and selecting a release tag reduces risk, but a tag does not by itself make referenced images immutable or safe.
If the repository, tag, or referenced image is compromised, execution could expose mounted files, listen on local ports, use the network, or run with whatever permissions the Docker configuration grants.
This is an active evaluation step, not merely a warning: the user is told to check out an external GitHub repository and then execute its Compose configuration. `docker compose up` starts containers defined by that external file, but the supplied material omits the Compose file, image digests, mounts, and permissions, so what would be downloaded or run—and what local data or ports it could access—cannot be verified. Reading the file and using a release tag helps review but does not supply the missing evidence. A user can request digest-pinned images and required permissions, and restrict network access, mounts, and credentials.
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```Show 1 other places
```bashdocker compose up# open http://localhost:4321 and complete /setup```