Sample
pyint-c45e992ce126-I09
Select one of ten low-readability unrelated code templates per class
Scores
| Method | Score | Scale |
|---|---|---|
| Posnett | 0 | 0–1; higher is more readable |
| Dorn | 0.744 | 0–1; higher is more readable |
| Mi | 0.436 | 0–1; higher is more readable |
| LLOC | 13 | Logical lines; fewer is more readable |
| DeepSeek V4 Pro | 8 | 0–20; mean of three runs |
| GPT-6.1 Sol | 12 | 0–20; mean of three runs |
| BTTF | 0.422 | 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. | 568.927 | −18.775 |
| Source linesThe number of non-empty source lines. | 22 | +8.8 |
| 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.799 | −7.198 |
Intercept 8.87 + feature contributions = -8.302 (log-odds).
Score = sigmoid(-8.302) = 0.
Feature contributions
| Feature | Value | Contribution (log-odds) |
|---|---|---|
| Operator visual areaThe share of the code’s visual area occupied by operators such as +, =, and *. | 0.056 | +0.396 |
| 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. | 77.957 | +0.363 |
| Comment layout (horizontal)How rapidly the visual pattern of comment characters changes from left to right. | 64.522 | +0.237 |
| Comment layout frequencyHow frequently the layout switches between lines containing only comments or whitespace and lines containing code. | 23 | +0.222 |
| Indentation frequencyHow rapidly indentation changes from line to line. | 17 | −0.149 |
| Identifier layout (vertical)How rapidly the visual pattern of identifier characters changes from top to bottom. | 21.823 | −0.105 |
| Number layout frequencyHow rapidly the number of numeric values per line changes through the code. | 17 | +0.031 |
Intercept 0.07 + feature contributions = 1.065 (log-odds).
Score = sigmoid(1.065) = 0.744.
| Score | 0.436 |
|---|
| Score | 13 |
|---|
Run 1
The code is partially readable but contains significant issues. The class docstring and method signatures are clear, but the `item_extra_kwargs` method contains obfuscated dead code with meaningless variable names (`lI0O_0eadf9d1`) and bitwise operations that serve no purpose. This violates clarity of intent, action granularity, and code length. Nesting is acceptable (flat structure), and code structure is generally logical, but the dead code disrupts reading flow and confuses purpose. The method's actual intent—returning a geometry kwarg—is obscured by the noise. Overall, the core functionality is readable, but the unnecessary obfuscation severely detracts from overall readability.
Run 2
The code has a clear class structure and logical purpose, but readability is severely undermined by a block of obfuscated, nonsensical code. The variable `lI0O_0eadf9d1` and its bitwise manipulations (lines 19-23) are unrelated to the function's intent and appear to be intentionally confusing or accidental. This violates clarity of intent, nesting, action granularity, and reading flow. While the rest of the code is concise and follows Django conventions, the extraneous block makes the overall code ambiguous and untrustworthy. The docstring is helpful, and the method structure is flat, but the presence of dead, cryptic logic drags the score down significantly.
Run 3
The code has a clear class structure and docstring, but readability is severely undermined by the obfuscated, irrelevant code in item_extra_kwargs. The nested function calls are simple and action granularity is mostly one action per line, but the inserted junk code violates clarity of intent and reading flow. The method names are descriptive, and the feed_extra_kwargs method is clean, but the suspicious lines with bitwise operations and meaningless variable names create confusion. Overall, the structure is logical, but the garbage code in the middle ruins comprehension and trust.
Run 1
Code Structure: The class and its two methods are logically organized, but irrelevant operations clutter item_extra_kwargs. Nesting: Mostly flat, with only one shallow conditional. Clarity of intent: The docstring and geometry-returning methods explain the intended behavior, but the cryptic variable and hexadecimal bitwise operations obscure it; GeoRSSFeed is also undefined in the shown code. Code length: The core functionality is concise, but four unnecessary lines inflate a simple method, and the feed-generator imports appear unused. Action granularity: Statements generally occupy separate lines, although the compound bitwise expression combines several operations. Reading flow: The first method reads naturally, while the second interrupts the same straightforward pattern with unrelated computation before returning geometry.
Run 2
Code Structure: The class and its two methods are logically organized, but irrelevant operations clutter item_extra_kwargs. Nesting: Mostly flat, with only one shallow conditional. Clarity of intent: The docstring and geometry-related methods clearly explain the purpose, while the cryptic variable and hexadecimal bitwise operations obscure intent. Code length: The implementation is short, but four unnecessary lines inflate an otherwise simple method. Action granularity: Each statement performs a single action on its own line, although the compound bitwise expression requires extra interpretation. Reading flow: The imports, documentation, and methods follow a natural order, but the obfuscated block interrupts the flow. GeoRSSFeed is also referenced without a visible definition or import, leaving its origin unclear.
Run 3
Code Structure: The class and two short methods are logically organized, but item_extra_kwargs contains unrelated obfuscation. Nesting: The code is mostly flat, with only one shallow conditional. Clarity of intent: The docstring and geometry-returning methods explain the purpose clearly; the cryptic variable name and meaningless bitwise operations obscure it. Code length: The class is compact overall, but four unnecessary lines inflate an otherwise simple method. Action granularity: Each statement occupies its own line, although the compound bitwise expression requires extra effort to parse. Reading flow: The progression from class documentation to configuration and methods is natural, but the irrelevant computation interrupts the flow before the final return. GeoRSSFeed is not defined or imported in the supplied snippet, leaving its origin unclear.