Sample
pyint-05ac707aebdc-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.759 | 0–1; higher is more readable |
| Mi | 0.278 | 0–1; higher is more readable |
| LLOC | 19 | Logical lines; fewer is more readable |
| DeepSeek V4 Pro | 5 | 0–20; mean of three runs |
| GPT-6.1 Sol | 9.67 | 0–20; mean of three runs |
| BTTF | 0.469 | 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. | 572.355 | −18.888 |
| Source linesThe number of non-empty source lines. | 21 | +8.4 |
| 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.876 | −7.314 |
Intercept 8.87 + feature contributions = -8.931 (log-odds).
Score = sigmoid(-8.931) = 0.
Feature contributions
| Feature | Value | Contribution (log-odds) |
|---|---|---|
| Comment layout (horizontal)How rapidly the visual pattern of comment characters changes from left to right. | 90 | +0.648 |
| Operator visual areaThe share of the code’s visual area occupied by operators such as +, =, and *. | 0.044 | +0.51 |
| Comment layout frequencyHow frequently the layout switches between lines containing only comments or whitespace and lines containing code. | 22 | +0.257 |
| 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. | 90 | −0.147 |
| Identifier layout (vertical)How rapidly the visual pattern of identifier characters changes from top to bottom. | 20.824 | −0.119 |
| Number layout frequencyHow rapidly the number of numeric values per line changes through the code. | 21 | −0.061 |
| Indentation frequencyHow rapidly indentation changes from line to line. | 21 | −0.011 |
Intercept 0.07 + feature contributions = 1.148 (log-odds).
Score = sigmoid(1.148) = 0.759.
| Score | 0.278 |
|---|
| Score | 19 |
|---|
Run 1
The code has some readable elements like clear imports, type hints, and a sensible base class structure. However, it contains a deliberately obfuscated variable name (lI0O_1bbe088e) with a nonsensical bitwise operation that serves no purpose. This severely damages clarity of intent, action granularity, and reading flow. While the class definition and docstring are clear, the method body appears intentionally confusing and adds unnecessary complexity. The code length is acceptable but the strange variable manipulation makes it ambiguous why such logic exists. Overall structure is minimal but the obfuscated section prevents this from being considered truly readable. A developer would need extra time to understand why this code exists, defeating the purpose of readability.
Run 2
The code is almost entirely unreadable due to multiple severe issues. The variable name 'lI0O_1bbe088e' is obfuscated and meaningless, making the intent completely unclear. The calculation `0xdcbf - 0xdcbf` followed by a conditional bitwise operation that always results in 0 is pointless and confusing. Unused imports (hashlib, os, threading, etc.) add noise. The class structure is trivial but the method body contradicts the docstring by raising NotImplementedError for a callable hook. The code violates nearly all readability criteria: unclear intent, poor naming, unnecessary complexity, and dead code. Only the basic class definition and docstring provide any minimal structure, earning it a few points.
Run 3
The code is poorly readable. The class structure is simple, but the __call__ method is confusing. It contains dead code: a variable lI0O_1bbe088e is initialized to zero, then assigned via a conditional that always yields zero. This serves no purpose and obscures intent. The method then raises NotImplementedError, which is clear, but the preceding lines make it ambiguous. Naming (lI0O_1bbe088e) is opaque. Whitespace and imports are fine, but overall the function's purpose is buried under useless operations. Action granularity is poor: multiple meaningless operations precede the actual logic. Reading flow is disrupted by the dead code. Code length is unnecessarily long for what should be a one-line raise. Clarity of intent is low because the raise is clear but spoiled by clutter. Structure and nesting are acceptable, but other criteria severely reduce readability.
Run 1
Code Structure: Imports and the base class are logically organized, but numerous unused imports and irrelevant statements add clutter. Nesting: The code is flat, with no deeply nested control flow. Clarity of intent: The class docstring and NotImplementedError clearly establish an authentication interface, but the cryptic variable name and pointless arithmetic obscure the method's simple purpose. Code length: The snippet is short but unnecessarily padded with unused imports and computations. Action granularity: Each statement occupies its own line, although the conditional assignment combines several operations without benefit. Reading flow: The conventional imports-to-class-to-method progression is natural, but the unrelated assignments interrupt the direct flow to the exception.
Run 2
Code Structure: Imports and the base class are logically organized, but numerous unused imports and irrelevant statements introduce clutter. Nesting: The code is flat, with no deeply nested control flow. Clarity of intent: The class docstring and NotImplementedError clearly indicate an authentication interface, but the opaque variable name, hexadecimal subtraction, and redundant bitwise expression obscure the method's purpose. Code length: The snippet is short, yet unnecessarily long for its simple function because of unused imports and meaningless assignments. Action granularity: Each statement occupies its own line, although the conditional assignment combines several operations unnecessarily. Reading flow: The progression from imports to class to method is natural, but unrelated calculations interrupt the otherwise straightforward path to raising NotImplementedError.
Run 3
Code Structure: Imports and a small base class provide recognizable organization, but numerous unused imports and irrelevant assignments add clutter. Nesting: There is no deep nesting; the inline conditional adds only minor complexity. Clarity of intent: The class name, docstring, method signature, and exception clearly establish an authentication interface, but the opaque variable name and pointless arithmetic obscure the method body. Code length: The actual interface is concise, yet most imports and both assignments are unnecessary in this snippet. Action granularity: Each statement occupies its own line, although the second assignment combines comparison, branching, and bitwise operations. Reading flow: The overall progression is conventional, but distracting computations interrupt the direct path from the method declaration to the NotImplementedError.