Sample
Dorn/python/117
Human rating uses the original dataset scale.
Scores
| Method | Score | Scale | Dataset rank (0–100) |
|---|---|---|---|
| Posnett | 0.133 | 0–1; higher is more readable | 74.9Δ 10.0 |
| Dorn | 0.435 | 0–1; higher is more readable | 35.9Δ 29.0 |
| Mi | 0.631 | 0–1; higher is more readable | 68.0Δ 3.1 |
| LLOC | 8 | Logical lines; fewer is more readable | 63.9Δ 1.0 |
| DeepSeek V4 Pro | 10.67 | 0–20; mean of three runs | 44.4Δ 20.5 |
| GPT-6.1 Sol | 14 | 0–20; mean of three runs | 41.4Δ 23.5 |
| BTTF | 0.528 | 0–1; higher is more readable | 52.6Δ 12.3 |
| Human | 3.51 | 1–5; original rating | 64.9 |
Views
Select the downloaded ZIP or its extracted folder. Files stay in your browser.
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. | 255.412 | −8.429 |
| 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.213 | −6.32 |
| Source linesThe number of non-empty source lines. | 10 | +4 |
Intercept 8.87 + feature contributions = -1.879 (log-odds).
Score = sigmoid(-1.879) = 0.133.
Feature contributions
| Feature | Value | Contribution (log-odds) |
|---|---|---|
| Comment layout (horizontal)How rapidly the visual pattern of comment characters changes from left to right. | 0 | −0.804 |
| Comment layout frequencyHow frequently the layout switches between lines containing only comments or whitespace and lines containing code. | 11 | +0.647 |
| Number layout frequencyHow rapidly the number of numeric values per line changes through the code. | 1 | +0.398 |
| Indentation frequencyHow rapidly indentation changes from line to line. | 10 | −0.391 |
| Operator visual areaThe share of the code’s visual area occupied by operators such as +, =, and *. | 0.064 | +0.322 |
| Identifier layout (vertical)How rapidly the visual pattern of identifier characters changes from top to bottom. | 9.871 | −0.272 |
| 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. | 92 | −0.232 |
Intercept 0.07 + feature contributions = -0.263 (log-odds).
Score = sigmoid(-0.263) = 0.435.
| Score | 0.631 |
|---|
| Score | 8 |
|---|
Run 1
The code is generally readable but has several issues. The structure is logical with a clear flow from directory check to file listing, but the triple nesting increases cognitive load. Intent is mostly clear, though the relationship between Release folders and bug fixes could be clearer. The code is concise but has a syntax error in the URL string (missing closing quote) and uses an undefined function `listPath`. The path check and listdir are on separate lines, but the nested print and function call are combined in one block. The reading flow is natural but disrupted by the missing quote and undefined function. The HTML output is embedded directly in Python logic, mixing concerns. Overall, it's readable enough to follow the basic purpose, but the nesting depth, potential errors, and mixed responsibilities lower its readability score.
Run 2
The code performs a narrow task but suffers from readability issues. It uses nested conditionals (if-foreach-if-if) which increases cognitive load, though nesting depth is moderate. Intent is somewhat clear—it lists bug fix releases—but the literal string 'Release' and the hardcoded URL are ambiguous magic values. The function name 'listPath' is vague and does not convey what it does. There is mixed abstraction: HTML output is embedded directly alongside filesystem logic. The code is concise, but the final print statement spans a long line with an HTML tag and an external URL, hurting readability. The flow feels natural top-to-bottom, but the overall organization could be improved by separating HTML generation from file traversal and using clearer naming and constants.
Run 3
The code is relatively simple but lacks clarity due to poor naming and ambiguous intent. Structure is mostly logical but the conditional nesting could be improved for readability. The variable 'fname' is not descriptive, and the hardcoded HTML link with a typo (missing closing quote) hurts clarity. Actions are mostly one per line, which is good, but the nested if-statements make the flow somewhat harder to follow. The code's purpose (generating HTML for bug fixes) is not immediately evident without surrounding context. No comments or docstrings explain the function's role. The link syntax error also shows a lack of care. Overall, it's readable enough for a short script, but improvements in naming, nesting, and error correction would help.
Run 1
Code Structure: Logically groups directory filtering and processing, followed by a navigation link. Nesting: Four indentation levels make a small operation more cumbersome to follow. Clarity of intent: Finding Release directories is clear, but listPath's behavior and the special treatment of '.' are unexplained. Code length: Concise, with no obvious unnecessary statements. Action granularity: Each line performs one primary action. Reading flow: The sequence from listing to filtering to processing is natural, though the final link is separate from the conditional work. Abbreviated names such as fname slightly reduce clarity. Legacy print syntax and the missing closing quote in the HTML href add minor reading friction.
Run 2
Code Structure: The directory filtering and processing are logically grouped. Nesting: Four nested control-flow levels make this short snippet harder to scan; guard clauses could flatten it. Clarity of intent: Finding Release directories and listing their contents is reasonably clear, though listPath's behavior is unspecified and fname names a directory. Code length: Concise, with little unnecessary code. Action granularity: Each line performs one main action. Reading flow: The sequence from filtering to printing and listing is natural, followed by a download link. However, the link's href lacks a closing quotation mark, obscuring the intended HTML, and legacy Python print syntax reduces familiarity for modern readers.
Run 3
Code Structure: Logically organized into directory traversal, filtering, and recursive processing, followed by a navigation link. Nesting: Four indentation levels make a short snippet harder to scan; guard clauses could flatten it. Clarity of intent: Release-directory processing is understandable, but listPath and fname provide limited semantic detail. The malformed HTML link obscures the intended output. Code length: Concise, with no substantial redundancy. Action granularity: Each statement performs one clear action. Reading flow: Execution proceeds naturally from filtering to output and recursion, although nested conditions interrupt the flow.