Golang Package Dependency Graph Traversal

via “dependency graph extraction and relationship analysis”

A Model Context Protocol (MCP) server that helps large language models index, search, and analyze code repositories with minimal setup

Unique: Extracts dependency relationships from indexed import statements without executing code or resolving external packages. Supports language-specific import syntax and can compute transitive dependencies efficiently.

vs others: More practical than runtime dependency analysis because it works without executing code; more accurate than static analysis tools because it uses parsed AST instead of regex.

via “dependency management and architecture visualization tool reference”

🦩 Tools for Go projects

Unique: Combines dependency management tools (go mod commands) with visualization utilities and architecture enforcement tools in a single reference, showing how to use them together to maintain architectural health. Includes both built-in Go tooling (go mod graph) and third-party visualization tools (modgraph, depcheck).

vs others: More actionable than raw 'go mod graph' output because it includes visualization tools and architecture enforcement patterns; more comprehensive than individual tool documentation because it shows the complete workflow from dependency analysis to architectural enforcement.

via “dependency tree visualization”

A powerful MCP (Model Context Protocol) Server that audits npm package dependencies for security vulnerabilities. Built with remote npm registry integration for real-time security checks.

Unique: Utilizes advanced graph visualization techniques to provide an interactive view of dependencies, which is often lacking in standard audit tools.

vs others: Offers a more intuitive and interactive way to explore dependencies compared to static reports from other auditing tools.

via “dependency and import graph extraction”

Compact, language-agnostic codebase mapper for LLM token efficiency.

Unique: Uses multi-pattern regex matching and heuristic fallback strategies to handle import syntax variations across languages, combined with optional path resolution configuration, enabling accurate dependency mapping even in polyglot codebases without language-specific tooling

vs others: Faster and more portable than language-specific tools (like npm audit or Python import analysis) because it avoids installing language runtimes and dependencies, while remaining accurate enough for architectural analysis and refactoring planning

via “repository structure and dependency graph analysis”

** - Leading AI-powered code assistant for advanced research, analysis and discovery across GitHub Repositories in large ecosystems

Unique: Builds queryable dependency graphs across multiple repositories by parsing standard manifest files and exposing them via MCP, enabling AI clients to understand ecosystem-wide architectural relationships without manual graph construction

vs others: Provides automated cross-repository dependency graph extraction through MCP, whereas tools like Dependabot focus on single-repository updates and most architecture analysis tools require manual input or local repository clones

via “golang-package-dependency-graph-traversal”

** - MCP server to provide golang packages and their information from pkg.go.dev

Unique: Exposes golang package dependency relationships through MCP, enabling LLM agents to programmatically traverse and analyze dependency graphs without manual pkg.go.dev navigation

vs others: Provides structured dependency lookup vs. requiring agents to parse pkg.go.dev HTML or manually inspect go.mod files, enabling automated dependency analysis within agent workflows

via “transitive dependency graph traversal and analysis”

** - iOS Swift Package Manager server written in Swift

Unique: Provides direct access to SPM's internal dependency graph representation, enabling efficient traversal without reconstructing the graph from manifest files, and supporting both forward and reverse dependency queries

vs others: More efficient than parsing manifests and reconstructing graphs manually because it leverages SPM's pre-computed graph structure, and provides accurate cycle detection that accounts for SPM's resolution semantics

via “package dependency graph extraction”

** - Search and get up-to-date information about NPM, Cargo, PyPi, and NuGet packages.

Unique: Parses and normalizes dependency manifests from four distinct package manager formats (package.json, Cargo.toml, PyPI metadata, NuGet packages.config) into a unified dependency schema without requiring local package installation or manifest downloads

vs others: Avoids the overhead of npm install or pip install by reading metadata directly from registries, making it 10-100x faster than local dependency resolution for quick audits