Sample
int-400ead167844-I11
Split eligible integer literals into pairs of short-named intermediate variables
Scores
| Method | Score | Scale |
|---|---|---|
| Posnett | 0 | 0–1; higher is more readable |
| Scalabrino | 0.78 | 0–1; higher is more readable |
| Dorn | 0.813 | 0–1; higher is more readable |
| Mi | 0.405 | 0–1; higher is more readable |
| LLOC | 53 | Logical lines; fewer is more readable |
| DeepSeek V4 Pro | 16.67 | 0–20; mean of three runs |
| GPT-6.1 Sol | 18 | 0–20; mean of three runs |
| BTTF | 0.595 | 0–1; higher is more readable |
Views
Loading feature diagnosis…
Source regions
Feature contributions
Feature contributions
| Feature | Value | Contribution (log-odds) |
|---|---|---|
| Halstead volumeHow much symbolic information the code contains. It combines the total number of operators and values with the number of distinct ones. | 4066.04 | −134.179 |
| Source linesThe number of non-empty source lines. | 185 | +74 |
| Byte entropyHow varied the bytes in the source text are. Repeated bytes give a lower value; a more even mixture gives a higher value. | 4.891 | −7.336 |
Intercept 8.87 + feature contributions = -58.645 (log-odds).
Score = sigmoid(-58.645) = 0.
| Score | 0.78 |
|---|
Feature contributions
| Feature | Value | Contribution (log-odds) |
|---|---|---|
| Comment layout frequencyHow frequently the layout switches between lines containing only comments or whitespace and lines containing code. | 186 | −5.549 |
| Indentation frequencyHow rapidly indentation changes from line to line. | 136 | +3.967 |
| Identifier layout (vertical)How rapidly the visual pattern of identifier characters changes from top to bottom. | 184.85 | +2.174 |
| Identifier layout (horizontal)How rapidly the visual pattern of identifier characters changes from left to right. It measures spatial frequency, not the meaning of the names. | 111.962 | −1.077 |
| Comment layout (horizontal)How rapidly the visual pattern of comment characters changes from left to right. | 111.962 | +1.002 |
| Operator visual areaThe share of the code’s visual area occupied by operators such as +, =, and *. | 0.047 | +0.488 |
| Number layout frequencyHow rapidly the number of numeric values per line changes through the code. | 1 | +0.398 |
Intercept 0.07 + feature contributions = 1.472 (log-odds).
Score = sigmoid(1.472) = 0.813.
| Score | 0.405 |
|---|
| Score | 53 |
|---|
Run 1
The code is well-structured with clear separation of concerns: configuration, registration, and descriptor storage. The class has a single responsibility and uses clear, descriptive method names. Nesting is minimal—only one level in the registerEndpoint and resolveContainerFactory methods. Javadoc comments effectively explain non-obvious behavior (like deferred factory resolution). The code is concise despite its length, with each method doing one clear thing. However, slightly reduced readability comes from some methods having multiple responsibilities (resolveContainerFactory has a factory caching side effect), and the registerAllEndpoints method triggers a side effect (setting startImmediately) that might not be obvious at first glance. The field ordering and grouping is logical. The use of separate descriptor class adds clarity. Overall, the code follows clean, maintainable patterns typical of well-written Spring configuration classes.
Run 2
The code demonstrates excellent readability. It follows a logical structure with fields grouped at the top, followed by setter/getter methods, lifecycle methods (afterPropertiesSet), and helper methods. Nesting is minimal with only one level in the main loops and conditionals. Intent is clearly conveyed through descriptive method names and comprehensive Javadoc comments. The code is concise without sacrificing clarity - each method serves a single purpose. Action granularity is appropriate with one main action per line, though line wrapping in resolveContainerFactory and registerListenerContainer slightly interrupts flow. Reading flow is natural, moving from configuration setters to the registration logic. Minor deductions include verbose Javadocs that could be trimmed and some line-wrapping that breaks visual continuity.
Run 3
The code is generally readable and follows a clear structure, with separated fields, setters, and business logic. The nesting is minimal, and each method has a single responsibility, contributing to clear action granularity. Javadocs and meaningful method/class names improve clarity of intent. However, some methods like resolveContainerFactory use multiple else-if branches and include comments that could be simplified, and the overall length is somewhat verbose due to boilerplate getters/setters and documentation. The reading flow is mostly natural, but the mixture of configuration logic and field declarations with inline comments slightly reduces smoothness. Overall, the code is maintainable but could be slightly more concise.
Run 1
Code Structure: Logically separates configuration accessors, lifecycle initialization, factory resolution, endpoint registration, and the descriptor class. Nesting: Shallow conditionals and a simple loop keep control flow easy to follow. Clarity of intent: Descriptive names, Javadoc, nullability annotations, and explicit assertions explain responsibilities and requirements; deferred registration and cached factory lookup require some state tracking. Code length: Implementation methods are concise, though extensive documentation and accessor boilerplate increase overall length. Action granularity: Statements generally perform one action each, with longer calls wrapped cleanly across lines. Reading flow: Configuration naturally precedes initialization and registration behavior, and factory fallback priority is explicit. Minor drawbacks include redundant else branches after returns and lifecycle behavior distributed across several methods.
Run 2
Code Structure: Well-organized fields, configuration accessors, lifecycle methods, registration logic, and a small descriptor class separate responsibilities clearly. Nesting: Shallow loops and conditional branches keep control flow easy to follow. Clarity of intent: Descriptive names, Javadoc, nullability annotations, and explicit assertions explain configuration requirements and registration behavior. Code length: Methods are concise, although extensive accessor documentation and boilerplate increase overall length. Action granularity: Statements generally perform one action each; wrapped calls preserve readability. Reading flow: Factory resolution follows a clear precedence, and endpoint registration naturally distinguishes deferred from immediate startup. Minor drawbacks include lifecycle behavior spread across several methods, mutable factory caching inside a resolution method, and configuration methods separating related operational logic.
Run 3
Code Structure: Configuration accessors, lifecycle registration, factory resolution, and the descriptor class are logically separated into focused methods. Nesting: Control flow is shallow, with a simple loop and straightforward conditional branches. Clarity of intent: Descriptive names, Javadoc, nullability annotations, and explicit assertions make responsibilities and expectations clear; the startImmediately flag requires some lifecycle context. Code length: Methods are concise, though extensive documentation and accessor boilerplate increase the overall reading length. Action granularity: Statements generally perform one action each, and multiline calls remain easy to follow. Reading flow: Consistent formatting and a clear factory-selection precedence support natural reading, although configuration methods occupy substantial space before the core behavior, and registration logic is split across lifecycle and public entry points.