In Review

Planned

In Progress

Completed

Main Roadmap

Probably in a separate tab of the IDE plugins.

Support displaying metrics in IDE

Dmitry Zhifarsky

New command: license audit

Add folder structure verification to structure analyzer

Finish structure analyzer

Show percentage of the duplicated code

Add DCM indicator for VS Code status bar

More security-based lint rules (?)

Create a plugin to run DCM LSP server using Zed. This will require creating a Rust-based plugin and submitting it to the list of Zed plugins.

Support Zed

AFAIK, this does not work as expected.

Support transitive conditional exports for unused code detection

Introduce "diff report"

add new commands to request documentation with steps and examples for each rule/metric if an agent does not know how to fix an issue

analyzer

Improve DCM MCP server

Unused ignores are supported only for “dcm analyze”. We should support showing unused ignores for all commands.But probably via an additional CLI option.

Show unused ignores for other commands

Add a new tab to the project page that provides actionable suggestions to enabling new rules, applying fixes and so on.

admin-panel

Advisory

New command: secrets detection

Should generate a comprehensive HTML report of all issues / metrics + visualisation.Additionally, it should provide actionable steps on resolving those issues.

New command: audit

Probably similar to what analyzer has.For example, <code>path - severity - rule id</code>

Introduce new "compact" output format

It’s outdated and should be updated. Probably should include the number of lint and unused code issues.

Rework tech-debt metric

Integration for Background Agents

Introduce merged HTML reports when called from a monorepo root

Metrics documentation is currently lacking.We need to update all metrics and explain how they should be addressed.

website

Update documentation for metrics

Show what contributes to a metric in the HTML report

Update default values for metrics used in widgets analyzer

Update default values for metrics

Introduce new metrics

Some fixes can break the code (e.g., removal of unused parameters).Such fixes should be hidden by a separate flag (for both CLI and fix on save).

Introduce "unsafe fixes"

Support detecting duplicate test cases

Make baseline newline-independent

Add IDE code completion when editing DCM configuration / rules

New command: analyze assets

For example, new top-level config for disabling ignores for rules, metrics, unused code, etc. Plus, per-rule config, e.g. <code>disable-ignores: true</code>.

Add a config option to disable ignores for certain rules

Use “dcm run” instead of just “dcm analyze” and add all supported options to the action configuration.This will allow running other commands (e.g. unused code detection) via GitHub action.