Sample
Human rating uses the original dataset scale.
| Method | Score | Scale | Dataset rank (0–100) |
|---|---|---|---|
| Posnett | 0.326 | 0–1; higher is more readable | 78.8Δ 15.6 |
| Dorn | 0.995 | 0–1; higher is more readable | 99.2Δ 4.7 |
| Mi | 0.732 | 0–1; higher is more readable | 90.0Δ 4.5 |
| LLOC | 1 | Logical lines; fewer is more readable | 97.9Δ 3.5 |
| DeepSeek V4 Pro | 8 | 0–20; mean of three runs | 29.4Δ 65.0 |
| GPT-6.1 Sol | 17.33 | 0–20; mean of three runs | 86.5Δ 7.9 |
| BTTF | 0.86 | 0–1; higher is more readable | 99.2Δ 4.7 |
| Human | 4.11 | 1–5; original rating | 94.4 |
Loading feature diagnosis…
| 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. | 209.215 | −6.904 |
| 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.46 | −6.69 |
| Source linesThe number of non-empty source lines. | 10 | +4 |
Intercept 8.87 + feature contributions = -0.724 (log-odds).
Score = sigmoid(-0.724) = 0.326.
| Feature | Value | Contribution (log-odds) |
|---|---|---|
| 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. | 0 | +3.665 |
| Comment layout frequencyHow frequently the layout switches between lines containing only comments or whitespace and lines containing code. | 1 | +1.001 |
| Operator visual areaThe share of the code’s visual area occupied by operators such as +, =, and *. | 0 | +0.942 |
| Indentation frequencyHow rapidly indentation changes from line to line. | 1 | −0.703 |
| Identifier layout (vertical)How rapidly the visual pattern of identifier characters changes from top to bottom. | 0 | −0.41 |
| Number layout frequencyHow rapidly the number of numeric values per line changes through the code. | 1 | +0.398 |
| Comment layout (horizontal)How rapidly the visual pattern of comment characters changes from left to right. | 68 | +0.293 |
Intercept 0.07 + feature contributions = 5.256 (log-odds).
Score = sigmoid(5.256) = 0.995.
| Score | 0.732 |
|---|
| Score | 1 |
|---|
The code demonstrates clear intent through comments, but all lines are commented out, making the code appear as configuration documentation rather than executable logic. Structure is flat and simple; nesting is nonexistent. However, the code's readability is limited because every line is a comment, obscuring whether these are intended as active settings or examples. Action granularity is clear—one setting per line—but the lack of active code reduces its functional clarity. Reading flow is natural but redundant since all lines begin with '#'.
This code consists entirely of commented-out configuration options with no active logic or structure. There is no meaningful organization, nesting, or action to evaluate. The intent appears to be documentation of unused settings, but without context or actual code, it is ambiguous and provides no functional value. It is concise (even empty), but the reading flow is unnatural as a code snippet because it only contains disabled lines. Action granularity is irrelevant. Overall, it is not readable as working code and would score very low for practical readability.
The code consists entirely of commented-out configuration settings with no active logic. While the structure is flat and each line is concise, readability is limited by the absence of context: there is no indication of what system uses these settings, no grouping or section headers, and no explanation of how they interact. The intent is partially clear from variable names (e.g., 'html_use_index'), but the repeated 'html_' prefix becomes redundant. Reading flow is natural but monotonous. Code length is minimal, yet the snippet lacks the surrounding configuration file context that would make it meaningful.
Code Structure: Related HTML configuration options are logically grouped and separated by blank lines. Nesting: There is no nesting, making the snippet easy to scan. Clarity of intent: Descriptive option names and explanatory comments communicate purpose, though html_additional_pages lacks an explanation and all settings are inactive. Code length: Concise, with little unnecessary content. Action granularity: Each line contains a single setting or explanation. Reading flow: Consistent comment-setting pairs create a natural flow, although the first option does not follow that pattern.
Code Structure: Related HTML configuration options are logically grouped and separated by blank lines. Nesting: There is no nesting, making the snippet easy to scan. Clarity of intent: Descriptive option names and explanatory comments communicate purpose, although all settings are commented out and the first option lacks an explanation. Code length: The snippet is concise, with only minor repetition in the comments. Action granularity: Each line contains one setting or one explanatory comment. Reading flow: Consistent formatting and straightforward ordering provide a natural flow, though distinguishing explanatory comments from disabled settings requires slight attention.
Code Structure: Configuration options are logically organized and separated by blank lines. Nesting: None, making the snippet easy to scan. Clarity of intent: Descriptive option names and explanatory comments clarify their purposes, although all settings are commented out and the first lacks an explanation. Code length: Concise, with little unnecessary content. Action granularity: Each line contains a single setting or comment. Reading flow: Consistent comment-setting pairs provide a natural flow; distinguishing explanatory comments from disabled settings would improve readability.