check-deps

To detect circular dependencies in a monorepo, run a full-repo analysis using the --all flag to scan all packages. The tool outputs a dependency graph and identifies circular dependencies with severity levels and actionable recommendations to resolve them.

Dependency version compatibility analysis checks version consistency across multiple packages within a monorepo to identify conflicting versions. It ensures uniform dependency versions are maintained across all packages to prevent runtime issues and module boundary violations.

You can check for missing dependencies by analysing a specified package path or running a full-repo scan with --all. The analysis detects missing or misaligned dependencies and hierarchy violations, providing actionable recommendations to maintain correct module boundaries.

Yes, this dependency analysis supports single-package scans, multi-package workstreams, and full monorepo analyses. You can target a specific package path to surface circular dependencies, version conflicts, and missing dependencies within an individual package.

The best way to visualise a dependency graph for version conflicts is to run a repo-wide analysis that generates the graph alongside detected issues. This approach highlights version inconsistencies across packages and provides actionable recommendations for resolving conflicts.

Circular dependencies cause runtime issues because they create cyclic module references that prevent proper execution order. Detecting these cycles across packages through dependency analysis helps prevent failures before they occur in the deployed environment.