Compose Explicit Dependency Inspector

How to use Compose Explicit Dependency Inspector

Trace explicit depends_on relationships in a self-contained services-only Compose model without starting containers. Review conditions, missing services, dependency layers, one concrete cycle witness and the transitive dependents of a selected service. Commands, healthchecks and image references remain inert source data.

1. Provide self-contained compose yaml or json, selected service for dependent tracing.
2. Choose the supported mode and run the tool. Review its assumptions and any reported errors.
3. Copy the result or download a separate output; reset to clear the current form.

Good to know

• 100 KB of UTF-8 YAML/JSON, 20,000 syntax nodes, 40 parsed levels, 500 services and 5,000 explicit dependency edges. Duplicate mapping keys, aliases, custom/unresolved tags, nonfinite scalars and prototype-related keys are refused.
• The parser library is loaded inside a module Worker before its ready signal. Preparation has a separate 10-second deadline and parsing/graph work has a 2-second computation deadline.
• This profile requires a self-contained services model. Includes, jobs, extends, profiles, links, volumes_from and service namespace references are refused instead of silently omitting their activation/dependency effects. Other settings are unvalidated inert data.
• The three explicit depends_on conditions and boolean required/restart options are retained. Missing required references suppress a layer order; missing optional references remain warnings. A layer order describes structural prerequisites, not real startup timing, command success or healthy state.
• Inputs are processed on this device and are not automatically saved or uploaded.