Answers are grounded in this paper and cite their sources.
Quantifying code quality and architectural soundness remains a persistent challenge in modern software engineering. Existing tools often rely on isolated or superficial metrics, lacking architectural awareness and actionable insight. This article introduces code health meter (CHM), a fully automated, referentially transparent framework for quantitative and graph-theoretic code quality assessment. CHM statically analyzes source code and produces a 6D signature per module, capturing semantic complexity (maintainability index, Halstead volume, cyclomatic complexity), architectural structure (graph centrality, modularity), and redundancy (code duplication via Rabin–Karp fingerprinting). The framework is designed to be deterministic, explainable, and amenable to longitudinal analysis. We validate CHM on a 14,000-line JavaScript system by tracking its evolution across multiple versions. Our analysis reveals increasing architectural fragmentation, rising code duplication, and declining maintainability. These findings demonstrate CHM’s capability to surface actionable architectural insights, quantify technical debt, and support evidence-driven refactoring decisions. CHM bridges the gap between classical software metrics and architectural reasoning, offering a robust foundation for integrating automated code health monitoring into engineering workflows.
No takes yet. Share an insight, caveat, or question.
Ben Khalfallah Hela (2025) studied this question.
Synapse has enriched 10 related papers. Consider them for comparative context: