Executive summary
elkowar/eww falls short of our standard for a preview release, held back most by its Accessibility lens, the interface's usability with a keyboard or assistive technology. It scores 54 out of 100 and is rated Adequate, and nine of its 14 critical findings are security problems in the build pipeline.
Accessibility, at 44, is the weakest lens and counts most in the score. The best first step for the work it takes is improving the documentation, worth about 5 points. Making the controls keyboard-usable would lift Accessibility itself, worth about 6 points. Raising Accessibility to 65 would lift the score to about 61.
Eight pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. One secret can leak from the build pipeline, and four packages carry licence risk. Pinning each tool to an exact version, limiting the secret to its own step and replacing or clearing the banned-licence packages would close these risks.
The product code is 12,033 lines, about €12,000 to rebuild.
If Accessibility rose from 44 to 65, the lowest score rated Strong, the score would rise from 54 to about 61.
New since the last survey: 10 findings
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement docs/theme/css/general.css
- Visual & motion safety · Animation without a prefers-reduced-motion guard docs/theme/css/chrome.css
- Visual & motion safety · Animation without a prefers-reduced-motion guard docs/theme/css/chrome.css
- Visual & motion safety · Animation without a prefers-reduced-motion guard docs/theme/css/general.css
Fixed since the last survey: 1 finding
- Supply-chain Provenance & Signing REDACTED
Rebuild cost: about €12,000 · Estimate
| Cost to rebuild | €4,000 to €20,000, for 66 to 209 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.8 at a score of 54. 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: 12,033 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 eww.paths | 2 eww.widgets.window | 3 eww_shared_util.span | 4 eww_shared_util.wrappers | 5 eww | 6 eww.config.eww_config | 7 eww.state.scope | 8 simplexpr.error | 9 yuck.config.monitor | 10 yuck.format_diagnostic | 11 simplexpr.dynval | 12 yuck.config.attributes | 13 yuck.config.backend_window_options | 14 notifier_host.host | 15 simplexpr.eval | 16 eww.widgets.systray | 17 simplexpr.parser.lexer | 18 yuck.parser.ast_iterator | 19 yuck.parser.from_ast | 20 yuck.config.var_definition | 21 yuck.parser.ast | 22 simplexpr.ast | 23 yuck.config.toplevel | 24 eww.state.scope_graph.internal | 25 yuck.config.script_var_definition | 26 yuck.config.widget_use | 27 yuck.config.window_geometry | 28 eww.config.script_var | 29 eww.script_var_handler | 30 eww.state.scope_graph | 31 yuck.config.widget_definition | 32 yuck.config.window_definition | 33 eww.widgets.build_widget | 34 eww.window_arguments | 35 yuck.config.validate | 36 eww.window_initiator | 37 eww.app | 38 eww.display_backend | 39 eww.display_backend.platform_wayland | 40 eww.display_backend.platform_x11 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 eww.paths | ||||||||||||||||||||||||||||||||||||||||
| 2 eww.widgets.window | ||||||||||||||||||||||||||||||||||||||||
| 3 eww_shared_util.span | ||||||||||||||||||||||||||||||||||||||||
| 4 eww_shared_util.wrappers | ||||||||||||||||||||||||||||||||||||||||
| 5 eww | 1 | |||||||||||||||||||||||||||||||||||||||
| 6 eww.config.eww_config | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 7 eww.state.scope | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 8 simplexpr.error | 2 | |||||||||||||||||||||||||||||||||||||||
| 9 yuck.config.monitor | 1 | |||||||||||||||||||||||||||||||||||||||
| 10 yuck.format_diagnostic | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 11 simplexpr.dynval | 4 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 12 yuck.config.attributes | 5 | 1 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 13 yuck.config.backend_window_options | 1 | 1 | 1 | 1 | 4 | |||||||||||||||||||||||||||||||||||
| 14 notifier_host.host | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 15 simplexpr.eval | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 16 eww.widgets.systray | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 simplexpr.parser.lexer | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 18 yuck.parser.ast_iterator | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 19 yuck.parser.from_ast | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 20 yuck.config.var_definition | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 21 yuck.parser.ast | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 22 simplexpr.ast | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 23 yuck.config.toplevel | 1 | 1 | 2 | 2 | ||||||||||||||||||||||||||||||||||||
| 24 eww.state.scope_graph.internal | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 25 yuck.config.script_var_definition | 3 | 3 | 2 | 2 | 2 | 1 | ||||||||||||||||||||||||||||||||||
| 26 yuck.config.widget_use | 9 | 1 | 1 | 3 | 3 | 1 | 3 | |||||||||||||||||||||||||||||||||
| 27 yuck.config.window_geometry | 1 | 1 | 1 | 3 | ||||||||||||||||||||||||||||||||||||
| 28 eww.config.script_var | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 29 eww.script_var_handler | 4 | 5 | ||||||||||||||||||||||||||||||||||||||
| 30 eww.state.scope_graph | 1 | 2 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 31 yuck.config.widget_definition | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 32 yuck.config.window_definition | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 33 eww.widgets.build_widget | 6 | 5 | ||||||||||||||||||||||||||||||||||||||
| 34 eww.window_arguments | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 35 yuck.config.validate | 2 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 36 eww.window_initiator | 1 | 1 | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||
| 37 eww.app | 1 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 3 | 1 | 1 | |||||||||||||||||||||||||||||
| 38 eww.display_backend | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 39 eww.display_backend.platform_wayland | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 40 eww.display_backend.platform_x11 | 3 | 3 | 1 |
5→1 eww uses eww.paths✕
- Connections
- 1 pair of types, where a type in eww uses a type in eww.paths.
- The types involved
eww.eww$module→eww.paths.EwwPaths
- Direction
- eww uses eww.paths, so a change to eww.paths can break eww, while a change to eww can't break eww.paths.
- Position
- Below the diagonal: eww uses a module listed above it, which is the healthy direction.
6→1 eww.config.eww_config uses eww.paths✕
- Connections
- 2 pairs of types, where a type in eww.config.eww_config uses a type in eww.paths.
- The types involved
eww.config.eww_config.EwwConfig→eww.paths.EwwPathseww.config.eww_config.eww_config$module→eww.paths.EwwPaths
- Direction
- eww.config.eww_config uses eww.paths, so a change to eww.paths can break eww.config.eww_config, while a change to eww.config.eww_config can't break eww.paths.
- Position
- Below the diagonal: eww.config.eww_config uses a module listed above it, which is the healthy direction.
6→4 eww.config.eww_config uses eww_shared_util.wrappers✕
- Connections
- 1 pair of types, where a type in eww.config.eww_config uses a type in eww_shared_util.wrappers.
- The types involved
eww.config.eww_config.EwwConfig→eww_shared_util.wrappers.VarName
- Direction
- eww.config.eww_config uses eww_shared_util.wrappers, so a change to eww_shared_util.wrappers can break eww.config.eww_config, while a change to eww.config.eww_config can't break eww_shared_util.wrappers.
- Position
- Below the diagonal: eww.config.eww_config uses a module listed above it, which is the healthy direction.
7→4 eww.state.scope uses eww_shared_util.wrappers✕
- Connections
- 1 pair of types, where a type in eww.state.scope uses a type in eww_shared_util.wrappers.
- The types involved
eww.state.scope.Listener→eww_shared_util.wrappers.VarName
- Direction
- eww.state.scope uses eww_shared_util.wrappers, so a change to eww_shared_util.wrappers can break eww.state.scope, while a change to eww.state.scope can't break eww_shared_util.wrappers.
- Position
- Below the diagonal: eww.state.scope uses a module listed above it, which is the healthy direction.
7→30 eww.state.scope uses eww.state.scope_graph part of a loop✕
- Connections
- 1 pair of types, where a type in eww.state.scope uses a type in eww.state.scope_graph.
- The types involved
eww.state.scope.Scope→eww.state.scope_graph.ScopeIndex
- Direction
- eww.state.scope uses eww.state.scope_graph, so a change to eww.state.scope_graph can break eww.state.scope, while a change to eww.state.scope can't break eww.state.scope_graph.
- 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→3 simplexpr.error uses eww_shared_util.span✕
- Connections
- 2 pairs of types, where a type in simplexpr.error uses a type in eww_shared_util.span.
- The types involved
simplexpr.error.ParseError→eww_shared_util.span.Spansimplexpr.error.ParseError→eww_shared_util.span.Spanned
- Direction
- simplexpr.error uses eww_shared_util.span, so a change to eww_shared_util.span can break simplexpr.error, while a change to simplexpr.error can't break eww_shared_util.span.
- Position
- Below the diagonal: simplexpr.error uses a module listed above it, which is the healthy direction.
9→11 yuck.config.monitor uses simplexpr.dynval part of a loop✕
- Connections
- 1 pair of types, where a type in yuck.config.monitor uses a type in simplexpr.dynval.
- The types involved
yuck.config.monitor.MonitorIdentifier→simplexpr.dynval.DynVal
- Direction
- yuck.config.monitor uses simplexpr.dynval, so a change to simplexpr.dynval can break yuck.config.monitor, while a change to yuck.config.monitor can't break simplexpr.dynval.
- 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→3 yuck.format_diagnostic uses eww_shared_util.span✕
- Connections
- 1 pair of types, where a type in yuck.format_diagnostic uses a type in eww_shared_util.span.
- The types involved
yuck.format_diagnostic.format_diagnostic$module→eww_shared_util.span.Span
- Direction
- yuck.format_diagnostic uses eww_shared_util.span, so a change to eww_shared_util.span can break yuck.format_diagnostic, while a change to yuck.format_diagnostic can't break eww_shared_util.span.
- Position
- Below the diagonal: yuck.format_diagnostic uses a module listed above it, which is the healthy direction.
10→8 yuck.format_diagnostic uses simplexpr.error✕
- Connections
- 1 pair of types, where a type in yuck.format_diagnostic uses a type in simplexpr.error.
- The types involved
yuck.format_diagnostic.format_diagnostic$module→simplexpr.error.ParseError
- Direction
- yuck.format_diagnostic uses simplexpr.error, so a change to simplexpr.error can break yuck.format_diagnostic, while a change to yuck.format_diagnostic can't break simplexpr.error.
- Position
- Below the diagonal: yuck.format_diagnostic uses a module listed above it, which is the healthy direction.
11→3 simplexpr.dynval uses eww_shared_util.span✕
- Connections
- 4 pairs of types, where a type in simplexpr.dynval uses a type in eww_shared_util.span.
- The types involved
simplexpr.dynval.ConversionError→eww_shared_util.span.Spansimplexpr.dynval.ConversionError→eww_shared_util.span.Spannedsimplexpr.dynval.DynVal→eww_shared_util.span.Spansimplexpr.dynval.DynVal→eww_shared_util.span.Spanned
- Direction
- simplexpr.dynval uses eww_shared_util.span, so a change to eww_shared_util.span can break simplexpr.dynval, while a change to simplexpr.dynval can't break eww_shared_util.span.
- Position
- Below the diagonal: simplexpr.dynval uses a module listed above it, which is the healthy direction.
11→9 simplexpr.dynval uses yuck.config.monitor✕
- Connections
- 1 pair of types, where a type in simplexpr.dynval uses a type in yuck.config.monitor.
- The types involved
simplexpr.dynval.DynVal→yuck.config.monitor.MonitorIdentifier
- Direction
- simplexpr.dynval uses yuck.config.monitor, so a change to yuck.config.monitor can break simplexpr.dynval, while a change to simplexpr.dynval can't break yuck.config.monitor.
- Position
- Below the diagonal: simplexpr.dynval uses a module listed above it, which is the healthy direction.
11→10 simplexpr.dynval uses yuck.format_diagnostic✕
- Connections
- 1 pair of types, where a type in simplexpr.dynval uses a type in yuck.format_diagnostic.
- The types involved
simplexpr.dynval.ConversionError→yuck.format_diagnostic.ToDiagnostic
- Direction
- simplexpr.dynval uses yuck.format_diagnostic, so a change to yuck.format_diagnostic can break simplexpr.dynval, while a change to simplexpr.dynval can't break yuck.format_diagnostic.
- Position
- Below the diagonal: simplexpr.dynval uses a module listed above it, which is the healthy direction.
12→3 yuck.config.attributes uses eww_shared_util.span✕
- Connections
- 5 pairs of types, where a type in yuck.config.attributes uses a type in eww_shared_util.span.
- The types involved
yuck.config.attributes.AttrEntry→eww_shared_util.span.Spanyuck.config.attributes.AttrError→eww_shared_util.span.Spanyuck.config.attributes.AttrError→eww_shared_util.span.Spannedyuck.config.attributes.AttrSpec→eww_shared_util.span.Spanyuck.config.attributes.Attributes→eww_shared_util.span.Span
- Direction
- yuck.config.attributes uses eww_shared_util.span, so a change to eww_shared_util.span can break yuck.config.attributes, while a change to yuck.config.attributes can't break eww_shared_util.span.
- Position
- Below the diagonal: yuck.config.attributes uses a module listed above it, which is the healthy direction.
12→4 yuck.config.attributes uses eww_shared_util.wrappers✕
- Connections
- 1 pair of types, where a type in yuck.config.attributes uses a type in eww_shared_util.wrappers.
- The types involved
yuck.config.attributes.AttrSpec→eww_shared_util.wrappers.AttrName
- Direction
- yuck.config.attributes uses eww_shared_util.wrappers, so a change to eww_shared_util.wrappers can break yuck.config.attributes, while a change to yuck.config.attributes can't break eww_shared_util.wrappers.
- Position
- Below the diagonal: yuck.config.attributes uses a module listed above it, which is the healthy direction.
12→10 yuck.config.attributes uses yuck.format_diagnostic✕
- Connections
- 1 pair of types, where a type in yuck.config.attributes uses a type in yuck.format_diagnostic.
- The types involved
yuck.config.attributes.AttrError→yuck.format_diagnostic.ToDiagnostic
- Direction
- yuck.config.attributes uses yuck.format_diagnostic, so a change to yuck.format_diagnostic can break yuck.config.attributes, while a change to yuck.config.attributes can't break yuck.format_diagnostic.
- Position
- Below the diagonal: yuck.config.attributes uses a module listed above it, which is the healthy direction.
12→19 yuck.config.attributes uses yuck.parser.from_ast part of a loop✕
- Connections
- 1 pair of types, where a type in yuck.config.attributes uses a type in yuck.parser.from_ast.
- The types involved
yuck.config.attributes.AttrSpec→yuck.parser.from_ast.FromAst
- Direction
- yuck.config.attributes uses yuck.parser.from_ast, so a change to yuck.parser.from_ast can break yuck.config.attributes, while a change to yuck.config.attributes can't break yuck.parser.from_ast.
- 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→21 yuck.config.attributes uses yuck.parser.ast part of a loop✕
- Connections
- 2 pairs of types, where a type in yuck.config.attributes uses a type in yuck.parser.ast.
- The types involved
yuck.config.attributes.AttrEntry→yuck.parser.ast.Astyuck.config.attributes.AttrSpec→yuck.parser.ast.Ast
- Direction
- yuck.config.attributes uses yuck.parser.ast, so a change to yuck.parser.ast can break yuck.config.attributes, while a change to yuck.config.attributes can't break yuck.parser.ast.
- 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.
13→3 yuck.config.backend_window_options uses eww_shared_util.span✕
- Connections
- 1 pair of types, where a type in yuck.config.backend_window_options uses a type in eww_shared_util.span.
- The types involved
yuck.config.backend_window_options.X11StrutDefinitionExpr→eww_shared_util.span.Span
- Direction
- yuck.config.backend_window_options uses eww_shared_util.span, so a change to eww_shared_util.span can break yuck.config.backend_window_options, while a change to yuck.config.backend_window_options can't break eww_shared_util.span.
- Position
- Below the diagonal: yuck.config.backend_window_options uses a module listed above it, which is the healthy direction.
13→12 yuck.config.backend_window_options uses yuck.config.attributes✕
- Connections
- 1 pair of types, where a type in yuck.config.backend_window_options uses a type in yuck.config.attributes.
- The types involved
yuck.config.backend_window_options.BackendWindowOptionsDef→yuck.config.attributes.Attributes
- Direction
- yuck.config.backend_window_options uses yuck.config.attributes, so a change to yuck.config.attributes can break yuck.config.backend_window_options, while a change to yuck.config.backend_window_options can't break yuck.config.attributes.
- Position
- Below the diagonal: yuck.config.backend_window_options uses a module listed above it, which is the healthy direction.
13→18 yuck.config.backend_window_options uses yuck.parser.ast_iterator part of a loop✕
- Connections
- 1 pair of types, where a type in yuck.config.backend_window_options uses a type in yuck.parser.ast_iterator.
- The types involved
yuck.config.backend_window_options.X11StrutDefinitionExpr→yuck.parser.ast_iterator.AstIterator
- Direction
- yuck.config.backend_window_options uses yuck.parser.ast_iterator, so a change to yuck.parser.ast_iterator can break yuck.config.backend_window_options, while a change to yuck.config.backend_window_options can't break yuck.parser.ast_iterator.
- 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.
13→19 yuck.config.backend_window_options uses yuck.parser.from_ast part of a loop✕
- Connections
- 1 pair of types, where a type in yuck.config.backend_window_options uses a type in yuck.parser.from_ast.
- The types involved
yuck.config.backend_window_options.X11StrutDefinitionExpr→yuck.parser.from_ast.FromAstElementContent
- Direction
- yuck.config.backend_window_options uses yuck.parser.from_ast, so a change to yuck.parser.from_ast can break yuck.config.backend_window_options, while a change to yuck.config.backend_window_options can't break yuck.parser.from_ast.
- 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.
13→22 yuck.config.backend_window_options uses simplexpr.ast part of a loop✕
- Connections
- 4 pairs of types, where a type in yuck.config.backend_window_options uses a type in simplexpr.ast.
- The types involved
yuck.config.backend_window_options.WlBackendWindowOptionsDef→simplexpr.ast.SimplExpryuck.config.backend_window_options.X11BackendWindowOptionsDef→simplexpr.ast.SimplExpryuck.config.backend_window_options.X11StrutDefinitionExpr→simplexpr.ast.SimplExpryuck.config.backend_window_options.backend_window_options$module→simplexpr.ast.SimplExpr
- Direction
- yuck.config.backend_window_options uses simplexpr.ast, so a change to simplexpr.ast can break yuck.config.backend_window_options, while a change to yuck.config.backend_window_options can't break simplexpr.ast.
- 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.
14→13 notifier_host.host uses yuck.config.backend_window_options✕
- Connections
- 1 pair of types, where a type in notifier_host.host uses a type in yuck.config.backend_window_options.
- The types involved
notifier_host.host.host$module→yuck.config.backend_window_options.Error
- Direction
- notifier_host.host uses yuck.config.backend_window_options, so a change to yuck.config.backend_window_options can break notifier_host.host, while a change to notifier_host.host can't break yuck.config.backend_window_options.
- Position
- Below the diagonal: notifier_host.host uses a module listed above it, which is the healthy direction.
14→16 notifier_host.host uses eww.widgets.systray part of a loop✕
- Connections
- 1 pair of types, where a type in notifier_host.host uses a type in eww.widgets.systray.
- The types involved
notifier_host.host.Host→eww.widgets.systray.Item
- Direction
- notifier_host.host uses eww.widgets.systray, so a change to eww.widgets.systray can break notifier_host.host, while a change to notifier_host.host can't break eww.widgets.systray.
- 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.
15→3 simplexpr.eval uses eww_shared_util.span✕
- Connections
- 2 pairs of types, where a type in simplexpr.eval uses a type in eww_shared_util.span.
- The types involved
simplexpr.eval.EvalError→eww_shared_util.span.Spansimplexpr.eval.EvalError→eww_shared_util.span.Spanned
- Direction
- simplexpr.eval uses eww_shared_util.span, so a change to eww_shared_util.span can break simplexpr.eval, while a change to simplexpr.eval can't break eww_shared_util.span.
- Position
- Below the diagonal: simplexpr.eval uses a module listed above it, which is the healthy direction.
15→10 simplexpr.eval uses yuck.format_diagnostic✕
- Connections
- 1 pair of types, where a type in simplexpr.eval uses a type in yuck.format_diagnostic.
- The types involved
simplexpr.eval.EvalError→yuck.format_diagnostic.ToDiagnostic
- Direction
- simplexpr.eval uses yuck.format_diagnostic, so a change to yuck.format_diagnostic can break simplexpr.eval, while a change to simplexpr.eval can't break yuck.format_diagnostic.
- Position
- Below the diagonal: simplexpr.eval uses a module listed above it, which is the healthy direction.
15→11 simplexpr.eval uses simplexpr.dynval✕
- Connections
- 1 pair of types, where a type in simplexpr.eval uses a type in simplexpr.dynval.
- The types involved
simplexpr.eval.eval$module→simplexpr.dynval.DynVal
- Direction
- simplexpr.eval uses simplexpr.dynval, so a change to simplexpr.dynval can break simplexpr.eval, while a change to simplexpr.eval can't break simplexpr.dynval.
- Position
- Below the diagonal: simplexpr.eval uses a module listed above it, which is the healthy direction.
15→13 simplexpr.eval uses yuck.config.backend_window_options✕
- Connections
- 1 pair of types, where a type in simplexpr.eval uses a type in yuck.config.backend_window_options.
- The types involved
simplexpr.eval.JaqParseError→yuck.config.backend_window_options.Error
- Direction
- simplexpr.eval uses yuck.config.backend_window_options, so a change to yuck.config.backend_window_options can break simplexpr.eval, while a change to simplexpr.eval can't break yuck.config.backend_window_options.
- Position
- Below the diagonal: simplexpr.eval uses a module listed above it, which is the healthy direction.
16→14 eww.widgets.systray uses notifier_host.host✕
- Connections
- 1 pair of types, where a type in eww.widgets.systray uses a type in notifier_host.host.
- The types involved
eww.widgets.systray.Tray→notifier_host.host.Host
- Direction
- eww.widgets.systray uses notifier_host.host, so a change to notifier_host.host can break eww.widgets.systray, while a change to eww.widgets.systray can't break notifier_host.host.
- Position
- Below the diagonal: eww.widgets.systray uses a module listed above it, which is the healthy direction.
17→3 simplexpr.parser.lexer uses eww_shared_util.span✕
- Connections
- 2 pairs of types, where a type in simplexpr.parser.lexer uses a type in eww_shared_util.span.
- The types involved
simplexpr.parser.lexer.LexicalError→eww_shared_util.span.Spansimplexpr.parser.lexer.LexicalError→eww_shared_util.span.Spanned
- Direction
- simplexpr.parser.lexer uses eww_shared_util.span, so a change to eww_shared_util.span can break simplexpr.parser.lexer, while a change to simplexpr.parser.lexer can't break eww_shared_util.span.
- Position
- Below the diagonal: simplexpr.parser.lexer uses a module listed above it, which is the healthy direction.
17→10 simplexpr.parser.lexer uses yuck.format_diagnostic✕
- Connections
- 1 pair of types, where a type in simplexpr.parser.lexer uses a type in yuck.format_diagnostic.
- The types involved
simplexpr.parser.lexer.LexicalError→yuck.format_diagnostic.ToDiagnostic
- Direction
- simplexpr.parser.lexer uses yuck.format_diagnostic, so a change to yuck.format_diagnostic can break simplexpr.parser.lexer, while a change to simplexpr.parser.lexer can't break yuck.format_diagnostic.
- Position
- Below the diagonal: simplexpr.parser.lexer uses a module listed above it, which is the healthy direction.
17→16 simplexpr.parser.lexer uses eww.widgets.systray✕
- Connections
- 1 pair of types, where a type in simplexpr.parser.lexer uses a type in eww.widgets.systray.
- The types involved
simplexpr.parser.lexer.Lexer→eww.widgets.systray.Item
- Direction
- simplexpr.parser.lexer uses eww.widgets.systray, so a change to eww.widgets.systray can break simplexpr.parser.lexer, while a change to simplexpr.parser.lexer can't break eww.widgets.systray.
- Position
- Below the diagonal: simplexpr.parser.lexer uses a module listed above it, which is the healthy direction.
18→3 yuck.parser.ast_iterator uses eww_shared_util.span✕
- Connections
- 1 pair of types, where a type in yuck.parser.ast_iterator uses a type in eww_shared_util.span.
- The types involved
yuck.parser.ast_iterator.AstIterator→eww_shared_util.span.Span
- Direction
- yuck.parser.ast_iterator uses eww_shared_util.span, so a change to eww_shared_util.span can break yuck.parser.ast_iterator, while a change to yuck.parser.ast_iterator can't break eww_shared_util.span.
- Position
- Below the diagonal: yuck.parser.ast_iterator uses a module listed above it, which is the healthy direction.
18→16 yuck.parser.ast_iterator uses eww.widgets.systray✕
- Connections
- 1 pair of types, where a type in yuck.parser.ast_iterator uses a type in eww.widgets.systray.
- The types involved
yuck.parser.ast_iterator.AstIterator→eww.widgets.systray.Item
- Direction
- yuck.parser.ast_iterator uses eww.widgets.systray, so a change to eww.widgets.systray can break yuck.parser.ast_iterator, while a change to yuck.parser.ast_iterator can't break eww.widgets.systray.
- Position
- Below the diagonal: yuck.parser.ast_iterator uses a module listed above it, which is the healthy direction.
18→21 yuck.parser.ast_iterator uses yuck.parser.ast part of a loop✕
- Connections
- 1 pair of types, where a type in yuck.parser.ast_iterator uses a type in yuck.parser.ast.
- The types involved
yuck.parser.ast_iterator.AstIterator→yuck.parser.ast.Ast
- Direction
- yuck.parser.ast_iterator uses yuck.parser.ast, so a change to yuck.parser.ast can break yuck.parser.ast_iterator, while a change to yuck.parser.ast_iterator can't break yuck.parser.ast.
- 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.
19→3 yuck.parser.from_ast uses eww_shared_util.span✕
- Connections
- 1 pair of types, where a type in yuck.parser.from_ast uses a type in eww_shared_util.span.
- The types involved
yuck.parser.from_ast.FromAstElementContent→eww_shared_util.span.Span
- Direction
- yuck.parser.from_ast uses eww_shared_util.span, so a change to eww_shared_util.span can break yuck.parser.from_ast, while a change to yuck.parser.from_ast can't break eww_shared_util.span.
- Position
- Below the diagonal: yuck.parser.from_ast uses a module listed above it, which is the healthy direction.
19→18 yuck.parser.from_ast uses yuck.parser.ast_iterator✕
- Connections
- 1 pair of types, where a type in yuck.parser.from_ast uses a type in yuck.parser.ast_iterator.
- The types involved
yuck.parser.from_ast.FromAstElementContent→yuck.parser.ast_iterator.AstIterator
- Direction
- yuck.parser.from_ast uses yuck.parser.ast_iterator, so a change to yuck.parser.ast_iterator can break yuck.parser.from_ast, while a change to yuck.parser.from_ast can't break yuck.parser.ast_iterator.
- Position
- Below the diagonal: yuck.parser.from_ast uses a module listed above it, which is the healthy direction.
19→21 yuck.parser.from_ast uses yuck.parser.ast part of a loop✕
- Connections
- 1 pair of types, where a type in yuck.parser.from_ast uses a type in yuck.parser.ast.
- The types involved
yuck.parser.from_ast.FromAst→yuck.parser.ast.Ast
- Direction
- yuck.parser.from_ast uses yuck.parser.ast, so a change to yuck.parser.ast can break yuck.parser.from_ast, while a change to yuck.parser.from_ast can't break yuck.parser.ast.
- 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.
20→3 yuck.config.var_definition uses eww_shared_util.span✕
- Connections
- 1 pair of types, where a type in yuck.config.var_definition uses a type in eww_shared_util.span.
- The types involved
yuck.config.var_definition.VarDefinition→eww_shared_util.span.Span
- Direction
- yuck.config.var_definition uses eww_shared_util.span, so a change to eww_shared_util.span can break yuck.config.var_definition, while a change to yuck.config.var_definition can't break eww_shared_util.span.
- Position
- Below the diagonal: yuck.config.var_definition uses a module listed above it, which is the healthy direction.
20→4 yuck.config.var_definition uses eww_shared_util.wrappers✕
- Connections
- 1 pair of types, where a type in yuck.config.var_definition uses a type in eww_shared_util.wrappers.
- The types involved
yuck.config.var_definition.VarDefinition→eww_shared_util.wrappers.VarName
- Direction
- yuck.config.var_definition uses eww_shared_util.wrappers, so a change to eww_shared_util.wrappers can break yuck.config.var_definition, while a change to yuck.config.var_definition can't break eww_shared_util.wrappers.
- Position
- Below the diagonal: yuck.config.var_definition uses a module listed above it, which is the healthy direction.
20→11 yuck.config.var_definition uses simplexpr.dynval✕
- Connections
- 1 pair of types, where a type in yuck.config.var_definition uses a type in simplexpr.dynval.
- The types involved
yuck.config.var_definition.VarDefinition→simplexpr.dynval.DynVal
- Direction
- yuck.config.var_definition uses simplexpr.dynval, so a change to simplexpr.dynval can break yuck.config.var_definition, while a change to yuck.config.var_definition can't break simplexpr.dynval.
- Position
- Below the diagonal: yuck.config.var_definition uses a module listed above it, which is the healthy direction.
20→18 yuck.config.var_definition uses yuck.parser.ast_iterator✕
- Connections
- 1 pair of types, where a type in yuck.config.var_definition uses a type in yuck.parser.ast_iterator.
- The types involved
yuck.config.var_definition.VarDefinition→yuck.parser.ast_iterator.AstIterator
- Direction
- yuck.config.var_definition uses yuck.parser.ast_iterator, so a change to yuck.parser.ast_iterator can break yuck.config.var_definition, while a change to yuck.config.var_definition can't break yuck.parser.ast_iterator.
- Position
- Below the diagonal: yuck.config.var_definition uses a module listed above it, which is the healthy direction.
20→19 yuck.config.var_definition uses yuck.parser.from_ast✕
- Connections
- 1 pair of types, where a type in yuck.config.var_definition uses a type in yuck.parser.from_ast.
- The types involved
yuck.config.var_definition.VarDefinition→yuck.parser.from_ast.FromAstElementContent
- Direction
- yuck.config.var_definition uses yuck.parser.from_ast, so a change to yuck.parser.from_ast can break yuck.config.var_definition, while a change to yuck.config.var_definition can't break yuck.parser.from_ast.
- Position
- Below the diagonal: yuck.config.var_definition uses a module listed above it, which is the healthy direction.
21→3 yuck.parser.ast uses eww_shared_util.span✕
- Connections
- 2 pairs of types, where a type in yuck.parser.ast uses a type in eww_shared_util.span.
- The types involved
yuck.parser.ast.Ast→eww_shared_util.span.Spanyuck.parser.ast.Ast→eww_shared_util.span.Spanned
- Direction
- yuck.parser.ast uses eww_shared_util.span, so a change to eww_shared_util.span can break yuck.parser.ast, while a change to yuck.parser.ast can't break eww_shared_util.span.
- Position
- Below the diagonal: yuck.parser.ast uses a module listed above it, which is the healthy direction.
21→19 yuck.parser.ast uses yuck.parser.from_ast✕
- Connections
- 1 pair of types, where a type in yuck.parser.ast uses a type in yuck.parser.from_ast.
- The types involved
yuck.parser.ast.Ast→yuck.parser.from_ast.FromAst
- Direction
- yuck.parser.ast uses yuck.parser.from_ast, so a change to yuck.parser.from_ast can break yuck.parser.ast, while a change to yuck.parser.ast can't break yuck.parser.from_ast.
- Position
- Below the diagonal: yuck.parser.ast uses a module listed above it, which is the healthy direction.
22→3 simplexpr.ast uses eww_shared_util.span✕
- Connections
- 2 pairs of types, where a type in simplexpr.ast uses a type in eww_shared_util.span.
- The types involved
simplexpr.ast.SimplExpr→eww_shared_util.span.Spansimplexpr.ast.SimplExpr→eww_shared_util.span.Spanned
- Direction
- simplexpr.ast uses eww_shared_util.span, so a change to eww_shared_util.span can break simplexpr.ast, while a change to simplexpr.ast can't break eww_shared_util.span.
- Position
- Below the diagonal: simplexpr.ast uses a module listed above it, which is the healthy direction.
22→4 simplexpr.ast uses eww_shared_util.wrappers✕
- Connections
- 1 pair of types, where a type in simplexpr.ast uses a type in eww_shared_util.wrappers.
- The types involved
simplexpr.ast.SimplExpr→eww_shared_util.wrappers.VarName
- Direction
- simplexpr.ast uses eww_shared_util.wrappers, so a change to eww_shared_util.wrappers can break simplexpr.ast, while a change to simplexpr.ast can't break eww_shared_util.wrappers.
- Position
- Below the diagonal: simplexpr.ast uses a module listed above it, which is the healthy direction.
22→19 simplexpr.ast uses yuck.parser.from_ast✕
- Connections
- 1 pair of types, where a type in simplexpr.ast uses a type in yuck.parser.from_ast.
- The types involved
simplexpr.ast.SimplExpr→yuck.parser.from_ast.FromAst
- Direction
- simplexpr.ast uses yuck.parser.from_ast, so a change to yuck.parser.from_ast can break simplexpr.ast, while a change to simplexpr.ast can't break yuck.parser.from_ast.
- Position
- Below the diagonal: simplexpr.ast uses a module listed above it, which is the healthy direction.
22→21 simplexpr.ast uses yuck.parser.ast✕
- Connections
- 1 pair of types, where a type in simplexpr.ast uses a type in yuck.parser.ast.
- The types involved
simplexpr.ast.SimplExpr→yuck.parser.ast.Ast
- Direction
- simplexpr.ast uses yuck.parser.ast, so a change to yuck.parser.ast can break simplexpr.ast, while a change to simplexpr.ast can't break yuck.parser.ast.
- Position
- Below the diagonal: simplexpr.ast uses a module listed above it, which is the healthy direction.
23→3 yuck.config.toplevel uses eww_shared_util.span✕
- Connections
- 1 pair of types, where a type in yuck.config.toplevel uses a type in eww_shared_util.span.
- The types involved
yuck.config.toplevel.Include→eww_shared_util.span.Span
- Direction
- yuck.config.toplevel uses eww_shared_util.span, so a change to eww_shared_util.span can break yuck.config.toplevel, while a change to yuck.config.toplevel can't break eww_shared_util.span.
- Position
- Below the diagonal: yuck.config.toplevel uses a module listed above it, which is the healthy direction.
23→18 yuck.config.toplevel uses yuck.parser.ast_iterator✕
- Connections
- 1 pair of types, where a type in yuck.config.toplevel uses a type in yuck.parser.ast_iterator.
- The types involved
yuck.config.toplevel.Include→yuck.parser.ast_iterator.AstIterator
- Direction
- yuck.config.toplevel uses yuck.parser.ast_iterator, so a change to yuck.parser.ast_iterator can break yuck.config.toplevel, while a change to yuck.config.toplevel can't break yuck.parser.ast_iterator.
- Position
- Below the diagonal: yuck.config.toplevel uses a module listed above it, which is the healthy direction.
23→19 yuck.config.toplevel uses yuck.parser.from_ast✕
- Connections
- 2 pairs of types, where a type in yuck.config.toplevel uses a type in yuck.parser.from_ast.
- The types involved
yuck.config.toplevel.Include→yuck.parser.from_ast.FromAstElementContentyuck.config.toplevel.TopLevel→yuck.parser.from_ast.FromAst
- Direction
- yuck.config.toplevel uses yuck.parser.from_ast, so a change to yuck.parser.from_ast can break yuck.config.toplevel, while a change to yuck.config.toplevel can't break yuck.parser.from_ast.
- Position
- Below the diagonal: yuck.config.toplevel uses a module listed above it, which is the healthy direction.
23→21 yuck.config.toplevel uses yuck.parser.ast✕
- Connections
- 2 pairs of types, where a type in yuck.config.toplevel uses a type in yuck.parser.ast.
- The types involved
yuck.config.toplevel.Config→yuck.parser.ast.Astyuck.config.toplevel.TopLevel→yuck.parser.ast.Ast
- Direction
- yuck.config.toplevel uses yuck.parser.ast, so a change to yuck.parser.ast can break yuck.config.toplevel, while a change to yuck.config.toplevel can't break yuck.parser.ast.
- Position
- Below the diagonal: yuck.config.toplevel uses a module listed above it, which is the healthy direction.
24→4 eww.state.scope_graph.internal uses eww_shared_util.wrappers✕
- Connections
- 2 pairs of types, where a type in eww.state.scope_graph.internal uses a type in eww_shared_util.wrappers.
- The types involved
eww.state.scope_graph.internal.ProvidedAttr→eww_shared_util.wrappers.AttrNameeww.state.scope_graph.internal.ScopeGraphInternal→eww_shared_util.wrappers.VarName
- Direction
- eww.state.scope_graph.internal uses eww_shared_util.wrappers, so a change to eww_shared_util.wrappers can break eww.state.scope_graph.internal, while a change to eww.state.scope_graph.internal can't break eww_shared_util.wrappers.
- Position
- Below the diagonal: eww.state.scope_graph.internal uses a module listed above it, which is the healthy direction.
24→7 eww.state.scope_graph.internal uses eww.state.scope✕
- Connections
- 1 pair of types, where a type in eww.state.scope_graph.internal uses a type in eww.state.scope.
- The types involved
eww.state.scope_graph.internal.ScopeGraphInternal→eww.state.scope.Scope
- Direction
- eww.state.scope_graph.internal uses eww.state.scope, so a change to eww.state.scope can break eww.state.scope_graph.internal, while a change to eww.state.scope_graph.internal can't break eww.state.scope.
- Position
- Below the diagonal: eww.state.scope_graph.internal uses a module listed above it, which is the healthy direction.
24→22 eww.state.scope_graph.internal uses simplexpr.ast✕
- Connections
- 1 pair of types, where a type in eww.state.scope_graph.internal uses a type in simplexpr.ast.
- The types involved
eww.state.scope_graph.internal.ProvidedAttr→simplexpr.ast.SimplExpr
- Direction
- eww.state.scope_graph.internal uses simplexpr.ast, so a change to simplexpr.ast can break eww.state.scope_graph.internal, while a change to eww.state.scope_graph.internal can't break simplexpr.ast.
- Position
- Below the diagonal: eww.state.scope_graph.internal uses a module listed above it, which is the healthy direction.
24→30 eww.state.scope_graph.internal uses eww.state.scope_graph part of a loop✕
- Connections
- 1 pair of types, where a type in eww.state.scope_graph.internal uses a type in eww.state.scope_graph.
- The types involved
eww.state.scope_graph.internal.ScopeGraphInternal→eww.state.scope_graph.ScopeIndex
- Direction
- eww.state.scope_graph.internal uses eww.state.scope_graph, so a change to eww.state.scope_graph can break eww.state.scope_graph.internal, while a change to eww.state.scope_graph.internal can't break eww.state.scope_graph.
- 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.
25→3 yuck.config.script_var_definition uses eww_shared_util.span✕
- Connections
- 3 pairs of types, where a type in yuck.config.script_var_definition uses a type in eww_shared_util.span.
- The types involved
yuck.config.script_var_definition.ListenScriptVar→eww_shared_util.span.Spanyuck.config.script_var_definition.PollScriptVar→eww_shared_util.span.Spanyuck.config.script_var_definition.ScriptVarDefinition→eww_shared_util.span.Span
- Direction
- yuck.config.script_var_definition uses eww_shared_util.span, so a change to eww_shared_util.span can break yuck.config.script_var_definition, while a change to yuck.config.script_var_definition can't break eww_shared_util.span.
- Position
- Below the diagonal: yuck.config.script_var_definition uses a module listed above it, which is the healthy direction.
25→4 yuck.config.script_var_definition uses eww_shared_util.wrappers✕
- Connections
- 3 pairs of types, where a type in yuck.config.script_var_definition uses a type in eww_shared_util.wrappers.
- The types involved
yuck.config.script_var_definition.ListenScriptVar→eww_shared_util.wrappers.VarNameyuck.config.script_var_definition.PollScriptVar→eww_shared_util.wrappers.VarNameyuck.config.script_var_definition.ScriptVarDefinition→eww_shared_util.wrappers.VarName
- Direction
- yuck.config.script_var_definition uses eww_shared_util.wrappers, so a change to eww_shared_util.wrappers can break yuck.config.script_var_definition, while a change to yuck.config.script_var_definition can't break eww_shared_util.wrappers.
- Position
- Below the diagonal: yuck.config.script_var_definition uses a module listed above it, which is the healthy direction.
25→11 yuck.config.script_var_definition uses simplexpr.dynval✕
- Connections
- 2 pairs of types, where a type in yuck.config.script_var_definition uses a type in simplexpr.dynval.
- The types involved
yuck.config.script_var_definition.ListenScriptVar→simplexpr.dynval.DynValyuck.config.script_var_definition.PollScriptVar→simplexpr.dynval.DynVal
- Direction
- yuck.config.script_var_definition uses simplexpr.dynval, so a change to simplexpr.dynval can break yuck.config.script_var_definition, while a change to yuck.config.script_var_definition can't break simplexpr.dynval.
- Position
- Below the diagonal: yuck.config.script_var_definition uses a module listed above it, which is the healthy direction.
25→18 yuck.config.script_var_definition uses yuck.parser.ast_iterator✕
- Connections
- 2 pairs of types, where a type in yuck.config.script_var_definition uses a type in yuck.parser.ast_iterator.
- The types involved
yuck.config.script_var_definition.ListenScriptVar→yuck.parser.ast_iterator.AstIteratoryuck.config.script_var_definition.PollScriptVar→yuck.parser.ast_iterator.AstIterator
- Direction
- yuck.config.script_var_definition uses yuck.parser.ast_iterator, so a change to yuck.parser.ast_iterator can break yuck.config.script_var_definition, while a change to yuck.config.script_var_definition can't break yuck.parser.ast_iterator.
- Position
- Below the diagonal: yuck.config.script_var_definition uses a module listed above it, which is the healthy direction.
25→19 yuck.config.script_var_definition uses yuck.parser.from_ast✕
- Connections
- 2 pairs of types, where a type in yuck.config.script_var_definition uses a type in yuck.parser.from_ast.
- The types involved
yuck.config.script_var_definition.ListenScriptVar→yuck.parser.from_ast.FromAstElementContentyuck.config.script_var_definition.PollScriptVar→yuck.parser.from_ast.FromAstElementContent
- Direction
- yuck.config.script_var_definition uses yuck.parser.from_ast, so a change to yuck.parser.from_ast can break yuck.config.script_var_definition, while a change to yuck.config.script_var_definition can't break yuck.parser.from_ast.
- Position
- Below the diagonal: yuck.config.script_var_definition uses a module listed above it, which is the healthy direction.
25→22 yuck.config.script_var_definition uses simplexpr.ast✕
- Connections
- 1 pair of types, where a type in yuck.config.script_var_definition uses a type in simplexpr.ast.
- The types involved
yuck.config.script_var_definition.PollScriptVar→simplexpr.ast.SimplExpr
- Direction
- yuck.config.script_var_definition uses simplexpr.ast, so a change to simplexpr.ast can break yuck.config.script_var_definition, while a change to yuck.config.script_var_definition can't break simplexpr.ast.
- Position
- Below the diagonal: yuck.config.script_var_definition uses a module listed above it, which is the healthy direction.
26→3 yuck.config.widget_use uses eww_shared_util.span✕
- Connections
- 9 pairs of types, where a type in yuck.config.widget_use uses a type in eww_shared_util.span.
- The types involved
yuck.config.widget_use.BasicWidgetUse→eww_shared_util.span.Spanyuck.config.widget_use.BasicWidgetUse→eww_shared_util.span.Spannedyuck.config.widget_use.ChildrenWidgetUse→eww_shared_util.span.Spanyuck.config.widget_use.ChildrenWidgetUse→eww_shared_util.span.Spannedyuck.config.widget_use.LoopWidgetUse→eww_shared_util.span.Spanyuck.config.widget_use.LoopWidgetUse→eww_shared_util.span.Spannedyuck.config.widget_use.WidgetUse→eww_shared_util.span.Spanyuck.config.widget_use.WidgetUse→eww_shared_util.span.Spannedyuck.config.widget_use.widget_use$module→eww_shared_util.span.Span
- Direction
- yuck.config.widget_use uses eww_shared_util.span, so a change to eww_shared_util.span can break yuck.config.widget_use, while a change to yuck.config.widget_use can't break eww_shared_util.span.
- Position
- Below the diagonal: yuck.config.widget_use uses a module listed above it, which is the healthy direction.
26→4 yuck.config.widget_use uses eww_shared_util.wrappers✕
- Connections
- 1 pair of types, where a type in yuck.config.widget_use uses a type in eww_shared_util.wrappers.
- The types involved
yuck.config.widget_use.LoopWidgetUse→eww_shared_util.wrappers.VarName
- Direction
- yuck.config.widget_use uses eww_shared_util.wrappers, so a change to eww_shared_util.wrappers can break yuck.config.widget_use, while a change to yuck.config.widget_use can't break eww_shared_util.wrappers.
- Position
- Below the diagonal: yuck.config.widget_use uses a module listed above it, which is the healthy direction.
26→12 yuck.config.widget_use uses yuck.config.attributes✕
- Connections
- 1 pair of types, where a type in yuck.config.widget_use uses a type in yuck.config.attributes.
- The types involved
yuck.config.widget_use.BasicWidgetUse→yuck.config.attributes.Attributes
- Direction
- yuck.config.widget_use uses yuck.config.attributes, so a change to yuck.config.attributes can break yuck.config.widget_use, while a change to yuck.config.widget_use can't break yuck.config.attributes.
- Position
- Below the diagonal: yuck.config.widget_use uses a module listed above it, which is the healthy direction.
26→18 yuck.config.widget_use uses yuck.parser.ast_iterator✕
- Connections
- 3 pairs of types, where a type in yuck.config.widget_use uses a type in yuck.parser.ast_iterator.
- The types involved
yuck.config.widget_use.BasicWidgetUse→yuck.parser.ast_iterator.AstIteratoryuck.config.widget_use.ChildrenWidgetUse→yuck.parser.ast_iterator.AstIteratoryuck.config.widget_use.LoopWidgetUse→yuck.parser.ast_iterator.AstIterator
- Direction
- yuck.config.widget_use uses yuck.parser.ast_iterator, so a change to yuck.parser.ast_iterator can break yuck.config.widget_use, while a change to yuck.config.widget_use can't break yuck.parser.ast_iterator.
- Position
- Below the diagonal: yuck.config.widget_use uses a module listed above it, which is the healthy direction.
26→19 yuck.config.widget_use uses yuck.parser.from_ast✕
- Connections
- 3 pairs of types, where a type in yuck.config.widget_use uses a type in yuck.parser.from_ast.
- The types involved
yuck.config.widget_use.ChildrenWidgetUse→yuck.parser.from_ast.FromAstElementContentyuck.config.widget_use.LoopWidgetUse→yuck.parser.from_ast.FromAstElementContentyuck.config.widget_use.WidgetUse→yuck.parser.from_ast.FromAst
- Direction
- yuck.config.widget_use uses yuck.parser.from_ast, so a change to yuck.parser.from_ast can break yuck.config.widget_use, while a change to yuck.config.widget_use can't break yuck.parser.from_ast.
- Position
- Below the diagonal: yuck.config.widget_use uses a module listed above it, which is the healthy direction.
26→21 yuck.config.widget_use uses yuck.parser.ast✕
- Connections
- 1 pair of types, where a type in yuck.config.widget_use uses a type in yuck.parser.ast.
- The types involved
yuck.config.widget_use.WidgetUse→yuck.parser.ast.Ast
- Direction
- yuck.config.widget_use uses yuck.parser.ast, so a change to yuck.parser.ast can break yuck.config.widget_use, while a change to yuck.config.widget_use can't break yuck.parser.ast.
- Position
- Below the diagonal: yuck.config.widget_use uses a module listed above it, which is the healthy direction.
26→22 yuck.config.widget_use uses simplexpr.ast✕
- Connections
- 3 pairs of types, where a type in yuck.config.widget_use uses a type in simplexpr.ast.
- The types involved
yuck.config.widget_use.ChildrenWidgetUse→simplexpr.ast.SimplExpryuck.config.widget_use.LoopWidgetUse→simplexpr.ast.SimplExpryuck.config.widget_use.widget_use$module→simplexpr.ast.SimplExpr
- Direction
- yuck.config.widget_use uses simplexpr.ast, so a change to simplexpr.ast can break yuck.config.widget_use, while a change to yuck.config.widget_use can't break simplexpr.ast.
- Position
- Below the diagonal: yuck.config.widget_use uses a module listed above it, which is the healthy direction.
27→3 yuck.config.window_geometry uses eww_shared_util.span✕
- Connections
- 1 pair of types, where a type in yuck.config.window_geometry uses a type in eww_shared_util.span.
- The types involved
yuck.config.window_geometry.WindowGeometryDef→eww_shared_util.span.Span
- Direction
- yuck.config.window_geometry uses eww_shared_util.span, so a change to eww_shared_util.span can break yuck.config.window_geometry, while a change to yuck.config.window_geometry can't break eww_shared_util.span.
- Position
- Below the diagonal: yuck.config.window_geometry uses a module listed above it, which is the healthy direction.
27→18 yuck.config.window_geometry uses yuck.parser.ast_iterator✕
- Connections
- 1 pair of types, where a type in yuck.config.window_geometry uses a type in yuck.parser.ast_iterator.
- The types involved
yuck.config.window_geometry.WindowGeometryDef→yuck.parser.ast_iterator.AstIterator
- Direction
- yuck.config.window_geometry uses yuck.parser.ast_iterator, so a change to yuck.parser.ast_iterator can break yuck.config.window_geometry, while a change to yuck.config.window_geometry can't break yuck.parser.ast_iterator.
- Position
- Below the diagonal: yuck.config.window_geometry uses a module listed above it, which is the healthy direction.
27→19 yuck.config.window_geometry uses yuck.parser.from_ast✕
- Connections
- 1 pair of types, where a type in yuck.config.window_geometry uses a type in yuck.parser.from_ast.
- The types involved
yuck.config.window_geometry.WindowGeometryDef→yuck.parser.from_ast.FromAstElementContent
- Direction
- yuck.config.window_geometry uses yuck.parser.from_ast, so a change to yuck.parser.from_ast can break yuck.config.window_geometry, while a change to yuck.config.window_geometry can't break yuck.parser.from_ast.
- Position
- Below the diagonal: yuck.config.window_geometry uses a module listed above it, which is the healthy direction.
27→22 yuck.config.window_geometry uses simplexpr.ast✕
- Connections
- 3 pairs of types, where a type in yuck.config.window_geometry uses a type in simplexpr.ast.
- The types involved
yuck.config.window_geometry.CoordsDef→simplexpr.ast.SimplExpryuck.config.window_geometry.WindowGeometryDef→simplexpr.ast.SimplExpryuck.config.window_geometry.window_geometry$module→simplexpr.ast.SimplExpr
- Direction
- yuck.config.window_geometry uses simplexpr.ast, so a change to simplexpr.ast can break yuck.config.window_geometry, while a change to yuck.config.window_geometry can't break simplexpr.ast.
- Position
- Below the diagonal: yuck.config.window_geometry uses a module listed above it, which is the healthy direction.
28→3 eww.config.script_var uses eww_shared_util.span✕
- Connections
- 1 pair of types, where a type in eww.config.script_var uses a type in eww_shared_util.span.
- The types involved
eww.config.script_var.script_var$module→eww_shared_util.span.Span
- Direction
- eww.config.script_var uses eww_shared_util.span, so a change to eww_shared_util.span can break eww.config.script_var, while a change to eww.config.script_var can't break eww_shared_util.span.
- Position
- Below the diagonal: eww.config.script_var uses a module listed above it, which is the healthy direction.
28→4 eww.config.script_var uses eww_shared_util.wrappers✕
- Connections
- 1 pair of types, where a type in eww.config.script_var uses a type in eww_shared_util.wrappers.
- The types involved
eww.config.script_var.script_var$module→eww_shared_util.wrappers.VarName
- Direction
- eww.config.script_var uses eww_shared_util.wrappers, so a change to eww_shared_util.wrappers can break eww.config.script_var, while a change to eww.config.script_var can't break eww_shared_util.wrappers.
- Position
- Below the diagonal: eww.config.script_var uses a module listed above it, which is the healthy direction.
28→25 eww.config.script_var uses yuck.config.script_var_definition✕
- Connections
- 1 pair of types, where a type in eww.config.script_var uses a type in yuck.config.script_var_definition.
- The types involved
eww.config.script_var.script_var$module→yuck.config.script_var_definition.ScriptVarDefinition
- Direction
- eww.config.script_var uses yuck.config.script_var_definition, so a change to yuck.config.script_var_definition can break eww.config.script_var, while a change to eww.config.script_var can't break yuck.config.script_var_definition.
- Position
- Below the diagonal: eww.config.script_var uses a module listed above it, which is the healthy direction.
29→4 eww.script_var_handler uses eww_shared_util.wrappers✕
- Connections
- 4 pairs of types, where a type in eww.script_var_handler uses a type in eww_shared_util.wrappers.
- The types involved
eww.script_var_handler.ListenVarHandler→eww_shared_util.wrappers.VarNameeww.script_var_handler.PollVarHandler→eww_shared_util.wrappers.VarNameeww.script_var_handler.ScriptVarHandler→eww_shared_util.wrappers.VarNameeww.script_var_handler.ScriptVarHandlerHandle→eww_shared_util.wrappers.VarName
- Direction
- eww.script_var_handler uses eww_shared_util.wrappers, so a change to eww_shared_util.wrappers can break eww.script_var_handler, while a change to eww.script_var_handler can't break eww_shared_util.wrappers.
- Position
- Below the diagonal: eww.script_var_handler uses a module listed above it, which is the healthy direction.
29→25 eww.script_var_handler uses yuck.config.script_var_definition✕
- Connections
- 5 pairs of types, where a type in eww.script_var_handler uses a type in yuck.config.script_var_definition.
- The types involved
eww.script_var_handler.ListenVarHandler→yuck.config.script_var_definition.ListenScriptVareww.script_var_handler.PollVarHandler→yuck.config.script_var_definition.PollScriptVareww.script_var_handler.ScriptVarHandler→yuck.config.script_var_definition.ScriptVarDefinitioneww.script_var_handler.ScriptVarHandlerHandle→yuck.config.script_var_definition.ScriptVarDefinitioneww.script_var_handler.script_var_handler$module→yuck.config.script_var_definition.PollScriptVar
- Direction
- eww.script_var_handler uses yuck.config.script_var_definition, so a change to yuck.config.script_var_definition can break eww.script_var_handler, while a change to eww.script_var_handler can't break yuck.config.script_var_definition.
- Position
- Below the diagonal: eww.script_var_handler uses a module listed above it, which is the healthy direction.
30→4 eww.state.scope_graph uses eww_shared_util.wrappers✕
- Connections
- 1 pair of types, where a type in eww.state.scope_graph uses a type in eww_shared_util.wrappers.
- The types involved
eww.state.scope_graph.ScopeGraph→eww_shared_util.wrappers.VarName
- Direction
- eww.state.scope_graph uses eww_shared_util.wrappers, so a change to eww_shared_util.wrappers can break eww.state.scope_graph, while a change to eww.state.scope_graph can't break eww_shared_util.wrappers.
- Position
- Below the diagonal: eww.state.scope_graph uses a module listed above it, which is the healthy direction.
30→7 eww.state.scope_graph uses eww.state.scope✕
- Connections
- 2 pairs of types, where a type in eww.state.scope_graph uses a type in eww.state.scope.
- The types involved
eww.state.scope_graph.ScopeGraph→eww.state.scope.Listenereww.state.scope_graph.ScopeGraph→eww.state.scope.Scope
- Direction
- eww.state.scope_graph uses eww.state.scope, so a change to eww.state.scope can break eww.state.scope_graph, while a change to eww.state.scope_graph can't break eww.state.scope.
- Position
- Below the diagonal: eww.state.scope_graph uses a module listed above it, which is the healthy direction.
30→11 eww.state.scope_graph uses simplexpr.dynval✕
- Connections
- 1 pair of types, where a type in eww.state.scope_graph uses a type in simplexpr.dynval.
- The types involved
eww.state.scope_graph.ScopeGraph→simplexpr.dynval.DynVal
- Direction
- eww.state.scope_graph uses simplexpr.dynval, so a change to simplexpr.dynval can break eww.state.scope_graph, while a change to eww.state.scope_graph can't break simplexpr.dynval.
- Position
- Below the diagonal: eww.state.scope_graph uses a module listed above it, which is the healthy direction.
30→22 eww.state.scope_graph uses simplexpr.ast✕
- Connections
- 1 pair of types, where a type in eww.state.scope_graph uses a type in simplexpr.ast.
- The types involved
eww.state.scope_graph.ScopeGraph→simplexpr.ast.SimplExpr
- Direction
- eww.state.scope_graph uses simplexpr.ast, so a change to simplexpr.ast can break eww.state.scope_graph, while a change to eww.state.scope_graph can't break simplexpr.ast.
- Position
- Below the diagonal: eww.state.scope_graph uses a module listed above it, which is the healthy direction.
30→24 eww.state.scope_graph uses eww.state.scope_graph.internal✕
- Connections
- 1 pair of types, where a type in eww.state.scope_graph uses a type in eww.state.scope_graph.internal.
- The types involved
eww.state.scope_graph.ScopeGraph→eww.state.scope_graph.internal.ScopeGraphInternal
- Direction
- eww.state.scope_graph uses eww.state.scope_graph.internal, so a change to eww.state.scope_graph.internal can break eww.state.scope_graph, while a change to eww.state.scope_graph can't break eww.state.scope_graph.internal.
- Position
- Below the diagonal: eww.state.scope_graph uses a module listed above it, which is the healthy direction.
31→3 yuck.config.widget_definition uses eww_shared_util.span✕
- Connections
- 1 pair of types, where a type in yuck.config.widget_definition uses a type in eww_shared_util.span.
- The types involved
yuck.config.widget_definition.WidgetDefinition→eww_shared_util.span.Span
- Direction
- yuck.config.widget_definition uses eww_shared_util.span, so a change to eww_shared_util.span can break yuck.config.widget_definition, while a change to yuck.config.widget_definition can't break eww_shared_util.span.
- Position
- Below the diagonal: yuck.config.widget_definition uses a module listed above it, which is the healthy direction.
31→12 yuck.config.widget_definition uses yuck.config.attributes✕
- Connections
- 1 pair of types, where a type in yuck.config.widget_definition uses a type in yuck.config.attributes.
- The types involved
yuck.config.widget_definition.WidgetDefinition→yuck.config.attributes.AttrSpec
- Direction
- yuck.config.widget_definition uses yuck.config.attributes, so a change to yuck.config.attributes can break yuck.config.widget_definition, while a change to yuck.config.widget_definition can't break yuck.config.attributes.
- Position
- Below the diagonal: yuck.config.widget_definition uses a module listed above it, which is the healthy direction.
31→18 yuck.config.widget_definition uses yuck.parser.ast_iterator✕
- Connections
- 1 pair of types, where a type in yuck.config.widget_definition uses a type in yuck.parser.ast_iterator.
- The types involved
yuck.config.widget_definition.WidgetDefinition→yuck.parser.ast_iterator.AstIterator
- Direction
- yuck.config.widget_definition uses yuck.parser.ast_iterator, so a change to yuck.parser.ast_iterator can break yuck.config.widget_definition, while a change to yuck.config.widget_definition can't break yuck.parser.ast_iterator.
- Position
- Below the diagonal: yuck.config.widget_definition uses a module listed above it, which is the healthy direction.
31→19 yuck.config.widget_definition uses yuck.parser.from_ast✕
- Connections
- 1 pair of types, where a type in yuck.config.widget_definition uses a type in yuck.parser.from_ast.
- The types involved
yuck.config.widget_definition.WidgetDefinition→yuck.parser.from_ast.FromAstElementContent
- Direction
- yuck.config.widget_definition uses yuck.parser.from_ast, so a change to yuck.parser.from_ast can break yuck.config.widget_definition, while a change to yuck.config.widget_definition can't break yuck.parser.from_ast.
- Position
- Below the diagonal: yuck.config.widget_definition uses a module listed above it, which is the healthy direction.
31→26 yuck.config.widget_definition uses yuck.config.widget_use✕
- Connections
- 1 pair of types, where a type in yuck.config.widget_definition uses a type in yuck.config.widget_use.
- The types involved
yuck.config.widget_definition.WidgetDefinition→yuck.config.widget_use.WidgetUse
- Direction
- yuck.config.widget_definition uses yuck.config.widget_use, so a change to yuck.config.widget_use can break yuck.config.widget_definition, while a change to yuck.config.widget_definition can't break yuck.config.widget_use.
- Position
- Below the diagonal: yuck.config.widget_definition uses a module listed above it, which is the healthy direction.
32→3 yuck.config.window_definition uses eww_shared_util.span✕
- Connections
- 1 pair of types, where a type in yuck.config.window_definition uses a type in eww_shared_util.span.
- The types involved
yuck.config.window_definition.WindowDefinition→eww_shared_util.span.Span
- Direction
- yuck.config.window_definition uses eww_shared_util.span, so a change to eww_shared_util.span can break yuck.config.window_definition, while a change to yuck.config.window_definition can't break eww_shared_util.span.
- Position
- Below the diagonal: yuck.config.window_definition uses a module listed above it, which is the healthy direction.
32→12 yuck.config.window_definition uses yuck.config.attributes✕
- Connections
- 1 pair of types, where a type in yuck.config.window_definition uses a type in yuck.config.attributes.
- The types involved
yuck.config.window_definition.WindowDefinition→yuck.config.attributes.AttrSpec
- Direction
- yuck.config.window_definition uses yuck.config.attributes, so a change to yuck.config.attributes can break yuck.config.window_definition, while a change to yuck.config.window_definition can't break yuck.config.attributes.
- Position
- Below the diagonal: yuck.config.window_definition uses a module listed above it, which is the healthy direction.
32→13 yuck.config.window_definition uses yuck.config.backend_window_options✕
- Connections
- 1 pair of types, where a type in yuck.config.window_definition uses a type in yuck.config.backend_window_options.
- The types involved
yuck.config.window_definition.WindowDefinition→yuck.config.backend_window_options.BackendWindowOptionsDef
- Direction
- yuck.config.window_definition uses yuck.config.backend_window_options, so a change to yuck.config.backend_window_options can break yuck.config.window_definition, while a change to yuck.config.window_definition can't break yuck.config.backend_window_options.
- Position
- Below the diagonal: yuck.config.window_definition uses a module listed above it, which is the healthy direction.
32→18 yuck.config.window_definition uses yuck.parser.ast_iterator✕
- Connections
- 1 pair of types, where a type in yuck.config.window_definition uses a type in yuck.parser.ast_iterator.
- The types involved
yuck.config.window_definition.WindowDefinition→yuck.parser.ast_iterator.AstIterator
- Direction
- yuck.config.window_definition uses yuck.parser.ast_iterator, so a change to yuck.parser.ast_iterator can break yuck.config.window_definition, while a change to yuck.config.window_definition can't break yuck.parser.ast_iterator.
- Position
- Below the diagonal: yuck.config.window_definition uses a module listed above it, which is the healthy direction.
32→19 yuck.config.window_definition uses yuck.parser.from_ast✕
- Connections
- 1 pair of types, where a type in yuck.config.window_definition uses a type in yuck.parser.from_ast.
- The types involved
yuck.config.window_definition.WindowDefinition→yuck.parser.from_ast.FromAstElementContent
- Direction
- yuck.config.window_definition uses yuck.parser.from_ast, so a change to yuck.parser.from_ast can break yuck.config.window_definition, while a change to yuck.config.window_definition can't break yuck.parser.from_ast.
- Position
- Below the diagonal: yuck.config.window_definition uses a module listed above it, which is the healthy direction.
32→22 yuck.config.window_definition uses simplexpr.ast✕
- Connections
- 1 pair of types, where a type in yuck.config.window_definition uses a type in simplexpr.ast.
- The types involved
yuck.config.window_definition.WindowDefinition→simplexpr.ast.SimplExpr
- Direction
- yuck.config.window_definition uses simplexpr.ast, so a change to simplexpr.ast can break yuck.config.window_definition, while a change to yuck.config.window_definition can't break simplexpr.ast.
- Position
- Below the diagonal: yuck.config.window_definition uses a module listed above it, which is the healthy direction.
32→26 yuck.config.window_definition uses yuck.config.widget_use✕
- Connections
- 1 pair of types, where a type in yuck.config.window_definition uses a type in yuck.config.widget_use.
- The types involved
yuck.config.window_definition.WindowDefinition→yuck.config.widget_use.WidgetUse
- Direction
- yuck.config.window_definition uses yuck.config.widget_use, so a change to yuck.config.widget_use can break yuck.config.window_definition, while a change to yuck.config.window_definition can't break yuck.config.widget_use.
- Position
- Below the diagonal: yuck.config.window_definition uses a module listed above it, which is the healthy direction.
32→27 yuck.config.window_definition uses yuck.config.window_geometry✕
- Connections
- 1 pair of types, where a type in yuck.config.window_definition uses a type in yuck.config.window_geometry.
- The types involved
yuck.config.window_definition.WindowDefinition→yuck.config.window_geometry.WindowGeometryDef
- Direction
- yuck.config.window_definition uses yuck.config.window_geometry, so a change to yuck.config.window_geometry can break yuck.config.window_definition, while a change to yuck.config.window_definition can't break yuck.config.window_geometry.
- Position
- Below the diagonal: yuck.config.window_definition uses a module listed above it, which is the healthy direction.
33→26 eww.widgets.build_widget uses yuck.config.widget_use✕
- Connections
- 6 pairs of types, where a type in eww.widgets.build_widget uses a type in yuck.config.widget_use.
- The types involved
eww.widgets.build_widget.BuilderArgs→yuck.config.widget_use.BasicWidgetUseeww.widgets.build_widget.CustomWidgetInvocation→yuck.config.widget_use.WidgetUseeww.widgets.build_widget.build_widget$module→yuck.config.widget_use.BasicWidgetUseeww.widgets.build_widget.build_widget$module→yuck.config.widget_use.ChildrenWidgetUseeww.widgets.build_widget.build_widget$module→yuck.config.widget_use.LoopWidgetUseeww.widgets.build_widget.build_widget$module→yuck.config.widget_use.WidgetUse
- Direction
- eww.widgets.build_widget uses yuck.config.widget_use, so a change to yuck.config.widget_use can break eww.widgets.build_widget, while a change to eww.widgets.build_widget can't break yuck.config.widget_use.
- Position
- Below the diagonal: eww.widgets.build_widget uses a module listed above it, which is the healthy direction.
33→30 eww.widgets.build_widget uses eww.state.scope_graph✕
- Connections
- 5 pairs of types, where a type in eww.widgets.build_widget uses a type in eww.state.scope_graph.
- The types involved
eww.widgets.build_widget.BuilderArgs→eww.state.scope_graph.ScopeGrapheww.widgets.build_widget.BuilderArgs→eww.state.scope_graph.ScopeIndexeww.widgets.build_widget.CustomWidgetInvocation→eww.state.scope_graph.ScopeIndexeww.widgets.build_widget.build_widget$module→eww.state.scope_graph.ScopeGrapheww.widgets.build_widget.build_widget$module→eww.state.scope_graph.ScopeIndex
- Direction
- eww.widgets.build_widget uses eww.state.scope_graph, so a change to eww.state.scope_graph can break eww.widgets.build_widget, while a change to eww.widgets.build_widget can't break eww.state.scope_graph.
- Position
- Below the diagonal: eww.widgets.build_widget uses a module listed above it, which is the healthy direction.
34→9 eww.window_arguments uses yuck.config.monitor✕
- Connections
- 1 pair of types, where a type in eww.window_arguments uses a type in yuck.config.monitor.
- The types involved
eww.window_arguments.WindowArguments→yuck.config.monitor.MonitorIdentifier
- Direction
- eww.window_arguments uses yuck.config.monitor, so a change to yuck.config.monitor can break eww.window_arguments, while a change to eww.window_arguments can't break yuck.config.monitor.
- Position
- Below the diagonal: eww.window_arguments uses a module listed above it, which is the healthy direction.
34→27 eww.window_arguments uses yuck.config.window_geometry✕
- Connections
- 1 pair of types, where a type in eww.window_arguments uses a type in yuck.config.window_geometry.
- The types involved
eww.window_arguments.WindowArguments→yuck.config.window_geometry.AnchorPoint
- Direction
- eww.window_arguments uses yuck.config.window_geometry, so a change to yuck.config.window_geometry can break eww.window_arguments, while a change to eww.window_arguments can't break yuck.config.window_geometry.
- Position
- Below the diagonal: eww.window_arguments uses a module listed above it, which is the healthy direction.
34→32 eww.window_arguments uses yuck.config.window_definition✕
- Connections
- 1 pair of types, where a type in eww.window_arguments uses a type in yuck.config.window_definition.
- The types involved
eww.window_arguments.WindowArguments→yuck.config.window_definition.WindowDefinition
- Direction
- eww.window_arguments uses yuck.config.window_definition, so a change to yuck.config.window_definition can break eww.window_arguments, while a change to eww.window_arguments can't break yuck.config.window_definition.
- Position
- Below the diagonal: eww.window_arguments uses a module listed above it, which is the healthy direction.
35→3 yuck.config.validate uses eww_shared_util.span✕
- Connections
- 2 pairs of types, where a type in yuck.config.validate uses a type in eww_shared_util.span.
- The types involved
yuck.config.validate.ValidationError→eww_shared_util.span.Spanyuck.config.validate.ValidationError→eww_shared_util.span.Spanned
- Direction
- yuck.config.validate uses eww_shared_util.span, so a change to eww_shared_util.span can break yuck.config.validate, while a change to yuck.config.validate can't break eww_shared_util.span.
- Position
- Below the diagonal: yuck.config.validate uses a module listed above it, which is the healthy direction.
35→4 yuck.config.validate uses eww_shared_util.wrappers✕
- Connections
- 1 pair of types, where a type in yuck.config.validate uses a type in eww_shared_util.wrappers.
- The types involved
yuck.config.validate.validate$module→eww_shared_util.wrappers.VarName
- Direction
- yuck.config.validate uses eww_shared_util.wrappers, so a change to eww_shared_util.wrappers can break yuck.config.validate, while a change to yuck.config.validate can't break eww_shared_util.wrappers.
- Position
- Below the diagonal: yuck.config.validate uses a module listed above it, which is the healthy direction.
35→10 yuck.config.validate uses yuck.format_diagnostic✕
- Connections
- 1 pair of types, where a type in yuck.config.validate uses a type in yuck.format_diagnostic.
- The types involved
yuck.config.validate.ValidationError→yuck.format_diagnostic.ToDiagnostic
- Direction
- yuck.config.validate uses yuck.format_diagnostic, so a change to yuck.format_diagnostic can break yuck.config.validate, while a change to yuck.config.validate can't break yuck.format_diagnostic.
- Position
- Below the diagonal: yuck.config.validate uses a module listed above it, which is the healthy direction.
35→23 yuck.config.validate uses yuck.config.toplevel✕
- Connections
- 1 pair of types, where a type in yuck.config.validate uses a type in yuck.config.toplevel.
- The types involved
yuck.config.validate.validate$module→yuck.config.toplevel.Config
- Direction
- yuck.config.validate uses yuck.config.toplevel, so a change to yuck.config.toplevel can break yuck.config.validate, while a change to yuck.config.validate can't break yuck.config.toplevel.
- Position
- Below the diagonal: yuck.config.validate uses a module listed above it, which is the healthy direction.
35→26 yuck.config.validate uses yuck.config.widget_use✕
- Connections
- 1 pair of types, where a type in yuck.config.validate uses a type in yuck.config.widget_use.
- The types involved
yuck.config.validate.validate$module→yuck.config.widget_use.WidgetUse
- Direction
- yuck.config.validate uses yuck.config.widget_use, so a change to yuck.config.widget_use can break yuck.config.validate, while a change to yuck.config.validate can't break yuck.config.widget_use.
- Position
- Below the diagonal: yuck.config.validate uses a module listed above it, which is the healthy direction.
35→31 yuck.config.validate uses yuck.config.widget_definition✕
- Connections
- 1 pair of types, where a type in yuck.config.validate uses a type in yuck.config.widget_definition.
- The types involved
yuck.config.validate.validate$module→yuck.config.widget_definition.WidgetDefinition
- Direction
- yuck.config.validate uses yuck.config.widget_definition, so a change to yuck.config.widget_definition can break yuck.config.validate, while a change to yuck.config.validate can't break yuck.config.widget_definition.
- Position
- Below the diagonal: yuck.config.validate uses a module listed above it, which is the healthy direction.
36→9 eww.window_initiator uses yuck.config.monitor✕
- Connections
- 1 pair of types, where a type in eww.window_initiator uses a type in yuck.config.monitor.
- The types involved
eww.window_initiator.WindowInitiator→yuck.config.monitor.MonitorIdentifier
- Direction
- eww.window_initiator uses yuck.config.monitor, so a change to yuck.config.monitor can break eww.window_initiator, while a change to eww.window_initiator can't break yuck.config.monitor.
- Position
- Below the diagonal: eww.window_initiator uses a module listed above it, which is the healthy direction.
36→13 eww.window_initiator uses yuck.config.backend_window_options✕
- Connections
- 1 pair of types, where a type in eww.window_initiator uses a type in yuck.config.backend_window_options.
- The types involved
eww.window_initiator.WindowInitiator→yuck.config.backend_window_options.BackendWindowOptions
- Direction
- eww.window_initiator uses yuck.config.backend_window_options, so a change to yuck.config.backend_window_options can break eww.window_initiator, while a change to eww.window_initiator can't break yuck.config.backend_window_options.
- Position
- Below the diagonal: eww.window_initiator uses a module listed above it, which is the healthy direction.
36→27 eww.window_initiator uses yuck.config.window_geometry✕
- Connections
- 1 pair of types, where a type in eww.window_initiator uses a type in yuck.config.window_geometry.
- The types involved
eww.window_initiator.WindowInitiator→yuck.config.window_geometry.WindowGeometry
- Direction
- eww.window_initiator uses yuck.config.window_geometry, so a change to yuck.config.window_geometry can break eww.window_initiator, while a change to eww.window_initiator can't break yuck.config.window_geometry.
- Position
- Below the diagonal: eww.window_initiator uses a module listed above it, which is the healthy direction.
36→32 eww.window_initiator uses yuck.config.window_definition✕
- Connections
- 2 pairs of types, where a type in eww.window_initiator uses a type in yuck.config.window_definition.
- The types involved
eww.window_initiator.WindowInitiator→yuck.config.window_definition.WindowDefinitioneww.window_initiator.WindowInitiator→yuck.config.window_definition.WindowStacking
- Direction
- eww.window_initiator uses yuck.config.window_definition, so a change to yuck.config.window_definition can break eww.window_initiator, while a change to eww.window_initiator can't break yuck.config.window_definition.
- Position
- Below the diagonal: eww.window_initiator uses a module listed above it, which is the healthy direction.
36→34 eww.window_initiator uses eww.window_arguments✕
- Connections
- 1 pair of types, where a type in eww.window_initiator uses a type in eww.window_arguments.
- The types involved
eww.window_initiator.WindowInitiator→eww.window_arguments.WindowArguments
- Direction
- eww.window_initiator uses eww.window_arguments, so a change to eww.window_arguments can break eww.window_initiator, while a change to eww.window_initiator can't break eww.window_arguments.
- Position
- Below the diagonal: eww.window_initiator uses a module listed above it, which is the healthy direction.
37→1 eww.app uses eww.paths✕
- Connections
- 1 pair of types, where a type in eww.app uses a type in eww.paths.
- The types involved
eww.app.App→eww.paths.EwwPaths
- Direction
- eww.app uses eww.paths, so a change to eww.paths can break eww.app, while a change to eww.app can't break eww.paths.
- Position
- Below the diagonal: eww.app uses a module listed above it, which is the healthy direction.
37→2 eww.app uses eww.widgets.window✕
- Connections
- 2 pairs of types, where a type in eww.app uses a type in eww.widgets.window.
- The types involved
eww.app.EwwWindow→eww.widgets.window.Windoweww.app.app$module→eww.widgets.window.Window
- Direction
- eww.app uses eww.widgets.window, so a change to eww.widgets.window can break eww.app, while a change to eww.app can't break eww.widgets.window.
- Position
- Below the diagonal: eww.app uses a module listed above it, which is the healthy direction.
37→4 eww.app uses eww_shared_util.wrappers✕
- Connections
- 1 pair of types, where a type in eww.app uses a type in eww_shared_util.wrappers.
- The types involved
eww.app.App→eww_shared_util.wrappers.VarName
- Direction
- eww.app uses eww_shared_util.wrappers, so a change to eww_shared_util.wrappers can break eww.app, while a change to eww.app can't break eww_shared_util.wrappers.
- Position
- Below the diagonal: eww.app uses a module listed above it, which is the healthy direction.
37→6 eww.app uses eww.config.eww_config✕
- Connections
- 1 pair of types, where a type in eww.app uses a type in eww.config.eww_config.
- The types involved
eww.app.App→eww.config.eww_config.EwwConfig
- Direction
- eww.app uses eww.config.eww_config, so a change to eww.config.eww_config can break eww.app, while a change to eww.app can't break eww.config.eww_config.
- Position
- Below the diagonal: eww.app uses a module listed above it, which is the healthy direction.
37→9 eww.app uses yuck.config.monitor✕
- Connections
- 1 pair of types, where a type in eww.app uses a type in yuck.config.monitor.
- The types involved
eww.app.app$module→yuck.config.monitor.MonitorIdentifier
- Direction
- eww.app uses yuck.config.monitor, so a change to yuck.config.monitor can break eww.app, while a change to eww.app can't break yuck.config.monitor.
- Position
- Below the diagonal: eww.app uses a module listed above it, which is the healthy direction.
37→11 eww.app uses simplexpr.dynval✕
- Connections
- 1 pair of types, where a type in eww.app uses a type in simplexpr.dynval.
- The types involved
eww.app.App→simplexpr.dynval.DynVal
- Direction
- eww.app uses simplexpr.dynval, so a change to simplexpr.dynval can break eww.app, while a change to eww.app can't break simplexpr.dynval.
- Position
- Below the diagonal: eww.app uses a module listed above it, which is the healthy direction.
37→27 eww.app uses yuck.config.window_geometry✕
- Connections
- 1 pair of types, where a type in eww.app uses a type in yuck.config.window_geometry.
- The types involved
eww.app.app$module→yuck.config.window_geometry.WindowGeometry
- Direction
- eww.app uses yuck.config.window_geometry, so a change to yuck.config.window_geometry can break eww.app, while a change to eww.app can't break yuck.config.window_geometry.
- Position
- Below the diagonal: eww.app uses a module listed above it, which is the healthy direction.
37→29 eww.app uses eww.script_var_handler✕
- Connections
- 1 pair of types, where a type in eww.app uses a type in eww.script_var_handler.
- The types involved
eww.app.App→eww.script_var_handler.ScriptVarHandlerHandle
- Direction
- eww.app uses eww.script_var_handler, so a change to eww.script_var_handler can break eww.app, while a change to eww.app can't break eww.script_var_handler.
- Position
- Below the diagonal: eww.app uses a module listed above it, which is the healthy direction.
37→30 eww.app uses eww.state.scope_graph✕
- Connections
- 3 pairs of types, where a type in eww.app uses a type in eww.state.scope_graph.
- The types involved
eww.app.App→eww.state.scope_graph.ScopeGrapheww.app.EwwWindow→eww.state.scope_graph.ScopeIndexeww.app.app$module→eww.state.scope_graph.ScopeIndex
- Direction
- eww.app uses eww.state.scope_graph, so a change to eww.state.scope_graph can break eww.app, while a change to eww.app can't break eww.state.scope_graph.
- Position
- Below the diagonal: eww.app uses a module listed above it, which is the healthy direction.
37→34 eww.app uses eww.window_arguments✕
- Connections
- 1 pair of types, where a type in eww.app uses a type in eww.window_arguments.
- The types involved
eww.app.App→eww.window_arguments.WindowArguments
- Direction
- eww.app uses eww.window_arguments, so a change to eww.window_arguments can break eww.app, while a change to eww.app can't break eww.window_arguments.
- Position
- Below the diagonal: eww.app uses a module listed above it, which is the healthy direction.
37→36 eww.app uses eww.window_initiator✕
- Connections
- 1 pair of types, where a type in eww.app uses a type in eww.window_initiator.
- The types involved
eww.app.app$module→eww.window_initiator.WindowInitiator
- Direction
- eww.app uses eww.window_initiator, so a change to eww.window_initiator can break eww.app, while a change to eww.app can't break eww.window_initiator.
- Position
- Below the diagonal: eww.app uses a module listed above it, which is the healthy direction.
38→2 eww.display_backend uses eww.widgets.window✕
- Connections
- 2 pairs of types, where a type in eww.display_backend uses a type in eww.widgets.window.
- The types involved
eww.display_backend.DisplayBackend→eww.widgets.window.Windoweww.display_backend.NoBackend→eww.widgets.window.Window
- Direction
- eww.display_backend uses eww.widgets.window, so a change to eww.widgets.window can break eww.display_backend, while a change to eww.display_backend can't break eww.widgets.window.
- Position
- Below the diagonal: eww.display_backend uses a module listed above it, which is the healthy direction.
38→36 eww.display_backend uses eww.window_initiator✕
- Connections
- 2 pairs of types, where a type in eww.display_backend uses a type in eww.window_initiator.
- The types involved
eww.display_backend.DisplayBackend→eww.window_initiator.WindowInitiatoreww.display_backend.NoBackend→eww.window_initiator.WindowInitiator
- Direction
- eww.display_backend uses eww.window_initiator, so a change to eww.window_initiator can break eww.display_backend, while a change to eww.display_backend can't break eww.window_initiator.
- Position
- Below the diagonal: eww.display_backend uses a module listed above it, which is the healthy direction.
39→2 eww.display_backend.platform_wayland uses eww.widgets.window✕
- Connections
- 1 pair of types, where a type in eww.display_backend.platform_wayland uses a type in eww.widgets.window.
- The types involved
eww.display_backend.platform_wayland.WaylandBackend→eww.widgets.window.Window
- Direction
- eww.display_backend.platform_wayland uses eww.widgets.window, so a change to eww.widgets.window can break eww.display_backend.platform_wayland, while a change to eww.display_backend.platform_wayland can't break eww.widgets.window.
- Position
- Below the diagonal: eww.display_backend.platform_wayland uses a module listed above it, which is the healthy direction.
39→36 eww.display_backend.platform_wayland uses eww.window_initiator✕
- Connections
- 1 pair of types, where a type in eww.display_backend.platform_wayland uses a type in eww.window_initiator.
- The types involved
eww.display_backend.platform_wayland.WaylandBackend→eww.window_initiator.WindowInitiator
- Direction
- eww.display_backend.platform_wayland uses eww.window_initiator, so a change to eww.window_initiator can break eww.display_backend.platform_wayland, while a change to eww.display_backend.platform_wayland can't break eww.window_initiator.
- Position
- Below the diagonal: eww.display_backend.platform_wayland uses a module listed above it, which is the healthy direction.
39→38 eww.display_backend.platform_wayland uses eww.display_backend✕
- Connections
- 1 pair of types, where a type in eww.display_backend.platform_wayland uses a type in eww.display_backend.
- The types involved
eww.display_backend.platform_wayland.WaylandBackend→eww.display_backend.DisplayBackend
- Direction
- eww.display_backend.platform_wayland uses eww.display_backend, so a change to eww.display_backend can break eww.display_backend.platform_wayland, while a change to eww.display_backend.platform_wayland can't break eww.display_backend.
- Position
- Below the diagonal: eww.display_backend.platform_wayland uses a module listed above it, which is the healthy direction.
40→2 eww.display_backend.platform_x11 uses eww.widgets.window✕
- Connections
- 3 pairs of types, where a type in eww.display_backend.platform_x11 uses a type in eww.widgets.window.
- The types involved
eww.display_backend.platform_x11.X11Backend→eww.widgets.window.Windoweww.display_backend.platform_x11.X11BackendConnection→eww.widgets.window.Windoweww.display_backend.platform_x11.platform_x11$module→eww.widgets.window.Window
- Direction
- eww.display_backend.platform_x11 uses eww.widgets.window, so a change to eww.widgets.window can break eww.display_backend.platform_x11, while a change to eww.display_backend.platform_x11 can't break eww.widgets.window.
- Position
- Below the diagonal: eww.display_backend.platform_x11 uses a module listed above it, which is the healthy direction.
40→36 eww.display_backend.platform_x11 uses eww.window_initiator✕
- Connections
- 3 pairs of types, where a type in eww.display_backend.platform_x11 uses a type in eww.window_initiator.
- The types involved
eww.display_backend.platform_x11.X11Backend→eww.window_initiator.WindowInitiatoreww.display_backend.platform_x11.X11BackendConnection→eww.window_initiator.WindowInitiatoreww.display_backend.platform_x11.platform_x11$module→eww.window_initiator.WindowInitiator
- Direction
- eww.display_backend.platform_x11 uses eww.window_initiator, so a change to eww.window_initiator can break eww.display_backend.platform_x11, while a change to eww.display_backend.platform_x11 can't break eww.window_initiator.
- Position
- Below the diagonal: eww.display_backend.platform_x11 uses a module listed above it, which is the healthy direction.
40→38 eww.display_backend.platform_x11 uses eww.display_backend✕
- Connections
- 1 pair of types, where a type in eww.display_backend.platform_x11 uses a type in eww.display_backend.
- The types involved
eww.display_backend.platform_x11.X11Backend→eww.display_backend.DisplayBackend
- Direction
- eww.display_backend.platform_x11 uses eww.display_backend, so a change to eww.display_backend can break eww.display_backend.platform_x11, while a change to eww.display_backend.platform_x11 can't break eww.display_backend.
- Position
- Below the diagonal: eww.display_backend.platform_x11 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 |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 20 | Medium |
| A05:2025 — Injection | 9 | High / Critical |
Roadmap
First, ensure all custom controls are fully keyboard-operable and anchors have valid hrefs to improve accessibility. Next, address the single documentation gap by updating the README and creating an Architecture Decision Record to capture key design choices. Finally, enforce visual safety by maintaining visible focus styles, respecting reduced motion preferences, and correcting low-contrast colors.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. | +5.4 pts | Low | Documentation Quality |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +5.4 pts | Low | ADR Quality |
| Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href. | +6.1 pts | Medium | Keyboard semantics |
| 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. | +5.3 pts | Medium | Visual & motion safety |
| 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. | +4.8 pts | Medium | Architecture documentation |
| Resolve the 4 Banned license finding(s) in License Compliance. | +2.2 pts | Low | License Compliance |
| 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 build/run (quick start) section to the root README — the first thing a newcomer needs. | +2.3 pts | Medium | Documentation (README) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.5 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Dependency Vulnerabilities: Medium CVE: REDACTED |
| crates/eww/src/app.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| crates/eww/src/display_backend.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| crates/eww/src/state/scope_graph.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| crates/eww/src/widgets/widget_definitions.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| crates/eww/src/widgets/circular_progressbar.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| crates/notifier_host/src/host.rs | 6.7 | Mixed | Explicit Debt: TodoComment |
| crates/yuck/src/format_diagnostic.rs | 6.7 | Mixed | Explicit Debt: TodoComment |
| crates/notifier_host/src/watcher.rs | 6.7 | Mixed | Explicit Debt: TodoComment |
| crates/simplexpr/src/eval.rs | 7.0 | Near-clean | Cyclomatic Complexity: simplexpr::eval::call_expr_function (cyclomatic 67) |
| crates/yuck/src/parser/ast.rs | 7.3 | Near-clean | Explicit Debt: TodoComment |
| crates/yuck/src/config/attributes.rs | 7.3 | Near-clean | Explicit Debt: TodoComment |
| crates/notifier_host/src/item.rs | 7.3 | Near-clean | Explicit Debt: TodoComment |
| crates/eww/src/widgets/build_widget.rs | 7.3 | Near-clean | Explicit Debt: TodoComment |
| crates/eww/src/widgets/systray.rs | 7.3 | Near-clean | Explicit Debt: TodoComment |
| crates/eww/src/main.rs | 7.8 | Near-clean | Cyclomatic Complexity: eww::run (cyclomatic 23) |
| crates/simplexpr/src/parser/lexer.rs | 7.8 | Near-clean | Cognitive Complexity: Lexer::string_lit (cognitive 29) |
| gen-docs.ts | 7.8 | Near-clean | Cognitive Complexity: gen-docs.parseDocs (cognitive 22) |
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. 63 of 63 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.8 — 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 — 63 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, 122 of 154 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 (.rs) 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 (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) 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 (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) 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.
- D11 Test Reliability — 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. Test source is present (.rs) and this repository declares a Cargo test suite (repository root, 11 test files), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D19 Documentation Quality — 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. 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.
- GD1 Unfinished & placeholder code — 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 reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Rust is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — 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 reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Rust is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- 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.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- 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").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- 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.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- 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.
- AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
- AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
- 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.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- 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
6 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was simplexpr::eval::call_expr_function at 67. 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 eww::widgets::widget_definitions::widget_use_to_gtk_widget at 26 — they are counted neither in the figure above nor in this dimension's score. 2 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: crates/eww/src/widgets/widget_definitions.rs (eww::widgets::widget_definitions::widget_use_to_gtk_widget at 26), crates/eww/src/opts.rs (ActionWithServer::into_daemon_command at 16). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 2 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with simplexpr::eval::call_expr_function (cyclomatic 67), SimplExpr::eval (cyclomatic 38). — 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 2 together lifts Cyclomatic Complexity from 8.0 to about 8.8/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
15 method(s) exceeded the cognitive complexity threshold of 15; the worst was simplexpr::eval::call_expr_function at 70.
What to do
- Bring the 1 body over 30 down to 30 or less in Cognitive Complexity — start with simplexpr::eval::call_expr_function (cognitive 70). — Refactoring it lifts Cognitive Complexity from 7.2 to about 8.1/10.
- 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
5 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 3 FileTooLong finding(s) in God Classes — start with widget_definitions.rs, highlight.js, app.rs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 FunctionTooLong finding(s) in God Classes — start with eval.rs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 MethodTooLong finding(s) in God Classes — start with app.rs. — 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
14 duplicated block group(s) detected. One further row reports members as variants of one another; it aggregates block groups already counted above and is not itself counted.
What to do
- Resolve the 3 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with eval.rs (2), widget_definitions.rs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with circular_progressbar.rs, watcher.rs, widget_definitions.rs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 Members sharing a duplicated core (4 members, 50+ identical tokens) finding(s) in Code Duplication — start with widget_definitions.rs. — 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
5 production modules (Cargo), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 1 module(s) off the main sequence.
D6 · Cohesion (LCOM4)
1 of 38 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with window_definition.rs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
20 test methods: 20 unit, 0 integration, 0 BDD, 0 e2e. The Rust suite contributes 20 `#[test]` function(s) across 11 file(s) declaring at least one; its unit/integration split is Cargo's own — 0 of those file(s) are integration-test targets under a crate's tests/ directory, and the rest are #[test] functions compiled into the crate they test.
D12 · Dependency Hygiene
18 outdated, 0 yanked direct Cargo dependencies. Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from REDACTED there.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
4 of 361 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's REDACTED closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository.
What to do
- Resolve the 4 Banned license finding(s) in License Compliance. — One of this dimension's main actionable groups (4 issue-level).
- Enforce License Compliance in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
1 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is crates/yuck/src/config/window_definition.rs. Counted over 50 of the 84 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
29 deducted task-comment markers across 12033 LoC (0.2/KLoC) → score 9.6. 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 29 TodoComment finding(s) in Explicit Debt — start with widget_definitions.rs (5), ast.rs (2), attributes.rs (2). — One of this dimension's main actionable groups (29 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.
D19 · Documentation Quality
0 of 1 documentation facets pass in full; short on: F2 example. 11 document(s) read across 1 unit(s).
What to do
- Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 recommendation-level).
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
0 of 6 build units (Cargo) flagged as possibly oversized/incoherent.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
9 finding(s): 0 critical, 9 high, 0 medium, 0 low. 8 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.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 8 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 (8 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
20 finding(s): 0 critical, 0 high, 20 medium, 0 low.
What to do
- Resolve the 9 Medium advisory (unmaintained) finding(s) in Dependency Vulnerabilities — start with REDACTED (9). — One of this dimension's main actionable groups (9 warning-level).
- Resolve the 6 Medium advisory (unsound) finding(s) in Dependency Vulnerabilities — start with REDACTED (6). — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 3 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 warning-level).
D34 · Knowledge Freshness
10 of 50 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is crates/notifier_host/src/watcher.rs. Counted over 50 of the 84 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 10 Orphaned file finding(s) in Knowledge Freshness — start with watcher.rs, graph.rs, systray.rs. — One of this dimension's main actionable groups (10 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
1 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 0 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.
What to do
- Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with rust-toolchain.toml. — One of this dimension's main actionable groups (1 warning-level).
Frontend & cross-cutting dimensions
AC2 · Forms & labels
AC3 · Page structure
AC4 · Keyboard semantics
- The repo's own CSS styles .menu-title with `cursor: pointer`, so this <h1> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler. — docs/theme/index.hbs:138
What to do
- Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC5 · ARIA correctness
AC6 · Visual & motion safety
- `.page` 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. — docs/theme/css/general.css:69
- `.js:not(.sidebar-resizing) .sidebar` moves (`transition: transform 0.3s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — docs/theme/css/chrome.css:333
- `.chapter li > a.toggle div` moves (`transition: transform 0.5s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — docs/theme/css/chrome.css:418
- `.js:not(.sidebar-resizing) .page-wrapper` moves (`transition: margin-left 0.3s ease, transform 0.3s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — docs/theme/css/general.css:77
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 3 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.
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.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX9 · CQS / query purity
M1 · Documentation (README)
What to do
- 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.
- Add a README to the 4 of 5 project(s) that lack one — worth up to 1.6 pts.
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.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
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.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
P1 · CI/CD gates
P10 · Library API & versioning
- 81/89 types (91%) 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 (Rust: `pub(crate)`, or keep the module private) so internals can change without breaking consumers.
P2 · Observability
P3 · Security & performance tooling
What to do
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
PF3 · Async & latency hygiene
S1 · Web-Security Posture
- `https://cdnjs.cloudflare.com/ajax/libs/mathjax/2.7.1/MathJax.js?config=TeX-AMS-MML_HTMLorMML` 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. — docs/theme/index.hbs:54
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
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
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
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
- This repository commits no tsconfig, so whatever type-checks it uses tsc's own defaults, in which `strict` and `strictNullChecks` are OFF: `string` admits `null` and `undefined`, and a value that is null is compiled through to the property access that throws. If the build passes `--strict` on a command line instead, put it in a committed tsconfig — this check reads configuration, and configuration is all it can read.
What to do
- The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
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 |
| AC4 · Keyboard semantics | 2.1.1, 2.4.3 | Partial signal |
| AC5 · ARIA correctness | 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 | 69% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 95% | Exemplary | Solid. |
| Maturity | 52% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 64% | Adequate — gated by D14 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 81% | Strong | Solid. |
| Accessibility | 44% | Weak — gated by AC4, AC6 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 2 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 2 observation(s) recorded · The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- X10 Duplicated predicate — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 control(s) we could not find positive evidence for
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 52 check(s) not relevant to this codebase
- AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
- AX1 Captive dependencies — Not applicable: Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one; this repository's TypeScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — Not applicable: Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- 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
- AX6 Interface segregation — no exported interface declares behaviour
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — 3 markup documents under demonstration, documentation or developer-tool trees (or modules the build marks non-production) but none in the product; no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — those pages are demos or docs for the code, not something this tier can boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no data at rest for these controls to protect.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository starts no server another machine can reach (no actix-web HttpServer, axum::serve, Rocket launch, warp::serve, poem or salvo Server, tonic Server::builder, hyper or tiny_http server outside examples and tests, none bound beyond loopback). Access control is therefore N/A here — a crate is authorized by the application that serves it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source 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, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source 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, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~24 lines of test source are present (.rs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — the .rs suite was found but not re-run
- 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.
- D21 Naming Consistency — Naming consistency is measured on C# only; JavaScript, Rust, TypeScript not measured.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust 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 .rs, .ts, 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 (.rs), 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.
- 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) — 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.
- 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.
- 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 — not scored — this repository shows only 1 of the 3 signals this lens looks for (7 value object(s))
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
- 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
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model 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
- M4 Documentation accuracy — Not applicable: the 11 current-state document(s) make no claim of a kind M4 checks. 24 claim(s) of kinds M4 does not check were not checked (environment variable 2, setting 21, cd 1); M4 checks only links and versions.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript, Rust source, so there is no service whose uptime a failing dependency could take down
- 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 (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) 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
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `#[bench]`, criterion's `bench_function`/`bench_with_input`, `#[divan::bench]` or `#[library_benchmark]` in any `.rs` file, or criterion, divan, iai or a `[[bench]]` target in a Cargo.toml, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not applicable: Rust spells out every heap allocation and makes borrowed slices (&[T], &str) its ordinary parameter types, so the allocation-aware style this card rewards elsewhere is the language's baseline rather than a rung to climb. TypeScript/JavaScript runs on a garbage-collected runtime that gives a program no allocation-control idiom to choose on a hot path — no pools, stack allocation or value types — so allocation awareness is not something this code can be rated on.
- X2 Cancellation propagation — no C# was loaded; this repository's Rust was read, and no request in it can be cancelled by a caller — a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. Rust's compiler refuses the unsynchronised version: a collection shared between a callback's thread and the waiting body must be `Sync`, which a `Vec`, `VecDeque` or `HashMap` is only behind a `Mutex`/`RwLock`, so the race this check looks for cannot be written in safe Rust. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
- 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.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Rust was read, and it logs through none: the `log` crate's macros take one finished message (as log4net does in C#; its `kv` values are an opt-in its backends mostly drop), `println!`/`eprintln!` are not loggers, or it makes no log call outside its tests and examples at all. Calls through `tracing` (`tracing::info!`, or `info!` imported from it) would be judged.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — 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 — 14 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Banned license: dbusmenu-gtk3
- Banned license: dbusmenu-glib
- Banned license: dbusmenu-gtk3-sys
- Banned license: dbusmenu-glib-sys
- Clickable element isn't keyboard-operable docs/theme/index.hbs:138
- REDACTED
Serious — 100 finding(s)
- TodoComment crates/yuck/src/format_diagnostic.rs:197
- TodoComment crates/yuck/src/parser/ast.rs:16
- TodoComment crates/yuck/src/parser/ast.rs:89
- TodoComment crates/yuck/src/parser/ast_iterator.rs:45
- TodoComment crates/yuck/src/config/attributes.rs:45
- TodoComment crates/yuck/src/config/attributes.rs:107
- TodoComment crates/yuck/src/config/script_var_definition.rs:44
- TodoComment crates/simplexpr/src/dynval.rs:214
- TodoComment crates/notifier_host/src/host.rs:15
- TodoComment crates/notifier_host/src/item.rs:62
- TodoComment crates/notifier_host/src/item.rs:109
- TodoComment crates/notifier_host/src/watcher.rs:36
- TodoComment crates/eww/src/app.rs:469
- TodoComment crates/eww/src/display_backend.rs:249
- TodoComment crates/eww/src/widgets/build_widget.rs:43
- TodoComment crates/eww/src/widgets/build_widget.rs:144
- TodoComment crates/eww/src/widgets/circular_progressbar.rs:100
- TodoComment crates/eww/src/widgets/transform.rs:128
- TodoComment crates/eww/src/widgets/def_widget_macro.rs:50
- TodoComment crates/eww/src/widgets/systray.rs:17
- TodoComment crates/eww/src/widgets/systray.rs:181
- TodoComment crates/eww/src/widgets/widget_definitions.rs:58
- TodoComment crates/eww/src/widgets/widget_definitions.rs:59
- TodoComment crates/eww/src/widgets/widget_definitions.rs:174
- TodoComment crates/eww/src/widgets/widget_definitions.rs:1075
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Animation without a prefers-reduced-motion guard docs/theme/css/chrome.css:333
- Animation without a prefers-reduced-motion guard docs/theme/css/chrome.css:418
- Animation without a prefers-reduced-motion guard docs/theme/css/general.css:77
- eww::run (cognitive 22) crates/eww/src/main.rs:94
- eww::server::cleanup_log_dir (cognitive 17) crates/eww/src/server.rs:298
- eww::app::get_monitor_from_display (cognitive 16) crates/eww/src/app.rs:733
- FileTooLong: widgets/widget_definitions.rs crates/eww/src/widgets/widget_definitions.rs
- FileTooLong: theme/highlight.js docs/theme/highlight.js
- FileTooLong: src/app.rs crates/eww/src/app.rs
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (6 lines × 2) crates/eww/src/widgets/widget_definitions.rs:551
- Duplicated block (6 lines × 2) crates/simplexpr/src/eval.rs:452
- Duplicated block (6 lines × 2) crates/simplexpr/src/eval.rs:326
- Duplicated block (5 lines × 2) crates/eww/src/widgets/circular_progressbar.rs:123
- Duplicated block (5 lines × 2) crates/notifier_host/src/watcher.rs:61
- Duplicated block (5 lines × 2) crates/eww/src/widgets/widget_definitions.rs:696
- App::try_handle_command (cognitive 26) crates/eww/src/app.rs:178
- App::open_window (cognitive 18) crates/eww/src/app.rs:422
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Focus outline removed in CSS without a :focus replacement docs/theme/css/general.css:69
- Accessibility enforcement below the top rung
- simplexpr::eval::call_expr_function (cyclomatic 67) crates/simplexpr/src/eval.rs:319
- SimplExpr::eval (cyclomatic 38) crates/simplexpr/src/eval.rs:192
- App::try_handle_command (cyclomatic 29) crates/eww/src/app.rs:178
- eww::run (cyclomatic 23) crates/eww/src/main.rs:94
- WaylandBackend::initialize_window (cyclomatic 19) crates/eww/src/display_backend.rs:45
- notifier_host::icon::load_icon_from_sni (cyclomatic 19) crates/notifier_host/src/icon.rs:124
- simplexpr::eval::call_expr_function (cognitive 70) crates/simplexpr/src/eval.rs:319
- SimplExpr::eval (cognitive 29) crates/simplexpr/src/eval.rs:192
- Lexer::string_lit (cognitive 29) crates/simplexpr/src/parser/lexer.rs:213
- GraphPriv::draw (cognitive 25) crates/eww/src/widgets/graph.rs:201
- WaylandBackend::initialize_window (cognitive 22) crates/eww/src/display_backend.rs:45
- gen-docs.parseDocs (cognitive 22) gen-docs.ts:98
- ScopeGraphInternal::validate (cognitive 19) crates/eww/src/state/scope_graph.rs:510
- notifier_host::host::run_host (cognitive 18) crates/notifier_host/src/host.rs:67
- EvalError::to_diagnostic (cognitive 17) crates/yuck/src/format_diagnostic.rs:186
- gen-docs.parseMagicVariables (cognitive 16) gen-docs.ts:21
- FunctionTooLong: simplexpr::eval::call_expr_function crates/simplexpr/src/eval.rs:319
- MethodTooLong: App.try_handle_command crates/eww/src/app.rs:178
- Members sharing a duplicated core (4 members, 50+ identical tokens) crates/eww/src/widgets/widget_definitions.rs:317
- Duplicated block (14 lines × 2) crates/simplexpr/src/parser/lexer.rs:143
- Duplicated block (13 lines × 2) crates/eww/src/widgets/widget_definitions.rs:336
- Duplicated block (12 lines × 2) crates/eww/src/widgets/widget_definitions.rs:705
- Duplicated block (9–10 lines × 4) crates/eww/src/widgets/widget_definitions.rs:335
- Duplicated block (8 lines × 2) crates/eww/src/widgets/circular_progressbar.rs:99
- Duplicated block (7 lines × 2) crates/eww/src/widgets/widget_definitions.rs:640
- Duplicated block (6 lines × 3) crates/simplexpr/src/eval.rs:348
- Duplicated block (6 lines × 4) crates/simplexpr/src/eval.rs:348
- End-of-life runtime: Rust 1.81 rust-toolchain.toml:1
- Low cohesion: WindowDefinition (LCOM4 4) crates/yuck/src/config/window_definition.rs:33
- Third-party script without Subresource Integrity docs/theme/index.hbs:54
Minor — 21 finding(s)
- Orphaned file crates/notifier_host/src/watcher.rs:1
- Orphaned file crates/eww/src/widgets/graph.rs:1
- Orphaned file crates/eww/src/widgets/systray.rs:1
- Orphaned file crates/eww/src/widgets/circular_progressbar.rs:1
- Orphaned file crates/notifier_host/src/icon.rs:1
- Orphaned file crates/eww/src/widgets/transform.rs:1
- Orphaned file gen-docs.ts:1
- Orphaned file crates/notifier_host/src/item.rs:1
- Orphaned file crates/notifier_host/src/host.rs:1
- Orphaned file crates/eww/src/window_arguments.rs:1
- Duplicated predicate crates/simplexpr/src/parser/lexer.rs:136
- Duplicated predicate crates/simplexpr/src/parser/lexer.rs:181
- Off-boarding risk: anonymized user #1
- Documentation: no build, run or usage example README.md:1
- No ADRs found
- Orphaned files with no living knowledge
- REDACTED
- No ADRs
- No architecture diagram/doc
- Large public API surface
- Strict null checking is not enabled everywhere the repository type-checks
Minor — 19 finding(s)
- Outdated: anyhow
- Outdated: bytesize
- Outdated: chrono
- Outdated: chrono-tz
- Outdated: clap
- Outdated: clap_complete
- Outdated: futures
- Outdated: gtk-layer-shell
- Outdated: libc
- Outdated: log
- Outdated: once_cell
- Outdated: ref-cast
- Outdated: regex
- Outdated: serde
- Outdated: serde_json
- Outdated: tokio
- Outdated: tokio-util
- Outdated: wait-timeout
- Off the main sequence: eww_shared_util
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-a37b944fcad74e86bc6c94fa79bf512e/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-a37b944fcad74e86bc6c94fa79bf512e/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 . | 9 | 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 . | 20 | 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. | 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 |