Understand your project's architecture before it becomes technical debt.

mdv is a language-agnostic CLI that parses go.mod, package.json, requirements.txt, and more into a unified, interactive dependency graph. It ships with a security auditor, a D3.js web UI, a diff engine, and a GitHub Actions composite action - covering the full dependency lifecycle in a single binary.

• Features
• Installation
• Quick Start
• Commands
• Output Formats
• GitHub Actions
• Build from Source
• Project Structure
• Branch Strategy
• CI/CD Pipelines
• Contributing
• License

Requires Go 1.22+.

go install github.com/devekkx/module-dependency-visualizer/cmd/mdv@latest

Download the archive for your platform from the Releases page, then extract and move to $PATH:

# Linux (amd64)
curl -fsSL https://github.com/devekkx/module-dependency-visualizer/releases/latest/download/mdv_latest_linux_amd64.tar.gz \
  | tar -xz -C /usr/local/bin mdv

# macOS (arm64 / Apple Silicon)
curl -fsSL https://github.com/devekkx/module-dependency-visualizer/releases/latest/download/mdv_latest_darwin_arm64.tar.gz \
  | tar -xz -C /usr/local/bin mdv

Verify checksums with the checksums.txt file included in each release.

No installation required - mount your project directory and run:

# Analyse
docker run --rm -v $(pwd):/work ghcr.io/devekkx/mdv analyse /work

# Export as DOT
docker run --rm -v $(pwd):/work ghcr.io/devekkx/mdv export /work --format dot

# Audit
docker run --rm -v $(pwd):/work ghcr.io/devekkx/mdv audit /work

# Serve (use --no-browser since there is no browser in the container)
docker run --rm -v $(pwd):/work -p 7777:7777 ghcr.io/devekkx/mdv serve /work --port 7777 --no-browser

Images are published to ghcr.io/devekkx/mdv for linux/amd64 and linux/arm64.

# Summarise dependencies in your terminal
mdv analyse .

# Launch the interactive web UI (port is auto-assigned, shown in output)
mdv serve .

# Use a fixed port
mdv serve . --port 7777

# Export a Graphviz SVG
mdv export . --format dot | dot -Tsvg -o deps.svg

# Paste a Mermaid diagram into GitHub or Notion
mdv export . --format mermaid

# Run a full security & license audit
mdv audit .

# See what changed since main
mdv diff . --from main

# Generate DEPENDENCIES.md with audit data
mdv docs . --output DEPENDENCIES.md --audit

Parse a project and emit a dependency summary.

mdv analyse <path> [flags]

Export the graph to a renderable format.

mdv export <path> --format <fmt> [flags]

--format is required: dot, mermaid, or json. Accepts the same depth/filter flags as analyse.

Run a standalone security, license, and version-conflict audit.

mdv audit <path>

Checks each dependency against the OSV database, flags non-permissive licenses, and detects packages required at multiple incompatible versions.

Launch an interactive D3.js dependency graph in your browser.

mdv serve <path> [--port <n>] [--no-browser]

Show dependency changes between two git refs.

mdv diff <path> --from <ref> [--to <ref>]

--from defaults to HEAD~1. --to defaults to the working tree. Outputs added, removed, and version-bumped dependencies.

Generate a DEPENDENCIES.md documentation file.

mdv docs <path> [-o DEPENDENCIES.md] [--audit]

Print version, commit hash, and build date.

The canonical, machine-readable graph. Powers all other exporters.

{
  "schema_version": "1.1.0",
  "generated_at":   "2024-11-01T10:00:00Z",
  "project":  { "name": "github.com/example/app", "language": "go", ... },
  "nodes":    [{ "id": "github.com/spf13/cobra@v1.8.0", "kind": "module", "indirect": false, ... }],
  "edges":    [{ "from": "github.com/example/app@", "to": "github.com/spf13/cobra@v1.8.0", "kind": "depends_on" }],
  "stats":    { "node_count": 8, "edge_count": 12, "max_depth": 3, "has_cycles": false }
}

See docs/schema-v1.md for the complete field reference.

mdv export . --format dot | dot -Tsvg -o deps.svg
mdv export . --format dot | dot -Tpng -o deps.png

Best for large graphs (hundreds to thousands of nodes).

mdv export . --format mermaid

Paste directly into GitHub Markdown, Notion, or Confluence. Renders reliably up to ~500 nodes; use DOT for larger graphs.

A composite action is available at .github/actions/mdv.

- uses: devekkx/module-dependency-visualizer/.github/actions/mdv@main
  with:
    audit: "true"
    diff: ${{ github.event.pull_request.base.sha }}
    generate-docs: "true"

Inputs

Outputs

Requirements: Go 1.21+

git clone https://github.com/devekkx/module-dependency-visualizer.git
cd module-dependency-visualizer

module-dependency-visualizer/
├── cmd/mdv/                   # Entry point
├── internal/
│   ├── audit/                 # OSV, license, and conflict checks
│   ├── cli/                   # Cobra command definitions
│   ├── config/                # Build metadata (version, commit, date)
│   ├── diff/                  # Dependency diff engine
│   ├── docgen/                # DEPENDENCIES.md generator
│   ├── exporter/
│   │   ├── dot/               # Graphviz DOT exporter
│   │   ├── jsonexp/           # JSON exporter
│   │   └── mermaid/           # Mermaid exporter
│   ├── graph/                 # Immutable graph model, builder, filters, traversal
│   ├── logging/               # Structured logger
│   ├── provider/
│   │   ├── golang/            # go mod graph provider
│   │   ├── node/              # npm/yarn/pnpm/bun provider
│   │   └── python/            # pip/poetry/pyproject provider
│   ├── schema/                # JSON schema encode/decode (v1.1)
│   └── server/                # Embedded D3.js HTTP server
├── docs/
│   ├── adr/                   # Architecture Decision Records
│   └── schema-v1.md           # JSON schema reference
├── website/                   # VitePress documentation site (→ Vercel)
│   └── docs/
│       ├── .vitepress/config.ts
│       ├── index.md
│       ├── getting-started.md
│       ├── commands.md
│       ├── formats.md
│       ├── schema.md
│       ├── github-actions.md
│       └── contributing.md
├── .github/
│   ├── actions/mdv/           # Composite GitHub Action
│   └── workflows/             # CI/CD pipelines (see below)
├── Makefile
├── go.mod
└── vercel.json                # Docs site deployment config

The project follows a three-tier promotion model:

feature/*  ──PR──▶  testing     (integration branch - CI runs here)
testing    ──PR──▶  develop     (stable dev - dep checks run here)
develop    ──PR──▶  production  (release-ready - full gate runs here)
production ──tag──▶  v*.*.*    (triggers GitHub Release)

Day-to-day flow:

1. Branch off testing: git checkout -b feature/my-thing testing
2. Open a PR to testing - CI runs unit tests, lint, and build.
3. Once merged, open a PR from testing → develop - dependency audit and security scan run.
4. When ready to ship, open a PR from develop → production - the full gate runs (tests, lint, security, cross-platform build, docs).
5. Tag the merge commit on production: git tag v1.2.3 && git push --tags - the release pipeline publishes binaries to GitHub Releases.

All pipelines live in .github/workflows/.

Runs on every pull request targeting testing. Stale runs are cancelled automatically on force-push.

The coverage report artifact (coverage.out) is uploaded from the stable matrix leg and kept for 7 days.

Runs on every pull request targeting develop. Posts a single auto-updating comment on the PR.

The strictest gate. All jobs must pass before merging to production.

Triggered by pushing a semver tag to production. Builds static binaries for all platforms, packages them with README.md and LICENSE, generates checksums.txt, and publishes a GitHub Release with auto-generated release notes.

# Cut a release from production
git checkout production
git tag v1.2.3
git push origin v1.2.3

Artifacts produced per release:

mdv_v1.2.3_linux_amd64.tar.gz
mdv_v1.2.3_linux_arm64.tar.gz
mdv_v1.2.3_darwin_amd64.tar.gz
mdv_v1.2.3_darwin_arm64.tar.gz
mdv_v1.2.3_windows_amd64.zip
checksums.txt

Validates the VitePress build on any PR that modifies the website/ directory. Uploads the built site as an artifact for preview.

See CONTRIBUTING.md for the full guide.

Quick summary:

1. Branch off testing
2. Make focused changes and write tests (80% coverage required)
3. Open a PR to testing - CI must pass
4. Follow Conventional Commits: feat:, fix:, docs:, refactor:, test:, chore:

MIT