Code Rule and Code Query
Hundreds of default code rules to check against best practices. Support for Code Query over C# LINQ (CQLinq) to easily customize rules and query code.
Our harness, your agent. NDepend.AI hands the issues found by NDepend to Claude Code, Codex, Copilot CLI, Junie, Kiro, Mistral Vibe, Muse Code or OpenCode, and verifies every fix with a build, the impacted tests and a new analysis. On eShopOnWeb: 496 of 511 issues fixed, 531 tests added, coverage from 45% to 98%.
Discover NDepend.AI See all run reports
Most companies have large systems that work together, often in mysterious ways. NDepend's in-depth reporting and toolset can help your company enforce its own coding standards and maintain complex projects.
Hundreds of default code rules to check against best practices. Support for Code Query over C# LINQ (CQLinq) to easily customize rules and query code.
Explore how the code is actually structured and shed light on architectural flaws thanks to the most powerful code dependency graph and dependency matrix available in the tool industry.
Your coding agent asks NDepend: the open-source MCP server gives it the issues, rules, quality gates, dependencies and metrics of your code, to fix NDepend rules, Roslyn Analyzers and R# Code Inspections issues while you steer.
A unique approach to continuously keep the technical debt under control and reimburse it with time.
Integrate NDepend analysis into your CI / CD pipeline and obtain interactive and detailed web reports to explore progression and prevent code quality degradation.
Fail the build pipeline upon customizable PASS / WARN / FAIL code quality and security criteria.
Gain a 360 view of your .NET code quality by importing your preferred Roslyn Analyzers' issues and ReSharper Code Inspections' issues into the NDepend web report and UI.
NDepend allows your team to accurately gauge the overall health of your application, no matter how complex it is.
Lines of Code, Cyclomatic Complexity, Coupling, Nesting Depth, Rank, NDepend supports them all (and much more).
Get Trend Charts about pretty much any code metrics to master the evolution of your application.
Import test coverage data, and make the most of it in the NDepend feature-rich context.
NDepend's reporting and analysis helps architects and developers to communicate and reduce confusion.
Spot too complex code at a glance thanks to unique diagramming capabilities.
Compare two versions of a code base and its issues set, and browse diff and changes in any way you can think of.
Be warned of potential build process problems before they end up causing friction and pain.
By mapping out the structure of the project, it is much easier to see how components and dependencies are connected.
Get rid of dependency cycles between components to achieve higher code maintainability.
NDepend helps maintaining clean side-effects free code to write highly maintainable products.
Integrate with Visual Studio, Azure DevOps, GitHub and any other CI/CD pipeline, super fast and lightweight analysis, NDepend is conceived for real-world programmers.
Write your own static analyzer based on NDepend.API, or tweak existing open-sources Power Tools.
Explore the issues-set in a few clicks and focus your effort on what is urgent and important.
For each issue, the cost to fix and the severity are estimated through smart and customizable C# formulas. Thus estimations proposed are realistic.
See some sample reports below:
Eight runs on eight open-source code bases fixed by NDepend.AI driving Claude Code (Opus as the premium model, Sonnet as the economy model). Each report opens on its AI Assistant tab: the complete log of the run, from the planning pass to the fix rounds, the parallel agent sessions, the tests, the change review and the final report, next to the NDepend report of the fixed code, diffed against the code at the start of the run.
| Code base | Issues fixed | Duration | Cost | Coverage | Tests (+written) | Bugs found |
|---|---|---|---|---|---|---|
| eShopOnWeb | 468 / 493 95% | 1h 21min | $44 | 45% → 97.5% | +506 619 green | 3 |
| NopCommerce (large scale fix) | 3,711 / 3,781 98% | 5h 23min | $261 | 23% → 43.6% | +3,476 4,580 green | 8 |
| Jellyfin (large scale fix) | 1,514 / 1,644 92% | 11h 23min | $543 | 31% → 56.2% | +4,303 8,017 green | 17 |
| Flow Launcher (large scale fix) | 2,837 / 3,109 91% | 6h 17min | $294 | 11% → 60.8% | +2,744 3,236 green | 5 |
| Spectre.Console (large scale fix) | 967 / 1,071 90% | 1h 31min | $64 | 71% → 98.5% | +1,507 2,747 green | 7 |
| Microsoft.FeatureManagement | 283 / 292 97% | 1h 06min | $25 | 78% → 99.6% | +200 347 green | 1 |
| Carter | 222 / 223 99% | 39min | $13 | 68% → 99.6% | +107 271 green | 0 |
| NodaTime | 354 / 387 91% | 1h 26min | $48 | 98% → 99.4% | +313 23,029 green | 0 |
The figures are those of each report's final report:
The same run on a small experiment code base TrainTrain, driving eight different coding agents: the same 22 issues to fix (architecture, naming, visibility, code coverage and a few issues to suppress on purpose), the same NDepend verification of every fix. Each report opens on its AI Assistant tab, with the complete log and the final report of the run.
| Coding agent | Issues fixed | Suppressed | Left on purpose | Still to fix | Duration | Cost | Coverage | Tests (+written) | Bugs found |
|---|---|---|---|---|---|---|---|---|---|
| 14 / 22 64% | 3 | 3 | 2 | 6min 35s | $1.65 | 69% → 77.4% | +7 29 green | 2 | |
| 13 / 22 59% | 4 | 3 | 2 | 5min 44s | ~$0.22 * | 69% → 77.2% | +7 29 green | 1 | |
| 14 / 22 64% | 4 | 3 | 1 | 16min 38s | ~$1.63 * | 69% → 78.7% | +15 37 green | 0 | |
| 14 / 22 64% | 3 | 3 | 2 | 9min 10s | $2.11 | 69% → 77.2% | +6 28 green | 2 | |
| 13 / 22 59% | 4 | 3 | 2 | 23min 28s | 18.8 credits | 69% → 77.2% | +12 34 green | 0 | |
| 15 / 22 68% | 4 | 3 | 0 | 19min 52s | $2.98 | 69% → 79.2% | +15 37 green | 0 | |
| 13 / 22 59% | 4 | 3 | 2 | 12min 01s | $5.51 | 69% → 77.2% | +12 34 green | 0 | |
| 13 / 22 59% | 4 | 3 | 2 | 39min 18s | $0 * | 69% → 89.4% | +17 39 green | 2 |
The figures are those of each report's final report:
GetTrain(), BookSeats() and GetBookingReference() create their own HttpClient
and call a remote HTTP service, with no way to pass in a fake: they need an integration test, not a unit test.
For these sample reports are imported:
Such serverless report can be generated by invoking... NDepend.Console.exe $absolute-path-to-an-NDepend-project-file$...from your CI/CD running on Windows, Linux and Mac
You can generate the report using a trial license, a Build-Machine license |
|