Today we’re excited to announce the release of DCM 1.9.0!

New "Recommended" presets, 13 new rules and many more improved, dedicated GitHub Action to run DCM checks 🚀.

Let’s go on a quick journey together to explore all updates!

Today we’re excited to announce the release of DCM 1.8.0!

New command to simplify integrating DCM into existing projects, 17 new rules (2 for the Patrol testing library 🚀), support for dart_frog files for check-unused-code and check-unused-files, Gitlab reporter format for all existing commands and more 🔥.

And with this release, DCM crossed the 200 rule mark 🥳 (currently 215)!

Let’s go on a quick journey together to explore all updates!

Today we’re excited to announce the release of DCM 1.7.0!

Improved developer experience with DCM configuration, 25 new rules, 24 existing rules improved and more! 🚀

Let’s go on a quick journey together to explore all the new features!

Today with the introduction of the new Individuals version we're announcing the beginning of the free version sunset.

We want to thank every user and especially contributors for being with us during those 3 years (that's how old DCM plugin version is).

Today we’re excited to announce the release of DCM 1.6.0! New Individuals version, customizable formatter with project-wide configuration 😱, complete rewrite of IntelliJ plugin, new rules and more! 🚀

Let’s go on a quick journey together to explore all the new features!

Today we’re excited to announce the off-schedule release of DCM for Teams 1.5.0! In this version we added Dart 3.0 support to existing rules, 17 new rules for Dart 3.0-only features 🚀 and more!

Let’s go on a quick journey together to explore all the new features!

Today we’re excited to announce the release of DCM for Teams 1.4.0! In this version we added a new assist called "Wrap with ...", new command to find unused or missing dependencies, 22 new rules (and 5 of them are for the provider package 😱) and more!

Let’s go on a quick journey together to explore all the new features!

While the benefits of using static analysis tools such as DCM are quite obvious, integrating them into an existing project can be challenging due to the many possible warnings that need attention. That's why developers prefer to add such tools in the early stages of a project and quickly give up when it comes to old existing codebases.

But when it comes to DCM there are several tricks you can use to significantly reduce the time spend on its integration.

Considering that DCM Teams is a paid product, it's reasonable to raise the question of what value a company will receive from using it.

Let's calculate the return on investment (the ratio between income and costs) from using DCM in the development process. Hopefully it will help you fully realize the rationality behind it.

We all make mistakes, it's a part of our developer journey. But there are different tools that can help us in our way of creating great software that helps other people. DCM (formerly Dart Code Metrics) is a great example of such a tool. It is a static analysis tool that detects the quality and consistency issues helping you reduce the number of bugs and deliver results faster to your users.

But before we begin, what does static analysis actually mean? Well, static analysis is the automated analysis of source code without executing the application. It does not know anything about how the code will be run, what actual data it will work with, etc. A good example of such tools is the Dart analyzer (you probably have it running right now, even if you are no aware of it) and any tool that is a linter.

How does it work? It would take a book (or maybe even two) to describe it in details, but in short, it runs a separate process that is able to parse your code into set of tokens, build AST and validate it based on some rules.

And yes, dynamic analysis also exists 🙂.

Let's take a look at the various problems that you might encounter in your code and how DCM can help you find them together.