Exposed docker-compose file
Your docker-compose file is publicly readable.
Why it matters
Your docker-compose file is publicly readable. These files routinely carry database passwords, service credentials, and API keys in their environment blocks, and they always describe your internal service topology — which databases, caches, and internal ports exist and how they connect. That combination turns a single foothold into a map of everything worth attacking next.
How ShipReady detects it
Finds files and endpoints that are reachable but should not be. Probes a fixed set of well-known paths — version control directories, environment files, build configuration, debug routes — and derives others from the page's own bundles, such as a source map alongside each script. Every result is gated on content, not status. Many single-page apps answer 200 for every unknown path by serving their index shell, so a 200 alone proves nothing: a source map must parse as one, a directory listing must carry the index signature. Without that gate this check would report an entire class of SPA as catastrophically exposed.
Detection is deterministic. ShipReady reports this only when it observes the condition directly, and prefers to miss a real problem over inventing one. Rule version 1.2.0.
How to fix it
This is the prompt ShipReady puts in your report — written to be pasted straight into Cursor, Claude Code, or whichever assistant built the app.
Your docker-compose file is publicly downloadable. First, rotate any credential that appears in it (database passwords, service tokens, API keys in `environment:` blocks) — assume they are compromised. Then stop shipping the file: deploy build output rather than the repository, add compose files to your deploy ignore list, and block requests to /docker-compose.y*ml at your web server, host, or CDN. Move secrets out of the file entirely and inject them as runtime environment variables or managed secrets instead.
Frequently asked questions
- What does "Exposed docker-compose file" mean?
- Your docker-compose file is publicly readable.
- How serious is it?
- ShipReady rates this high. Fix before launch. A real weakness that an attacker can act on.
- How do I fix it?
- Paste the fix prompt on this page into Cursor, Claude Code or your AI editor. It is the same prompt ShipReady puts in your report.
- Can I check my own site?
- Yes — ShipReady scans up to ten pages of any public site for free and reports this alongside every other check.
Related checks
Does your site have this?
ShipReady checks this and 73 other things across up to ten pages of your site. Free, no signup.
Scan my site