JArchitect
Quantify and manage Java code quality with LINQ-powered static analysis and dependency visualization.

The industry-standard PHP static analyzer for detecting code smells, complexity, and over-engineered architecture.
PHPMD (PHP Mess Detector) is a mature, high-performance static analysis tool designed to identify potential problems within PHP source code. Functioning as a PHP-equivalent to the Java tool PMD, it utilizes the PDepend engine to parse source files and apply a series of sophisticated rule-sets. In the 2026 landscape, PHPMD remains a critical component of the PHP ecosystem, positioned as the middle-layer of quality assurance between basic linting (PHP_CodeSniffer) and deep formal verification (PHPStan/Psalm). Its primary value proposition lies in its ability to detect 'soft' architectural failures—such as high Cyclomatic Complexity, N-Path Complexity, and the 'God Object' anti-pattern—which automated testing often misses. The tool is highly extensible, allowing engineering leads to define custom XML rulesets that enforce organizational coding standards. Architecturally, it operates via a Command Line Interface (CLI), making it natively compatible with modern containerized CI/CD pipelines. By 2026, its integration with AI-driven refactoring agents has solidified its role, providing the objective metrics required for AI to suggest safe code transformations without increasing technical debt.
Calculates the number of linearly independent paths through a program's source code using the PDepend engine.
Quantify and manage Java code quality with LINQ-powered static analysis and dependency visualization.
Enterprise-grade static code analysis for .NET and C++ powered by the ReSharper engine.
Automate code reviews and security analysis with zero-noise static analysis.
Visual software architecture and quality analysis for sustainable code health.
Verified feedback from the global deployment network.
Post queries, share implementation strategies, and help other users.
Measures the number of acyclic execution paths through a method, providing a deeper look than standard CC.
Detects high degrees of dependency between classes which indicates rigid architecture.
Scans for unused parameters, local variables, and private properties that clutter the memory footprint.
Includes rules for CamelCase, UpperCase, and other stylistic choices that might not be errors but affect readability.
Users can compose specific rules from different sets into a single project-wide XML file.
Allows developers to 'baseline' existing mess and only report new violations in incoming code.
Preventing developers from merging overly complex code that increases technical debt.
Registry Updated:2/7/2026
Quickly identifying the most dangerous parts of a legacy monolith for refactoring.
Ensuring new junior developers adhere to naming and complexity standards.