Public report of XiaoMi/MiNLP, published 14 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 14 November 2026, 14:34 UTC · Survey ID cd_c469557117ce471e84efc8ae5f9d803d
XiaoMi/MiNLP
Measured 14 November 2026, 14:34 UTC, at code version 3745b4a
CAI scoreWeak
CriticalWeakAdequateStrongExemplary
Down 1 since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A small codebase: 14,940 lines of product code in 6 projects, tests not counted · Estimated rebuild effort: under 0.1 person-years · Weakest lens: Accessibility, 17
Findings by how serious they are
9 critical170 serious91 minor
12 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
14 November 2026, 14:34 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that
implements it, and today the Canine Code Analyzer is the only one that does.
The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
56of 56 dimensions measured by tools.
257of 270 findings point to an exact file and line, so you can open each one in the code. The other 13 concern the repository as a whole, such as missing documentation.
56dimensions across 7 lenses, read from 14,940 lines of product code in 6 projects.
XiaoMi/MiNLP falls short of our standard for production, held back most by its Accessibility lens, the interface's usability with a keyboard or assistive technology. It scores 38 out of 100 and is rated Weak, and five of its nine critical findings are security problems in the build pipeline.
Accessibility, at 17, is the weakest lens and counts most in the score. The best first steps are labelling the form fields and buttons and fixing focus, motion and contrast, each worth about 11 points. Raising Accessibility to 70 would lift the score to about 56.
Four pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. One pipeline step runs a download nobody checks, and one button or link has no name a screen reader can say. Pinning each tool to an exact version, checking the download against a checksum and naming the buttons and links would close these risks. The two pages that don't say their language need their language set.
The product code is 14,940 lines, about €14,000 to rebuild. Two of our security checks couldn't finish, among them the one for known security holes in its packages, so those results are missing, not clean passes.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
Code Duplication · Edited copy of a member (26 corresponding lines) duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/engine/VarcharLookup.scala
Code Duplication · Edited copy of a member (23 corresponding lines) duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/task/PlaceExtractor.scala
Code Duplication · Edited copy of a member (14 corresponding lines) duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/numeral/Prods.scala
Code Duplication · Edited copy of a member (8 corresponding lines) duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/Types.scala
Code Duplication · Edited copy of a member (9 corresponding lines) duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/engine/Engine.scala
Code Duplication · Edited copy of a member (7 corresponding lines) duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/helper/HolidayProvider.scala
We compare every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 192 findings
These 192 critical or serious findings were in the previous survey, on 26 October 2026, and are gone from this one. The first 100 are listed here.
Visual & motion safety · Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/index.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/index.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/index.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/index.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/index.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/index.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/index.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/index.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/index.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/index.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/index.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/index.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/index.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/index.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/index.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/index.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/index.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/index.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/index.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/index.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/index.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/index.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/index.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/index.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/index.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/index.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/index.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/index.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/index.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/index.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/index.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/index.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/index.css
Visual & motion safety · Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/main.css
Visual & motion safety · Animation without a prefers-reduced-motion guard duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css
Visual & motion safety · Animation without a prefers-reduced-motion guard duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css
Visual & motion safety · Animation without a prefers-reduced-motion guard duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css
Visual & motion safety · Animation without a prefers-reduced-motion guard duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css
Visual & motion safety · Animation without a prefers-reduced-motion guard duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css
Visual & motion safety · Animation without a prefers-reduced-motion guard duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css
Visual & motion safety · Animation without a prefers-reduced-motion guard duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css
Visual & motion safety · Animation without a prefers-reduced-motion guard duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css
Visual & motion safety · Animation without a prefers-reduced-motion guard duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css
Visual & motion safety · Animation without a prefers-reduced-motion guard duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css
Visual & motion safety · Animation without a prefers-reduced-motion guard duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css
Visual & motion safety · Animation without a prefers-reduced-motion guard duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css
Visual & motion safety · Animation without a prefers-reduced-motion guard duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css
Visual & motion safety · Animation without a prefers-reduced-motion guard duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css
Visual & motion safety · Animation without a prefers-reduced-motion guard duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css
Visual & motion safety · Animation without a prefers-reduced-motion guard duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css
Visual & motion safety · Animation without a prefers-reduced-motion guard duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css
Visual & motion safety · Animation without a prefers-reduced-motion guard duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css
Visual & motion safety · Animation without a prefers-reduced-motion guard duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css
Visual & motion safety · Animation without a prefers-reduced-motion guard duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css
Visual & motion safety · Animation without a prefers-reduced-motion guard duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css
Visual & motion safety · Animation without a prefers-reduced-motion guard duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css
Visual & motion safety · Animation without a prefers-reduced-motion guard duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css
Visual & motion safety · Animation without a prefers-reduced-motion guard duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css
Visual & motion safety · Animation without a prefers-reduced-motion guard duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css
Visual & motion safety · Animation without a prefers-reduced-motion guard duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css
Visual & motion safety · Animation without a prefers-reduced-motion guard duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css
Visual & motion safety · Animation without a prefers-reduced-motion guard duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css
Visual & motion safety · Animation without a prefers-reduced-motion guard duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css
Visual & motion safety · Animation without a prefers-reduced-motion guard duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css
Visual & motion safety · Animation without a prefers-reduced-motion guard duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css
Visual & motion safety · Animation without a prefers-reduced-motion guard duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css
Visual & motion safety · Animation without a prefers-reduced-motion guard duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css
Visual & motion safety · Animation without a prefers-reduced-motion guard duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css
Visual & motion safety · Animation without a prefers-reduced-motion guard duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css
Visual & motion safety · Animation without a prefers-reduced-motion guard duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css
Visual & motion safety · Animation without a prefers-reduced-motion guard duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css
Visual & motion safety · Animation without a prefers-reduced-motion guard duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css
Visual & motion safety · Animation without a prefers-reduced-motion guard duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css
Rebuild cost: about €14,000 · Estimate
Cost to rebuild
€4,800 to €24,000, for 80 to 253 hours of work, under 0.1 person-years for one engineer
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 38. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Small: 14,940 lines of product code
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
Raises the score by about 11 points · Medium effort · Forms & labels
2
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Raises the score by about 7 points · Medium effort · Page structure
Diagnosis: what the measurements show together
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €14,000 to build again, under 0.1 person-years of work. Its weakest lens is Accessibility, at 17 (Critical). Accessibility is about whether the interface is built so that everyone can use it, including people who can't see the screen or can't use a mouse. Because the weakest lens counts most in the score, work on Accessibility also moves the score most.
Based on: the rebuild estimate · the Accessibility grade · how much each lens counts
What to do: Start with the Accessibility actions in Top priorities.
If you do one thing first · First action
Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label. Of all the actions in this report, it raises the score most for the work it takes: about 11 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 7.4 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 2% to 5% on every change.
How this is estimated: It rests on an assumption of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4)
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
68 modules, with 126 dependencies between them. One loop runs through 9 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 28 more are left out to keep it readable.
Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
dimension.time.Types uses dimension.time.enums, so a change to dimension.time.enums can break dimension.time.Types, while a change to dimension.time.Types can't break dimension.time.enums.
Position
Below the diagonal: dimension.time.Types uses a module listed above it, which is the healthy direction.
dimension.time uses dimension.time.form, so a change to dimension.time.form can break dimension.time, while a change to dimension.time can't break dimension.time.form.
Position
Below the diagonal: dimension.time uses a module listed above it, which is the healthy direction.
dimension.time uses dimension.time.enums, so a change to dimension.time.enums can break dimension.time, while a change to dimension.time can't break dimension.time.enums.
Position
Below the diagonal: dimension.time uses a module listed above it, which is the healthy direction.
dimension.time uses dimension.time.Types, so a change to dimension.time.Types can break dimension.time, while a change to dimension.time can't break dimension.time.Types.
Position
Below the diagonal: dimension.time uses a module listed above it, which is the healthy direction.
9→10 dimension.time uses dimension.time.predicatespart of a loop✕
Connections
2 pairs of types, where a type in dimension.time uses a type in dimension.time.predicates.
dimension.time uses dimension.time.predicates, so a change to dimension.time.predicates can break dimension.time, while a change to dimension.time can't break dimension.time.predicates.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
dimension.time.predicates uses dimension.time.enums, so a change to dimension.time.enums can break dimension.time.predicates, while a change to dimension.time.predicates can't break dimension.time.enums.
Position
Below the diagonal: dimension.time.predicates uses a module listed above it, which is the healthy direction.
dimension.time.predicates uses dimension.time, so a change to dimension.time can break dimension.time.predicates, while a change to dimension.time.predicates can't break dimension.time.
Position
Below the diagonal: dimension.time.predicates uses a module listed above it, which is the healthy direction.
dimension uses dimension.place.Types, so a change to dimension.place.Types can break dimension, while a change to dimension can't break dimension.place.Types.
Position
Below the diagonal: dimension uses a module listed above it, which is the healthy direction.
dimension uses dimension.time.enums, so a change to dimension.time.enums can break dimension, while a change to dimension can't break dimension.time.enums.
Position
Below the diagonal: dimension uses a module listed above it, which is the healthy direction.
dimension uses dimension.time.Types, so a change to dimension.time.Types can break dimension, while a change to dimension can't break dimension.time.Types.
Position
Below the diagonal: dimension uses a module listed above it, which is the healthy direction.
dimension uses dimension.time.predicates, so a change to dimension.time.predicates can break dimension, while a change to dimension can't break dimension.time.predicates.
Position
Below the diagonal: dimension uses a module listed above it, which is the healthy direction.
dimension uses com.xiaomi.duckling, so a change to com.xiaomi.duckling can break dimension, while a change to dimension can't break com.xiaomi.duckling.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
com.xiaomi.duckling uses dimension, so a change to dimension can break com.xiaomi.duckling, while a change to com.xiaomi.duckling can't break dimension.
Position
Below the diagonal: com.xiaomi.duckling uses a module listed above it, which is the healthy direction.
dimension.age uses dimension.numeral, so a change to dimension.numeral can break dimension.age, while a change to dimension.age can't break dimension.numeral.
Position
Below the diagonal: dimension.age uses a module listed above it, which is the healthy direction.
dimension.bloodtype uses dimension, so a change to dimension can break dimension.bloodtype, while a change to dimension.bloodtype can't break dimension.
Position
Below the diagonal: dimension.bloodtype uses a module listed above it, which is the healthy direction.
dimension.constellation uses dimension, so a change to dimension can break dimension.constellation, while a change to dimension.constellation can't break dimension.
Position
Below the diagonal: dimension.constellation uses a module listed above it, which is the healthy direction.
dimension.constellation uses Types, so a change to Types can break dimension.constellation, while a change to dimension.constellation can't break Types.
Position
Below the diagonal: dimension.constellation uses a module listed above it, which is the healthy direction.
dimension.duplicate uses dimension, so a change to dimension can break dimension.duplicate, while a change to dimension.duplicate can't break dimension.
Position
Below the diagonal: dimension.duplicate uses a module listed above it, which is the healthy direction.
dimension.multichar uses dimension, so a change to dimension can break dimension.multichar, while a change to dimension.multichar can't break dimension.
Position
Below the diagonal: dimension.multichar uses a module listed above it, which is the healthy direction.
dimension.numeral.fraction uses dimension, so a change to dimension can break dimension.numeral.fraction, while a change to dimension.numeral.fraction can't break dimension.
Position
Below the diagonal: dimension.numeral.fraction uses a module listed above it, which is the healthy direction.
dimension.numeral.fraction uses Types, so a change to Types can break dimension.numeral.fraction, while a change to dimension.numeral.fraction can't break Types.
Position
Below the diagonal: dimension.numeral.fraction uses a module listed above it, which is the healthy direction.
dimension.numeral.multiple uses dimension, so a change to dimension can break dimension.numeral.multiple, while a change to dimension.numeral.multiple can't break dimension.
Position
Below the diagonal: dimension.numeral.multiple uses a module listed above it, which is the healthy direction.
dimension.numeral.multiple uses Types, so a change to Types can break dimension.numeral.multiple, while a change to dimension.numeral.multiple can't break Types.
Position
Below the diagonal: dimension.numeral.multiple uses a module listed above it, which is the healthy direction.
dimension.numeral.seq uses dimension, so a change to dimension can break dimension.numeral.seq, while a change to dimension.numeral.seq can't break dimension.
Position
Below the diagonal: dimension.numeral.seq uses a module listed above it, which is the healthy direction.
dimension.place uses dimension.place.Types, so a change to dimension.place.Types can break dimension.place, while a change to dimension.place can't break dimension.place.Types.
Position
Below the diagonal: dimension.place uses a module listed above it, which is the healthy direction.
dimension.rating uses dimension.numeral, so a change to dimension.numeral can break dimension.rating, while a change to dimension.rating can't break dimension.numeral.
Position
Below the diagonal: dimension.rating uses a module listed above it, which is the healthy direction.
dimension.time.date uses dimension.time, so a change to dimension.time can break dimension.time.date, while a change to dimension.time.date can't break dimension.time.
Position
Below the diagonal: dimension.time.date uses a module listed above it, which is the healthy direction.
dimension.time.date uses dimension, so a change to dimension can break dimension.time.date, while a change to dimension.time.date can't break dimension.
Position
Below the diagonal: dimension.time.date uses a module listed above it, which is the healthy direction.
dimension.time.duration uses dimension, so a change to dimension can break dimension.time.duration, while a change to dimension.time.duration can't break dimension.
Position
Below the diagonal: dimension.time.duration uses a module listed above it, which is the healthy direction.
dimension.time.duration uses Types, so a change to Types can break dimension.time.duration, while a change to dimension.time.duration can't break Types.
Position
Below the diagonal: dimension.time.duration uses a module listed above it, which is the healthy direction.
dimension.time.grain uses dimension, so a change to dimension can break dimension.time.grain, while a change to dimension.time.grain can't break dimension.
Position
Below the diagonal: dimension.time.grain uses a module listed above it, which is the healthy direction.
dimension.time.helper uses dimension.time.form, so a change to dimension.time.form can break dimension.time.helper, while a change to dimension.time.helper can't break dimension.time.form.
Position
Below the diagonal: dimension.time.helper uses a module listed above it, which is the healthy direction.
dimension.time.helper uses engine.LexiconLookup, so a change to engine.LexiconLookup can break dimension.time.helper, while a change to dimension.time.helper can't break engine.LexiconLookup.
Position
Below the diagonal: dimension.time.helper uses a module listed above it, which is the healthy direction.
dimension.time.helper uses dimension.time.enums, so a change to dimension.time.enums can break dimension.time.helper, while a change to dimension.time.helper can't break dimension.time.enums.
Position
Below the diagonal: dimension.time.helper uses a module listed above it, which is the healthy direction.
dimension.time.helper uses dimension.time.Types, so a change to dimension.time.Types can break dimension.time.helper, while a change to dimension.time.helper can't break dimension.time.Types.
Position
Below the diagonal: dimension.time.helper uses a module listed above it, which is the healthy direction.
dimension.time.helper uses dimension.time, so a change to dimension.time can break dimension.time.helper, while a change to dimension.time.helper can't break dimension.time.
Position
Below the diagonal: dimension.time.helper uses a module listed above it, which is the healthy direction.
dimension.time.helper uses dimension.time.predicates, so a change to dimension.time.predicates can break dimension.time.helper, while a change to dimension.time.helper can't break dimension.time.predicates.
Position
Below the diagonal: dimension.time.helper uses a module listed above it, which is the healthy direction.
dimension.time.rule uses engine.LexiconLookup, so a change to engine.LexiconLookup can break dimension.time.rule, while a change to dimension.time.rule can't break engine.LexiconLookup.
Position
Below the diagonal: dimension.time.rule uses a module listed above it, which is the healthy direction.
dimension.time.rule uses dimension.time, so a change to dimension.time can break dimension.time.rule, while a change to dimension.time.rule can't break dimension.time.
Position
Below the diagonal: dimension.time.rule uses a module listed above it, which is the healthy direction.
dimension.time.rule uses dimension.time.predicates, so a change to dimension.time.predicates can break dimension.time.rule, while a change to dimension.time.rule can't break dimension.time.predicates.
Position
Below the diagonal: dimension.time.rule uses a module listed above it, which is the healthy direction.
dimension.time.repeat uses dimension.time.Types, so a change to dimension.time.Types can break dimension.time.repeat, while a change to dimension.time.repeat can't break dimension.time.Types.
Position
Below the diagonal: dimension.time.repeat uses a module listed above it, which is the healthy direction.
dimension.time.repeat uses dimension.time, so a change to dimension.time can break dimension.time.repeat, while a change to dimension.time.repeat can't break dimension.time.
Position
Below the diagonal: dimension.time.repeat uses a module listed above it, which is the healthy direction.
dimension.time.repeat uses dimension, so a change to dimension can break dimension.time.repeat, while a change to dimension.time.repeat can't break dimension.
Position
Below the diagonal: dimension.time.repeat uses a module listed above it, which is the healthy direction.
dimension.time.repeat uses dimension.time.duration, so a change to dimension.time.duration can break dimension.time.repeat, while a change to dimension.time.repeat can't break dimension.time.duration.
Position
Below the diagonal: dimension.time.repeat uses a module listed above it, which is the healthy direction.
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2025 — Injection
8
High / Critical
A03:2025 — Software Supply Chain Failures
6
Medium
Roadmap
Top priorities: Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label; Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1; Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Add a SAST step to CI running what this repository's stack ships: scalafix or scapegoat — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
Code Duplication: Edited copy of a member (9 corresponding lines)
How the grades work
Every finding carries one of four grades. Three say how serious it is. The fourth says this
survey could not settle it — and it is a grade, not a gap.
Critical — 9
A definite problem that already costs you something and drags the score down: a
missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here
tends to cause failures elsewhere.
Serious — 170
Likely wrong, but not failing yet. It degrades
the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to
carry for two years either.
Minor — 91
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 12
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 56 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.
What we checked — 56 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 257 of 270 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.scala) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.scala) and this repository declares an sbt build (duckling-fork-chinese, 36 test files), but it was not re-run: the analyzer environment could not run it. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — 3 shipped Python distribution(s) were read, but the outdated signal needs pypi.org, and no declaration here carries an exact pin to ask about — a floor or a range installs the newest release it admits and cannot be behind one, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares an sbt build (build.sbt), but the licence verdict published here was taken over its Python distribution dependencies. Nothing was read about its sbt dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D19 Documentation Quality — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
D30 Dependency Vulnerabilities — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Osv: osv-scanner exited 1 with no findings — dependency CVEs were not measured. 'osv-scanner' exited 1 and produced no findings, and that exit code has no documented repo-side meaning — so this run measured nothing, and nothing here is a statement about the repository.
D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `duckling-fork-chinese/server/src/main/resources/static/js/element-ui.js`, `duckling-fork-chinese/server/src/main/resources/static/js/index.js` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
D43 Malicious Dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Osv: osv-scanner exited 1 with no findings — dependency CVEs were not measured. 'osv-scanner' exited 1 and produced no findings, and that exit code has no documented repo-side meaning — so this run measured nothing, and nothing here is a statement about the repository.
AC6 Visual & motion safety — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 174 further occurrence(s) are not listed individually; the score already reflects all 214.
AX1 Captive dependencies — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
AXB1 Runtime evidence locked — no reproducible boot — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Subject: 4 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
X27 Collection changed while being enumerated — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
34 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was vue.enter at 50. A further 2 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being vue.eventsMixin at 18 — they are counted neither in the figure above nor in this dimension's score.
+ 25 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 6 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with vue.enter (cyclomatic 50), vue.parseFilters (cyclomatic 40), vue.createPatchFunction::hydrate (cyclomatic 32). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 6 together lifts Cyclomatic Complexity from 6.4 to about 7.1/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 49 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 6 bodies over 60 down to 60 or less in Cognitive Complexity — start with vue.processAttrs (cognitive 94), vue.parseHTML (cognitive 82), loadjs (cognitive 77). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 6 together lifts Cognitive Complexity from 3.8 to about 4.8/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes9.4 / 10Stronggated by 2 serious findings✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 1 FileTooLong finding(s) in God Classes — start with vue.js. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 TooManyMethods finding(s) in God Classes — start with TimeDataHelpers.scala. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.
3 duplicated block group(s) detected. 1.3 % of the production lines (197 of 14,940) are in a reported copy. A further 6 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
Edited copy of a member (26 corresponding lines)duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/engine/VarcharLookup.scala:92
Edited copy of a member (23 corresponding lines)duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/task/PlaceExtractor.scala:30
Edited copy of a member (14 corresponding lines)duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/numeral/Prods.scala:124
Edited copy of a member (8 corresponding lines)duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/Types.scala:289
Edited copy of a member (9 corresponding lines)duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/engine/Engine.scala:48
+ 4 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 Edited copy of a member (26 corresponding lines) finding(s) in Code Duplication — start with VarcharLookup.scala. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Edited copy of a member (23 corresponding lines) finding(s) in Code Duplication — start with PlaceExtractor.scala. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Edited copy of a member (14 corresponding lines) finding(s) in Code Duplication — start with Prods.scala. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling8.7 / 10Strong✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
6 production modules (Python+sbt), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; a dependsOn spread (deps: _*) and a project whose directory a helper computes are not visible there; 1 module(s) off the main sequence, with abstractness counted on 4 of the 6 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
Off the main sequence: core
What to do
Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 34 shipped Python distribution(s) use a banned license. Licences were resolved from PyPI over the distributions a consumer installs — this repository's 3 declared runtime requirement(s) closed transitively over each distribution's published `requires_dist` (31 reached that way). Requirements it states ONLY under an extra, a PEP 735 dependency group, a Poetry dev group or a dev-named requirements file are excluded: pip does not install any of them for a consumer. ★ This repository commits no dependency lockfile that this pass reads, so each licence is the one PyPI publishes for the distribution's CURRENT release rather than for a pinned version. 4 of them publish no licence on PyPI this pass can read; that is missing data, not a violation, and none of them is charged. ★ COVERAGE OF THIS VERDICT: it grades this repository's Python distribution dependencies and nothing else. The repository also declares an sbt build (build.sbt), and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
2 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/package.scala. Counted over 64 of the 216 production source files in this repository: 143 are under the ~2,400-byte size floor this dimension measures over, and the remaining 9 have no attributable history left to measure.
Off-boarding risk: anonymized user #1
✓ On the Gold path — maintain.
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
4 deducted task-comment markers across 14940 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
Resolve the 4 TodoComment finding(s) in Explicit Debt — start with Rules.scala (2), OverlapResolver.scala, Weeks.scala. — One of this dimension's main actionable groups (4 warning-level).
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.sbt. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.
1 of 2 build units (Python, sbt) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
8 finding(s): 0 critical, 5 high, 3 medium, 0 low. 4 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 3 file(s) — `duckling-fork-chinese/server/src/main/resources/static/js/element-ui.js`, `duckling-fork-chinese/server/src/main/resources/static/js/index.js`, `duckling-fork-chinese/server/src/main/resources/static/js/vue.js` — so no absence of findings in them is evidence of anything, and nothing in them was analysed. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
REDACTED
REDACTED
REDACTED
REDACTED
What to do
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
No action in Static Analysis (SAST) — all 4 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (4 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
73 of 73 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/Rules.scala. Counted over 73 of the 216 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Most significant orphaned file · ×2duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/Rules.scala:1
Dormant codebase
What to do
Resolve the 71 Orphaned file finding(s) in Knowledge Freshness — start with Rules.scala (13), Examples.scala (6), Types.scala (3). — One of this dimension's main actionable groups (71 recommendation-level).
Resolve the 2 Most significant orphaned file finding(s) in Knowledge Freshness — start with Rules.scala, Examples.scala. — One of this dimension's main actionable groups (2 recommendation-level).
Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 2 Change coupling finding(s) in Change Coupling — start with Rules.scala (2). — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 Change-coupling hub finding(s) in Change Coupling — start with Examples.scala. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 0 platform declaration(s) and 3 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
✓ On the Gold path — maintain.
Detailed fixes: d44_recommendation.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC2 · Forms & labels1.0 / 10Critical✓ Tool-verified
Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.
Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. — duckling-fork-chinese/server/src/main/resources/static/js/vue.js:8529
A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label. — duckling-fork-chinese/server/src/main/resources/static/js/vue.js:11840
What to do
Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
Do you agree with this assessment?
AC3 · Page structure3.8 / 10Weak✓ Tool-verified
Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.
Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). (×2) — duckling-fork-chinese/server/src/main/resources/static/js/vue.js:11866, duckling-fork-chinese/server/src/main/resources/template.html:1
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×2) — duckling-fork-chinese/server/src/main/resources/static/js/vue.js:11866, duckling-fork-chinese/server/src/main/resources/template.html:1
What to do
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.
Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.
Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
`.button` sets color: white on background-color: #4CAF50 — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — duckling-fork-chinese/server/src/main/resources/templates/index.html:77
`.el-pagination.is-background .el-pager li:not(.disabled).active` sets color: #FFF on background-color: #409EFF — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. This is a MINIFIED, build-generated sheet — editing the literal here is undone by the next vendor drop or rebuild, so override the rule in your own stylesheet (or fix it upstream / in the source the bundle is built from). (×2) — duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1, duckling-fork-chinese/server/src/main/resources/static/css/index.css:1
`.el-date-table td.current:not(.disabled) span` sets color: #FFF on background-color: #409EFF — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. This is a MINIFIED, build-generated sheet — editing the literal here is undone by the next vendor drop or rebuild, so override the rule in your own stylesheet (or fix it upstream / in the source the bundle is built from). (×2) — duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1, duckling-fork-chinese/server/src/main/resources/static/css/index.css:1
`.el-date-table td.selected span` sets color: #FFF on background-color: #409EFF — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. This is a MINIFIED, build-generated sheet — editing the literal here is undone by the next vendor drop or rebuild, so override the rule in your own stylesheet (or fix it upstream / in the source the bundle is built from). (×2) — duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1, duckling-fork-chinese/server/src/main/resources/static/css/index.css:1
`.el-month-table td.end-date .cell,.el-month-table td.start-date .cell` sets color: #FFF on background-color: #409EFF — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. This is a MINIFIED, build-generated sheet — editing the literal here is undone by the next vendor drop or rebuild, so override the rule in your own stylesheet (or fix it upstream / in the source the bundle is built from). (×2) — duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1, duckling-fork-chinese/server/src/main/resources/static/css/index.css:1
`div.fancy-select div.trigger` sets color: #4B5468 on background-color: #99A5BE — 3.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — duckling-fork-chinese/server/src/main/resources/static/css/fancy_select.css:21
`div.fancy-select div.trigger.open` sets color: #7A8498 on background-color: #4A5368 — 2.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — duckling-fork-chinese/server/src/main/resources/static/css/fancy_select.css:55
`.btn-danger, #try .no-results .feedback.init button, .feedback.clicked button` sets color: #fff on background-color: #d9534f — 4.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — duckling-fork-chinese/server/src/main/resources/static/css/main.css:2144
`.btn-danger .badge, #try .no-results .feedback.init button .badge, .feedback.clicked button .badge` sets color: #d9534f on background-color: #fff — 4.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — duckling-fork-chinese/server/src/main/resources/static/css/main.css:2157
`.nav-pills > li.active > a, .nav-pills > li.active > a:hover, .nav-pills > li.active > a:focus` sets color: #fff on background-color: #428bca — 3.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — duckling-fork-chinese/server/src/main/resources/static/css/main.css:2272
`div.fancy-select div.trigger.open` sets color: #1a85b8 on background-color: #f2f2f2 — 3.7:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — duckling-fork-chinese/server/src/main/resources/static/css/main.css:2568
`div.fancy-select ul.options li:hover, div.fancy-select ul.options li.hover` sets color: #21a9c1 on background-color: #f2f2f2 — 2.5:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — duckling-fork-chinese/server/src/main/resources/static/css/main.css:2580
`div.fancy-select ul.options li.selected` sets color: #fafafa on background-color: #1a85b8 — 4.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — duckling-fork-chinese/server/src/main/resources/static/css/main.css:2583
`#try .try-it button` sets color: #fafafa on background-color: #2197c9 — 3.2:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — duckling-fork-chinese/server/src/main/resources/static/css/main.css:2751
`.feedback.init button` sets color: #1a769d on background-color: #ebebeb — 4.3:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — duckling-fork-chinese/server/src/main/resources/static/css/main.css:2831
`.el-dropdown .el-dropdown-selfdefine:focus:not(.focusing)` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1
`.el-pagination button:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1
`.el-dialog__headerbtn` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1
`.el-menu--horizontal>.el-submenu:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1
`.el-radio-button` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1
`.el-radio-button__inner` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1
`.el-radio-button__orig-radio` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1
`.el-switch__core` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1
`.el-select__input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1
`.el-table-filter__bottom button:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1
`.el-date-editor .el-range-input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1
`.el-picker-panel__shortcut` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1
`.el-picker-panel__btn` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1
`.el-picker-panel__icon-btn` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1
`.el-time-panel__btn` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1
`.el-message-box__headerbtn` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1
`.el-tabs__item:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1
`.el-carousel__arrow` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1
`.el-carousel__button` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1
`.el-collapse-item__header` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1
`.el-cascader__search-input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1
What to do
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Other · Architecture — Whether any singleton service captures a scoped/transient dependency — a silent lifetime/threading bug.
Method: Roslyn scan: DI registrations parsed from AddSingleton/Scoped/Transient; each singleton checked for captured shorter-lifetime dependencies. Exhaustive, deterministic.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
Other · Architecture — Whether singleton services avoid mutable shared instance state that concurrent callers would race on.
Method: Roslyn scan: singleton field mutations unguarded by lock or Interlocked, per type; syntax-based guard detection. Deterministic, traceable per field.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.
`DuckDate` declares 17 abstract members: `year`, `month`, `dayOfMonth`, `of`, `minusDays`, `dayOfWeek`, `withYear`, `withMonth`, `withDayOfMonth`, `plusDays`, `plusWeeks`, `plusMonths`, `plusYears`, `toLunar`, `toSolar`, `lengthOfMonth`, `comparedTo`. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/Types.scala:36
What to do
Split fat interfaces into focused role-interfaces so clients depend only on what they use.
Other · Code Health — Unreviewed-generation residue in this repository's Scala: methods whose whole body is still `???` or a "not implemented" throw where nothing overrides them, and placeholder text (lorem ipsum, changeme/replace_me…) left in strings of non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.
Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords, in this repository's Scala: methods whose body is `???` or only throws a "not implemented" error, methods that take inputs and return a constant or do nothing, dead `if (false)` branches, and skeleton classes most of whose methods are holes.
Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
The root README is 14 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, in the README and in the repository documents it links, it found no a build/run or getting-started section, no a testing section, no an architecture or project-map section. Sections are matched on HEADING text only, so material written under a heading this check does not recognise — or with no heading at all — is not seen and this row may understate what the document covers. — README.md:1
What to do
Expand the README with getting-started, architecture overview and a project map.
Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
Do you agree with this assessment?
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
Do you agree with this assessment?
P2 · Observability7.0 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
No static application security testing detected. For this repository's stack, add scalafix or scapegoat (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 3 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:4
What to do
Add a SAST step to CI running what this repository's stack ships: scalafix or scapegoat — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
What to do
Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.
Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.
No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
Readiness · Performance — Whether the code protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.
Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI; off .NET, the same ladder over Go testing.B, Rust criterion/#[bench]/divan, JMH/kotlinx-benchmark, pytest-benchmark/asv/pyperf, tinybench/mitata/vitest bench/benchmark.js and Swift package-benchmark — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.
A JMH/Jetpack Benchmark suite exists but nothing turns on its allocation measurement — allocations (the main way hot code pressures a garbage collector or allocator) aren't being measured. — duckling-fork-chinese/benchmark/src/main/java/com/xiaomi/duckling/benchmark/DateTimeBenchmark.java
What to do
Run JMH with the GC profiler (`-prof gc`, or addProfiler(GCProfiler.class)) so allocation rate regressions are visible, not just time.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
Other · Security — Only what this repository's own non-C# files could be read for was assessed — markup this repository SHIPS is scored for third-party script integrity whether or not the repository serves it itself, since a page handed to a consumer runs in that consumer’s origin. Nothing else in this dimension was assessed: the transport, cookie, input-validation and crypto controls are read from a source model that was not loaded for this repository’s language, so their absence here is not a finding about this repository.
Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.
`https://maxcdn.bootstrapcdn.com/bootstrap/3.3.4/js/bootstrap.min.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. 2 such include(s) across the repository's markup. — duckling-fork-chinese/server/src/main/resources/templates/index.html:26
What to do
Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.
Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped4.9 / 10Weak✓ Tool-verified
Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.
Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.
`getLocalTime()` is text this program did not author, and it is written into the text of an element through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:103
`cur` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — duckling-fork-chinese/server/src/main/resources/static/js/vue.js:7634
What to do
Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
Do you agree with this assessment?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether an enhanced `for` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is iterating invalidates the fail-fast iterator it is holding, so the next `next()` throws `ConcurrentModificationException` and the remaining elements are never seen. Whether a `for` loop leaves the `dict`, `set` or `deque` it is walking alone — CPython's iterators over those check that the collection has not changed size since the loop began, so a body that removes from (or empties) the very collection the loop is walking makes the next step raise `RuntimeError: dictionary changed size during iteration` and the remaining items are never seen. Whether a `for` comprehension or `foreach` leaves the mutable collection it is walking alone — an `ArrayBuffer` or `ListBuffer` counts its changes and its iterator checks the count, an `ArrayDeque` (and `mutable.Queue`/`mutable.Stack`) is walked by index up to its starting length, and a `java.util` collection walked through `asScala` is fail-fast, so a body that adds to or removes from the very collection the loop is walking makes a later step throw `ConcurrentModificationException` (`IndexOutOfBoundsException` for a deque) and the remaining elements are never seen.
Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×8) — REDACTED:143, REDACTED:163, REDACTED:194, …
What to do
Swallowed exception (empty catch)
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.
Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.
Other · Code Health — Whether Scala's null is held to the type system and not undermined by assertions — a file compiled with `-Yexplicit-nulls` is one where `String` excludes null and `String | Null` admits it, a file under WartRemover's `Null` wart or Scalafix's `DisableSyntax.noNulls` is one whose code cannot write `null` and must say `Option`, and each `.nn`, `import scala.language.unsafeNulls` or null-lint suppression is the author overruling that.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
No build over this repository's 190 Scala product file(s) passes `-Yexplicit-nulls`, enables WartRemover's `Null` wart or runs Scalafix's `DisableSyntax.noNulls`, so every reference type admits null and nothing reports a `null` written into the code or returned from a Java API — the first one to reach a method call is a `NullPointerException`. `Option` by convention is a habit no tool here holds the code to.
What to do
On Scala 3, add `-Yexplicit-nulls` to `scalacOptions` so `String` and `String | Null` mean different things, and type each Java API's result as nullable where it can return null; on Scala 2 (or as a first step), enable WartRemover's `Null` wart (`wartremoverErrors += Wart.Null`) or Scalafix's `DisableSyntax.noNulls = true` so the code holds absence in `Option`. Then pay the assertions down rather than adding to them: each `.nn` is a null the compiler could not rule out — wrap the Java value in `Option(…)` at the boundary, pattern-match on `null` once there, or change the API so the null cannot arrive; an `unsafeNulls` import switches the checking off for everything after it.
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 10 of 55 WCAG 2.2 Level A/AA success criteria (18%; ≈20% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 45 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 3 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
X10 Duplicated predicate — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 56 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — no test/production split to check
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C3 Audit Trail — No personal data detected in a persisted data model — no PII-named column (email, first_name, date_of_birth, phone_number, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, a MongoDB or Cassandra driver, JDBC) imported either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database or data-store client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, JDBC, MongoDB, Cassandra, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database or data-store client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, JDBC, MongoDB, Cassandra, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
D10 Test Quality — ~1981 lines of test source are present (.scala) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
D11 Test Reliability — Test reliability not included — the .scala suite was found but not re-run
D12 Dependency Hygiene — Not scored — 3 shipped Python distribution(s) were read, but the outdated signal needs pypi.org, and no declaration here carries an exact pin to ask about — a floor or a range installs the newest release it admits and cannot be behind one, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D19 Documentation Quality — D19 reads .NET projects and npm packages as units; 1 folder(s) declared by setup.py were not judged for an overview, an example or the map.
D21 Naming Consistency — D21 withholds its case and prefix conventions rows: 3 candidate(s) found and not reported.
D22 Internal API Consistency — API consistency is measured on C# only; the exposed Python surface was not measured.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .java, .py, .scala source were not judged.
D25 ADR Conformance — no ADRs to check
D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.scala), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D30 Dependency Vulnerabilities — Scanner failed to run — not a clean result
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
D32 Data Compliance (PII/GDPR) — 2 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D43 Malicious Dependencies — Scanner failed to run — not a clean result
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage not included — suite not readable by the collector
DM1 Domain Modelling — applicable but not scored (1 of 2 signals for this style — below the bar we score at): 115 value object(s)
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HTTP client call or construction in the JVM, JavaScript/TypeScript, Python source (service entry point: duckling-fork-chinese/server/src/main/scala/com/xiaomi/duckling/server/DucklingApplication.java:6 (@SpringBootApplication))
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X2 Cancellation propagation — no C# was loaded; this repository's Scala, Java and Python were read, and no request in it can be cancelled by a caller — a Scala request takes no token: a Future cannot be cancelled, and cats-effect, ZIO and Monix interrupt the fiber that made the request from outside the call, not through a parameter; a Java request off Android takes no token: it is cancelled through the handle it returns (Future.cancel, Call.cancel, a Disposable), ambiently (io.grpc.Context) or by interrupting its thread, not through a parameter; a Python request takes no token: asyncio cancels the task and trio or anyio the scope that made it, from outside the call, and requests, httpx, aiohttp and gRPC take a timeout, not a cancellation
X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
<html> without a lang duckling-fork-chinese/server/src/main/resources/static/js/vue.js:11866— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang duckling-fork-chinese/server/src/main/resources/template.html:1— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
AC2 · Forms & labels· <select> without a programmatic label · ×1
<select> without a programmatic label duckling-fork-chinese/server/src/main/resources/static/js/vue.js:8529— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
AC2 · Forms & labels· Link with no accessible name · ×1
Link with no accessible name duckling-fork-chinese/server/src/main/resources/static/js/vue.js:11840— A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
AC6 · Visual & motion safety· Focus outline removed in CSS without a · ×21
Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1— `.el-dropdown .el-dropdown-selfdefine:focus:not(.focusing)` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1— `.el-pagination button:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1— `.el-dialog__headerbtn` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1— `.el-menu--horizontal>.el-submenu:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1— `.el-radio-button` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1— `.el-radio-button__inner` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1— `.el-radio-button__orig-radio` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1— `.el-switch__core` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1— `.el-select__input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1— `.el-table-filter__bottom button:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1— `.el-date-editor .el-range-input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1— `.el-picker-panel__shortcut` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1— `.el-picker-panel__btn` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1— `.el-picker-panel__icon-btn` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1— `.el-time-panel__btn` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1— `.el-message-box__headerbtn` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1— `.el-tabs__item:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1— `.el-carousel__arrow` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1— `.el-carousel__button` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1— `.el-collapse-item__header` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1— `.el-cascader__search-input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Low contrast colour pair in CSS (2.8:1) duckling-fork-chinese/server/src/main/resources/templates/index.html:77— `.button` sets color: white on background-color: #4CAF50 — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (2.8:1) duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1— `.el-pagination.is-background .el-pager li:not(.disabled).active` sets color: #FFF on background-color: #409EFF — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. This is a MINIFIED, build-generated sheet — editing the literal here is undone by the next vendor drop or rebuild, so override the rule in your own stylesheet (or fix it upstream / in the source the bundle is built from).
Low contrast colour pair in CSS (2.8:1) duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1— `.el-date-table td.current:not(.disabled) span` sets color: #FFF on background-color: #409EFF — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. This is a MINIFIED, build-generated sheet — editing the literal here is undone by the next vendor drop or rebuild, so override the rule in your own stylesheet (or fix it upstream / in the source the bundle is built from).
Low contrast colour pair in CSS (2.8:1) duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1— `.el-date-table td.selected span` sets color: #FFF on background-color: #409EFF — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. This is a MINIFIED, build-generated sheet — editing the literal here is undone by the next vendor drop or rebuild, so override the rule in your own stylesheet (or fix it upstream / in the source the bundle is built from).
Low contrast colour pair in CSS (2.8:1) duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1— `.el-month-table td.end-date .cell,.el-month-table td.start-date .cell` sets color: #FFF on background-color: #409EFF — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. This is a MINIFIED, build-generated sheet — editing the literal here is undone by the next vendor drop or rebuild, so override the rule in your own stylesheet (or fix it upstream / in the source the bundle is built from).
Low contrast colour pair in CSS (2.8:1) duckling-fork-chinese/server/src/main/resources/static/css/index.css:1— `.el-pagination.is-background .el-pager li:not(.disabled).active` sets color: #FFF on background-color: #409EFF — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. This is a MINIFIED, build-generated sheet — editing the literal here is undone by the next vendor drop or rebuild, so override the rule in your own stylesheet (or fix it upstream / in the source the bundle is built from).
Low contrast colour pair in CSS (2.8:1) duckling-fork-chinese/server/src/main/resources/static/css/index.css:1— `.el-date-table td.current:not(.disabled) span` sets color: #FFF on background-color: #409EFF — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. This is a MINIFIED, build-generated sheet — editing the literal here is undone by the next vendor drop or rebuild, so override the rule in your own stylesheet (or fix it upstream / in the source the bundle is built from).
Low contrast colour pair in CSS (2.8:1) duckling-fork-chinese/server/src/main/resources/static/css/index.css:1— `.el-date-table td.selected span` sets color: #FFF on background-color: #409EFF — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. This is a MINIFIED, build-generated sheet — editing the literal here is undone by the next vendor drop or rebuild, so override the rule in your own stylesheet (or fix it upstream / in the source the bundle is built from).
Low contrast colour pair in CSS (2.8:1) duckling-fork-chinese/server/src/main/resources/static/css/index.css:1— `.el-month-table td.end-date .cell,.el-month-table td.start-date .cell` sets color: #FFF on background-color: #409EFF — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. This is a MINIFIED, build-generated sheet — editing the literal here is undone by the next vendor drop or rebuild, so override the rule in your own stylesheet (or fix it upstream / in the source the bundle is built from).
Swallowed exception (empty catch) REDACTED:143— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) REDACTED:163— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) REDACTED:194— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) REDACTED:212— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) REDACTED:228— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:557— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:7653— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:7675— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
TodoComment duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/ranking/OverlapResolver.scala:56— // TODO 现在只做了sliding判断左右交叉时,左应该如何处理,最后一个应该与入列的结果的最后一个进行比较 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/rule/Weeks.scala:88— // TODO 测试简化为一条效率是否有提升 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/age/Rules.scala:41— // TODO 如果有需要,细化区间左的开闭 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/age/Rules.scala:51— // TODO 如果有需要,细化区间右的开闭 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
vue.createPatchFunction::hydrate (cognitive 75) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:6348— vue.createPatchFunction::hydrate has cognitive complexity 75 (threshold 15). Drivers by points: if/else 20 (57 pts), boolean chains 10, loops 2 (8 pts) (nesting depth added 43). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function. This shape REPEATS in the file: 3 other methods here (vue.createPatchFunction::createElm, vue.createPatchFunction::updateChildren, vue.createPatchFunction::patchVnode) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This file is where this pass's cognitive complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 45 of the 58 methods over the threshold — including the worst — and 712 of the 909 points over it (78%), 5.8× the next-largest file (REDACTED at 122). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
vue.createPatchFunction::patchVnode (cognitive 37) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:6253— vue.createPatchFunction::patchVnode has cognitive complexity 37 (threshold 15). Drivers by points: if/else 19 (27 pts), boolean chains 8, loops 1 (2 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: 3 other methods here (vue.createPatchFunction::createElm, vue.createPatchFunction::updateChildren, vue.createPatchFunction::hydrate) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This file is where this pass's cognitive complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 45 of the 58 methods over the threshold — including the worst — and 712 of the 909 points over it (78%), 5.8× the next-largest file (REDACTED at 122). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
vue.createPatchFunction::updateChildren (cognitive 27) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:6156— vue.createPatchFunction::updateChildren has cognitive complexity 27 (threshold 15). Drivers by points: if/else 14 (22 pts), boolean chains 4, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: 3 other methods here (vue.createPatchFunction::createElm, vue.createPatchFunction::patchVnode, vue.createPatchFunction::hydrate) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This file is where this pass's cognitive complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 45 of the 58 methods over the threshold — including the worst — and 712 of the 909 points over it (78%), 5.8× the next-largest file (REDACTED at 122). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
vue.createPatchFunction::createElm (cognitive 16) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:5895— vue.createPatchFunction::createElm has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 3 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: 3 other methods here (vue.createPatchFunction::updateChildren, vue.createPatchFunction::patchVnode, vue.createPatchFunction::hydrate) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This file is where this pass's cognitive complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 45 of the 58 methods over the threshold — including the worst — and 712 of the 909 points over it (78%), 5.8× the next-largest file (REDACTED at 122). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
Low contrast colour pair in CSS (4.0:1) duckling-fork-chinese/server/src/main/resources/static/css/main.css:2144— `.btn-danger, #try .no-results .feedback.init button, .feedback.clicked button` sets color: #fff on background-color: #d9534f — 4.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (4.0:1) duckling-fork-chinese/server/src/main/resources/static/css/main.css:2157— `.btn-danger .badge, #try .no-results .feedback.init button .badge, .feedback.clicked button .badge` sets color: #d9534f on background-color: #fff — 4.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (4.0:1) duckling-fork-chinese/server/src/main/resources/static/css/main.css:2583— `div.fancy-select ul.options li.selected` sets color: #fafafa on background-color: #1a85b8 — 4.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
vue.createPatchFunction::hydrate (cyclomatic 32) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:6348— vue.createPatchFunction::hydrate has cyclomatic complexity 32 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: 2 other methods here (vue.createPatchFunction::updateChildren, vue.createPatchFunction::patchVnode) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This file is where this pass's cyclomatic complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 28 of the 33 methods over the threshold — including the worst — and 247 of the 274 points over it (90%), 24.7× the next-largest file (REDACTED at 10). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
vue.createPatchFunction::patchVnode (cyclomatic 31) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:6253— vue.createPatchFunction::patchVnode has cyclomatic complexity 31 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: 2 other methods here (vue.createPatchFunction::updateChildren, vue.createPatchFunction::hydrate) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This file is where this pass's cyclomatic complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 28 of the 33 methods over the threshold — including the worst — and 247 of the 274 points over it (90%), 24.7× the next-largest file (REDACTED at 10). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
vue.createPatchFunction::updateChildren (cyclomatic 19) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:6156— vue.createPatchFunction::updateChildren has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: 2 other methods here (vue.createPatchFunction::patchVnode, vue.createPatchFunction::hydrate) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This file is where this pass's cyclomatic complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 28 of the 33 methods over the threshold — including the worst — and 247 of the 274 points over it (90%), 24.7× the next-largest file (REDACTED at 10). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
AC3 · Page structure· Page without a main landmark · ×2
Page without a main landmark duckling-fork-chinese/server/src/main/resources/static/js/vue.js:11866— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark duckling-fork-chinese/server/src/main/resources/template.html:1— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
vue.parseHTML::parseEndTag (cyclomatic 18) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:9481— vue.parseHTML::parseEndTag has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: 2 other methods here (vue.parseHTML, vue.parseHTML::handleStartTag) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This file is where this pass's cyclomatic complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 28 of the 33 methods over the threshold — including the worst — and 247 of the 274 points over it (90%), 24.7× the next-largest file (REDACTED at 10). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
vue.parseHTML::handleStartTag (cyclomatic 16) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:9438— vue.parseHTML::handleStartTag has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: 2 other methods here (vue.parseHTML, vue.parseHTML::parseEndTag) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This is NOT this file's highest cyclomatic complexity: vue.eventsMixin (cyclomatic 18) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score. This file is where this pass's cyclomatic complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 28 of the 33 methods over the threshold — including the worst — and 247 of the 274 points over it (90%), 24.7× the next-largest file (REDACTED at 10). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
vue.parseHTML::parseEndTag (cognitive 29) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:9481— vue.parseHTML::parseEndTag has cognitive complexity 29 (threshold 15). Drivers by points: if/else 13 (22 pts), loops 2 (4 pts), boolean chains 3 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: 2 other methods here (vue.parseHTML, vue.parseHTML::handleStartTag) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This file is where this pass's cognitive complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 45 of the 58 methods over the threshold — including the worst — and 712 of the 909 points over it (78%), 5.8× the next-largest file (REDACTED at 122). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
vue.parseHTML::handleStartTag (cognitive 17) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:9438— vue.parseHTML::handleStartTag has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (9 pts), boolean chains 5, ternaries 1 (2 pts), loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: 2 other methods here (vue.parseHTML, vue.parseHTML::parseEndTag) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This file is where this pass's cognitive complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 45 of the 58 methods over the threshold — including the worst — and 712 of the 909 points over it (78%), 5.8× the next-largest file (REDACTED at 122). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
Change coupling: Rules.scala ↔ Examples.scala duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/duration/Rules.scala:1— `duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/duration/Rules.scala` and `duckling-fork-chinese/learning/src/main/scala/com/xiaomi/duckling/dimension/time/duration/Examples.scala` change together 90% of the time (9 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `25a2a693` [DUCK] 修复“去年上半年”的“上半年”结合错误 (#257); `75e4c6ca` duration: 增加 一点五二小时 类的支持 (#252); `b57e890a` 支持“1分30秒” (#202) — run `git show` on any of them.
Change coupling: Rules.scala ↔ Examples.scala duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/repeat/Rules.scala:1— `duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/repeat/Rules.scala` and `duckling-fork-chinese/learning/src/main/scala/com/xiaomi/duckling/dimension/time/repeat/Examples.scala` change together 82% of the time (9 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `968b1bef` 修复 (#236); `b6966253` [DUCK] repeat 增加 重复区间+时间点/区间 的能力 (#230); `8959819e` 支持"工作日[每天]三点"的说法 (#224) — run `git show` on any of them.
X24 · Document value interpolated into markup unescaped· Untrusted text written into markup unescaped · ×2
Untrusted text written into markup unescaped REDACTED:103— `getLocalTime()` is text this program did not author, and it is written into the text of an element through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped duckling-fork-chinese/server/src/main/resources/static/js/vue.js:7634— `cur` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Low contrast colour pair in CSS (3.1:1) duckling-fork-chinese/server/src/main/resources/static/css/fancy_select.css:21— `div.fancy-select div.trigger` sets color: #4B5468 on background-color: #99A5BE — 3.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (2.0:1) duckling-fork-chinese/server/src/main/resources/static/css/fancy_select.css:55— `div.fancy-select div.trigger.open` sets color: #7A8498 on background-color: #4A5368 — 2.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (3.6:1) duckling-fork-chinese/server/src/main/resources/static/css/main.css:2272— `.nav-pills > li.active > a, .nav-pills > li.active > a:hover, .nav-pills > li.active > a:focus` sets color: #fff on background-color: #428bca — 3.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (3.7:1) duckling-fork-chinese/server/src/main/resources/static/css/main.css:2568— `div.fancy-select div.trigger.open` sets color: #1a85b8 on background-color: #f2f2f2 — 3.7:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (2.5:1) duckling-fork-chinese/server/src/main/resources/static/css/main.css:2580— `div.fancy-select ul.options li:hover, div.fancy-select ul.options li.hover` sets color: #21a9c1 on background-color: #f2f2f2 — 2.5:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (3.2:1) duckling-fork-chinese/server/src/main/resources/static/css/main.css:2751— `#try .try-it button` sets color: #fafafa on background-color: #2197c9 — 3.2:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (4.3:1) duckling-fork-chinese/server/src/main/resources/static/css/main.css:2831— `.feedback.init button` sets color: #1a769d on background-color: #ebebeb — 4.3:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
vue.enter (cyclomatic 50) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:8110— vue.enter has cyclomatic complexity 50 (threshold 15). Of this number, 38 points are the body's own statements and 12 belong to 3 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This file is where this pass's cyclomatic complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 28 of the 33 methods over the threshold — including the worst — and 247 of the 274 points over it (90%), 24.7× the next-largest file (REDACTED at 10). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
vue.parseFilters (cyclomatic 40) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:6823— vue.parseFilters has cyclomatic complexity 40 (threshold 15). Of this number, 39 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 28 of the 33 methods over the threshold — including the worst — and 247 of the 274 points over it (90%), 24.7× the next-largest file (REDACTED at 10). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
vue.resolveAsyncComponent (cyclomatic 31) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:3612— vue.resolveAsyncComponent has cyclomatic complexity 31 (threshold 15). Of this number, 22 points are the body's own statements and 9 belong to 5 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 28 of the 33 methods over the threshold — including the worst — and 247 of the 274 points over it (90%), 24.7× the next-largest file (REDACTED at 10). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
vue.parseHTML (cyclomatic 31) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:9280— vue.parseHTML has cyclomatic complexity 31 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: 2 other methods here (vue.parseHTML::handleStartTag, vue.parseHTML::parseEndTag) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This file is where this pass's cyclomatic complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 28 of the 33 methods over the threshold — including the worst — and 247 of the 274 points over it (90%), 24.7× the next-largest file (REDACTED at 10). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
vue.processAttrs (cyclomatic 30) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:10265— vue.processAttrs has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 28 of the 33 methods over the threshold — including the worst — and 247 of the 274 points over it (90%), 24.7× the next-largest file (REDACTED at 10). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
vue.leave (cyclomatic 28) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:8261— vue.leave has cyclomatic complexity 28 (threshold 15). Most of this is not in the body itself: 12 of the 28 points are its own statements and the rest belongs to 3 function items inside it that branch (performLeave, a function literal at line 8305, a function literal at line 8344). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest. This file is where this pass's cyclomatic complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 28 of the 33 methods over the threshold — including the worst — and 247 of the 274 points over it (90%), 24.7× the next-largest file (REDACTED at 10). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
vue.updateDOMProps (cyclomatic 26) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:7588— vue.updateDOMProps has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 28 of the 33 methods over the threshold — including the worst — and 247 of the 274 points over it (90%), 24.7× the next-largest file (REDACTED at 10). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
vue.processSlotContent (cyclomatic 26) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:10102— vue.processSlotContent has cyclomatic complexity 26 (threshold 15). Of this number, 25 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 28 of the 33 methods over the threshold — including the worst — and 247 of the 274 points over it (90%), 24.7× the next-largest file (REDACTED at 10). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
bfwone.loadjs (cyclomatic 25) REDACTED:135— bfwone.loadjs has cyclomatic complexity 25 (threshold 15). Of this number, 15 points are the body's own statements and 10 belong to 3 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
vue._createElement (cyclomatic 25) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:3363— vue._createElement has cyclomatic complexity 25 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This file is where this pass's cyclomatic complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 28 of the 33 methods over the threshold — including the worst — and 247 of the 274 points over it (90%), 24.7× the next-largest file (REDACTED at 10). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
(anonymous) (cyclomatic 25) REDACTED:2— (anonymous) has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
vue.genElement (cyclomatic 24) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:10942— vue.genElement has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 28 of the 33 methods over the threshold — including the worst — and 247 of the 274 points over it (90%), 24.7× the next-largest file (REDACTED at 10). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
vue.defineReactive$$1 (cyclomatic 22) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:1014— vue.defineReactive$$1 has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 9 of the 22 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 1052, 1039). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest. This file is where this pass's cyclomatic complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 28 of the 33 methods over the threshold — including the worst — and 247 of the 274 points over it (90%), 24.7× the next-largest file (REDACTED at 10). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
vue.addHandler (cyclomatic 22) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:6982— vue.addHandler has cyclomatic complexity 22 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This file is where this pass's cyclomatic complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 28 of the 33 methods over the threshold — including the worst — and 247 of the 274 points over it (90%), 24.7× the next-largest file (REDACTED at 10). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
vue.createPatchFunction.patch (cyclomatic 21) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:6452— vue.createPatchFunction.patch has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 28 of the 33 methods over the threshold — including the worst — and 247 of the 274 points over it (90%), 24.7× the next-largest file (REDACTED at 10). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
vue.genData$2 (cyclomatic 21) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:11093— vue.genData$2 has cyclomatic complexity 21 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This file is where this pass's cyclomatic complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 28 of the 33 methods over the threshold — including the worst — and 247 of the 274 points over it (90%), 24.7× the next-largest file (REDACTED at 10). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
time.resolveTimeData (cyclomatic 20) duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/package.scala:83— time.resolveTimeData has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
vue.normalizeArrayChildren (cyclomatic 18) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:2376— vue.normalizeArrayChildren has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 28 of the 33 methods over the threshold — including the worst — and 247 of the 274 points over it (90%), 24.7× the next-largest file (REDACTED at 10). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
vue.normalizeScopedSlots (cyclomatic 18) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:2545— vue.normalizeScopedSlots has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 28 of the 33 methods over the threshold — including the worst — and 247 of the 274 points over it (90%), 24.7× the next-largest file (REDACTED at 10). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
vue.parse::closeElement (cyclomatic 18) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:9621— vue.parse::closeElement has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 28 of the 33 methods over the threshold — including the worst — and 247 of the 274 points over it (90%), 24.7× the next-largest file (REDACTED at 10). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
vue.resolveSlots (cyclomatic 17) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:2499— vue.resolveSlots has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: vue.eventsMixin (cyclomatic 18) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score. This file is where this pass's cyclomatic complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 28 of the 33 methods over the threshold — including the worst — and 247 of the 274 points over it (90%), 24.7× the next-largest file (REDACTED at 10). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
vue.bindObjectProps (cyclomatic 17) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:2752— vue.bindObjectProps has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 5 of the 17 points are its own statements and the rest belongs to one function item inside it that branches (loop). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest. This is NOT this file's highest cyclomatic complexity: vue.eventsMixin (cyclomatic 18) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score. This file is where this pass's cyclomatic complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 28 of the 33 methods over the threshold — including the worst — and 247 of the 274 points over it (90%), 24.7× the next-largest file (REDACTED at 10). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
vue.updateChildComponent (cyclomatic 17) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:4086— vue.updateChildComponent has cyclomatic complexity 17 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This is NOT this file's highest cyclomatic complexity: vue.eventsMixin (cyclomatic 18) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score. This file is where this pass's cyclomatic complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 28 of the 33 methods over the threshold — including the worst — and 247 of the 274 points over it (90%), 24.7× the next-largest file (REDACTED at 10). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
vue.updateAttrs (cyclomatic 17) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:6681— vue.updateAttrs has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: vue.eventsMixin (cyclomatic 18) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score. This file is where this pass's cyclomatic complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 28 of the 33 methods over the threshold — including the worst — and 247 of the 274 points over it (90%), 24.7× the next-largest file (REDACTED at 10). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
FuzzyDayIntervals.updatePredicateByFuzzyInterval (cyclomatic 16) duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/rule/FuzzyDayIntervals.scala:174— FuzzyDayIntervals.updatePredicateByFuzzyInterval has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
NaiveBayesConsole.setOptions (cyclomatic 16) duckling-fork-chinese/learning/src/main/scala/com/xiaomi/duckling/task/NaiveBayesConsole.scala:114— NaiveBayesConsole.setOptions has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
vue.genHandler (cyclomatic 16) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:10798— vue.genHandler has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: vue.eventsMixin (cyclomatic 18) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score. This file is where this pass's cyclomatic complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 28 of the 33 methods over the threshold — including the worst — and 247 of the 274 points over it (90%), 24.7× the next-largest file (REDACTED at 10). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
vue.Vue.$mount (cyclomatic 16) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:11857— vue.Vue.$mount has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: vue.eventsMixin (cyclomatic 18) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score. This file is where this pass's cyclomatic complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 28 of the 33 methods over the threshold — including the worst — and 247 of the 274 points over it (90%), 24.7× the next-largest file (REDACTED at 10). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
vue.processAttrs (cognitive 94) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:10265— vue.processAttrs has cognitive complexity 94 (threshold 15). Drivers by points: if/else 24 (86 pts), boolean chains 7, loops 1 (nesting depth added 62). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function. This file is where this pass's cognitive complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 45 of the 58 methods over the threshold — including the worst — and 712 of the 909 points over it (78%), 5.8× the next-largest file (REDACTED at 122). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
vue.parseHTML (cognitive 82) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:9280— vue.parseHTML has cognitive complexity 82 (threshold 15). Drivers by points: if/else 43 (112 pts), boolean chains 19, loops 6 (12 pts), ternaries 1 (2 pts) (nesting depth added 76). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function. This shape REPEATS in the file: 2 other methods here (vue.parseHTML::handleStartTag, vue.parseHTML::parseEndTag) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This file is where this pass's cognitive complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 45 of the 58 methods over the threshold — including the worst — and 712 of the 909 points over it (78%), 5.8× the next-largest file (REDACTED at 122). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
loadjs (cognitive 77) REDACTED:135— loadjs has cognitive complexity 77 (threshold 15). Drivers by points: if/else 22 (54 pts), error handling 5 (17 pts), loops 1 (4 pts), boolean chains 2 (nesting depth added 47). Of this number, 36 points are the body's own statements and 41 belong to 3 function items inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
(anonymous) (cognitive 75) REDACTED:2— (anonymous) has cognitive complexity 75 (threshold 15). Drivers by points: if/else 21 (62 pts), loops 2 (6 pts), ternaries 1 (6 pts), boolean chains 1 (nesting depth added 50). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
vue.createPatchFunction.patch (cognitive 71) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:6452— vue.createPatchFunction.patch has cognitive complexity 71 (threshold 15). Drivers by points: if/else 17 (44 pts), loops 4 (22 pts), ternaries 1 (3 pts), boolean chains 2 (nesting depth added 47). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function. This file is where this pass's cognitive complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 45 of the 58 methods over the threshold — including the worst — and 712 of the 909 points over it (78%), 5.8× the next-largest file (REDACTED at 122). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
vue.resolveAsyncComponent (cognitive 56) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:3612— vue.resolveAsyncComponent has cognitive complexity 56 (threshold 15). Drivers by points: if/else 20 (46 pts), boolean chains 6, loops 1 (2 pts), ternaries 1 (2 pts) (nesting depth added 28). Of this number, 41 points are the body's own statements and 15 belong to 5 function items inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function. This file is where this pass's cognitive complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 45 of the 58 methods over the threshold — including the worst — and 712 of the 909 points over it (78%), 5.8× the next-largest file (REDACTED at 122). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
vue.parseFilters (cognitive 55) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:6823— vue.parseFilters has cognitive complexity 55 (threshold 15). Drivers by points: if/else 18 (38 pts), boolean chains 7, loops 3 (7 pts), match/switch 1 (3 pts) (nesting depth added 26). Of this number, 54 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 45 of the 58 methods over the threshold — including the worst — and 712 of the 909 points over it (78%), 5.8× the next-largest file (REDACTED at 122). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
vue.enter (cognitive 52) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:8110— vue.enter has cognitive complexity 52 (threshold 15). Drivers by points: if/else 14 (21 pts), boolean chains 20, ternaries 9 (10 pts), loops 1 (nesting depth added 8). Of this number, 37 points are the body's own statements and 15 belong to 3 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 45 of the 58 methods over the threshold — including the worst — and 712 of the 909 points over it (78%), 5.8× the next-largest file (REDACTED at 122). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
time.resolveTimeData (cognitive 47) duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/package.scala:83— time.resolveTimeData has cognitive complexity 47 (threshold 15). Drivers by points: if/else 18 (31 pts), match/switch 5 (14 pts), boolean chains 2 (nesting depth added 22). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
vue.updateDOMProps (cognitive 43) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:7588— vue.updateDOMProps has cognitive complexity 43 (threshold 15). Drivers by points: if/else 11 (22 pts), loops 4 (8 pts), boolean chains 7, error handling 1 (3 pts), ternaries 1 (3 pts) (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 45 of the 58 methods over the threshold — including the worst — and 712 of the 909 points over it (78%), 5.8× the next-largest file (REDACTED at 122). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
vue.processSlotContent (cognitive 39) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:10102— vue.processSlotContent has cognitive complexity 39 (threshold 15). Drivers by points: if/else 15 (30 pts), boolean chains 9 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 45 of the 58 methods over the threshold — including the worst — and 712 of the 909 points over it (78%), 5.8× the next-largest file (REDACTED at 122). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
vue.normalizeArrayChildren (cognitive 31) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:2376— vue.normalizeArrayChildren has cognitive complexity 31 (threshold 15). Drivers by points: if/else 11 (25 pts), boolean chains 5, loops 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 45 of the 58 methods over the threshold — including the worst — and 712 of the 909 points over it (78%), 5.8× the next-largest file (REDACTED at 122). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
vue.leave (cognitive 31) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:8261— vue.leave has cognitive complexity 31 (threshold 15). Drivers by points: if/else 14 (20 pts), boolean chains 10, ternaries 1 (nesting depth added 6). Most of this is not in the body itself: 12 of the 31 points are its own statements and the rest belongs to 3 function items inside it that branch (performLeave, a function literal at line 8344, a function literal at line 8305). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest. This file is where this pass's cognitive complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 45 of the 58 methods over the threshold — including the worst — and 712 of the 909 points over it (78%), 5.8× the next-largest file (REDACTED at 122). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
vue.genHandler (cognitive 31) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:10798— vue.genHandler has cognitive complexity 31 (threshold 15). Drivers by points: if/else 11 (19 pts), ternaries 3 (9 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 45 of the 58 methods over the threshold — including the worst — and 712 of the 909 points over it (78%), 5.8× the next-largest file (REDACTED at 122). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
vue.Vue.$mount (cognitive 31) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:11857— vue.Vue.$mount has cognitive complexity 31 (threshold 15). Drivers by points: if/else 12 (27 pts), boolean chains 4 (nesting depth added 15). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function. This file is where this pass's cognitive complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 45 of the 58 methods over the threshold — including the worst — and 712 of the 909 points over it (78%), 5.8× the next-largest file (REDACTED at 122). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
vue._createElement (cognitive 29) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:3363— vue._createElement has cognitive complexity 29 (threshold 15). Drivers by points: if/else 17 (20 pts), boolean chains 9 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level. This file is where this pass's cognitive complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 45 of the 58 methods over the threshold — including the worst — and 712 of the 909 points over it (78%), 5.8× the next-largest file (REDACTED at 122). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
vue.generateCodeFrame (cognitive 29) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:11572— vue.generateCodeFrame has cognitive complexity 29 (threshold 15). Drivers by points: if/else 7 (18 pts), ternaries 1 (5 pts), loops 2 (4 pts), boolean chains 2 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 45 of the 58 methods over the threshold — including the worst — and 712 of the 909 points over it (78%), 5.8× the next-largest file (REDACTED at 122). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
vue.bindObjectProps (cognitive 28) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:2752— vue.bindObjectProps has cognitive complexity 28 (threshold 15). Drivers by points: if/else 8 (18 pts), boolean chains 7, loops 1 (3 pts) (nesting depth added 12). Most of this is not in the body itself: 10 of the 28 points are its own statements and the rest belongs to one function item inside it that branches (loop). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest. This file is where this pass's cognitive complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 45 of the 58 methods over the threshold — including the worst — and 712 of the 909 points over it (78%), 5.8× the next-largest file (REDACTED at 122). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
vue.genElement (cognitive 28) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:10942— vue.genElement has cognitive complexity 28 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 9, ternaries 1 (3 pts), loops 1 (2 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 45 of the 58 methods over the threshold — including the worst — and 712 of the 909 points over it (78%), 5.8× the next-largest file (REDACTED at 122). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
vue._update (cognitive 27) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:6573— vue._update has cognitive complexity 27 (threshold 15). Drivers by points: if/else 10 (18 pts), loops 4 (7 pts), boolean chains 2 (nesting depth added 11). Of this number, 23 points are the body's own statements and 4 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 45 of the 58 methods over the threshold — including the worst — and 712 of the 909 points over it (78%), 5.8× the next-largest file (REDACTED at 122). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
vue.defineReactive$$1 (cognitive 25) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:1014— vue.defineReactive$$1 has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 10, ternaries 2 (nesting depth added 3). Most of this is not in the body itself: 8 of the 25 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 1052, 1039). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest. This file is where this pass's cognitive complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 45 of the 58 methods over the threshold — including the worst — and 712 of the 909 points over it (78%), 5.8× the next-largest file (REDACTED at 122). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
vue.resolveInject (cognitive 24) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:2456— vue.resolveInject has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (16 pts), loops 2 (5 pts), ternaries 1 (2 pts), boolean chains 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 45 of the 58 methods over the threshold — including the worst — and 712 of the 909 points over it (78%), 5.8× the next-largest file (REDACTED at 122). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
vue.addHandler (cognitive 24) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:6982— vue.addHandler has cognitive complexity 24 (threshold 15). Drivers by points: if/else 16 (18 pts), boolean chains 4, ternaries 1 (2 pts) (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level. This file is where this pass's cognitive complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 45 of the 58 methods over the threshold — including the worst — and 712 of the 909 points over it (78%), 5.8× the next-largest file (REDACTED at 122). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
Rules.intersectProd (cognitive 23) duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/date/Rules.scala:339— Rules.intersectProd has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (12 pts), match/switch 2 (5 pts), boolean chains 3, loops 1 (3 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
vue.parse::closeElement (cognitive 23) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:9621— vue.parse::closeElement has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 8, loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 45 of the 58 methods over the threshold — including the worst — and 712 of the 909 points over it (78%), 5.8× the next-largest file (REDACTED at 122). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
vue.checkNode (cognitive 23) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:11483— vue.checkNode has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (18 pts), loops 2 (5 pts) (nesting depth added 13). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function. This file is where this pass's cognitive complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 45 of the 58 methods over the threshold — including the worst — and 712 of the 909 points over it (78%), 5.8× the next-largest file (REDACTED at 122). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
PhraseLookup.lookupPhrase (cognitive 22) duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/engine/PhraseLookup.scala:41— PhraseLookup.lookupPhrase has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (15 pts), loops 2 (7 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Rules.intersectToken (cognitive 21) duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/Rules.scala:173— Rules.intersectToken has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (13 pts), boolean chains 4, match/switch 2 (4 pts) (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
vue.resolveSlots (cognitive 21) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:2499— vue.resolveSlots has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 7, loops 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 45 of the 58 methods over the threshold — including the worst — and 712 of the 909 points over it (78%), 5.8× the next-largest file (REDACTED at 122). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
vue.genData$2 (cognitive 21) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:11093— vue.genData$2 has cognitive complexity 21 (threshold 15). Drivers by points: if/else 18 (19 pts), boolean chains 1, loops 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This file is where this pass's cognitive complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 45 of the 58 methods over the threshold — including the worst — and 712 of the 909 points over it (78%), 5.8× the next-largest file (REDACTED at 122). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
FuzzyDayIntervals.updatePredicateByFuzzyInterval (cognitive 20) duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/rule/FuzzyDayIntervals.scala:174— FuzzyDayIntervals.updatePredicateByFuzzyInterval has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 8, loops 1 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
vue.handleError (cognitive 20) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:1827— vue.handleError has cognitive complexity 20 (threshold 15). Drivers by points: if/else 3 (9 pts), loops 2 (6 pts), error handling 1 (5 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 45 of the 58 methods over the threshold — including the worst — and 712 of the 909 points over it (78%), 5.8× the next-largest file (REDACTED at 122). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
vue.updateAttrs (cognitive 20) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:6681— vue.updateAttrs has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 6, loops 2 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 45 of the 58 methods over the threshold — including the worst — and 712 of the 909 points over it (78%), 5.8× the next-largest file (REDACTED at 122). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
vue.markStaticRoots (cognitive 20) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:10661— vue.markStaticRoots has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (10 pts), loops 2 (6 pts), boolean chains 4 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 45 of the 58 methods over the threshold — including the worst — and 712 of the 909 points over it (78%), 5.8× the next-largest file (REDACTED at 122). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
time.copyGrain (cognitive 19) duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/package.scala:235— time.copyGrain has cognitive complexity 19 (threshold 15). Drivers by points: if/else 12 (16 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
vue.renderList (cognitive 19) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:2629— vue.renderList has cognitive complexity 19 (threshold 15). Drivers by points: loops 4 (10 pts), if/else 6 (7 pts), boolean chains 2 (nesting depth added 7). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This file is where this pass's cognitive complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 45 of the 58 methods over the threshold — including the worst — and 712 of the 909 points over it (78%), 5.8× the next-largest file (REDACTED at 122). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
vue.createCompileToFunctionFn.compileToFunctions (cognitive 19) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:11638— vue.createCompileToFunctionFn.compileToFunctions has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 5, error handling 1, ternaries 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level. This file is where this pass's cognitive complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 45 of the 58 methods over the threshold — including the worst — and 712 of the 909 points over it (78%), 5.8× the next-largest file (REDACTED at 122). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
TimePredicateHelpers.takeN (cognitive 18) duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/helper/TimePredicateHelpers.scala:162— TimePredicateHelpers.takeN has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (11 pts), match/switch 4 (6 pts), boolean chains 1 (nesting depth added 3). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
time.runReplacePartPredicate (cognitive 18) duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/package.scala:191— time.runReplacePartPredicate has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (10 pts), match/switch 1 (4 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
VarcharLookup.leftVarcharExpansion (cognitive 18) duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/engine/VarcharLookup.scala:92— VarcharLookup.leftVarcharExpansion has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (15 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (VarcharLookup.rightVarcharExpansion) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
VarcharLookup.rightVarcharExpansion (cognitive 18) duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/engine/VarcharLookup.scala:119— VarcharLookup.rightVarcharExpansion has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (15 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (VarcharLookup.leftVarcharExpansion) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
vue.looseEqual (cognitive 18) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:296— vue.looseEqual has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 7, error handling 1 (2 pts) (nesting depth added 2). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This file is where this pass's cognitive complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 45 of the 58 methods over the threshold — including the worst — and 712 of the 909 points over it (78%), 5.8× the next-largest file (REDACTED at 122). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
vue.normalizeScopedSlots (cognitive 18) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:2545— vue.normalizeScopedSlots has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 4, loops 2 (3 pts), ternaries 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 45 of the 58 methods over the threshold — including the worst — and 712 of the 909 points over it (78%), 5.8× the next-largest file (REDACTED at 122). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
vue.preTransformNode (cognitive 18) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:10481— vue.preTransformNode has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (13 pts), ternaries 1 (3 pts), boolean chains 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 45 of the 58 methods over the threshold — including the worst — and 712 of the 909 points over it (78%), 5.8× the next-largest file (REDACTED at 122). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
vue.markStatic$1 (cognitive 18) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:10629— vue.markStatic$1 has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 2 (5 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 45 of the 58 methods over the threshold — including the worst — and 712 of the 909 points over it (78%), 5.8× the next-largest file (REDACTED at 122). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
vue.mergeDataOrFn (cognitive 17) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:1212— vue.mergeDataOrFn has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (9 pts), ternaries 4 (8 pts) (nesting depth added 7). Most of this is not in the body itself: 6 of the 17 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 1237, 1230). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest. This file is where this pass's cognitive complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 45 of the 58 methods over the threshold — including the worst — and 712 of the 909 points over it (78%), 5.8× the next-largest file (REDACTED at 122). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
vue.actuallySetSelected (cognitive 17) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:8524— vue.actuallySetSelected has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (15 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 45 of the 58 methods over the threshold — including the worst — and 712 of the 909 points over it (78%), 5.8× the next-largest file (REDACTED at 122). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
NaiveBayesConsole.setOptions (cognitive 16) duckling-fork-chinese/learning/src/main/scala/com/xiaomi/duckling/task/NaiveBayesConsole.scala:114— NaiveBayesConsole.setOptions has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (11 pts), match/switch 1 (4 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
vue.assertProp (cognitive 16) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:1682— vue.assertProp has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (9 pts), boolean chains 5, loops 1 (2 pts) (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition. This file is where this pass's cognitive complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 45 of the 58 methods over the threshold — including the worst — and 712 of the 909 points over it (78%), 5.8× the next-largest file (REDACTED at 122). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
vue.initComputed (cognitive 16) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:4750— vue.initComputed has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 2, ternaries 1 (2 pts), loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 45 of the 58 methods over the threshold — including the worst — and 712 of the 909 points over it (78%), 5.8× the next-largest file (REDACTED at 122). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
vue.genDefaultModel (cognitive 16) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:7416— vue.genDefaultModel has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 6, if/else 5, ternaries 3 (5 pts) (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition. This file is where this pass's cognitive complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 45 of the 58 methods over the threshold — including the worst — and 712 of the 909 points over it (78%), 5.8× the next-largest file (REDACTED at 122). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
vue.createCompilerCreator.createCompiler.compile (cognitive 16) duckling-fork-chinese/server/src/main/resources/static/js/vue.js:11739— vue.createCompilerCreator.createCompiler.compile has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (10 pts), boolean chains 3, loops 1 (2 pts), ternaries 1 (nesting depth added 6). Of this number, 15 points are the body's own statements and 1 belongs to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: duckling-fork-chinese/server/src/main/resources/static/js/vue.js holds 45 of the 58 methods over the threshold — including the worst — and 712 of the 909 points over it (78%), 5.8× the next-largest file (REDACTED at 122). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
FileTooLong: js/vue.js duckling-fork-chinese/server/src/main/resources/static/js/vue.js— FileTooLong — 7067 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 6567 over it, 14.13× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
TooManyMethods: TimeDataHelpers duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/helper/TimeDataHelpers.scala:31— TooManyMethods — 31 methods. The bar is 30 methods; this is 1 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Change-coupling hub: Examples.scala → Rules.scala, FuzzyDayIntervals.scala, Times.scala duckling-fork-chinese/learning/src/main/scala/com/xiaomi/duckling/dimension/time/Examples.scala— `duckling-fork-chinese/learning/src/main/scala/com/xiaomi/duckling/dimension/time/Examples.scala` changes together with 3 other files — `duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/Rules.scala`, `duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/rule/FuzzyDayIntervals.scala`, `duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/rule/Times.scala` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
D4 · Code Duplication· Edited copy of a member (26 corresponding lines) · ×1
Edited copy of a member (26 corresponding lines) duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/engine/VarcharLookup.scala:92— duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/engine/VarcharLookup.scala:92-117 | duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/engine/VarcharLookup.scala:119-149 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (23 corresponding lines) · ×1
Edited copy of a member (23 corresponding lines) duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/task/PlaceExtractor.scala:30— duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/task/PlaceExtractor.scala:30-52 | duckling-fork-chinese/server/src/main/scala/com/xiaomi/duckling/PlaceQuery.scala:28-51 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (14 corresponding lines) · ×1
Edited copy of a member (14 corresponding lines) duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/numeral/Prods.scala:124— duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/numeral/Prods.scala:124-137 | duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/numeral/Prods.scala:139-152 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (8 corresponding lines) · ×1
Edited copy of a member (8 corresponding lines) duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/Types.scala:289— duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/Types.scala:289-299 | duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/Types.scala:301-308 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (9 corresponding lines) · ×1
Edited copy of a member (9 corresponding lines) duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/engine/Engine.scala:48— duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/engine/Engine.scala:48-56 | duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/engine/Engine.scala:61-69 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (7 corresponding lines) · ×1
Edited copy of a member (7 corresponding lines) duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/helper/HolidayProvider.scala:259— duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/helper/HolidayProvider.scala:259-265 | duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/rule/LunarDays.scala:53-59 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (21 lines × 2) duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/task/PlaceExtractor.scala:32— duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/task/PlaceExtractor.scala:32-52 | duckling-fork-chinese/server/src/main/scala/com/xiaomi/duckling/PlaceQuery.scala:31-51 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/task/PlaceExtractor.scala:32` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) duckling-fork-chinese/learning/src/main/scala/com/xiaomi/duckling/task/NaiveBayesConsole.scala:170— duckling-fork-chinese/learning/src/main/scala/com/xiaomi/duckling/task/NaiveBayesConsole.scala:170-174 | duckling-fork-chinese/learning/src/main/scala/com/xiaomi/duckling/task/NaiveBayesDebug.scala:39-43 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6 lines × 2) duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/task/PlaceExtractor.scala:54— duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/task/PlaceExtractor.scala:54-59 | duckling-fork-chinese/server/src/main/scala/com/xiaomi/duckling/PlaceQuery.scala:53-58 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Off the main sequence: core — core: abstractness 0.06, instability 0.00, distance 0.94 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
P12 · CI test-gate honesty· Coverage collected but not gated · ×1
Coverage collected but not gated — CI collects a coverage report but no step enforces a minimum — coverage could halve and CI stays green. Add a step that fails the build when coverage drops below a floor (your coverage tool's minimum-threshold flag, or a coverage-gate action) so the number guards something. What was searched, so you can tell an absence from a miss: this repository's CI files AND its coverage configuration — the well-known coverage and test-runner config files, read at the repository root and inside workspace package directories two levels down, so a floor declared beside the tests rather than in the pipeline is credited — matched against the threshold settings this check knows by name. A floor set in your coverage service's web UI rather than in a committed file, or under a setting whose name is not one of those, is not seen here.
Third-party script without Subresource Integrity duckling-fork-chinese/server/src/main/resources/templates/index.html:26— `https://maxcdn.bootstrapcdn.com/bootstrap/3.3.4/js/bootstrap.min.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. 2 such include(s) across the repository's markup.
Orphaned file duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/helper/HolidayProvider.scala:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/package.scala:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/date/Rules.scala:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/Time.scala:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/Types.scala:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/engine/Engine.scala:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/predicates.scala:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/helper/TimePredicateHelpers.scala:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/Types.scala:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/rule/FuzzyDayIntervals.scala:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/helper/TimeDataHelpers.scala:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/duration/Rules.scala:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/repeat/Rules.scala:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/numeral/Rules.scala:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/rule/Times.scala:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file duckling-fork-chinese/learning/src/main/scala/com/xiaomi/duckling/task/NaiveBayesConsole.scala:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/ranking/OverlapResolver.scala:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/helper/TimeObjectHelpers.scala:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file duckling-fork-chinese/learning/src/main/scala/com/xiaomi/duckling/ranking/AnswersSelection.scala:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file minlp-tokenizer/minlptokenizer/tokenizer.py:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/Document.scala:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/JsonSerde.scala:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/engine/VarcharLookup.scala:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file duckling-fork-chinese/learning/src/main/scala/com/xiaomi/duckling/ranking/NaiveBayesLearning.scala:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/numeral/Prods.scala:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
+ 46 more in this group — see findings.md.
D34 · Knowledge Freshness· Most significant orphaned file · ×2
Most significant orphaned file duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/Rules.scala:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Most significant orphaned file duckling-fork-chinese/learning/src/main/scala/com/xiaomi/duckling/dimension/time/Examples.scala:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Duplicated predicate duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/task/PlaceExtractor.scala:56— `c.category == "国家" && c.name != "中华人民共和国"` appears character-identically in 2 files — duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/task/PlaceExtractor.scala, duckling-fork-chinese/server/src/main/scala/com/xiaomi/duckling/PlaceQuery.scala. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/Rules.scala:177— `td1.timeGrain > Day && td2.timeGrain < Day` appears character-identically in 2 files — duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/Rules.scala, duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/date/Rules.scala. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Fat interface: DuckDate (17 abstract members) duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/Types.scala:36— `DuckDate` declares 17 abstract members: `year`, `month`, `dayOfMonth`, `of`, `minusDays`, `dayOfWeek`, `withYear`, `withMonth`, `withDayOfMonth`, `plusDays`, `plusWeeks`, `plusMonths`, `plusYears`, `toLunar`, `toSolar`, `lengthOfMonth`, `comparedTo`. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 2 significant file(s) lose their only recent owner: duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/package.scala, duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/duration/Rules.scala. Pair on, review, or document these before any departure.
No ADRs found duckling-fork-chinese/build.sbt:20— No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `duckling-fork-chinese/build.sbt` makes this repository a deployable product (line 20).
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 1 of 2 project(s) overshoot their size bounds, lowering Project Cohesion to 0.0/10. The most over is `duckling-fork-chinese` (25721 LoC, 331 module-visible types across 84 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
Dormant codebase — 73 of 73 significant files have no living knowledge — the codebase as a whole is dormant, not 73 separate risks. Counted over 73 of the 216 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over. Re-engage owners or document before change.
Thin README README.md:1— The root README is 14 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, in the README and in the repository documents it links, it found no a build/run or getting-started section, no a testing section, no an architecture or project-map section. Sections are matched on HEADING text only, so material written under a heading this check does not recognise — or with no heading at all — is not seen and this row may understate what the document covers.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
No SAST REDACTED:4— No static application security testing detected. For this repository's stack, add scalafix or scapegoat (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 3 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
No release approval gate — The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
Benchmarks don't track allocations duckling-fork-chinese/benchmark/src/main/java/com/xiaomi/duckling/benchmark/DateTimeBenchmark.java— A JMH/Jetpack Benchmark suite exists but nothing turns on its allocation measurement — allocations (the main way hot code pressures a garbage collector or allocator) aren't being measured.
X5 · Nullable reference types· Scala's null is not held to the type system everywhere · ×1
Scala's null is not held to the type system everywhere — No build over this repository's 190 Scala product file(s) passes `-Yexplicit-nulls`, enables WartRemover's `Null` wart or runs Scalafix's `DisableSyntax.noNulls`, so every reference type admits null and nothing reports a `null` written into the code or returned from a Java API — the first one to reach a method call is a `NullPointerException`. `Option` by convention is a habit no tool here holds the code to.
Silent fallback default in catch duckling-fork-chinese/server/src/main/resources/static/js/vue.js:320— `looseEqual` swallows every exception into `return false` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 2 file(s) — `duckling-fork-chinese/server/src/main/resources/static/js/element-ui.js`, `duckling-fork-chinese/server/src/main/resources/static/js/index.js` — so the PII/GDPR sweep did not cover them at all.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a1da7b-0367-7349-91db-64e73c1ebbf9 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 9 · Warnings: 170 · Recommendations: 91 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 14-11-2026 @ 14:34 UTC.
Downloadable artifacts
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.