repowiserepowise
Sign in
docker/compose
OverviewDocsArchitectureKnowledge GraphFilesCode HealthSecurityRefactoring

People & History

CommitsContributorsDecisions
Chat
Stats
repowiserepowise
ExplorePricingDocs
Sign in
repowisedocker/compose
CO
CO

docker / compose

Define and run multi-container applications with Docker

Go★ 38,290
Use in your agentAsk this codebase

github.com/docker/compose·Indexed at 9d444a6·3mo ago·Up to date with upstream

About this codebase

383 files and 2,008 symbols in 5 modules, led by Go (259 files) and Dockerfile (1).

Built from the index

Start reading

  • Knowledge graph383 files and how they depend on each other.→
  • Expand ~ in --env-file pathsDecisionProposed decision, from a pull request.→

Code health

6.2out of 10Fair

This codebase scores 6.2 out of 10 for code health, which we rate fair. It also scores maintainability 7.7 and static performance 9.8 out of 10. The three are scored separately and never blended into one number. Risk is concentrated, as it usually is: 22 of 383 files are git hotspots, and they average 3.3 — which is where the fixes pay off most.

Full health report →

On the leaderboards:#16 of 19 Go repos

Do next

1 thing worth doing this quarter.

Worth planning

  • Delete 40 unused symbols and files (231 lines)

    Nothing in the graph reaches them, across 24 files; every reader and agent pays to skip them.

    symbols
    40
    lines
    231
    safe to delete
    Yes(inferred)
    Small effort

Improve what Repowise can see

  • Add a test coverage report

    Without one, Repowise cannot tell tested code from untested code, so every test-related action says “unknown”.

    line coverage
    Unknown, no report
    Small effort
All actions in the Overview →

Use docker/compose in your agent

Point Claude Code, Cursor, Codex or VS Code at this repository. Your agent gets the index this page is built from: cited answers, callers, history and health for any file.

https://api.repowise.dev/mcp/docker/compose

One command, run anywhere. Adds the server to your local Claude Code config.

Docs
bash
claude mcp add --transport http repowise https://api.repowise.dev/mcp/docker/compose \
  --header "Authorization: Bearer rw_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
The snippet shows a placeholder key. Generate one to get a copyable secret.
Sign in and create an API key to connect.Sign in

This repo is public, so anyone with a Repowise account and an API key can connect.

Try asking

  • get_overview()
  • get_answer("how is compose put together?")
  • get_why("why is compose structured this way?")

Prefer local? pip install repowise && repowise init indexes your own checkout, no account needed.

Go deeper

  • OverviewEverything the index found, what changed this week, commits and decisions.→
  • DocumentationModule-by-module documentation, written from the source.→
  • ArchitectureDependency graph, layers and third-party dependencies.→
  • Code healthEvery file's score, the findings behind it, tests and refactoring plans.→
  • CommitsEach commit's effect on code health, with agent provenance.→
  • ContributorsWho owns what, and where one person holds most of the knowledge.→
  • DecisionsArchitectural decisions mined from commits and pull requests.→
  • Ask this codebaseSign inGrounded answers over the indexed code.→

Maintain this repo? Claim the page

Sign in with GitHub and we check that you are an admin or maintainer of docker/compose. Then add a badge to the README that links readers here.

Use this repo from Claude or ChatGPT

Add this URL as a custom connector and sign in with repowise when asked. No API key to copy.

https://api.repowise.dev/mcp/docker/compose
Sign up to connect

For maintainers

Add a badge to your README

Every badge is public, cached, and updates on its own after every index. Nothing to install.

Repowise badge

Links to this page, with no score on it. Adding it also re-indexes the repo every week.

Repowise badge preview
[![repowise.dev](https://api.repowise.dev/badge/wiki/docker/compose.svg)](https://repowise.dev/repo/docker/compose?src=badge_wiki)

Code health badge

The repo's health score out of 10, from the latest index.

Code health badge preview
[![repowise.dev code health](https://api.repowise.dev/badge/health/docker/compose.svg)](https://repowise.dev/repo/docker/compose?src=badge_health)

Code health card

A larger card with the score, its change since the last index, and when it was measured. The HTML version follows the reader's light or dark theme.

Code health card preview
[![repowise.dev code health](https://api.repowise.dev/badge/health/docker/compose.svg?style=card)](https://repowise.dev/repo/docker/compose?src=badge_card)

How docker/compose works

Define and run multi-container applications with Docker This page is a map of the docker/compose repository, written primarily in Go, rebuilt from the source each time it is indexed. Repowise parses every symbol, computes a dependency graph, scores per-file code health from complexity, duplication, test coverage and churn, mines git history for hotspots and ownership, and lifts the architectural decisions into documentation you can read here or query through MCP.

The codebase has 383 files and 2,008 symbols in 5 modules, led by Go, Dockerfile and Makefile. Code health is 6.2 out of 10, rated fair.

Use the links above to open each view, or connect this repository to your agent for grounded answers inside Claude, Cursor, Codex or VS Code.