Question 1

How does CK compare to SonarQube for Java code metrics?

Accepted Answer

CK focuses on static analysis with a comprehensive, extensible metric suite for deep code quality insights, while SonarQube offers broader features like security analysis, quality gates, and IDE integration. CK is more lightweight and customizable for research or specific metric needs.

Question 2

How to integrate CK into a Maven project?

Accepted Answer

Add CK as a dependency in your pom.xml using the Maven Central artifact, then use the CK class programmatically; the README provides a snippet and references the Runner.java example for configuration and execution.

Question 3

What metrics does CK calculate for code cohesion?

Accepted Answer

CK includes LCOM, LCOM*, TCC, and LCC metrics to measure cohesion, with details on their calculations and limitations provided in the README, such as LCOM being less reliable and TCC focusing on direct connections between methods.

Question 4

Can CK analyze Java 17 or newer code?

Accepted Answer

CK uses Eclipse JDT set to Java 11 by default, but the README outlines steps to update it for newer versions by modifying AST parser settings and dependencies, though this requires manual intervention and testing.

Question 5

How accurate is CK's static analysis for method invocations?

Accepted Answer

CK's static analysis is generally accurate but has limitations; for example, the RFC metric may fail with method overloading, and it relies on source code parsing, so it might miss dynamic invocations via reflection or frameworks.

Question 6

How to extend CK with custom metrics?

Accepted Answer

Implement the ClassLevelMetric or MethodLevelMetric interface, then use the MetricsFinder utility for dynamic loading; the README describes the extensible architecture using design patterns like Visitor and Factory for easy integration.

ck

What is ck?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions