Sample
int-ebb46e485306-I05
Rewrite eligible decimal integer literals in hexadecimal notation
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 | 17 | 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 is well-structured with clear class responsibilities and conventional Spring patterns. Fields are grouped logically, methods are focused, and Javadoc is thorough. Nesting is shallow, with only one level in if/else branches and loops. Action granularity is generally one action per line, though a few lines combine operator concatenation. The resolveContainerFactory method reads naturally with explicit fallback logic. Minor readability weaknesses include some long method signatures and documentation that borders on verbose, plus occasional multi-concern lines in exception construction. Overall, the code is highly readable, maintainable, and follows idiomatic Spring style, making the intent clear to experienced Java developers.
Run 3
The code is well-structured and highly readable. It follows a logical organization with clear field declarations, standard getters/setters, and well-separated methods. Nesting is minimal—only the resolveContainerFactory method has a multi-branch conditional, but it remains flat and easy to follow. Intent is explicit through descriptive method and variable names, and Javadoc comments clarify non-obvious behaviors. Code length is appropriate; no method is unnecessarily long. Action granularity is mostly one action per line, though a few lines combine multiple operations (e.g., the registerListenerContainer call with resolveContainerFactory as an argument). Reading flow is natural: setup methods, lifecycle hook, registration logic, and a private supporting class. The only minor deductions are for the slightly dense conditional resolution logic and a few multi-action lines, but overall readability is strong.
Run 1
Code Structure: Logically separates configuration accessors, lifecycle initialization, factory resolution, endpoint registration, and the descriptor class. Nesting: Shallow loops and conditional branches keep control flow easy to follow. Clarity of intent: Descriptive names, Javadoc, nullability annotations, and explicit assertions explain responsibilities and requirements; the lifecycle-dependent startImmediately flag requires some contextual understanding. Code length: Implementation methods are concise, though extensive documentation and accessor boilerplate lengthen the class. Action granularity: Statements generally perform one action each, with multiline calls formatted clearly. Reading flow: Configuration leads naturally into initialization and registration logic. The factory fallback chain is straightforward, although redundant else branches after returns and implicit factory caching introduce minor reading friction.
Run 2
Code Structure: Well organized into configuration accessors, lifecycle registration, factory resolution, and a small descriptor class, with focused methods. Nesting: Shallow loops and conditionals keep control flow easy to follow. Clarity of intent: Descriptive names, Javadoc, nullability annotations, and assertions clearly communicate responsibilities and prerequisites; the state-dependent startup behavior requires some tracing. Code length: Implementation is concise, although extensive accessor documentation and boilerplate increase scanning time. Action granularity: Statements generally perform one action each, with sensible wrapping for longer calls. Reading flow: Consistent formatting and clear factory-selection precedence support natural reading, though understanding deferred versus immediate registration requires moving between methods. Overall, highly readable with minor verbosity and lifecycle-related complexity.
Run 3
Code Structure: Well-organized fields, configuration accessors, lifecycle methods, registration logic, and a small descriptor class separate responsibilities clearly. Nesting: Shallow loops and conditionals keep control flow easy to follow. Clarity of intent: Descriptive names, nullability annotations, assertions, and Javadoc explain endpoint registration and factory selection; the state-dependent startup behavior requires some cross-method tracking. Code length: Methods are concise, though extensive documentation and accessor boilerplate lengthen the class. Action granularity: Statements generally perform one action each, with readable wrapping for longer calls. Reading flow: Consistent formatting and logical grouping support natural reading, although factory resolution appears before the public registration methods, and mutable lifecycle state slightly complicates tracing execution.