Executive summary
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 39 out of 100 and is rated Weak, and seven of its 11 critical findings are security problems in the build pipeline and in its code.
Accessibility, at 20, 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 8 points. Raising Accessibility to 70 would lift the score to about 55.
Four pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Two places in the code run text as code, which an attacker could use, and one pipeline step runs a download nobody checks. Pinning each tool to an exact version, replacing text run as code with direct calls and checking the download against a checksum 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.
If Accessibility rose from 20 to 70, the lowest score rated Strong, the score would rise from 39 to about 55.
New since the last survey: 51 findings
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Exception handling · Swallowed exception (empty catch) REDACTED
- Exception handling · Swallowed exception (empty catch) REDACTED
- Exception handling · Swallowed exception (empty catch) REDACTED
- Exception handling · Swallowed exception (empty catch) REDACTED
- Exception handling · Swallowed exception (empty catch) REDACTED
- Exception handling · Swallowed exception (empty catch) REDACTED
- Exception handling · Swallowed exception (empty catch) REDACTED
- Exception handling · Swallowed exception (empty catch) REDACTED
- 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/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/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
Fixed since the last survey: 20 findings
- Supply-chain Provenance & Signing REDACTED
- Type Safety · Type Safety
- Code Duplication · Forked directory tree (20 identical files, ~15718 lines × 2 trees) REDACTED
- Code Duplication · Wholesale file copy (228 identical lines × 2 files) REDACTED
- Code Duplication · Wholesale file copy (60 identical lines × 2 files) duckling-fork-chinese/server/src/main/resources/static/js/duckling-extract.js
- Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 25, cognitive 75) REDACTED
- Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 25, cognitive 75) duckling-fork-chinese/server/target/scala-2.11/classes/static/js/bfwone.js
- Cyclomatic Complexity · Complex function loadjs (cyclomatic 14, cognitive 36) REDACTED
- Cyclomatic Complexity · Complex function loadjs (cyclomatic 14, cognitive 36) duckling-fork-chinese/server/target/scala-2.11/classes/static/js/bfwone.js
- Test Coverage · Test Coverage
- Forms & labels · <select> without a programmatic label duckling-fork-chinese/server/target/scala-2.11/classes/static/js/vue.js
- Forms & labels · Link with no accessible name duckling-fork-chinese/server/target/scala-2.11/classes/static/js/vue.js
- Page structure · <html> without a lang duckling-fork-chinese/server/target/scala-2.11/classes/static/js/vue.js
- Page structure · Page without a main landmark duckling-fork-chinese/server/target/scala-2.11/classes/static/js/vue.js
- Page structure · <html> without a lang duckling-fork-chinese/server/target/scala-2.11/classes/template.html
- Page structure · Page without a main landmark duckling-fork-chinese/server/target/scala-2.11/classes/template.html
- Visual & motion safety · Low contrast colour pair in CSS (2.8:1) duckling-fork-chinese/server/target/scala-2.11/classes/templates/index.html
- Visual & motion safety · Low contrast colour pair in CSS (2.8:1) duckling-fork-chinese/server/target/scala-2.11/classes/static/css/element-ui.css
- Visual & motion safety · Low contrast colour pair in CSS (2.8:1) duckling-fork-chinese/server/target/scala-2.11/classes/static/css/index.css
- Visual & motion safety · Low contrast colour pair in CSS (3.6:1) duckling-fork-chinese/server/target/scala-2.11/classes/static/css/main.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 39. 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. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 engine.LexiconLookup | 2 ranking.Types | 3 dimension.currency | 4 dimension.numeral | 5 dimension.time.duration | 6 dimension.time.enums | 7 types | 8 dimension.time.Types | 9 dimension.time.predicates | 10 dimension.time | 11 dimension | 12 Types | 13 com.xiaomi.duckling | 14 constraints | 15 dimension.time.helper | 16 dimension.time.rule | 17 dimension.act | 18 dimension.age | 19 dimension.bloodtype | 20 dimension.constellation | 21 dimension.duplicate | 22 dimension.episode | 23 dimension.gender | 24 dimension.level | 25 dimension.multichar | 26 dimension.music | 27 dimension.numeral.fraction | 28 dimension.numeral.multiple | 29 dimension.numeral.seq | 30 dimension.ordinal | 31 dimension.phoneno | 32 dimension.place | 33 dimension.quantity | 34 dimension.rating | 35 dimension.time.date | 36 dimension.time.grain | 37 dimension.time.repeat | 38 dimension.url | 39 engine | 40 ranking |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 engine.LexiconLookup | ||||||||||||||||||||||||||||||||||||||||
| 2 ranking.Types | ||||||||||||||||||||||||||||||||||||||||
| 3 dimension.currency | 4 | 4 | 1 | |||||||||||||||||||||||||||||||||||||
| 4 dimension.numeral | 4 | 9 | 1 | |||||||||||||||||||||||||||||||||||||
| 5 dimension.time.duration | 4 | 4 | 1 | |||||||||||||||||||||||||||||||||||||
| 6 dimension.time.enums | 4 | |||||||||||||||||||||||||||||||||||||||
| 7 types | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 8 dimension.time.Types | 2 | |||||||||||||||||||||||||||||||||||||||
| 9 dimension.time.predicates | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 10 dimension.time | 1 | 1 | 1 | 2 | 5 | 2 | 4 | 13 | 1 | |||||||||||||||||||||||||||||||
| 11 dimension | 2 | 1 | 2 | 1 | 1 | 3 | 1 | 1 | 15 | 1 | ||||||||||||||||||||||||||||||
| 12 Types | 1 | 1 | 1 | 2 | 1 | 1 | 4 | |||||||||||||||||||||||||||||||||
| 13 com.xiaomi.duckling | 7 | 3 | 14 | |||||||||||||||||||||||||||||||||||||
| 14 constraints | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 15 dimension.time.helper | 3 | 3 | 4 | 3 | 3 | 3 | ||||||||||||||||||||||||||||||||||
| 16 dimension.time.rule | 2 | 1 | 2 | 3 | ||||||||||||||||||||||||||||||||||||
| 17 dimension.act | 4 | 1 | ||||||||||||||||||||||||||||||||||||||
| 18 dimension.age | 1 | 4 | 3 | 1 | ||||||||||||||||||||||||||||||||||||
| 19 dimension.bloodtype | 4 | 4 | 1 | |||||||||||||||||||||||||||||||||||||
| 20 dimension.constellation | 4 | 5 | 1 | |||||||||||||||||||||||||||||||||||||
| 21 dimension.duplicate | 4 | 4 | 1 | |||||||||||||||||||||||||||||||||||||
| 22 dimension.episode | 4 | 1 | ||||||||||||||||||||||||||||||||||||||
| 23 dimension.gender | 4 | 4 | 1 | |||||||||||||||||||||||||||||||||||||
| 24 dimension.level | 4 | 1 | ||||||||||||||||||||||||||||||||||||||
| 25 dimension.multichar | 4 | 4 | 1 | |||||||||||||||||||||||||||||||||||||
| 26 dimension.music | 4 | 4 | 1 | |||||||||||||||||||||||||||||||||||||
| 27 dimension.numeral.fraction | 4 | 4 | 1 | |||||||||||||||||||||||||||||||||||||
| 28 dimension.numeral.multiple | 4 | 4 | 1 | |||||||||||||||||||||||||||||||||||||
| 29 dimension.numeral.seq | 4 | 4 | 1 | |||||||||||||||||||||||||||||||||||||
| 30 dimension.ordinal | 4 | 4 | 1 | |||||||||||||||||||||||||||||||||||||
| 31 dimension.phoneno | 4 | 4 | 1 | |||||||||||||||||||||||||||||||||||||
| 32 dimension.place | 4 | 4 | 1 | |||||||||||||||||||||||||||||||||||||
| 33 dimension.quantity | 4 | 5 | 1 | |||||||||||||||||||||||||||||||||||||
| 34 dimension.rating | 1 | 4 | 3 | 1 | ||||||||||||||||||||||||||||||||||||
| 35 dimension.time.date | 1 | 4 | 4 | 1 | ||||||||||||||||||||||||||||||||||||
| 36 dimension.time.grain | 2 | 5 | 1 | |||||||||||||||||||||||||||||||||||||
| 37 dimension.time.repeat | 2 | 1 | 3 | 4 | 4 | 1 | ||||||||||||||||||||||||||||||||||
| 38 dimension.url | 4 | 4 | 1 | |||||||||||||||||||||||||||||||||||||
| 39 engine | 1 | 8 | 6 | 6 | ||||||||||||||||||||||||||||||||||||
| 40 ranking | 4 | 3 | 15 | 1 |
3→11 dimension.currency uses dimension part of a loop✕
- Connections
- 4 pairs of types, where a type in dimension.currency uses a type in dimension.
- The types involved
com.xiaomi.duckling.dimension.currency.Currency→com.xiaomi.duckling.dimension.Dimensioncom.xiaomi.duckling.dimension.currency.Examples→com.xiaomi.duckling.dimension.DimExamplescom.xiaomi.duckling.dimension.currency.Examples→com.xiaomi.duckling.dimension.Dimensioncom.xiaomi.duckling.dimension.currency.Rules→com.xiaomi.duckling.dimension.DimRules
- Direction
- dimension.currency uses dimension, so a change to dimension can break dimension.currency, while a change to dimension.currency can't break dimension.
- 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.
3→12 dimension.currency uses Types part of a loop✕
- Connections
- 4 pairs of types, where a type in dimension.currency uses a type in Types.
- The types involved
com.xiaomi.duckling.dimension.currency.CurrencyData→com.xiaomi.duckling.Types.Contextcom.xiaomi.duckling.dimension.currency.CurrencyData→com.xiaomi.duckling.Types.Optionscom.xiaomi.duckling.dimension.currency.CurrencyData→com.xiaomi.duckling.Types.Resolvablecom.xiaomi.duckling.dimension.currency.Rules→com.xiaomi.duckling.Types.Token
- Direction
- dimension.currency uses Types, so a change to Types can break dimension.currency, while a change to dimension.currency can't break Types.
- 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.
3→13 dimension.currency uses com.xiaomi.duckling part of a loop✕
- Connections
- 1 pair of types, where a type in dimension.currency uses a type in com.xiaomi.duckling.
- The types involved
com.xiaomi.duckling.dimension.currency.Currency→com.xiaomi.duckling.Rules
- Direction
- dimension.currency uses com.xiaomi.duckling, so a change to com.xiaomi.duckling can break dimension.currency, while a change to dimension.currency 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.
4→11 dimension.numeral uses dimension part of a loop✕
- Connections
- 4 pairs of types, where a type in dimension.numeral uses a type in dimension.
- The types involved
com.xiaomi.duckling.dimension.numeral.Examples→com.xiaomi.duckling.dimension.DimExamplescom.xiaomi.duckling.dimension.numeral.Examples→com.xiaomi.duckling.dimension.Dimensioncom.xiaomi.duckling.dimension.numeral.Numeral→com.xiaomi.duckling.dimension.Dimensioncom.xiaomi.duckling.dimension.numeral.Rules→com.xiaomi.duckling.dimension.DimRules
- Direction
- dimension.numeral uses dimension, so a change to dimension can break dimension.numeral, while a change to dimension.numeral can't break dimension.
- 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.
4→12 dimension.numeral uses Types part of a loop✕
- Connections
- 9 pairs of types, where a type in dimension.numeral uses a type in Types.
- The types involved
com.xiaomi.duckling.dimension.numeral.IntervalValue→com.xiaomi.duckling.Types.ResolvedValuecom.xiaomi.duckling.dimension.numeral.NumeralData→com.xiaomi.duckling.Types.Contextcom.xiaomi.duckling.dimension.numeral.NumeralData→com.xiaomi.duckling.Types.Optionscom.xiaomi.duckling.dimension.numeral.NumeralData→com.xiaomi.duckling.Types.Resolvablecom.xiaomi.duckling.dimension.numeral.Predicates→com.xiaomi.duckling.Types.Tokencom.xiaomi.duckling.dimension.numeral.Prods→com.xiaomi.duckling.Types.Tokencom.xiaomi.duckling.dimension.numeral.fraction→com.xiaomi.duckling.Types.Tokencom.xiaomi.duckling.dimension.numeral.multiple→com.xiaomi.duckling.Types.Tokencom.xiaomi.duckling.dimension.numeral.seq→com.xiaomi.duckling.Types.Token
- Direction
- dimension.numeral uses Types, so a change to Types can break dimension.numeral, while a change to dimension.numeral can't break Types.
- 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.
4→13 dimension.numeral uses com.xiaomi.duckling part of a loop✕
- Connections
- 1 pair of types, where a type in dimension.numeral uses a type in com.xiaomi.duckling.
- The types involved
com.xiaomi.duckling.dimension.numeral.Numeral→com.xiaomi.duckling.Rules
- Direction
- dimension.numeral uses com.xiaomi.duckling, so a change to com.xiaomi.duckling can break dimension.numeral, while a change to dimension.numeral 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.
5→11 dimension.time.duration uses dimension part of a loop✕
- Connections
- 4 pairs of types, where a type in dimension.time.duration uses a type in dimension.
- The types involved
com.xiaomi.duckling.dimension.time.duration.Duration→com.xiaomi.duckling.dimension.Dimensioncom.xiaomi.duckling.dimension.time.duration.Examples→com.xiaomi.duckling.dimension.DimExamplescom.xiaomi.duckling.dimension.time.duration.Examples→com.xiaomi.duckling.dimension.Dimensioncom.xiaomi.duckling.dimension.time.duration.Rules→com.xiaomi.duckling.dimension.DimRules
- 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
- 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.
5→12 dimension.time.duration uses Types part of a loop✕
- Connections
- 4 pairs of types, where a type in dimension.time.duration uses a type in Types.
- The types involved
com.xiaomi.duckling.dimension.time.duration.DurationData→com.xiaomi.duckling.Types.Contextcom.xiaomi.duckling.dimension.time.duration.DurationData→com.xiaomi.duckling.Types.Optionscom.xiaomi.duckling.dimension.time.duration.DurationData→com.xiaomi.duckling.Types.Resolvablecom.xiaomi.duckling.dimension.time.duration.DurationData→com.xiaomi.duckling.Types.ResolvedValue
- 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
- 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.
5→13 dimension.time.duration uses com.xiaomi.duckling part of a loop✕
- Connections
- 1 pair of types, where a type in dimension.time.duration uses a type in com.xiaomi.duckling.
- The types involved
com.xiaomi.duckling.dimension.time.duration.Duration→com.xiaomi.duckling.Rules
- Direction
- dimension.time.duration uses com.xiaomi.duckling, so a change to com.xiaomi.duckling can break dimension.time.duration, while a change to dimension.time.duration 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.
6→12 dimension.time.enums uses Types part of a loop✕
- Connections
- 4 pairs of types, where a type in dimension.time.enums uses a type in Types.
- The types involved
com.xiaomi.duckling.dimension.time.enums.Grain→com.xiaomi.duckling.Types.Contextcom.xiaomi.duckling.dimension.time.enums.Grain→com.xiaomi.duckling.Types.Optionscom.xiaomi.duckling.dimension.time.enums.Grain→com.xiaomi.duckling.Types.Resolvablecom.xiaomi.duckling.dimension.time.enums.Grain→com.xiaomi.duckling.Types.ResolvedValue
- Direction
- dimension.time.enums uses Types, so a change to Types can break dimension.time.enums, while a change to dimension.time.enums can't break Types.
- 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.
7→12 types uses Types part of a loop✕
- Connections
- 2 pairs of types, where a type in types uses a type in Types.
- The types involved
com.xiaomi.duckling.types.Node→com.xiaomi.duckling.Types.Rangecom.xiaomi.duckling.types.Node→com.xiaomi.duckling.Types.Token
- Direction
- types uses Types, so a change to Types can break types, while a change to types can't break Types.
- 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.
7→13 types uses com.xiaomi.duckling part of a loop✕
- Connections
- 1 pair of types, where a type in types uses a type in com.xiaomi.duckling.
- The types involved
com.xiaomi.duckling.types.Node→com.xiaomi.duckling.Document
- Direction
- types uses com.xiaomi.duckling, so a change to com.xiaomi.duckling can break types, while a change to types 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.
8→6 dimension.time.Types uses dimension.time.enums✕
- Connections
- 2 pairs of types, where a type in dimension.time.Types uses a type in dimension.time.enums.
- The types involved
com.xiaomi.duckling.dimension.time.Types.DuckDateTime→com.xiaomi.duckling.dimension.time.enums.Calendarcom.xiaomi.duckling.dimension.time.Types.TimeObject→com.xiaomi.duckling.dimension.time.enums.Calendar
- Direction
- 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.
9→6 dimension.time.predicates uses dimension.time.enums✕
- Connections
- 1 pair of types, where a type in dimension.time.predicates uses a type in dimension.time.enums.
- The types involved
com.xiaomi.duckling.dimension.time.predicates.TimeDatePredicate→com.xiaomi.duckling.dimension.time.enums.Calendar
- Direction
- 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.
9→10 dimension.time.predicates uses dimension.time part of a loop✕
- Connections
- 2 pairs of types, where a type in dimension.time.predicates uses a type in dimension.time.
- The types involved
com.xiaomi.duckling.dimension.time.predicates.ReplacePartPredicate→com.xiaomi.duckling.dimension.time.TimeDatacom.xiaomi.duckling.dimension.time.predicates.SequencePredicate→com.xiaomi.duckling.dimension.time.TimeData
- 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
- 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.
10→2 dimension.time uses ranking.Types✕
- Connections
- 1 pair of types, where a type in dimension.time uses a type in ranking.Types.
- The types involved
com.xiaomi.duckling.dimension.time.Time→com.xiaomi.duckling.ranking.Types.Feature
- Direction
- dimension.time uses ranking.Types, so a change to ranking.Types can break dimension.time, while a change to dimension.time can't break ranking.Types.
- Position
- Below the diagonal: dimension.time uses a module listed above it, which is the healthy direction.
10→5 dimension.time uses dimension.time.duration✕
- Connections
- 1 pair of types, where a type in dimension.time uses a type in dimension.time.duration.
- The types involved
com.xiaomi.duckling.dimension.time.duration→com.xiaomi.duckling.dimension.time.duration.DurationData
- Direction
- dimension.time uses dimension.time.duration, so a change to dimension.time.duration can break dimension.time, while a change to dimension.time can't break dimension.time.duration.
- Position
- Below the diagonal: dimension.time uses a module listed above it, which is the healthy direction.
10→6 dimension.time uses dimension.time.enums✕
- Connections
- 1 pair of types, where a type in dimension.time uses a type in dimension.time.enums.
- The types involved
com.xiaomi.duckling.dimension.time.TimeData→com.xiaomi.duckling.dimension.time.enums.Calendar
- 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.
10→7 dimension.time uses types✕
- Connections
- 2 pairs of types, where a type in dimension.time uses a type in types.
- The types involved
com.xiaomi.duckling.dimension.time.Prods→com.xiaomi.duckling.types.Nodecom.xiaomi.duckling.dimension.time.Time→com.xiaomi.duckling.types.Node
- Direction
- dimension.time uses types, so a change to types can break dimension.time, while a change to dimension.time can't break types.
- Position
- Below the diagonal: dimension.time uses a module listed above it, which is the healthy direction.
10→8 dimension.time uses dimension.time.Types✕
- Connections
- 5 pairs of types, where a type in dimension.time uses a type in dimension.time.Types.
- The types involved
com.xiaomi.duckling.dimension.time.Helpers→com.xiaomi.duckling.dimension.time.Types.InstantValuecom.xiaomi.duckling.dimension.time.TimeData→com.xiaomi.duckling.dimension.time.Types.TimeObjectcom.xiaomi.duckling.dimension.time.TimeValue→com.xiaomi.duckling.dimension.time.Types.SingleTimeValuecom.xiaomi.duckling.dimension.time.Types→com.xiaomi.duckling.dimension.time.Types.TimeContextcom.xiaomi.duckling.dimension.time.Types→com.xiaomi.duckling.dimension.time.Types.TimeObject
- 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.
10→9 dimension.time uses dimension.time.predicates✕
- Connections
- 2 pairs of types, where a type in dimension.time uses a type in dimension.time.predicates.
- The types involved
com.xiaomi.duckling.dimension.time.Helpers→com.xiaomi.duckling.dimension.time.predicates.TimePredicatecom.xiaomi.duckling.dimension.time.TimeData→com.xiaomi.duckling.dimension.time.predicates.TimePredicate
- Direction
- 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
- Below the diagonal: dimension.time uses a module listed above it, which is the healthy direction.
10→11 dimension.time uses dimension part of a loop✕
- Connections
- 4 pairs of types, where a type in dimension.time uses a type in dimension.
- The types involved
com.xiaomi.duckling.dimension.time.Examples→com.xiaomi.duckling.dimension.DimExamplescom.xiaomi.duckling.dimension.time.Examples→com.xiaomi.duckling.dimension.Dimensioncom.xiaomi.duckling.dimension.time.Rules→com.xiaomi.duckling.dimension.DimRulescom.xiaomi.duckling.dimension.time.Time→com.xiaomi.duckling.dimension.Dimension
- Direction
- dimension.time uses dimension, so a change to dimension can break dimension.time, while a change to dimension.time can't break dimension.
- 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.
10→12 dimension.time uses Types part of a loop✕
- Connections
- 13 pairs of types, where a type in dimension.time uses a type in Types.
- The types involved
com.xiaomi.duckling.dimension.time.Helpers→com.xiaomi.duckling.Types.Rulecom.xiaomi.duckling.dimension.time.Helpers→com.xiaomi.duckling.Types.Tokencom.xiaomi.duckling.dimension.time.Prods→com.xiaomi.duckling.Types.Optionscom.xiaomi.duckling.dimension.time.Prods→com.xiaomi.duckling.Types.Tokencom.xiaomi.duckling.dimension.time.Rules→com.xiaomi.duckling.Types.Optionscom.xiaomi.duckling.dimension.time.Rules→com.xiaomi.duckling.Types.Rulecom.xiaomi.duckling.dimension.time.Rules→com.xiaomi.duckling.Types.Tokencom.xiaomi.duckling.dimension.time.Time→com.xiaomi.duckling.Types.Tokencom.xiaomi.duckling.dimension.time.TimeData→com.xiaomi.duckling.Types.Contextcom.xiaomi.duckling.dimension.time.TimeData→com.xiaomi.duckling.Types.Optionscom.xiaomi.duckling.dimension.time.TimeData→com.xiaomi.duckling.Types.Resolvablecom.xiaomi.duckling.dimension.time.TimeValue→com.xiaomi.duckling.Types.ResolvedValuecom.xiaomi.duckling.dimension.time.duration→com.xiaomi.duckling.Types.Token
- Direction
- dimension.time uses Types, so a change to Types can break dimension.time, while a change to dimension.time can't break Types.
- 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.
10→13 dimension.time uses com.xiaomi.duckling part of a loop✕
- Connections
- 1 pair of types, where a type in dimension.time uses a type in com.xiaomi.duckling.
- The types involved
com.xiaomi.duckling.dimension.time.Time→com.xiaomi.duckling.Rules
- Direction
- dimension.time uses com.xiaomi.duckling, so a change to com.xiaomi.duckling can break dimension.time, while a change to dimension.time 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.
11→2 dimension uses ranking.Types✕
- Connections
- 2 pairs of types, where a type in dimension uses a type in ranking.Types.
- The types involved
com.xiaomi.duckling.dimension.Dimension→com.xiaomi.duckling.ranking.Types.Featurecom.xiaomi.duckling.dimension.implicits→com.xiaomi.duckling.ranking.Types.Feature
- Direction
- dimension uses ranking.Types, so a change to ranking.Types can break dimension, while a change to dimension can't break ranking.Types.
- Position
- Below the diagonal: dimension uses a module listed above it, which is the healthy direction.
11→3 dimension uses dimension.currency✕
- Connections
- 1 pair of types, where a type in dimension uses a type in dimension.currency.
- The types involved
com.xiaomi.duckling.dimension.currency→com.xiaomi.duckling.dimension.currency.CurrencyData
- Direction
- dimension uses dimension.currency, so a change to dimension.currency can break dimension, while a change to dimension can't break dimension.currency.
- Position
- Below the diagonal: dimension uses a module listed above it, which is the healthy direction.
11→4 dimension uses dimension.numeral✕
- Connections
- 2 pairs of types, where a type in dimension uses a type in dimension.numeral.
- The types involved
com.xiaomi.duckling.dimension.age→com.xiaomi.duckling.dimension.numeral.IntervalValuecom.xiaomi.duckling.dimension.rating→com.xiaomi.duckling.dimension.numeral.IntervalValue
- Direction
- dimension uses dimension.numeral, so a change to dimension.numeral can break dimension, while a change to dimension can't break dimension.numeral.
- Position
- Below the diagonal: dimension uses a module listed above it, which is the healthy direction.
11→6 dimension uses dimension.time.enums✕
- Connections
- 1 pair of types, where a type in dimension uses a type in dimension.time.enums.
- The types involved
com.xiaomi.duckling.dimension.time→com.xiaomi.duckling.dimension.time.enums.Calendar
- 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.
11→7 dimension uses types✕
- Connections
- 1 pair of types, where a type in dimension uses a type in types.
- The types involved
com.xiaomi.duckling.dimension.Dimension→com.xiaomi.duckling.types.Node
- Direction
- dimension uses types, so a change to types can break dimension, while a change to dimension can't break types.
- Position
- Below the diagonal: dimension uses a module listed above it, which is the healthy direction.
11→8 dimension uses dimension.time.Types✕
- Connections
- 3 pairs of types, where a type in dimension uses a type in dimension.time.Types.
- The types involved
com.xiaomi.duckling.dimension.time→com.xiaomi.duckling.dimension.time.Types.DuckDateTimecom.xiaomi.duckling.dimension.time→com.xiaomi.duckling.dimension.time.Types.TimeContextcom.xiaomi.duckling.dimension.time→com.xiaomi.duckling.dimension.time.Types.TimeObject
- 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.
11→9 dimension uses dimension.time.predicates✕
- Connections
- 1 pair of types, where a type in dimension uses a type in dimension.time.predicates.
- The types involved
com.xiaomi.duckling.dimension.time→com.xiaomi.duckling.dimension.time.predicates.TimePredicate
- 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.
11→10 dimension uses dimension.time✕
- Connections
- 1 pair of types, where a type in dimension uses a type in dimension.time.
- The types involved
com.xiaomi.duckling.dimension.time→com.xiaomi.duckling.dimension.time.TimeData
- Direction
- dimension uses dimension.time, so a change to dimension.time can break dimension, while a change to dimension can't break dimension.time.
- Position
- Below the diagonal: dimension uses a module listed above it, which is the healthy direction.
11→12 dimension uses Types part of a loop✕
- Connections
- 15 pairs of types, where a type in dimension uses a type in Types.
- The types involved
com.xiaomi.duckling.dimension.DimRules→com.xiaomi.duckling.Types.Rulecom.xiaomi.duckling.dimension.Dimension→com.xiaomi.duckling.Types.Tokencom.xiaomi.duckling.dimension.Dimensions→com.xiaomi.duckling.Types.Rulecom.xiaomi.duckling.dimension.act→com.xiaomi.duckling.Types.Tokencom.xiaomi.duckling.dimension.age→com.xiaomi.duckling.Types.Tokencom.xiaomi.duckling.dimension.duplicate→com.xiaomi.duckling.Types.Tokencom.xiaomi.duckling.dimension.implicits→com.xiaomi.duckling.Types.Rangecom.xiaomi.duckling.dimension.level→com.xiaomi.duckling.Types.Tokencom.xiaomi.duckling.dimension.multichar→com.xiaomi.duckling.Types.Tokencom.xiaomi.duckling.dimension.ordinal→com.xiaomi.duckling.Types.Tokencom.xiaomi.duckling.dimension.phoneno→com.xiaomi.duckling.Types.Tokencom.xiaomi.duckling.dimension.rating→com.xiaomi.duckling.Types.Resolvablecom.xiaomi.duckling.dimension.rating→com.xiaomi.duckling.Types.Tokencom.xiaomi.duckling.dimension.season→com.xiaomi.duckling.Types.Tokencom.xiaomi.duckling.dimension.url→com.xiaomi.duckling.Types.Token
- Direction
- dimension uses Types, so a change to Types can break dimension, while a change to dimension can't break Types.
- 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.
11→13 dimension uses com.xiaomi.duckling part of a loop✕
- Connections
- 1 pair of types, where a type in dimension uses a type in com.xiaomi.duckling.
- The types involved
com.xiaomi.duckling.dimension.Dimension→com.xiaomi.duckling.Document
- 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.
12→1 Types uses engine.LexiconLookup✕
- Connections
- 1 pair of types, where a type in Types uses a type in engine.LexiconLookup.
- The types involved
com.xiaomi.duckling.Types.ItemLexicon→com.xiaomi.duckling.engine.LexiconLookup.Dict
- Direction
- Types uses engine.LexiconLookup, so a change to engine.LexiconLookup can break Types, while a change to Types can't break engine.LexiconLookup.
- Position
- Below the diagonal: Types uses a module listed above it, which is the healthy direction.
12→2 Types uses ranking.Types✕
- Connections
- 1 pair of types, where a type in Types uses a type in ranking.Types.
- The types involved
com.xiaomi.duckling.Types.Answer→com.xiaomi.duckling.ranking.Types.Feature
- Direction
- Types uses ranking.Types, so a change to ranking.Types can break Types, while a change to Types can't break ranking.Types.
- Position
- Below the diagonal: Types uses a module listed above it, which is the healthy direction.
12→4 Types uses dimension.numeral✕
- Connections
- 1 pair of types, where a type in Types uses a type in dimension.numeral.
- The types involved
com.xiaomi.duckling.Types.Options→com.xiaomi.duckling.dimension.numeral.NumeralOptions
- Direction
- Types uses dimension.numeral, so a change to dimension.numeral can break Types, while a change to Types can't break dimension.numeral.
- Position
- Below the diagonal: Types uses a module listed above it, which is the healthy direction.
12→7 Types uses types✕
- Connections
- 2 pairs of types, where a type in Types uses a type in types.
- The types involved
com.xiaomi.duckling.Types.Entity→com.xiaomi.duckling.types.Nodecom.xiaomi.duckling.Types.ResolvedToken→com.xiaomi.duckling.types.Node
- Direction
- Types uses types, so a change to types can break Types, while a change to Types can't break types.
- Position
- Below the diagonal: Types uses a module listed above it, which is the healthy direction.
12→8 Types uses dimension.time.Types✕
- Connections
- 1 pair of types, where a type in Types uses a type in dimension.time.Types.
- The types involved
com.xiaomi.duckling.Types.Context→com.xiaomi.duckling.dimension.time.Types.DuckDateTime
- Direction
- Types uses dimension.time.Types, so a change to dimension.time.Types can break Types, while a change to Types can't break dimension.time.Types.
- Position
- Below the diagonal: Types uses a module listed above it, which is the healthy direction.
12→10 Types uses dimension.time✕
- Connections
- 1 pair of types, where a type in Types uses a type in dimension.time.
- The types involved
com.xiaomi.duckling.Types.Options→com.xiaomi.duckling.dimension.time.TimeOptions
- Direction
- Types uses dimension.time, so a change to dimension.time can break Types, while a change to Types can't break dimension.time.
- Position
- Below the diagonal: Types uses a module listed above it, which is the healthy direction.
12→11 Types uses dimension✕
- Connections
- 4 pairs of types, where a type in Types uses a type in dimension.
- The types involved
com.xiaomi.duckling.Types.Answer→com.xiaomi.duckling.dimension.Dimensioncom.xiaomi.duckling.Types.Options→com.xiaomi.duckling.dimension.Dimensioncom.xiaomi.duckling.Types.ResolvedVal→com.xiaomi.duckling.dimension.Dimensioncom.xiaomi.duckling.Types.Token→com.xiaomi.duckling.dimension.Dimension
- Direction
- Types uses dimension, so a change to dimension can break Types, while a change to Types can't break dimension.
- Position
- Below the diagonal: Types uses a module listed above it, which is the healthy direction.
13→7 com.xiaomi.duckling uses types✕
- Connections
- 7 pairs of types, where a type in com.xiaomi.duckling uses a type in types.
- The types involved
com.xiaomi.duckling.Api→com.xiaomi.duckling.types.LanguageInfocom.xiaomi.duckling.Document→com.xiaomi.duckling.types.DependencyEdgecom.xiaomi.duckling.Document→com.xiaomi.duckling.types.LanguageInfocom.xiaomi.duckling.Document→com.xiaomi.duckling.types.Nodecom.xiaomi.duckling.Document→com.xiaomi.duckling.types.TokenLabelcom.xiaomi.duckling.DuckParser→com.xiaomi.duckling.types.LanguageInfocom.xiaomi.duckling.TokenVisualization→com.xiaomi.duckling.types.Node
- Direction
- com.xiaomi.duckling uses types, so a change to types can break com.xiaomi.duckling, while a change to com.xiaomi.duckling can't break types.
- Position
- Below the diagonal: com.xiaomi.duckling uses a module listed above it, which is the healthy direction.
13→11 com.xiaomi.duckling uses dimension✕
- Connections
- 3 pairs of types, where a type in com.xiaomi.duckling uses a type in dimension.
- The types involved
com.xiaomi.duckling.DuckParser→com.xiaomi.duckling.dimension.Dimensioncom.xiaomi.duckling.Rules→com.xiaomi.duckling.dimension.Dimensioncom.xiaomi.duckling.Types→com.xiaomi.duckling.dimension.Dimension
- Direction
- 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.
13→12 com.xiaomi.duckling uses Types✕
- Connections
- 14 pairs of types, where a type in com.xiaomi.duckling uses a type in Types.
- The types involved
com.xiaomi.duckling.Api→com.xiaomi.duckling.Types.Answercom.xiaomi.duckling.Api→com.xiaomi.duckling.Types.Contextcom.xiaomi.duckling.Api→com.xiaomi.duckling.Types.Entitycom.xiaomi.duckling.Api→com.xiaomi.duckling.Types.Optionscom.xiaomi.duckling.Api→com.xiaomi.duckling.Types.ResolvedTokencom.xiaomi.duckling.Document→com.xiaomi.duckling.Types.Rangecom.xiaomi.duckling.DuckParser→com.xiaomi.duckling.Types.Answercom.xiaomi.duckling.DuckParser→com.xiaomi.duckling.Types.Contextcom.xiaomi.duckling.DuckParser→com.xiaomi.duckling.Types.Optionscom.xiaomi.duckling.JsonSerde→com.xiaomi.duckling.Types.ResolvedTokencom.xiaomi.duckling.JsonSerde→com.xiaomi.duckling.Types.ResolvedValuecom.xiaomi.duckling.PlaceQuery→com.xiaomi.duckling.Types.ResolvedTokencom.xiaomi.duckling.Rules→com.xiaomi.duckling.Types.Rulecom.xiaomi.duckling.TokenVisualization→com.xiaomi.duckling.Types.Answer
- Direction
- com.xiaomi.duckling uses Types, so a change to Types can break com.xiaomi.duckling, while a change to com.xiaomi.duckling can't break Types.
- Position
- Below the diagonal: com.xiaomi.duckling uses a module listed above it, which is the healthy direction.
14→7 constraints uses types✕
- Connections
- 2 pairs of types, where a type in constraints uses a type in types.
- The types involved
com.xiaomi.duckling.constraints.Constraint→com.xiaomi.duckling.types.LanguageInfocom.xiaomi.duckling.constraints.TokenSpan→com.xiaomi.duckling.types.LanguageInfo
- Direction
- constraints uses types, so a change to types can break constraints, while a change to constraints can't break types.
- Position
- Below the diagonal: constraints uses a module listed above it, which is the healthy direction.
14→12 constraints uses Types✕
- Connections
- 2 pairs of types, where a type in constraints uses a type in Types.
- The types involved
com.xiaomi.duckling.constraints.Constraint→com.xiaomi.duckling.Types.ResolvedTokencom.xiaomi.duckling.constraints.TokenSpan→com.xiaomi.duckling.Types.ResolvedToken
- Direction
- constraints uses Types, so a change to Types can break constraints, while a change to constraints can't break Types.
- Position
- Below the diagonal: constraints uses a module listed above it, which is the healthy direction.
15→1 dimension.time.helper uses engine.LexiconLookup✕
- Connections
- 3 pairs of types, where a type in dimension.time.helper uses a type in engine.LexiconLookup.
- The types involved
com.xiaomi.duckling.dimension.time.helper.HolidayProvider→com.xiaomi.duckling.engine.LexiconLookup.Dictcom.xiaomi.duckling.dimension.time.helper.LocalHolidayProvider→com.xiaomi.duckling.engine.LexiconLookup.Dictcom.xiaomi.duckling.dimension.time.helper.SolarTermProvider→com.xiaomi.duckling.engine.LexiconLookup.Dict
- 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.
15→6 dimension.time.helper uses dimension.time.enums✕
- Connections
- 3 pairs of types, where a type in dimension.time.helper uses a type in dimension.time.enums.
- The types involved
com.xiaomi.duckling.dimension.time.helper.TimeDataHelpers→com.xiaomi.duckling.dimension.time.enums.Calendarcom.xiaomi.duckling.dimension.time.helper.TimeObjectHelpers→com.xiaomi.duckling.dimension.time.enums.Calendarcom.xiaomi.duckling.dimension.time.helper.TimeValueHelpers→com.xiaomi.duckling.dimension.time.enums.Calendar
- 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.
15→8 dimension.time.helper uses dimension.time.Types✕
- Connections
- 4 pairs of types, where a type in dimension.time.helper uses a type in dimension.time.Types.
- The types involved
com.xiaomi.duckling.dimension.time.helper.TimeObjectHelpers→com.xiaomi.duckling.dimension.time.Types.DuckDateTimecom.xiaomi.duckling.dimension.time.helper.TimeObjectHelpers→com.xiaomi.duckling.dimension.time.Types.SingleTimeValuecom.xiaomi.duckling.dimension.time.helper.TimeObjectHelpers→com.xiaomi.duckling.dimension.time.Types.TimeObjectcom.xiaomi.duckling.dimension.time.helper.TimeValueHelpers→com.xiaomi.duckling.dimension.time.Types.DuckDateTime
- 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.
15→9 dimension.time.helper uses dimension.time.predicates✕
- Connections
- 3 pairs of types, where a type in dimension.time.helper uses a type in dimension.time.predicates.
- The types involved
com.xiaomi.duckling.dimension.time.helper.TimePredicateHelpers→com.xiaomi.duckling.dimension.time.predicates.CycleSeriesPredicatecom.xiaomi.duckling.dimension.time.helper.TimePredicateHelpers→com.xiaomi.duckling.dimension.time.predicates.SeriesPredicatecom.xiaomi.duckling.dimension.time.helper.TimePredicateHelpers→com.xiaomi.duckling.dimension.time.predicates.TimePredicate
- 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.
15→10 dimension.time.helper uses dimension.time✕
- Connections
- 3 pairs of types, where a type in dimension.time.helper uses a type in dimension.time.
- The types involved
com.xiaomi.duckling.dimension.time.helper.TimeDataHelpers→com.xiaomi.duckling.dimension.time.TimeDatacom.xiaomi.duckling.dimension.time.helper.TimePredicateHelpers→com.xiaomi.duckling.dimension.time.TimeDatacom.xiaomi.duckling.dimension.time.helper.TimeValueHelpers→com.xiaomi.duckling.dimension.time.TimeValue
- 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.
15→12 dimension.time.helper uses Types✕
- Connections
- 3 pairs of types, where a type in dimension.time.helper uses a type in Types.
- The types involved
com.xiaomi.duckling.dimension.time.helper.HolidayProvider→com.xiaomi.duckling.Types.Tokencom.xiaomi.duckling.dimension.time.helper.LocalHolidayProvider→com.xiaomi.duckling.Types.Tokencom.xiaomi.duckling.dimension.time.helper.TimeValueHelpers→com.xiaomi.duckling.Types.Context
- Direction
- dimension.time.helper uses Types, so a change to Types can break dimension.time.helper, while a change to dimension.time.helper can't break Types.
- Position
- Below the diagonal: dimension.time.helper uses a module listed above it, which is the healthy direction.
16→1 dimension.time.rule uses engine.LexiconLookup✕
- Connections
- 2 pairs of types, where a type in dimension.time.rule uses a type in engine.LexiconLookup.
- The types involved
com.xiaomi.duckling.dimension.time.rule.Holidays→com.xiaomi.duckling.engine.LexiconLookup.Dictcom.xiaomi.duckling.dimension.time.rule.SolarTerms→com.xiaomi.duckling.engine.LexiconLookup.Dict
- 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.
16→9 dimension.time.rule uses dimension.time.predicates✕
- Connections
- 1 pair of types, where a type in dimension.time.rule uses a type in dimension.time.predicates.
- The types involved
com.xiaomi.duckling.dimension.time.rule.FuzzyDayIntervals→com.xiaomi.duckling.dimension.time.predicates.TimeDatePredicate
- 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.
16→10 dimension.time.rule uses dimension.time✕
- Connections
- 2 pairs of types, where a type in dimension.time.rule uses a type in dimension.time.
- The types involved
com.xiaomi.duckling.dimension.time.rule.FuzzyDayIntervals→com.xiaomi.duckling.dimension.time.TimeDatacom.xiaomi.duckling.dimension.time.rule.LunarDays→com.xiaomi.duckling.dimension.time.TimeData
- 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.
16→12 dimension.time.rule uses Types✕
- Connections
- 3 pairs of types, where a type in dimension.time.rule uses a type in Types.
- The types involved
com.xiaomi.duckling.dimension.time.rule.FuzzyDayIntervals→com.xiaomi.duckling.Types.Tokencom.xiaomi.duckling.dimension.time.rule.Holidays→com.xiaomi.duckling.Types.Tokencom.xiaomi.duckling.dimension.time.rule.Weeks→com.xiaomi.duckling.Types.Rule
- Direction
- dimension.time.rule uses Types, so a change to Types can break dimension.time.rule, while a change to dimension.time.rule can't break Types.
- Position
- Below the diagonal: dimension.time.rule uses a module listed above it, which is the healthy direction.
17→11 dimension.act uses dimension✕
- Connections
- 4 pairs of types, where a type in dimension.act uses a type in dimension.
- The types involved
com.xiaomi.duckling.dimension.act.Act→com.xiaomi.duckling.dimension.Dimensioncom.xiaomi.duckling.dimension.act.Examples→com.xiaomi.duckling.dimension.DimExamplescom.xiaomi.duckling.dimension.act.Examples→com.xiaomi.duckling.dimension.Dimensioncom.xiaomi.duckling.dimension.act.Rules→com.xiaomi.duckling.dimension.DimRules
- Direction
- dimension.act uses dimension, so a change to dimension can break dimension.act, while a change to dimension.act can't break dimension.
- Position
- Below the diagonal: dimension.act uses a module listed above it, which is the healthy direction.
17→13 dimension.act uses com.xiaomi.duckling✕
- Connections
- 1 pair of types, where a type in dimension.act uses a type in com.xiaomi.duckling.
- The types involved
com.xiaomi.duckling.dimension.act.Act→com.xiaomi.duckling.Rules
- Direction
- dimension.act uses com.xiaomi.duckling, so a change to com.xiaomi.duckling can break dimension.act, while a change to dimension.act can't break com.xiaomi.duckling.
- Position
- Below the diagonal: dimension.act uses a module listed above it, which is the healthy direction.
18→4 dimension.age uses dimension.numeral✕
- Connections
- 1 pair of types, where a type in dimension.age uses a type in dimension.numeral.
- The types involved
com.xiaomi.duckling.dimension.age.AgeData→com.xiaomi.duckling.dimension.numeral.IntervalValue
- 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.
18→11 dimension.age uses dimension✕
- Connections
- 4 pairs of types, where a type in dimension.age uses a type in dimension.
- The types involved
com.xiaomi.duckling.dimension.age.Age→com.xiaomi.duckling.dimension.Dimensioncom.xiaomi.duckling.dimension.age.Examples→com.xiaomi.duckling.dimension.DimExamplescom.xiaomi.duckling.dimension.age.Examples→com.xiaomi.duckling.dimension.Dimensioncom.xiaomi.duckling.dimension.age.Rules→com.xiaomi.duckling.dimension.DimRules
- Direction
- dimension.age uses dimension, so a change to dimension can break dimension.age, while a change to dimension.age can't break dimension.
- Position
- Below the diagonal: dimension.age uses a module listed above it, which is the healthy direction.
18→12 dimension.age uses Types✕
- Connections
- 3 pairs of types, where a type in dimension.age uses a type in Types.
- The types involved
com.xiaomi.duckling.dimension.age.AgeData→com.xiaomi.duckling.Types.Contextcom.xiaomi.duckling.dimension.age.AgeData→com.xiaomi.duckling.Types.Optionscom.xiaomi.duckling.dimension.age.AgeData→com.xiaomi.duckling.Types.Resolvable
- Direction
- dimension.age uses Types, so a change to Types can break dimension.age, while a change to dimension.age can't break Types.
- Position
- Below the diagonal: dimension.age uses a module listed above it, which is the healthy direction.
18→13 dimension.age uses com.xiaomi.duckling✕
- Connections
- 1 pair of types, where a type in dimension.age uses a type in com.xiaomi.duckling.
- The types involved
com.xiaomi.duckling.dimension.age.Age→com.xiaomi.duckling.Rules
- Direction
- dimension.age uses com.xiaomi.duckling, so a change to com.xiaomi.duckling can break dimension.age, while a change to dimension.age can't break com.xiaomi.duckling.
- Position
- Below the diagonal: dimension.age uses a module listed above it, which is the healthy direction.
19→11 dimension.bloodtype uses dimension✕
- Connections
- 4 pairs of types, where a type in dimension.bloodtype uses a type in dimension.
- The types involved
com.xiaomi.duckling.dimension.bloodtype.BloodType→com.xiaomi.duckling.dimension.Dimensioncom.xiaomi.duckling.dimension.bloodtype.Examples→com.xiaomi.duckling.dimension.DimExamplescom.xiaomi.duckling.dimension.bloodtype.Examples→com.xiaomi.duckling.dimension.Dimensioncom.xiaomi.duckling.dimension.bloodtype.Rules→com.xiaomi.duckling.dimension.DimRules
- 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.
19→12 dimension.bloodtype uses Types✕
- Connections
- 4 pairs of types, where a type in dimension.bloodtype uses a type in Types.
- The types involved
com.xiaomi.duckling.dimension.bloodtype.BloodTypeData→com.xiaomi.duckling.Types.Contextcom.xiaomi.duckling.dimension.bloodtype.BloodTypeData→com.xiaomi.duckling.Types.Optionscom.xiaomi.duckling.dimension.bloodtype.BloodTypeData→com.xiaomi.duckling.Types.Resolvablecom.xiaomi.duckling.dimension.bloodtype.BloodTypeData→com.xiaomi.duckling.Types.ResolvedValue
- Direction
- dimension.bloodtype uses Types, so a change to Types can break dimension.bloodtype, while a change to dimension.bloodtype can't break Types.
- Position
- Below the diagonal: dimension.bloodtype uses a module listed above it, which is the healthy direction.
19→13 dimension.bloodtype uses com.xiaomi.duckling✕
- Connections
- 1 pair of types, where a type in dimension.bloodtype uses a type in com.xiaomi.duckling.
- The types involved
com.xiaomi.duckling.dimension.bloodtype.BloodType→com.xiaomi.duckling.Rules
- Direction
- dimension.bloodtype uses com.xiaomi.duckling, so a change to com.xiaomi.duckling can break dimension.bloodtype, while a change to dimension.bloodtype can't break com.xiaomi.duckling.
- Position
- Below the diagonal: dimension.bloodtype uses a module listed above it, which is the healthy direction.
20→11 dimension.constellation uses dimension✕
- Connections
- 4 pairs of types, where a type in dimension.constellation uses a type in dimension.
- The types involved
com.xiaomi.duckling.dimension.constellation.Constellation→com.xiaomi.duckling.dimension.Dimensioncom.xiaomi.duckling.dimension.constellation.Examples→com.xiaomi.duckling.dimension.DimExamplescom.xiaomi.duckling.dimension.constellation.Examples→com.xiaomi.duckling.dimension.Dimensioncom.xiaomi.duckling.dimension.constellation.Rules→com.xiaomi.duckling.dimension.DimRules
- 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.
20→12 dimension.constellation uses Types✕
- Connections
- 5 pairs of types, where a type in dimension.constellation uses a type in Types.
- The types involved
com.xiaomi.duckling.dimension.constellation.ConstellationData→com.xiaomi.duckling.Types.Contextcom.xiaomi.duckling.dimension.constellation.ConstellationData→com.xiaomi.duckling.Types.Optionscom.xiaomi.duckling.dimension.constellation.ConstellationData→com.xiaomi.duckling.Types.Resolvablecom.xiaomi.duckling.dimension.constellation.ConstellationData→com.xiaomi.duckling.Types.ResolvedValuecom.xiaomi.duckling.dimension.constellation.Rules→com.xiaomi.duckling.Types.Token
- 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.
20→13 dimension.constellation uses com.xiaomi.duckling✕
- Connections
- 1 pair of types, where a type in dimension.constellation uses a type in com.xiaomi.duckling.
- The types involved
com.xiaomi.duckling.dimension.constellation.Constellation→com.xiaomi.duckling.Rules
- Direction
- dimension.constellation uses com.xiaomi.duckling, so a change to com.xiaomi.duckling can break dimension.constellation, while a change to dimension.constellation can't break com.xiaomi.duckling.
- Position
- Below the diagonal: dimension.constellation uses a module listed above it, which is the healthy direction.
21→11 dimension.duplicate uses dimension✕
- Connections
- 4 pairs of types, where a type in dimension.duplicate uses a type in dimension.
- The types involved
com.xiaomi.duckling.dimension.duplicate.Duplicate→com.xiaomi.duckling.dimension.Dimensioncom.xiaomi.duckling.dimension.duplicate.Examples→com.xiaomi.duckling.dimension.DimExamplescom.xiaomi.duckling.dimension.duplicate.Examples→com.xiaomi.duckling.dimension.Dimensioncom.xiaomi.duckling.dimension.duplicate.Rules→com.xiaomi.duckling.dimension.DimRules
- 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.
21→12 dimension.duplicate uses Types✕
- Connections
- 4 pairs of types, where a type in dimension.duplicate uses a type in Types.
- The types involved
com.xiaomi.duckling.dimension.duplicate.DuplicateData→com.xiaomi.duckling.Types.Contextcom.xiaomi.duckling.dimension.duplicate.DuplicateData→com.xiaomi.duckling.Types.Optionscom.xiaomi.duckling.dimension.duplicate.DuplicateData→com.xiaomi.duckling.Types.Resolvablecom.xiaomi.duckling.dimension.duplicate.DuplicateData→com.xiaomi.duckling.Types.ResolvedValue
- Direction
- dimension.duplicate uses Types, so a change to Types can break dimension.duplicate, while a change to dimension.duplicate can't break Types.
- Position
- Below the diagonal: dimension.duplicate uses a module listed above it, which is the healthy direction.
21→13 dimension.duplicate uses com.xiaomi.duckling✕
- Connections
- 1 pair of types, where a type in dimension.duplicate uses a type in com.xiaomi.duckling.
- The types involved
com.xiaomi.duckling.dimension.duplicate.Duplicate→com.xiaomi.duckling.Rules
- Direction
- dimension.duplicate uses com.xiaomi.duckling, so a change to com.xiaomi.duckling can break dimension.duplicate, while a change to dimension.duplicate can't break com.xiaomi.duckling.
- Position
- Below the diagonal: dimension.duplicate uses a module listed above it, which is the healthy direction.
22→11 dimension.episode uses dimension✕
- Connections
- 4 pairs of types, where a type in dimension.episode uses a type in dimension.
- The types involved
com.xiaomi.duckling.dimension.episode.Episode→com.xiaomi.duckling.dimension.Dimensioncom.xiaomi.duckling.dimension.episode.Examples→com.xiaomi.duckling.dimension.DimExamplescom.xiaomi.duckling.dimension.episode.Examples→com.xiaomi.duckling.dimension.Dimensioncom.xiaomi.duckling.dimension.episode.Rules→com.xiaomi.duckling.dimension.DimRules
- Direction
- dimension.episode uses dimension, so a change to dimension can break dimension.episode, while a change to dimension.episode can't break dimension.
- Position
- Below the diagonal: dimension.episode uses a module listed above it, which is the healthy direction.
22→13 dimension.episode uses com.xiaomi.duckling✕
- Connections
- 1 pair of types, where a type in dimension.episode uses a type in com.xiaomi.duckling.
- The types involved
com.xiaomi.duckling.dimension.episode.Episode→com.xiaomi.duckling.Rules
- Direction
- dimension.episode uses com.xiaomi.duckling, so a change to com.xiaomi.duckling can break dimension.episode, while a change to dimension.episode can't break com.xiaomi.duckling.
- Position
- Below the diagonal: dimension.episode uses a module listed above it, which is the healthy direction.
23→11 dimension.gender uses dimension✕
- Connections
- 4 pairs of types, where a type in dimension.gender uses a type in dimension.
- The types involved
com.xiaomi.duckling.dimension.gender.Examples→com.xiaomi.duckling.dimension.DimExamplescom.xiaomi.duckling.dimension.gender.Examples→com.xiaomi.duckling.dimension.Dimensioncom.xiaomi.duckling.dimension.gender.Gender→com.xiaomi.duckling.dimension.Dimensioncom.xiaomi.duckling.dimension.gender.Rules→com.xiaomi.duckling.dimension.DimRules
- Direction
- dimension.gender uses dimension, so a change to dimension can break dimension.gender, while a change to dimension.gender can't break dimension.
- Position
- Below the diagonal: dimension.gender uses a module listed above it, which is the healthy direction.
23→12 dimension.gender uses Types✕
- Connections
- 4 pairs of types, where a type in dimension.gender uses a type in Types.
- The types involved
com.xiaomi.duckling.dimension.gender.GenderData→com.xiaomi.duckling.Types.Contextcom.xiaomi.duckling.dimension.gender.GenderData→com.xiaomi.duckling.Types.Optionscom.xiaomi.duckling.dimension.gender.GenderData→com.xiaomi.duckling.Types.Resolvablecom.xiaomi.duckling.dimension.gender.GenderData→com.xiaomi.duckling.Types.ResolvedValue
- Direction
- dimension.gender uses Types, so a change to Types can break dimension.gender, while a change to dimension.gender can't break Types.
- Position
- Below the diagonal: dimension.gender uses a module listed above it, which is the healthy direction.
23→13 dimension.gender uses com.xiaomi.duckling✕
- Connections
- 1 pair of types, where a type in dimension.gender uses a type in com.xiaomi.duckling.
- The types involved
com.xiaomi.duckling.dimension.gender.Gender→com.xiaomi.duckling.Rules
- Direction
- dimension.gender uses com.xiaomi.duckling, so a change to com.xiaomi.duckling can break dimension.gender, while a change to dimension.gender can't break com.xiaomi.duckling.
- Position
- Below the diagonal: dimension.gender uses a module listed above it, which is the healthy direction.
24→11 dimension.level uses dimension✕
- Connections
- 4 pairs of types, where a type in dimension.level uses a type in dimension.
- The types involved
com.xiaomi.duckling.dimension.level.Examples→com.xiaomi.duckling.dimension.DimExamplescom.xiaomi.duckling.dimension.level.Examples→com.xiaomi.duckling.dimension.Dimensioncom.xiaomi.duckling.dimension.level.Level→com.xiaomi.duckling.dimension.Dimensioncom.xiaomi.duckling.dimension.level.Rules→com.xiaomi.duckling.dimension.DimRules
- Direction
- dimension.level uses dimension, so a change to dimension can break dimension.level, while a change to dimension.level can't break dimension.
- Position
- Below the diagonal: dimension.level uses a module listed above it, which is the healthy direction.
24→13 dimension.level uses com.xiaomi.duckling✕
- Connections
- 1 pair of types, where a type in dimension.level uses a type in com.xiaomi.duckling.
- The types involved
com.xiaomi.duckling.dimension.level.Level→com.xiaomi.duckling.Rules
- Direction
- dimension.level uses com.xiaomi.duckling, so a change to com.xiaomi.duckling can break dimension.level, while a change to dimension.level can't break com.xiaomi.duckling.
- Position
- Below the diagonal: dimension.level uses a module listed above it, which is the healthy direction.
25→11 dimension.multichar uses dimension✕
- Connections
- 4 pairs of types, where a type in dimension.multichar uses a type in dimension.
- The types involved
com.xiaomi.duckling.dimension.multichar.Examples→com.xiaomi.duckling.dimension.DimExamplescom.xiaomi.duckling.dimension.multichar.Examples→com.xiaomi.duckling.dimension.Dimensioncom.xiaomi.duckling.dimension.multichar.MultiChar→com.xiaomi.duckling.dimension.Dimensioncom.xiaomi.duckling.dimension.multichar.Rules→com.xiaomi.duckling.dimension.DimRules
- 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.
25→12 dimension.multichar uses Types✕
- Connections
- 4 pairs of types, where a type in dimension.multichar uses a type in Types.
- The types involved
com.xiaomi.duckling.dimension.multichar.MultiCharData→com.xiaomi.duckling.Types.Contextcom.xiaomi.duckling.dimension.multichar.MultiCharData→com.xiaomi.duckling.Types.Optionscom.xiaomi.duckling.dimension.multichar.MultiCharData→com.xiaomi.duckling.Types.Resolvablecom.xiaomi.duckling.dimension.multichar.MultiCharData→com.xiaomi.duckling.Types.ResolvedValue
- Direction
- dimension.multichar uses Types, so a change to Types can break dimension.multichar, while a change to dimension.multichar can't break Types.
- Position
- Below the diagonal: dimension.multichar uses a module listed above it, which is the healthy direction.
25→13 dimension.multichar uses com.xiaomi.duckling✕
- Connections
- 1 pair of types, where a type in dimension.multichar uses a type in com.xiaomi.duckling.
- The types involved
com.xiaomi.duckling.dimension.multichar.MultiChar→com.xiaomi.duckling.Rules
- Direction
- dimension.multichar uses com.xiaomi.duckling, so a change to com.xiaomi.duckling can break dimension.multichar, while a change to dimension.multichar can't break com.xiaomi.duckling.
- Position
- Below the diagonal: dimension.multichar uses a module listed above it, which is the healthy direction.
26→11 dimension.music uses dimension✕
- Connections
- 4 pairs of types, where a type in dimension.music uses a type in dimension.
- The types involved
com.xiaomi.duckling.dimension.music.Examples→com.xiaomi.duckling.dimension.DimExamplescom.xiaomi.duckling.dimension.music.Examples→com.xiaomi.duckling.dimension.Dimensioncom.xiaomi.duckling.dimension.music.Lyric→com.xiaomi.duckling.dimension.Dimensioncom.xiaomi.duckling.dimension.music.Rules→com.xiaomi.duckling.dimension.DimRules
- Direction
- dimension.music uses dimension, so a change to dimension can break dimension.music, while a change to dimension.music can't break dimension.
- Position
- Below the diagonal: dimension.music uses a module listed above it, which is the healthy direction.
26→12 dimension.music uses Types✕
- Connections
- 4 pairs of types, where a type in dimension.music uses a type in Types.
- The types involved
com.xiaomi.duckling.dimension.music.LyricData→com.xiaomi.duckling.Types.Contextcom.xiaomi.duckling.dimension.music.LyricData→com.xiaomi.duckling.Types.Optionscom.xiaomi.duckling.dimension.music.LyricData→com.xiaomi.duckling.Types.Resolvablecom.xiaomi.duckling.dimension.music.LyricData→com.xiaomi.duckling.Types.ResolvedValue
- Direction
- dimension.music uses Types, so a change to Types can break dimension.music, while a change to dimension.music can't break Types.
- Position
- Below the diagonal: dimension.music uses a module listed above it, which is the healthy direction.
26→13 dimension.music uses com.xiaomi.duckling✕
- Connections
- 1 pair of types, where a type in dimension.music uses a type in com.xiaomi.duckling.
- The types involved
com.xiaomi.duckling.dimension.music.Lyric→com.xiaomi.duckling.Rules
- Direction
- dimension.music uses com.xiaomi.duckling, so a change to com.xiaomi.duckling can break dimension.music, while a change to dimension.music can't break com.xiaomi.duckling.
- Position
- Below the diagonal: dimension.music uses a module listed above it, which is the healthy direction.
27→11 dimension.numeral.fraction uses dimension✕
- Connections
- 4 pairs of types, where a type in dimension.numeral.fraction uses a type in dimension.
- The types involved
com.xiaomi.duckling.dimension.numeral.fraction.Examples→com.xiaomi.duckling.dimension.DimExamplescom.xiaomi.duckling.dimension.numeral.fraction.Examples→com.xiaomi.duckling.dimension.Dimensioncom.xiaomi.duckling.dimension.numeral.fraction.Fraction→com.xiaomi.duckling.dimension.Dimensioncom.xiaomi.duckling.dimension.numeral.fraction.Rules→com.xiaomi.duckling.dimension.DimRules
- 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.
27→12 dimension.numeral.fraction uses Types✕
- Connections
- 4 pairs of types, where a type in dimension.numeral.fraction uses a type in Types.
- The types involved
com.xiaomi.duckling.dimension.numeral.fraction.FractionData→com.xiaomi.duckling.Types.Contextcom.xiaomi.duckling.dimension.numeral.fraction.FractionData→com.xiaomi.duckling.Types.NumeralValuecom.xiaomi.duckling.dimension.numeral.fraction.FractionData→com.xiaomi.duckling.Types.Optionscom.xiaomi.duckling.dimension.numeral.fraction.FractionData→com.xiaomi.duckling.Types.Resolvable
- 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.
27→13 dimension.numeral.fraction uses com.xiaomi.duckling✕
- Connections
- 1 pair of types, where a type in dimension.numeral.fraction uses a type in com.xiaomi.duckling.
- The types involved
com.xiaomi.duckling.dimension.numeral.fraction.Fraction→com.xiaomi.duckling.Rules
- Direction
- dimension.numeral.fraction uses com.xiaomi.duckling, so a change to com.xiaomi.duckling can break dimension.numeral.fraction, while a change to dimension.numeral.fraction can't break com.xiaomi.duckling.
- Position
- Below the diagonal: dimension.numeral.fraction uses a module listed above it, which is the healthy direction.
28→11 dimension.numeral.multiple uses dimension✕
- Connections
- 4 pairs of types, where a type in dimension.numeral.multiple uses a type in dimension.
- The types involved
com.xiaomi.duckling.dimension.numeral.multiple.Examples→com.xiaomi.duckling.dimension.DimExamplescom.xiaomi.duckling.dimension.numeral.multiple.Examples→com.xiaomi.duckling.dimension.Dimensioncom.xiaomi.duckling.dimension.numeral.multiple.Multiple→com.xiaomi.duckling.dimension.Dimensioncom.xiaomi.duckling.dimension.numeral.multiple.Rules→com.xiaomi.duckling.dimension.DimRules
- 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.
28→12 dimension.numeral.multiple uses Types✕
- Connections
- 4 pairs of types, where a type in dimension.numeral.multiple uses a type in Types.
- The types involved
com.xiaomi.duckling.dimension.numeral.multiple.MultipleData→com.xiaomi.duckling.Types.Contextcom.xiaomi.duckling.dimension.numeral.multiple.MultipleData→com.xiaomi.duckling.Types.NumeralValuecom.xiaomi.duckling.dimension.numeral.multiple.MultipleData→com.xiaomi.duckling.Types.Optionscom.xiaomi.duckling.dimension.numeral.multiple.MultipleData→com.xiaomi.duckling.Types.Resolvable
- 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.
28→13 dimension.numeral.multiple uses com.xiaomi.duckling✕
- Connections
- 1 pair of types, where a type in dimension.numeral.multiple uses a type in com.xiaomi.duckling.
- The types involved
com.xiaomi.duckling.dimension.numeral.multiple.Multiple→com.xiaomi.duckling.Rules
- Direction
- dimension.numeral.multiple uses com.xiaomi.duckling, so a change to com.xiaomi.duckling can break dimension.numeral.multiple, while a change to dimension.numeral.multiple can't break com.xiaomi.duckling.
- Position
- Below the diagonal: dimension.numeral.multiple uses a module listed above it, which is the healthy direction.
29→11 dimension.numeral.seq uses dimension✕
- Connections
- 4 pairs of types, where a type in dimension.numeral.seq uses a type in dimension.
- The types involved
com.xiaomi.duckling.dimension.numeral.seq.DigitSequence→com.xiaomi.duckling.dimension.Dimensioncom.xiaomi.duckling.dimension.numeral.seq.Examples→com.xiaomi.duckling.dimension.DimExamplescom.xiaomi.duckling.dimension.numeral.seq.Examples→com.xiaomi.duckling.dimension.Dimensioncom.xiaomi.duckling.dimension.numeral.seq.Rules→com.xiaomi.duckling.dimension.DimRules
- 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.
29→12 dimension.numeral.seq uses Types✕
- Connections
- 4 pairs of types, where a type in dimension.numeral.seq uses a type in Types.
- The types involved
com.xiaomi.duckling.dimension.numeral.seq.DigitSequenceData→com.xiaomi.duckling.Types.Contextcom.xiaomi.duckling.dimension.numeral.seq.DigitSequenceData→com.xiaomi.duckling.Types.Optionscom.xiaomi.duckling.dimension.numeral.seq.DigitSequenceData→com.xiaomi.duckling.Types.Resolvablecom.xiaomi.duckling.dimension.numeral.seq.DigitSequenceData→com.xiaomi.duckling.Types.ResolvedValue
- Direction
- dimension.numeral.seq uses Types, so a change to Types can break dimension.numeral.seq, while a change to dimension.numeral.seq can't break Types.
- Position
- Below the diagonal: dimension.numeral.seq uses a module listed above it, which is the healthy direction.
29→13 dimension.numeral.seq uses com.xiaomi.duckling✕
- Connections
- 1 pair of types, where a type in dimension.numeral.seq uses a type in com.xiaomi.duckling.
- The types involved
com.xiaomi.duckling.dimension.numeral.seq.DigitSequence→com.xiaomi.duckling.Rules
- Direction
- dimension.numeral.seq uses com.xiaomi.duckling, so a change to com.xiaomi.duckling can break dimension.numeral.seq, while a change to dimension.numeral.seq can't break com.xiaomi.duckling.
- Position
- Below the diagonal: dimension.numeral.seq uses a module listed above it, which is the healthy direction.
30→11 dimension.ordinal uses dimension✕
- Connections
- 4 pairs of types, where a type in dimension.ordinal uses a type in dimension.
- The types involved
com.xiaomi.duckling.dimension.ordinal.Examples→com.xiaomi.duckling.dimension.DimExamplescom.xiaomi.duckling.dimension.ordinal.Examples→com.xiaomi.duckling.dimension.Dimensioncom.xiaomi.duckling.dimension.ordinal.Ordinal→com.xiaomi.duckling.dimension.Dimensioncom.xiaomi.duckling.dimension.ordinal.Rules→com.xiaomi.duckling.dimension.DimRules
- Direction
- dimension.ordinal uses dimension, so a change to dimension can break dimension.ordinal, while a change to dimension.ordinal can't break dimension.
- Position
- Below the diagonal: dimension.ordinal uses a module listed above it, which is the healthy direction.
30→12 dimension.ordinal uses Types✕
- Connections
- 4 pairs of types, where a type in dimension.ordinal uses a type in Types.
- The types involved
com.xiaomi.duckling.dimension.ordinal.OrdinalData→com.xiaomi.duckling.Types.Contextcom.xiaomi.duckling.dimension.ordinal.OrdinalData→com.xiaomi.duckling.Types.Optionscom.xiaomi.duckling.dimension.ordinal.OrdinalData→com.xiaomi.duckling.Types.Resolvablecom.xiaomi.duckling.dimension.ordinal.OrdinalData→com.xiaomi.duckling.Types.ResolvedValue
- Direction
- dimension.ordinal uses Types, so a change to Types can break dimension.ordinal, while a change to dimension.ordinal can't break Types.
- Position
- Below the diagonal: dimension.ordinal uses a module listed above it, which is the healthy direction.
30→13 dimension.ordinal uses com.xiaomi.duckling✕
- Connections
- 1 pair of types, where a type in dimension.ordinal uses a type in com.xiaomi.duckling.
- The types involved
com.xiaomi.duckling.dimension.ordinal.Ordinal→com.xiaomi.duckling.Rules
- Direction
- dimension.ordinal uses com.xiaomi.duckling, so a change to com.xiaomi.duckling can break dimension.ordinal, while a change to dimension.ordinal can't break com.xiaomi.duckling.
- Position
- Below the diagonal: dimension.ordinal uses a module listed above it, which is the healthy direction.
31→11 dimension.phoneno uses dimension✕
- Connections
- 4 pairs of types, where a type in dimension.phoneno uses a type in dimension.
- The types involved
com.xiaomi.duckling.dimension.phoneno.Examples→com.xiaomi.duckling.dimension.DimExamplescom.xiaomi.duckling.dimension.phoneno.Examples→com.xiaomi.duckling.dimension.Dimensioncom.xiaomi.duckling.dimension.phoneno.PhoneNumber→com.xiaomi.duckling.dimension.Dimensioncom.xiaomi.duckling.dimension.phoneno.Rules→com.xiaomi.duckling.dimension.DimRules
- Direction
- dimension.phoneno uses dimension, so a change to dimension can break dimension.phoneno, while a change to dimension.phoneno can't break dimension.
- Position
- Below the diagonal: dimension.phoneno uses a module listed above it, which is the healthy direction.
31→12 dimension.phoneno uses Types✕
- Connections
- 4 pairs of types, where a type in dimension.phoneno uses a type in Types.
- The types involved
com.xiaomi.duckling.dimension.phoneno.PhoneNumberData→com.xiaomi.duckling.Types.Contextcom.xiaomi.duckling.dimension.phoneno.PhoneNumberData→com.xiaomi.duckling.Types.Optionscom.xiaomi.duckling.dimension.phoneno.PhoneNumberData→com.xiaomi.duckling.Types.Resolvablecom.xiaomi.duckling.dimension.phoneno.PhoneNumberData→com.xiaomi.duckling.Types.ResolvedValue
- Direction
- dimension.phoneno uses Types, so a change to Types can break dimension.phoneno, while a change to dimension.phoneno can't break Types.
- Position
- Below the diagonal: dimension.phoneno uses a module listed above it, which is the healthy direction.
31→13 dimension.phoneno uses com.xiaomi.duckling✕
- Connections
- 1 pair of types, where a type in dimension.phoneno uses a type in com.xiaomi.duckling.
- The types involved
com.xiaomi.duckling.dimension.phoneno.PhoneNumber→com.xiaomi.duckling.Rules
- Direction
- dimension.phoneno uses com.xiaomi.duckling, so a change to com.xiaomi.duckling can break dimension.phoneno, while a change to dimension.phoneno can't break com.xiaomi.duckling.
- Position
- Below the diagonal: dimension.phoneno uses a module listed above it, which is the healthy direction.
32→11 dimension.place uses dimension✕
- Connections
- 4 pairs of types, where a type in dimension.place uses a type in dimension.
- The types involved
com.xiaomi.duckling.dimension.place.Examples→com.xiaomi.duckling.dimension.DimExamplescom.xiaomi.duckling.dimension.place.Examples→com.xiaomi.duckling.dimension.Dimensioncom.xiaomi.duckling.dimension.place.Place→com.xiaomi.duckling.dimension.Dimensioncom.xiaomi.duckling.dimension.place.Rules→com.xiaomi.duckling.dimension.DimRules
- Direction
- dimension.place uses dimension, so a change to dimension can break dimension.place, while a change to dimension.place can't break dimension.
- Position
- Below the diagonal: dimension.place uses a module listed above it, which is the healthy direction.
32→12 dimension.place uses Types✕
- Connections
- 4 pairs of types, where a type in dimension.place uses a type in Types.
- The types involved
com.xiaomi.duckling.dimension.place.PlaceData→com.xiaomi.duckling.Types.Contextcom.xiaomi.duckling.dimension.place.PlaceData→com.xiaomi.duckling.Types.Optionscom.xiaomi.duckling.dimension.place.PlaceData→com.xiaomi.duckling.Types.Resolvablecom.xiaomi.duckling.dimension.place.PlaceData→com.xiaomi.duckling.Types.ResolvedValue
- Direction
- dimension.place uses Types, so a change to Types can break dimension.place, while a change to dimension.place can't break Types.
- Position
- Below the diagonal: dimension.place uses a module listed above it, which is the healthy direction.
32→13 dimension.place uses com.xiaomi.duckling✕
- Connections
- 1 pair of types, where a type in dimension.place uses a type in com.xiaomi.duckling.
- The types involved
com.xiaomi.duckling.dimension.place.Place→com.xiaomi.duckling.Rules
- Direction
- dimension.place uses com.xiaomi.duckling, so a change to com.xiaomi.duckling can break dimension.place, while a change to dimension.place can't break com.xiaomi.duckling.
- Position
- Below the diagonal: dimension.place uses a module listed above it, which is the healthy direction.
33→11 dimension.quantity uses dimension✕
- Connections
- 4 pairs of types, where a type in dimension.quantity uses a type in dimension.
- The types involved
com.xiaomi.duckling.dimension.quantity.Examples→com.xiaomi.duckling.dimension.DimExamplescom.xiaomi.duckling.dimension.quantity.Examples→com.xiaomi.duckling.dimension.Dimensioncom.xiaomi.duckling.dimension.quantity.Quantity→com.xiaomi.duckling.dimension.Dimensioncom.xiaomi.duckling.dimension.quantity.Rules→com.xiaomi.duckling.dimension.DimRules
- Direction
- dimension.quantity uses dimension, so a change to dimension can break dimension.quantity, while a change to dimension.quantity can't break dimension.
- Position
- Below the diagonal: dimension.quantity uses a module listed above it, which is the healthy direction.
33→12 dimension.quantity uses Types✕
- Connections
- 5 pairs of types, where a type in dimension.quantity uses a type in Types.
- The types involved
com.xiaomi.duckling.dimension.quantity.QuantityData→com.xiaomi.duckling.Types.Contextcom.xiaomi.duckling.dimension.quantity.QuantityData→com.xiaomi.duckling.Types.Optionscom.xiaomi.duckling.dimension.quantity.QuantityData→com.xiaomi.duckling.Types.Resolvablecom.xiaomi.duckling.dimension.quantity.QuantityData→com.xiaomi.duckling.Types.ResolvedValuecom.xiaomi.duckling.dimension.quantity.QuantityValue→com.xiaomi.duckling.Types.ResolvedValue
- Direction
- dimension.quantity uses Types, so a change to Types can break dimension.quantity, while a change to dimension.quantity can't break Types.
- Position
- Below the diagonal: dimension.quantity uses a module listed above it, which is the healthy direction.
33→13 dimension.quantity uses com.xiaomi.duckling✕
- Connections
- 1 pair of types, where a type in dimension.quantity uses a type in com.xiaomi.duckling.
- The types involved
com.xiaomi.duckling.dimension.quantity.Quantity→com.xiaomi.duckling.Rules
- Direction
- dimension.quantity uses com.xiaomi.duckling, so a change to com.xiaomi.duckling can break dimension.quantity, while a change to dimension.quantity can't break com.xiaomi.duckling.
- Position
- Below the diagonal: dimension.quantity uses a module listed above it, which is the healthy direction.
34→4 dimension.rating uses dimension.numeral✕
- Connections
- 1 pair of types, where a type in dimension.rating uses a type in dimension.numeral.
- The types involved
com.xiaomi.duckling.dimension.rating.RatingData→com.xiaomi.duckling.dimension.numeral.IntervalValue
- 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.
34→11 dimension.rating uses dimension✕
- Connections
- 4 pairs of types, where a type in dimension.rating uses a type in dimension.
- The types involved
com.xiaomi.duckling.dimension.rating.Examples→com.xiaomi.duckling.dimension.DimExamplescom.xiaomi.duckling.dimension.rating.Examples→com.xiaomi.duckling.dimension.Dimensioncom.xiaomi.duckling.dimension.rating.Rating→com.xiaomi.duckling.dimension.Dimensioncom.xiaomi.duckling.dimension.rating.Rules→com.xiaomi.duckling.dimension.DimRules
- Direction
- dimension.rating uses dimension, so a change to dimension can break dimension.rating, while a change to dimension.rating can't break dimension.
- Position
- Below the diagonal: dimension.rating uses a module listed above it, which is the healthy direction.
34→12 dimension.rating uses Types✕
- Connections
- 3 pairs of types, where a type in dimension.rating uses a type in Types.
- The types involved
com.xiaomi.duckling.dimension.rating.RatingData→com.xiaomi.duckling.Types.Contextcom.xiaomi.duckling.dimension.rating.RatingData→com.xiaomi.duckling.Types.Optionscom.xiaomi.duckling.dimension.rating.RatingData→com.xiaomi.duckling.Types.Resolvable
- Direction
- dimension.rating uses Types, so a change to Types can break dimension.rating, while a change to dimension.rating can't break Types.
- Position
- Below the diagonal: dimension.rating uses a module listed above it, which is the healthy direction.
34→13 dimension.rating uses com.xiaomi.duckling✕
- Connections
- 1 pair of types, where a type in dimension.rating uses a type in com.xiaomi.duckling.
- The types involved
com.xiaomi.duckling.dimension.rating.Rating→com.xiaomi.duckling.Rules
- Direction
- dimension.rating uses com.xiaomi.duckling, so a change to com.xiaomi.duckling can break dimension.rating, while a change to dimension.rating can't break com.xiaomi.duckling.
- Position
- Below the diagonal: dimension.rating uses a module listed above it, which is the healthy direction.
35→10 dimension.time.date uses dimension.time✕
- Connections
- 1 pair of types, where a type in dimension.time.date uses a type in dimension.time.
- The types involved
com.xiaomi.duckling.dimension.time.date.Rules→com.xiaomi.duckling.dimension.time.TimeData
- 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.
35→11 dimension.time.date uses dimension✕
- Connections
- 4 pairs of types, where a type in dimension.time.date uses a type in dimension.
- The types involved
com.xiaomi.duckling.dimension.time.date.Date→com.xiaomi.duckling.dimension.Dimensioncom.xiaomi.duckling.dimension.time.date.Examples→com.xiaomi.duckling.dimension.DimExamplescom.xiaomi.duckling.dimension.time.date.Examples→com.xiaomi.duckling.dimension.Dimensioncom.xiaomi.duckling.dimension.time.date.Rules→com.xiaomi.duckling.dimension.DimRules
- 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.
35→12 dimension.time.date uses Types✕
- Connections
- 4 pairs of types, where a type in dimension.time.date uses a type in Types.
- The types involved
com.xiaomi.duckling.dimension.time.date.Date→com.xiaomi.duckling.Types.Rulecom.xiaomi.duckling.dimension.time.date.Rules→com.xiaomi.duckling.Types.ItemRegexcom.xiaomi.duckling.dimension.time.date.Rules→com.xiaomi.duckling.Types.Rulecom.xiaomi.duckling.dimension.time.date.Rules→com.xiaomi.duckling.Types.Token
- Direction
- dimension.time.date uses Types, so a change to Types can break dimension.time.date, while a change to dimension.time.date can't break Types.
- Position
- Below the diagonal: dimension.time.date uses a module listed above it, which is the healthy direction.
35→13 dimension.time.date uses com.xiaomi.duckling✕
- Connections
- 1 pair of types, where a type in dimension.time.date uses a type in com.xiaomi.duckling.
- The types involved
com.xiaomi.duckling.dimension.time.date.Date→com.xiaomi.duckling.Rules
- Direction
- dimension.time.date uses com.xiaomi.duckling, so a change to com.xiaomi.duckling can break dimension.time.date, while a change to dimension.time.date can't break com.xiaomi.duckling.
- Position
- Below the diagonal: dimension.time.date uses a module listed above it, which is the healthy direction.
36→11 dimension.time.grain uses dimension✕
- Connections
- 2 pairs of types, where a type in dimension.time.grain uses a type in dimension.
- The types involved
com.xiaomi.duckling.dimension.time.grain.Rules→com.xiaomi.duckling.dimension.DimRulescom.xiaomi.duckling.dimension.time.grain.TimeGrain→com.xiaomi.duckling.dimension.Dimension
- 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.
36→12 dimension.time.grain uses Types✕
- Connections
- 5 pairs of types, where a type in dimension.time.grain uses a type in Types.
- The types involved
com.xiaomi.duckling.dimension.time.grain.GrainData→com.xiaomi.duckling.Types.Contextcom.xiaomi.duckling.dimension.time.grain.GrainData→com.xiaomi.duckling.Types.Optionscom.xiaomi.duckling.dimension.time.grain.GrainData→com.xiaomi.duckling.Types.Resolvablecom.xiaomi.duckling.dimension.time.grain.GrainData→com.xiaomi.duckling.Types.ResolvedValuecom.xiaomi.duckling.dimension.time.grain.Rules→com.xiaomi.duckling.Types.Rule
- Direction
- dimension.time.grain uses Types, so a change to Types can break dimension.time.grain, while a change to dimension.time.grain can't break Types.
- Position
- Below the diagonal: dimension.time.grain uses a module listed above it, which is the healthy direction.
36→13 dimension.time.grain uses com.xiaomi.duckling✕
- Connections
- 1 pair of types, where a type in dimension.time.grain uses a type in com.xiaomi.duckling.
- The types involved
com.xiaomi.duckling.dimension.time.grain.TimeGrain→com.xiaomi.duckling.Rules
- Direction
- dimension.time.grain uses com.xiaomi.duckling, so a change to com.xiaomi.duckling can break dimension.time.grain, while a change to dimension.time.grain can't break com.xiaomi.duckling.
- Position
- Below the diagonal: dimension.time.grain uses a module listed above it, which is the healthy direction.
37→5 dimension.time.repeat uses dimension.time.duration✕
- Connections
- 2 pairs of types, where a type in dimension.time.repeat uses a type in dimension.time.duration.
- The types involved
com.xiaomi.duckling.dimension.time.repeat.RepeatData→com.xiaomi.duckling.dimension.time.duration.DurationDatacom.xiaomi.duckling.dimension.time.repeat.RepeatValue→com.xiaomi.duckling.dimension.time.duration.DurationData
- 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.
37→8 dimension.time.repeat uses dimension.time.Types✕
- Connections
- 1 pair of types, where a type in dimension.time.repeat uses a type in dimension.time.Types.
- The types involved
com.xiaomi.duckling.dimension.time.repeat.RepeatValue→com.xiaomi.duckling.dimension.time.Types.DuckDateTime
- 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.
37→10 dimension.time.repeat uses dimension.time✕
- Connections
- 3 pairs of types, where a type in dimension.time.repeat uses a type in dimension.time.
- The types involved
com.xiaomi.duckling.dimension.time.repeat.Examples→com.xiaomi.duckling.dimension.time.TimeValuecom.xiaomi.duckling.dimension.time.repeat.RepeatData→com.xiaomi.duckling.dimension.time.TimeDatacom.xiaomi.duckling.dimension.time.repeat.Rules→com.xiaomi.duckling.dimension.time.TimeData
- 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.
37→11 dimension.time.repeat uses dimension✕
- Connections
- 4 pairs of types, where a type in dimension.time.repeat uses a type in dimension.
- The types involved
com.xiaomi.duckling.dimension.time.repeat.Examples→com.xiaomi.duckling.dimension.DimExamplescom.xiaomi.duckling.dimension.time.repeat.Examples→com.xiaomi.duckling.dimension.Dimensioncom.xiaomi.duckling.dimension.time.repeat.Repeat→com.xiaomi.duckling.dimension.Dimensioncom.xiaomi.duckling.dimension.time.repeat.Rules→com.xiaomi.duckling.dimension.DimRules
- 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.
37→12 dimension.time.repeat uses Types✕
- Connections
- 4 pairs of types, where a type in dimension.time.repeat uses a type in Types.
- The types involved
com.xiaomi.duckling.dimension.time.repeat.RepeatData→com.xiaomi.duckling.Types.Contextcom.xiaomi.duckling.dimension.time.repeat.RepeatData→com.xiaomi.duckling.Types.Optionscom.xiaomi.duckling.dimension.time.repeat.RepeatData→com.xiaomi.duckling.Types.Resolvablecom.xiaomi.duckling.dimension.time.repeat.RepeatValue→com.xiaomi.duckling.Types.ResolvedValue
- Direction
- dimension.time.repeat uses Types, so a change to Types can break dimension.time.repeat, while a change to dimension.time.repeat can't break Types.
- Position
- Below the diagonal: dimension.time.repeat uses a module listed above it, which is the healthy direction.
37→13 dimension.time.repeat uses com.xiaomi.duckling✕
- Connections
- 1 pair of types, where a type in dimension.time.repeat uses a type in com.xiaomi.duckling.
- The types involved
com.xiaomi.duckling.dimension.time.repeat.Repeat→com.xiaomi.duckling.Rules
- Direction
- dimension.time.repeat uses com.xiaomi.duckling, so a change to com.xiaomi.duckling can break dimension.time.repeat, while a change to dimension.time.repeat can't break com.xiaomi.duckling.
- Position
- Below the diagonal: dimension.time.repeat uses a module listed above it, which is the healthy direction.
38→11 dimension.url uses dimension✕
- Connections
- 4 pairs of types, where a type in dimension.url uses a type in dimension.
- The types involved
com.xiaomi.duckling.dimension.url.DuckURL→com.xiaomi.duckling.dimension.Dimensioncom.xiaomi.duckling.dimension.url.Examples→com.xiaomi.duckling.dimension.DimExamplescom.xiaomi.duckling.dimension.url.Examples→com.xiaomi.duckling.dimension.Dimensioncom.xiaomi.duckling.dimension.url.Rules→com.xiaomi.duckling.dimension.DimRules
- Direction
- dimension.url uses dimension, so a change to dimension can break dimension.url, while a change to dimension.url can't break dimension.
- Position
- Below the diagonal: dimension.url uses a module listed above it, which is the healthy direction.
38→12 dimension.url uses Types✕
- Connections
- 4 pairs of types, where a type in dimension.url uses a type in Types.
- The types involved
com.xiaomi.duckling.dimension.url.UrlData→com.xiaomi.duckling.Types.Contextcom.xiaomi.duckling.dimension.url.UrlData→com.xiaomi.duckling.Types.Optionscom.xiaomi.duckling.dimension.url.UrlData→com.xiaomi.duckling.Types.Resolvablecom.xiaomi.duckling.dimension.url.UrlData→com.xiaomi.duckling.Types.ResolvedValue
- Direction
- dimension.url uses Types, so a change to Types can break dimension.url, while a change to dimension.url can't break Types.
- Position
- Below the diagonal: dimension.url uses a module listed above it, which is the healthy direction.
38→13 dimension.url uses com.xiaomi.duckling✕
- Connections
- 1 pair of types, where a type in dimension.url uses a type in com.xiaomi.duckling.
- The types involved
com.xiaomi.duckling.dimension.url.DuckURL→com.xiaomi.duckling.Rules
- Direction
- dimension.url uses com.xiaomi.duckling, so a change to com.xiaomi.duckling can break dimension.url, while a change to dimension.url can't break com.xiaomi.duckling.
- Position
- Below the diagonal: dimension.url uses a module listed above it, which is the healthy direction.
39→1 engine uses engine.LexiconLookup✕
- Connections
- 1 pair of types, where a type in engine uses a type in engine.LexiconLookup.
- The types involved
com.xiaomi.duckling.engine.LexiconLookup→com.xiaomi.duckling.engine.LexiconLookup.Dict
- Direction
- engine uses engine.LexiconLookup, so a change to engine.LexiconLookup can break engine, while a change to engine can't break engine.LexiconLookup.
- Position
- Below the diagonal: engine uses a module listed above it, which is the healthy direction.
39→7 engine uses types✕
- Connections
- 8 pairs of types, where a type in engine uses a type in types.
- The types involved
com.xiaomi.duckling.engine.Engine→com.xiaomi.duckling.types.LanguageInfocom.xiaomi.duckling.engine.Engine→com.xiaomi.duckling.types.Nodecom.xiaomi.duckling.engine.LexiconLookup→com.xiaomi.duckling.types.Nodecom.xiaomi.duckling.engine.MultiCharLookup→com.xiaomi.duckling.types.Nodecom.xiaomi.duckling.engine.PhraseLookup→com.xiaomi.duckling.types.Nodecom.xiaomi.duckling.engine.RegexLookup→com.xiaomi.duckling.types.Nodecom.xiaomi.duckling.engine.Stash→com.xiaomi.duckling.types.Nodecom.xiaomi.duckling.engine.VarcharLookup→com.xiaomi.duckling.types.Node
- Direction
- engine uses types, so a change to types can break engine, while a change to engine can't break types.
- Position
- Below the diagonal: engine uses a module listed above it, which is the healthy direction.
39→12 engine uses Types✕
- Connections
- 6 pairs of types, where a type in engine uses a type in Types.
- The types involved
com.xiaomi.duckling.engine.Engine→com.xiaomi.duckling.Types.Contextcom.xiaomi.duckling.engine.Engine→com.xiaomi.duckling.Types.Optionscom.xiaomi.duckling.engine.Engine→com.xiaomi.duckling.Types.PatternItemcom.xiaomi.duckling.engine.Engine→com.xiaomi.duckling.Types.ResolvedTokencom.xiaomi.duckling.engine.Engine→com.xiaomi.duckling.Types.Rulecom.xiaomi.duckling.engine.VarcharLookup→com.xiaomi.duckling.Types.Options
- Direction
- engine uses Types, so a change to Types can break engine, while a change to engine can't break Types.
- Position
- Below the diagonal: engine uses a module listed above it, which is the healthy direction.
39→13 engine uses com.xiaomi.duckling✕
- Connections
- 6 pairs of types, where a type in engine uses a type in com.xiaomi.duckling.
- The types involved
com.xiaomi.duckling.engine.Engine→com.xiaomi.duckling.Documentcom.xiaomi.duckling.engine.LexiconLookup→com.xiaomi.duckling.Documentcom.xiaomi.duckling.engine.MultiCharLookup→com.xiaomi.duckling.Documentcom.xiaomi.duckling.engine.PhraseLookup→com.xiaomi.duckling.Documentcom.xiaomi.duckling.engine.RegexLookup→com.xiaomi.duckling.Documentcom.xiaomi.duckling.engine.VarcharLookup→com.xiaomi.duckling.Document
- Direction
- engine uses com.xiaomi.duckling, so a change to com.xiaomi.duckling can break engine, while a change to engine can't break com.xiaomi.duckling.
- Position
- Below the diagonal: engine uses a module listed above it, which is the healthy direction.
40→7 ranking uses types✕
- Connections
- 4 pairs of types, where a type in ranking uses a type in types.
- The types involved
com.xiaomi.duckling.ranking.NaiveBayesLearning→com.xiaomi.duckling.types.Nodecom.xiaomi.duckling.ranking.NaiveBayesRank→com.xiaomi.duckling.types.Nodecom.xiaomi.duckling.ranking.OverlapResolver→com.xiaomi.duckling.types.Nodecom.xiaomi.duckling.ranking.Rank→com.xiaomi.duckling.types.Node
- Direction
- ranking uses types, so a change to types can break ranking, while a change to ranking can't break types.
- Position
- Below the diagonal: ranking uses a module listed above it, which is the healthy direction.
40→11 ranking uses dimension✕
- Connections
- 3 pairs of types, where a type in ranking uses a type in dimension.
- The types involved
com.xiaomi.duckling.ranking.AnswersSelection→com.xiaomi.duckling.dimension.Dimensioncom.xiaomi.duckling.ranking.OverlapResolver→com.xiaomi.duckling.dimension.Dimensioncom.xiaomi.duckling.ranking.Rank→com.xiaomi.duckling.dimension.Dimension
- Direction
- ranking uses dimension, so a change to dimension can break ranking, while a change to ranking can't break dimension.
- Position
- Below the diagonal: ranking uses a module listed above it, which is the healthy direction.
40→12 ranking uses Types✕
- Connections
- 15 pairs of types, where a type in ranking uses a type in Types.
- The types involved
com.xiaomi.duckling.ranking.CorpusSets→com.xiaomi.duckling.Types.ResolvedValuecom.xiaomi.duckling.ranking.NaiveBayesLearning→com.xiaomi.duckling.Types.Contextcom.xiaomi.duckling.ranking.NaiveBayesLearning→com.xiaomi.duckling.Types.Optionscom.xiaomi.duckling.ranking.NaiveBayesLearning→com.xiaomi.duckling.Types.ResolvedTokencom.xiaomi.duckling.ranking.NaiveBayesLearning→com.xiaomi.duckling.Types.Rulecom.xiaomi.duckling.ranking.NaiveBayesRank→com.xiaomi.duckling.Types.Answercom.xiaomi.duckling.ranking.OverlapResolver→com.xiaomi.duckling.Types.Answercom.xiaomi.duckling.ranking.OverlapResolver→com.xiaomi.duckling.Types.Rulecom.xiaomi.duckling.ranking.Rank→com.xiaomi.duckling.Types.Answercom.xiaomi.duckling.ranking.Rank→com.xiaomi.duckling.Types.Contextcom.xiaomi.duckling.ranking.Rank→com.xiaomi.duckling.Types.Optionscom.xiaomi.duckling.ranking.Rank→com.xiaomi.duckling.Types.RankOptionscom.xiaomi.duckling.ranking.Rank→com.xiaomi.duckling.Types.ResolvedTokencom.xiaomi.duckling.ranking.Testing→com.xiaomi.duckling.Types.Contextcom.xiaomi.duckling.ranking.Testing→com.xiaomi.duckling.Types.Options
- Direction
- ranking uses Types, so a change to Types can break ranking, while a change to ranking can't break Types.
- Position
- Below the diagonal: ranking uses a module listed above it, which is the healthy direction.
40→13 ranking uses com.xiaomi.duckling✕
- Connections
- 1 pair of types, where a type in ranking uses a type in com.xiaomi.duckling.
- The types involved
com.xiaomi.duckling.ranking.Rank→com.xiaomi.duckling.Document
- Direction
- ranking uses com.xiaomi.duckling, so a change to com.xiaomi.duckling can break ranking, while a change to ranking can't break com.xiaomi.duckling.
- Position
- Below the diagonal: ranking uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 15 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 6 | Medium |
Roadmap
First, ensure every form control and button has a proper programmatic label to replace placeholders. Next, improve visual safety by maintaining visible focus styles, respecting reduced motion preferences, and fixing low-contrast colors. Then, establish correct page structure by adding language attributes, titles, and main landmarks while keeping headings ordered. Finally, enforce accessibility in your test suite to block regressions in CI, and add static analysis to your build pipeline to catch security issues early.
| 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. | +7.9 pts | Medium | Forms & labels |
| 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. | +7.9 pts | Medium | Visual & motion safety |
| Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh. | +4.4 pts | Medium | Page structure |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +2.2 pts | Low | ADR Quality |
| Enforce accessibility in the test suite you already have: assert the accessibility invariants over the HTML your app renders — parse the rendered output in an existing test, or drive a real browser from one — and gate that test in CI so a regression blocks the merge. | +4.2 pts | Medium | A11y enforcement |
| 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. | +3.4 pts | Medium | Security & performance tooling |
| Resolve the 71 Orphaned file finding(s) in Knowledge Freshness — start with Rules.scala (13), Examples.scala (6), Types.scala (3). | +2.0 pts | Medium | Knowledge Freshness |
| 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. | +1.6 pts | Medium | Architecture documentation |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.0 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/package.scala | 7.2 | Mixed | Cyclomatic Complexity: time.resolveTimeData (cyclomatic 20) |
| duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/age/Rules.scala | 7.3 | Mixed | Explicit Debt: TodoComment |
| duckling-fork-chinese/learning/src/main/scala/com/xiaomi/duckling/task/NaiveBayesConsole.scala | 7.4 | Mixed | Cyclomatic Complexity: NaiveBayesConsole.setOptions (cyclomatic 16) |
| duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/task/PlaceExtractor.scala | 7.4 | Mixed | Code Duplication: Duplicated block (14 lines × 2) |
| duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/rule/FuzzyDayIntervals.scala | 7.8 | Mixed | Cyclomatic Complexity: FuzzyDayIntervals.updatePredicateByFuzzyInterval (cyclomatic 16) |
| duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/engine/VarcharLookup.scala | 7.8 | Mixed | Cognitive Complexity: VarcharLookup.leftVarcharExpansion (cognitive 18) |
| duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/ranking/OverlapResolver.scala | 8.2 | Near-clean | Explicit Debt: TodoComment |
| duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/rule/Weeks.scala | 8.2 | Near-clean | Explicit Debt: TodoComment |
| duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/date/Rules.scala | 8.5 | Near-clean | Cognitive Complexity: Rules.intersectProd (cognitive 23) |
| duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/engine/PhraseLookup.scala | 8.5 | Near-clean | Cognitive Complexity: PhraseLookup.lookupPhrase (cognitive 22) |
| duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/Rules.scala | 8.5 | Near-clean | Cognitive Complexity: Rules.intersectToken (cognitive 21) |
| duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/helper/TimePredicateHelpers.scala | 8.5 | Near-clean | Cognitive Complexity: TimePredicateHelpers.takeN (cognitive 18) |
| duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/helper/TimeDataHelpers.scala | 8.5 | Near-clean | God Classes: TooManyMethods: TimeDataHelpers |
| duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/duration/Rules.scala | 8.5 | Near-clean | Change Coupling: Change coupling: Rules.scala ↔ Examples.scala |
| duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/repeat/Rules.scala | 8.5 | Near-clean | Change Coupling: Change coupling: Rules.scala ↔ Examples.scala |
| duckling-fork-chinese/learning/src/main/scala/com/xiaomi/duckling/dimension/time/Examples.scala | 8.5 | Near-clean | Change Coupling: Change-coupling hub: Examples.scala → Rules.scala, FuzzyDayIntervals.scala, Times.scala |
How the grades work
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.
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.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
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
Watchdog 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. 70 of 70 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
What we checked — 70 dimensions across the health lenses
- 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, 254 of 273 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — 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.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Watchdog duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
| LLM (sampled · advisory) | Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement | — | ◐ LLM · sampled · advisory |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — Watchdog 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. To have real coverage read, produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D12 Dependency Hygiene — not measured this run — Watchdog 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 — Watchdog measured this, but not all of it. What it 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 — Watchdog 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 — Watchdog 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. D21's deterministic naming 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. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — Watchdog 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 — Watchdog 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. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — not measured this run — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog measured this, but not all of it. What it 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. 161 further occurrence(s) are not listed individually; the score already reflects all 201.
- AXB1 Runtime evidence locked — no reproducible boot — not measured this run — Watchdog 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. Watchdog then boots 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 — Watchdog 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 — Watchdog 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 — Watchdog measured this, but not all of it. What it 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). 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.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does 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
- 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.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D11 Test Reliability: Flakiness is inferred from history/markers — Watchdog runs the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- 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 is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
- 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.
- AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
- 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: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
- 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.
Dimensions
D1 · Cyclomatic Complexity
33 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.
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.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
58 method(s) exceeded the cognitive complexity threshold of 15; the worst was vue.processAttrs at 94.
What to do
- Bring the 5 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 5 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.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
2 god class(es) detected.
What to do
- Resolve the 1 FileTooLong finding(s) in God Classes — start with REDACTED. — 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).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
4 duplicated block group(s) detected.
What to do
- Resolve the 2 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with PlaceExtractor.scala (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Duplicated block (14 lines × 2) finding(s) in Code Duplication — start with PlaceExtractor.scala. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with NaiveBayesConsole.scala. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
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).
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).
- Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
0 of 4 classes have LCOM4 above 3.
D9 · Test Distribution
84 test methods: 84 unit, 0 integration, 0 BDD, 0 e2e. The Python suite contributes 7 test function(s) across 3 file(s) declaring at least one — every `def test…` in a file pytest or unittest would collect, which is those frameworks' own definition of a case; a parametrize table counts once, so this is a floor. Its tier split is read from file names and paths only. The Scala suite contributes 77 test case(s) across 33 file(s) in a test source set declaring at least one — every `test("…")`, `it("…")`, `property("…")` and `"…" in {…}` registration and every JUnit `@Test`, which is how munit, ScalaTest, utest, ZIO Test and specs2 declare a case; a case registered under a computed name is not counted, so this is a floor. Its tier split is INFERRED from paths and file names, except sbt's src/it source set, which the build declares.
D11 · Test Reliability
0 flaky across 1 measured tier(s). Scala (duckling-fork-chinese, 36 test files): measured (0 flaky).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
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.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
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.
D17 · Explicit Debt
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.
What to do
- 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).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 2 build units (Python, sbt) flagged as possibly oversized/incoherent.
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).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
15 finding(s): 0 critical, 7 high, 8 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`, `REDACTED` — 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.
What to do
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-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).
D34 · Knowledge Freshness
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.
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).
D35 · Change Coupling
Strongest change-coupling: Rules.scala↔Examples.scala 90%; Rules.scala↔Examples.scala 82%; FuzzyDayIntervals.scala↔Examples.scala 61%
What to do
- 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).
D36 · Supply-chain Provenance & Signing
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- 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).
D44 · Platform End-of-Life
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.
Frontend & cross-cutting dimensions
AC2 · Forms & labels
- This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. — REDACTED: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. — REDACTED: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.
AC3 · Page structure
- The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). (×2) — REDACTED: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) — REDACTED: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.
AC6 · Visual & motion safety
- `.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:35
- `.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
- `.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
- `.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. (×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-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. (×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-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. (×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-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-tree-node` 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
- `.el-color-dropdown__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-input.is-active .el-input__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-input-group__append: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-link` 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-checkbox__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-checkbox__original` 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-checkbox-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` 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-checkbox-button__original` 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__original` 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-node` 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.
AC7 · A11y enforcement
- No accessibility enforcement found — no automated accessibility check runs over the HTML your app renders. Assert the accessibility invariants over that HTML in the test suite you already have (parse the output and assert, or drive a browser), and gate that test in CI so a regression blocks the merge. What was searched, so you can tell an absence from a miss: the 4 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
What to do
- Enforce accessibility in the test suite you already have: assert the accessibility invariants over the HTML your app renders — parse the rendered output in an existing test, or drive a real browser from one — and gate that test in CI so a regression blocks the merge.
AX1 · Captive dependencies
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX2 · Stateful singletons
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
- `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.
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
M1 · Documentation (README)
- The root README is 14 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, 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.
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.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
M2 · Architecture documentation
- 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.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
- 12/12 types (100%) declared in the published library are public. For a library, every public type is a stability contract — keep implementation types off the surface and expose only the intended API.
What to do
- Keep implementation types off the public surface (Java: package-private (no modifier), or leave its package out of `module-info` exports) so internals can change without breaking consumers.
P2 · Observability
What to do
- Consider OpenTelemetry tracing/metrics (@opentelemetry/sdk-node) and a health-check endpoint (@godaddy/terminus or a /health route) for operability.
P3 · Security & performance tooling
- 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 2025 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.
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.
P4 · Deployment & Rollback
- 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.
P6 · Release Hygiene
- 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.
PF1 · Benchmark discipline
- 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.
PF2 · Allocation hygiene
- None of the allocation-aware idioms this check reads was found in the Java and Scala production code (Java: NIO buffer views, MemorySegment, primitive collections, pooled buffers, presized collections; Scala: value classes (AnyVal), @specialized, primitive collections, presized builders). If this code sits on a hot path, these reduce the allocation pressure it creates — a bonus, not a requirement.
What to do
- Java: on hot paths, work through buffer views (ByteBuffer/LongBuffer slices, MemorySegment) instead of copies, avoid boxing with primitive collections (fastutil, Eclipse Collections, HPPC, Trove), presize collections and StringBuilders, and pool expensive buffers (Netty's pooled allocator, commons-pool).
- Scala: on hot paths, make small wrappers value classes (extends AnyVal), @specialized generic code over primitives, use primitive collections, and presize builders.
PF3 · Async & latency hygiene
S1 · Web-Security Posture
- `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.
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
- `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. — REDACTED: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.
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- 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)
X30 · Support guard that admits what it rejects
X4 · Structured logging
X5 · Nullable reference types
- 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.
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
| AC7 · A11y enforcement | enforcement — no page criterion | Enforcement posture (process) |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 61% | Adequate — gated by D2, X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 90% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 56% | Adequate — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 47% | Weak — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 72% | Adequate — gated by D29, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 20% | Critical — gated by AC2, AC3, AC6 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 76% | Strong | Strongest area. |
Unscored — 3 check(s) recorded observations but carry no score
- 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
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 45 check(s) not relevant to this codebase
- 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.
- 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 as units only; 1 folder(s) declared by setup.py were not judged for an overview, an example or the map.
- D21 Naming Consistency — Naming consistency is measured on C# only; Java, JavaScript, Python, Scala not measured.
- 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+ projects each declaring an entity of their own. 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# and Visual Basic comments only — this repository's production source is .java, .py, .scala, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- 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.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- 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 — no coverage report found on disk — produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- 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
- 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)
Critical — 11 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <html> without a lang REDACTED:11866
- <html> without a lang duckling-fork-chinese/server/src/main/resources/template.html:1
- REDACTED
- REDACTED
- <select> without a programmatic label REDACTED:8529
- Link with no accessible name REDACTED:11840
- REDACTED
Serious — 169 finding(s)
- Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1
- Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1
- Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1
- Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1
- Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1
- Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1
- Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1
- Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1
- Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1
- Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1
- Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1
- Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1
- Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1
- Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1
- Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1
- Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1
- Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1
- Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1
- Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1
- Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1
- Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1
- Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1
- Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1
- Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1
- Focus outline removed in CSS without a :focus replacement duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1
- Swallowed exception (empty catch) REDACTED:143
- Swallowed exception (empty catch) REDACTED:163
- Swallowed exception (empty catch) REDACTED:194
- Swallowed exception (empty catch) REDACTED:212
- Swallowed exception (empty catch) REDACTED:228
- Swallowed exception (empty catch) REDACTED:557
- Swallowed exception (empty catch) REDACTED:7653
- Swallowed exception (empty catch) REDACTED:7675
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- TodoComment duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/ranking/OverlapResolver.scala:56
- TodoComment duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/rule/Weeks.scala:88
- TodoComment duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/age/Rules.scala:41
- TodoComment duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/age/Rules.scala:51
- vue.createPatchFunction::hydrate (cognitive 75) REDACTED:6348
- vue.createPatchFunction::patchVnode (cognitive 37) REDACTED:6253
- vue.createPatchFunction::updateChildren (cognitive 27) REDACTED:6156
- vue.createPatchFunction::createElm (cognitive 16) REDACTED:5895
- Low contrast colour pair in CSS (2.8:1) duckling-fork-chinese/server/src/main/resources/templates/index.html:35
- Low contrast colour pair in CSS (2.8:1) duckling-fork-chinese/server/src/main/resources/static/css/element-ui.css:1
- Low contrast colour pair in CSS (2.8:1) duckling-fork-chinese/server/src/main/resources/static/css/index.css:1
- vue.createPatchFunction::hydrate (cyclomatic 32) REDACTED:6348
- vue.createPatchFunction::patchVnode (cyclomatic 31) REDACTED:6253
- vue.createPatchFunction::updateChildren (cyclomatic 19) REDACTED:6156
- Page without a main landmark REDACTED:11866
- Page without a main landmark duckling-fork-chinese/server/src/main/resources/template.html:1
- vue.parseHTML::parseEndTag (cyclomatic 18) REDACTED:9481
- vue.parseHTML::handleStartTag (cyclomatic 16) REDACTED:9438
- vue.parseHTML::parseEndTag (cognitive 29) REDACTED:9481
- vue.parseHTML::handleStartTag (cognitive 17) REDACTED:9438
- REDACTED
- REDACTED
- Change coupling: Rules.scala ↔ Examples.scala duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/duration/Rules.scala:1
- Change coupling: Rules.scala ↔ Examples.scala duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/repeat/Rules.scala:1
- REDACTED
- REDACTED
- Duplicated block (6 lines × 2) duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/task/PlaceExtractor.scala:47
- Duplicated block (6 lines × 2) duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/task/PlaceExtractor.scala:54
- Untrusted text written into markup unescaped REDACTED:103
- Untrusted text written into markup unescaped REDACTED:7634
- Low contrast colour pair in CSS (3.6:1) duckling-fork-chinese/server/src/main/resources/static/css/main.css:2272
- Accessibility enforcement below the top rung
- vue.enter (cyclomatic 50) REDACTED:8110
- vue.parseFilters (cyclomatic 40) REDACTED:6823
- vue.resolveAsyncComponent (cyclomatic 31) REDACTED:3612
- vue.parseHTML (cyclomatic 31) REDACTED:9280
- vue.processAttrs (cyclomatic 30) REDACTED:10265
- vue.leave (cyclomatic 28) REDACTED:8261
- vue.updateDOMProps (cyclomatic 26) REDACTED:7588
- vue.processSlotContent (cyclomatic 26) REDACTED:10102
- bfwone.loadjs (cyclomatic 25) REDACTED:135
- vue._createElement (cyclomatic 25) REDACTED:3363
- (anonymous) (cyclomatic 25) REDACTED:2
- vue.genElement (cyclomatic 24) REDACTED:10942
- vue.defineReactive$$1 (cyclomatic 22) REDACTED:1014
- vue.addHandler (cyclomatic 22) REDACTED:6982
- vue.genData$2 (cyclomatic 21) REDACTED:11093
- time.resolveTimeData (cyclomatic 20) duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/package.scala:83
- vue.normalizeArrayChildren (cyclomatic 18) REDACTED:2376
- vue.normalizeScopedSlots (cyclomatic 18) REDACTED:2545
- vue.parse::closeElement (cyclomatic 18) REDACTED:9621
- vue.resolveSlots (cyclomatic 17) REDACTED:2499
- vue.bindObjectProps (cyclomatic 17) REDACTED:2752
- vue.updateChildComponent (cyclomatic 17) REDACTED:4086
- vue.updateAttrs (cyclomatic 17) REDACTED:6681
- FuzzyDayIntervals.updatePredicateByFuzzyInterval (cyclomatic 16) duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/rule/FuzzyDayIntervals.scala:174
- NaiveBayesConsole.setOptions (cyclomatic 16) duckling-fork-chinese/learning/src/main/scala/com/xiaomi/duckling/task/NaiveBayesConsole.scala:114
- vue.genHandler (cyclomatic 16) REDACTED:10798
- vue.Vue.$mount (cyclomatic 16) REDACTED:11857
- vue.processAttrs (cognitive 94) REDACTED:10265
- vue.parseHTML (cognitive 82) REDACTED:9280
- loadjs (cognitive 77) REDACTED:135
- (anonymous) (cognitive 75) REDACTED:2
- vue.resolveAsyncComponent (cognitive 56) REDACTED:3612
- vue.parseFilters (cognitive 55) REDACTED:6823
- vue.enter (cognitive 52) REDACTED:8110
- time.resolveTimeData (cognitive 47) duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/package.scala:83
- vue.updateDOMProps (cognitive 43) REDACTED:7588
- vue.processSlotContent (cognitive 39) REDACTED:10102
- vue.normalizeArrayChildren (cognitive 31) REDACTED:2376
- vue.leave (cognitive 31) REDACTED:8261
- vue.genHandler (cognitive 31) REDACTED:10798
- vue.Vue.$mount (cognitive 31) REDACTED:11857
- vue._createElement (cognitive 29) REDACTED:3363
- vue.generateCodeFrame (cognitive 29) REDACTED:11572
- vue.bindObjectProps (cognitive 28) REDACTED:2752
- vue.genElement (cognitive 28) REDACTED:10942
- vue._update (cognitive 27) REDACTED:6573
- vue.defineReactive$$1 (cognitive 25) REDACTED:1014
- vue.resolveInject (cognitive 24) REDACTED:2456
- vue.addHandler (cognitive 24) REDACTED:6982
- Rules.intersectProd (cognitive 23) duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/date/Rules.scala:339
- vue.parse::closeElement (cognitive 23) REDACTED:9621
- vue.checkNode (cognitive 23) REDACTED:11483
- PhraseLookup.lookupPhrase (cognitive 22) duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/engine/PhraseLookup.scala:41
- Rules.intersectToken (cognitive 21) duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/Rules.scala:173
- vue.resolveSlots (cognitive 21) REDACTED:2499
- vue.genData$2 (cognitive 21) REDACTED:11093
- FuzzyDayIntervals.updatePredicateByFuzzyInterval (cognitive 20) duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/rule/FuzzyDayIntervals.scala:174
- vue.handleError (cognitive 20) REDACTED:1827
- vue.updateAttrs (cognitive 20) REDACTED:6681
- vue.markStaticRoots (cognitive 20) REDACTED:10661
- time.copyGrain (cognitive 19) duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/package.scala:235
- vue.renderList (cognitive 19) REDACTED:2629
- vue.createCompileToFunctionFn (cognitive 19) REDACTED:11635
- TimePredicateHelpers.takeN (cognitive 18) duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/helper/TimePredicateHelpers.scala:162
- time.runReplacePartPredicate (cognitive 18) duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/package.scala:191
- VarcharLookup.leftVarcharExpansion (cognitive 18) duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/engine/VarcharLookup.scala:92
- VarcharLookup.rightVarcharExpansion (cognitive 18) duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/engine/VarcharLookup.scala:119
- vue.looseEqual (cognitive 18) REDACTED:296
- vue.normalizeScopedSlots (cognitive 18) REDACTED:2545
- vue.preTransformNode (cognitive 18) REDACTED:10481
- vue.markStatic$1 (cognitive 18) REDACTED:10629
- vue.mergeDataOrFn (cognitive 17) REDACTED:1212
- vue.actuallySetSelected (cognitive 17) REDACTED:8524
- NaiveBayesConsole.setOptions (cognitive 16) duckling-fork-chinese/learning/src/main/scala/com/xiaomi/duckling/task/NaiveBayesConsole.scala:114
- vue.assertProp (cognitive 16) REDACTED:1682
- vue.initComputed (cognitive 16) REDACTED:4750
- vue.genDefaultModel (cognitive 16) REDACTED:7416
- vue.createCompilerCreator (cognitive 16) REDACTED:11737
- REDACTED
- FileTooLong: REDACTED REDACTED
- TooManyMethods: TimeDataHelpers duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/helper/TimeDataHelpers.scala:31
- 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
- REDACTED
- Duplicated block (14 lines × 2) duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/task/PlaceExtractor.scala:32
- Duplicated block (5 lines × 2) duckling-fork-chinese/learning/src/main/scala/com/xiaomi/duckling/task/NaiveBayesConsole.scala:170
- Off the main sequence: core
- Coverage collected but not gated
- Third-party script without Subresource Integrity duckling-fork-chinese/server/src/main/resources/templates/index.html:26
Minor — 93 finding(s)
- Orphaned file duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/helper/HolidayProvider.scala:1
- Orphaned file duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/package.scala:1
- Orphaned file duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/date/Rules.scala:1
- Orphaned file duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/Time.scala:1
- Orphaned file duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/Types.scala:1
- Orphaned file duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/engine/Engine.scala:1
- Orphaned file duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/predicates.scala:1
- Orphaned file duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/helper/TimePredicateHelpers.scala:1
- Orphaned file duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/Types.scala:1
- Orphaned file duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/rule/FuzzyDayIntervals.scala:1
- Orphaned file duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/helper/TimeDataHelpers.scala:1
- Orphaned file duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/duration/Rules.scala:1
- Orphaned file duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/repeat/Rules.scala:1
- Orphaned file duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/numeral/Rules.scala:1
- Orphaned file duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/rule/Times.scala:1
- Orphaned file duckling-fork-chinese/learning/src/main/scala/com/xiaomi/duckling/task/NaiveBayesConsole.scala:1
- Orphaned file duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/ranking/OverlapResolver.scala:1
- Orphaned file duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/helper/TimeObjectHelpers.scala:1
- Orphaned file duckling-fork-chinese/learning/src/main/scala/com/xiaomi/duckling/ranking/AnswersSelection.scala:1
- Orphaned file minlp-tokenizer/minlptokenizer/tokenizer.py:1
- Orphaned file duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/Document.scala:1
- Orphaned file duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/JsonSerde.scala:1
- Orphaned file duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/engine/VarcharLookup.scala:1
- Orphaned file duckling-fork-chinese/learning/src/main/scala/com/xiaomi/duckling/ranking/NaiveBayesLearning.scala:1
- Orphaned file duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/numeral/Prods.scala:1
- Most significant orphaned file duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/Rules.scala:1
- Most significant orphaned file duckling-fork-chinese/learning/src/main/scala/com/xiaomi/duckling/dimension/time/Examples.scala:1
- Duplicated predicate duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/task/PlaceExtractor.scala:56
- Duplicated predicate duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/Rules.scala:177
- Fat interface: DuckDate (17 abstract members) duckling-fork-chinese/core/src/main/scala/com/xiaomi/duckling/dimension/time/Types.scala:36
- Off-boarding risk: anonymized user #1
- No ADRs found
- Projects may be oversized for their cohesion
- Dormant codebase
- REDACTED
- REDACTED
- REDACTED
- Thin README
- No ADRs
- Large public API surface
- No SAST
- No release approval gate
- No changelog
- Benchmarks don't track allocations duckling-fork-chinese/benchmark/src/main/java/com/xiaomi/duckling/benchmark/DateTimeBenchmark.java
- No allocation-aware idioms detected
- Scala's null is not held to the type system everywhere
- Silent fallback default in catch REDACTED:320
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-255ecf0175e548b3a7e443f208aa9bac/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-255ecf0175e548b3a7e443f208aa9bac/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 15 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | 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. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | 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. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | 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. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | 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. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | 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. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |