docker-project-foundations
Pass
Audited by Gen Agent Trust Hub on Sep 29, 2026
Risk Level: SAFECREDENTIALS_UNSAFECOMMAND_EXECUTIONINDIRECT_PROMPT_INJECTION
Full Analysis
- Hardcoded Development Credentials: The
assets/compose-dev.yamltemplate includes a default fallback password (apppass) and hardcoded connection strings (postgres://appuser:${POSTGRES_PASSWORD:-apppass}@db:5432/appdb) to enable one-command startup for local development. While the documentation inSKILL.mdlabels these as fallbacks and recommends using.envoverrides, hardcoded credentials in configuration templates are a security pattern to monitor. - Automated Command Execution: The
scripts/verify-setup.shscript executesdocker compose config --quietto validate the syntax of generated configuration files. This is a standard verification tool used to ensure project readiness but involves the automated invocation of the Docker CLI. - Indirect Prompt Injection Surface: The skill processes user-provided project requirements to generate specific configuration files, which presents a surface for potential instruction interpolation.
- Ingestion points: User project descriptions and service requirements are used to populate templates in
assets/and directives inSKILL.md. - Boundary markers: The skill provides a comprehensive
.dockerignoreexample to limit context exposure and instructs the use of BuildKit secret mounts for registry credentials. - Capability inventory: The skill facilitates the creation of
Dockerfileandcompose.yamlfiles, as well as the execution of Docker build and orchestration commands. - Sanitization: The guidance explicitly warns against copying credential files or using
ARG/ENVfor secrets, promoting BuildKit secrets as a more secure alternative.
Audit Metadata