Executive summary
trunk-rs/trunk falls short of our standard for a preview release, held back most by its Production Readiness lens, the way the code is tested, built, released and run. It scores 59 out of 100 and is rated Adequate, and all 39 of its critical findings are security problems.
Production Readiness, at 50, is the weakest lens and counts most in the score. The best first step is fixing the password or key in the code, worth about 7 points. Protecting outgoing calls with timeouts would lift Production Readiness itself, worth about 4 points. Raising Production Readiness to 62 would lift the score to about 65.
Twenty-six pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Four pipeline steps run downloads nobody checks, and four secrets can leak from the build pipeline. Pinning each tool to an exact version, checking each download against a checksum and limiting each secret to its own step would close these risks. Fixing the weaknesses the scanner points to would fix the two security weaknesses in the code.
The product code is 9,955 lines, about €13,000 to rebuild.
If Production Readiness rose from 50 to 62, the lowest score rated Strong, the score would rise from 59 to about 65.
New since the last survey: 10 findings
- Dependency Hygiene · Yanked release: tokio
- Static Analysis (SAST) · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
Fixed since the last survey: 5 findings
- Static Analysis (SAST) · High: REDACTED REDACTED
- Static Analysis (SAST) · High: REDACTED REDACTED
- Dependency Vulnerabilities · Medium vulnerability: RUSTSEC-2026-0346 REDACTED
- Supply-chain Provenance & Signing REDACTED
- Supply-chain Provenance & Signing REDACTED
Rebuild cost: about €13,000 · Estimate
| Cost to rebuild | €4,300 to €22,000, for 72 to 228 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 59. 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: 9,955 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: which parts of the code depend on which
| uses → | 1 cmd.config | 2 cmd.tools | 3 common.html_rewrite | 4 config.manifest | 5 config.types.address_family | 6 config.types.cross_origin | 7 config.types.uri | 8 config.types.ws | 9 processing.integrity | 10 tools.retry | 11 cmd.core | 12 cmd.watch | 13 config.models.node_package | 14 config.models.proxy | 15 pipelines | 16 pipelines.html | 17 pipelines.rust.sri | 18 pipelines.rust.wasm_bindgen | 19 cmd.serve | 20 config.models.hook | 21 config.rt.core | 22 pipelines.copy_file | 23 pipelines.css | 24 pipelines.icon | 25 pipelines.inline | 26 pipelines.js | 27 pipelines.rust.output | 28 pipelines.sass | 29 pipelines.tailwind_css_extra | 30 config.models | 31 pipelines.rust | 32 pipelines.tailwind_css | 33 cmd.clean | 34 config.models.serve | 35 config.rt | 36 config.rt.clean | 37 config.rt.watch | 38 config.rt.serve | 39 watch | 40 serve |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 cmd.config | ||||||||||||||||||||||||||||||||||||||||
| 2 cmd.tools | ||||||||||||||||||||||||||||||||||||||||
| 3 common.html_rewrite | ||||||||||||||||||||||||||||||||||||||||
| 4 config.manifest | ||||||||||||||||||||||||||||||||||||||||
| 5 config.types.address_family | ||||||||||||||||||||||||||||||||||||||||
| 6 config.types.cross_origin | ||||||||||||||||||||||||||||||||||||||||
| 7 config.types.uri | ||||||||||||||||||||||||||||||||||||||||
| 8 config.types.ws | ||||||||||||||||||||||||||||||||||||||||
| 9 processing.integrity | ||||||||||||||||||||||||||||||||||||||||
| 10 tools.retry | ||||||||||||||||||||||||||||||||||||||||
| 11 cmd.core | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 cmd.watch | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 config.models.node_package | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 config.models.proxy | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 15 pipelines | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 pipelines.html | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 17 pipelines.rust.sri | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 18 pipelines.rust.wasm_bindgen | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 19 cmd.serve | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 20 config.models.hook | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 21 config.rt.core | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 pipelines.copy_file | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 23 pipelines.css | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 24 pipelines.icon | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 25 pipelines.inline | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 26 pipelines.js | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 27 pipelines.rust.output | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 28 pipelines.sass | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 29 pipelines.tailwind_css_extra | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 30 config.models | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 31 pipelines.rust | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 32 pipelines.tailwind_css | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 33 cmd.clean | 1 | |||||||||||||||||||||||||||||||||||||||
| 34 config.models.serve | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 35 config.rt | 1 | |||||||||||||||||||||||||||||||||||||||
| 36 config.rt.clean | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 37 config.rt.watch | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 38 config.rt.serve | 1 | 1 | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||
| 39 watch | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 40 serve | 1 | 3 | 1 |
11→30 cmd.core uses config.models part of a loop✕
- Connections
- 1 pair of types, where a type in cmd.core uses a type in config.models.
- The types involved
trunk.cmd.core.Core→trunk.config.models.Configuration
- Direction
- cmd.core uses config.models, so a change to config.models can break cmd.core, while a change to cmd.core can't break config.models.
- 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→30 cmd.watch uses config.models part of a loop✕
- Connections
- 1 pair of types, where a type in cmd.watch uses a type in config.models.
- The types involved
trunk.cmd.watch.Watch→trunk.config.models.Configuration
- Direction
- cmd.watch uses config.models, so a change to config.models can break cmd.watch, while a change to cmd.watch can't break config.models.
- 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→30 config.models.node_package uses config.models part of a loop✕
- Connections
- 1 pair of types, where a type in config.models.node_package uses a type in config.models.
- The types involved
trunk.config.models.node_package.NodePackages→trunk.config.models.ConfigModel
- Direction
- config.models.node_package uses config.models, so a change to config.models can break config.models.node_package, while a change to config.models.node_package can't break config.models.
- 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→7 config.models.proxy uses config.types.uri✕
- Connections
- 1 pair of types, where a type in config.models.proxy uses a type in config.types.uri.
- The types involved
trunk.config.models.proxy.Proxy→trunk.config.types.uri.Uri
- Direction
- config.models.proxy uses config.types.uri, so a change to config.types.uri can break config.models.proxy, while a change to config.models.proxy can't break config.types.uri.
- Position
- Below the diagonal: config.models.proxy uses a module listed above it, which is the healthy direction.
14→30 config.models.proxy uses config.models part of a loop✕
- Connections
- 1 pair of types, where a type in config.models.proxy uses a type in config.models.
- The types involved
trunk.config.models.proxy.Proxies→trunk.config.models.ConfigModel
- Direction
- config.models.proxy uses config.models, so a change to config.models can break config.models.proxy, while a change to config.models.proxy can't break config.models.
- 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 pipelines uses common.html_rewrite✕
- Connections
- 1 pair of types, where a type in pipelines uses a type in common.html_rewrite.
- The types involved
trunk.pipelines.TrunkAssetPipelineOutput→trunk.common.html_rewrite.Document
- Direction
- pipelines uses common.html_rewrite, so a change to common.html_rewrite can break pipelines, while a change to pipelines can't break common.html_rewrite.
- Position
- Below the diagonal: pipelines uses a module listed above it, which is the healthy direction.
16→3 pipelines.html uses common.html_rewrite✕
- Connections
- 1 pair of types, where a type in pipelines.html uses a type in common.html_rewrite.
- The types involved
trunk.pipelines.html.HtmlPipeline→trunk.common.html_rewrite.Document
- Direction
- pipelines.html uses common.html_rewrite, so a change to common.html_rewrite can break pipelines.html, while a change to pipelines.html can't break common.html_rewrite.
- Position
- Below the diagonal: pipelines.html uses a module listed above it, which is the healthy direction.
16→8 pipelines.html uses config.types.ws✕
- Connections
- 1 pair of types, where a type in pipelines.html uses a type in config.types.ws.
- The types involved
trunk.pipelines.html.HtmlPipeline→trunk.config.types.ws.WsProtocol
- Direction
- pipelines.html uses config.types.ws, so a change to config.types.ws can break pipelines.html, while a change to pipelines.html can't break config.types.ws.
- Position
- Below the diagonal: pipelines.html uses a module listed above it, which is the healthy direction.
17→3 pipelines.rust.sri uses common.html_rewrite✕
- Connections
- 1 pair of types, where a type in pipelines.rust.sri uses a type in common.html_rewrite.
- The types involved
trunk.pipelines.rust.sri.SriResult→trunk.common.html_rewrite.Document
- Direction
- pipelines.rust.sri uses common.html_rewrite, so a change to common.html_rewrite can break pipelines.rust.sri, while a change to pipelines.rust.sri can't break common.html_rewrite.
- Position
- Below the diagonal: pipelines.rust.sri uses a module listed above it, which is the healthy direction.
17→6 pipelines.rust.sri uses config.types.cross_origin✕
- Connections
- 1 pair of types, where a type in pipelines.rust.sri uses a type in config.types.cross_origin.
- The types involved
trunk.pipelines.rust.sri.SriResult→trunk.config.types.cross_origin.CrossOrigin
- Direction
- pipelines.rust.sri uses config.types.cross_origin, so a change to config.types.cross_origin can break pipelines.rust.sri, while a change to pipelines.rust.sri can't break config.types.cross_origin.
- Position
- Below the diagonal: pipelines.rust.sri uses a module listed above it, which is the healthy direction.
17→9 pipelines.rust.sri uses processing.integrity✕
- Connections
- 2 pairs of types, where a type in pipelines.rust.sri uses a type in processing.integrity.
- The types involved
trunk.pipelines.rust.sri.SriBuilder→trunk.processing.integrity.IntegrityTypetrunk.pipelines.rust.sri.SriEntry→trunk.processing.integrity.OutputDigest
- Direction
- pipelines.rust.sri uses processing.integrity, so a change to processing.integrity can break pipelines.rust.sri, while a change to pipelines.rust.sri can't break processing.integrity.
- Position
- Below the diagonal: pipelines.rust.sri uses a module listed above it, which is the healthy direction.
18→2 pipelines.rust.wasm_bindgen uses cmd.tools✕
- Connections
- 1 pair of types, where a type in pipelines.rust.wasm_bindgen uses a type in cmd.tools.
- The types involved
trunk.pipelines.rust.wasm_bindgen.wasm_bindgen$module→trunk.cmd.tools.Tools
- Direction
- pipelines.rust.wasm_bindgen uses cmd.tools, so a change to cmd.tools can break pipelines.rust.wasm_bindgen, while a change to pipelines.rust.wasm_bindgen can't break cmd.tools.
- Position
- Below the diagonal: pipelines.rust.wasm_bindgen uses a module listed above it, which is the healthy direction.
18→4 pipelines.rust.wasm_bindgen uses config.manifest✕
- Connections
- 1 pair of types, where a type in pipelines.rust.wasm_bindgen uses a type in config.manifest.
- The types involved
trunk.pipelines.rust.wasm_bindgen.wasm_bindgen$module→trunk.config.manifest.CargoMetadata
- Direction
- pipelines.rust.wasm_bindgen uses config.manifest, so a change to config.manifest can break pipelines.rust.wasm_bindgen, while a change to pipelines.rust.wasm_bindgen can't break config.manifest.
- Position
- Below the diagonal: pipelines.rust.wasm_bindgen uses a module listed above it, which is the healthy direction.
19→5 cmd.serve uses config.types.address_family✕
- Connections
- 1 pair of types, where a type in cmd.serve uses a type in config.types.address_family.
- The types involved
trunk.cmd.serve.Serve→trunk.config.types.address_family.AddressFamily
- Direction
- cmd.serve uses config.types.address_family, so a change to config.types.address_family can break cmd.serve, while a change to cmd.serve can't break config.types.address_family.
- Position
- Below the diagonal: cmd.serve uses a module listed above it, which is the healthy direction.
19→7 cmd.serve uses config.types.uri✕
- Connections
- 1 pair of types, where a type in cmd.serve uses a type in config.types.uri.
- The types involved
trunk.cmd.serve.ProxyArgs→trunk.config.types.uri.Uri
- Direction
- cmd.serve uses config.types.uri, so a change to config.types.uri can break cmd.serve, while a change to cmd.serve can't break config.types.uri.
- Position
- Below the diagonal: cmd.serve uses a module listed above it, which is the healthy direction.
19→8 cmd.serve uses config.types.ws✕
- Connections
- 1 pair of types, where a type in cmd.serve uses a type in config.types.ws.
- The types involved
trunk.cmd.serve.Serve→trunk.config.types.ws.WsProtocol
- Direction
- cmd.serve uses config.types.ws, so a change to config.types.ws can break cmd.serve, while a change to cmd.serve can't break config.types.ws.
- Position
- Below the diagonal: cmd.serve uses a module listed above it, which is the healthy direction.
19→12 cmd.serve uses cmd.watch✕
- Connections
- 1 pair of types, where a type in cmd.serve uses a type in cmd.watch.
- The types involved
trunk.cmd.serve.Serve→trunk.cmd.watch.Watch
- Direction
- cmd.serve uses cmd.watch, so a change to cmd.watch can break cmd.serve, while a change to cmd.serve can't break cmd.watch.
- Position
- Below the diagonal: cmd.serve uses a module listed above it, which is the healthy direction.
19→30 cmd.serve uses config.models part of a loop✕
- Connections
- 1 pair of types, where a type in cmd.serve uses a type in config.models.
- The types involved
trunk.cmd.serve.Serve→trunk.config.models.Configuration
- Direction
- cmd.serve uses config.models, so a change to config.models can break cmd.serve, while a change to cmd.serve can't break config.models.
- 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→15 config.models.hook uses pipelines✕
- Connections
- 1 pair of types, where a type in config.models.hook uses a type in pipelines.
- The types involved
trunk.config.models.hook.Hook→trunk.pipelines.PipelineStage
- Direction
- config.models.hook uses pipelines, so a change to pipelines can break config.models.hook, while a change to config.models.hook can't break pipelines.
- Position
- Below the diagonal: config.models.hook uses a module listed above it, which is the healthy direction.
20→30 config.models.hook uses config.models part of a loop✕
- Connections
- 1 pair of types, where a type in config.models.hook uses a type in config.models.
- The types involved
trunk.config.models.hook.Hooks→trunk.config.models.ConfigModel
- Direction
- config.models.hook uses config.models, so a change to config.models can break config.models.hook, while a change to config.models.hook can't break config.models.
- 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.
21→11 config.rt.core uses cmd.core✕
- Connections
- 1 pair of types, where a type in config.rt.core uses a type in cmd.core.
- The types involved
trunk.config.rt.core.RtcCore→trunk.cmd.core.Core
- Direction
- config.rt.core uses cmd.core, so a change to cmd.core can break config.rt.core, while a change to config.rt.core can't break cmd.core.
- Position
- Below the diagonal: config.rt.core uses a module listed above it, which is the healthy direction.
22→3 pipelines.copy_file uses common.html_rewrite✕
- Connections
- 1 pair of types, where a type in pipelines.copy_file uses a type in common.html_rewrite.
- The types involved
trunk.pipelines.copy_file.CopyFileOutput→trunk.common.html_rewrite.Document
- Direction
- pipelines.copy_file uses common.html_rewrite, so a change to common.html_rewrite can break pipelines.copy_file, while a change to pipelines.copy_file can't break common.html_rewrite.
- Position
- Below the diagonal: pipelines.copy_file uses a module listed above it, which is the healthy direction.
22→15 pipelines.copy_file uses pipelines✕
- Connections
- 1 pair of types, where a type in pipelines.copy_file uses a type in pipelines.
- The types involved
trunk.pipelines.copy_file.CopyFile→trunk.pipelines.AssetFile
- Direction
- pipelines.copy_file uses pipelines, so a change to pipelines can break pipelines.copy_file, while a change to pipelines.copy_file can't break pipelines.
- Position
- Below the diagonal: pipelines.copy_file uses a module listed above it, which is the healthy direction.
23→3 pipelines.css uses common.html_rewrite✕
- Connections
- 1 pair of types, where a type in pipelines.css uses a type in common.html_rewrite.
- The types involved
trunk.pipelines.css.CssOutput→trunk.common.html_rewrite.Document
- Direction
- pipelines.css uses common.html_rewrite, so a change to common.html_rewrite can break pipelines.css, while a change to pipelines.css can't break common.html_rewrite.
- Position
- Below the diagonal: pipelines.css uses a module listed above it, which is the healthy direction.
23→9 pipelines.css uses processing.integrity✕
- Connections
- 2 pairs of types, where a type in pipelines.css uses a type in processing.integrity.
- The types involved
trunk.pipelines.css.Css→trunk.processing.integrity.IntegrityTypetrunk.pipelines.css.CssOutput→trunk.processing.integrity.OutputDigest
- Direction
- pipelines.css uses processing.integrity, so a change to processing.integrity can break pipelines.css, while a change to pipelines.css can't break processing.integrity.
- Position
- Below the diagonal: pipelines.css uses a module listed above it, which is the healthy direction.
23→15 pipelines.css uses pipelines✕
- Connections
- 1 pair of types, where a type in pipelines.css uses a type in pipelines.
- The types involved
trunk.pipelines.css.Css→trunk.pipelines.AssetFile
- Direction
- pipelines.css uses pipelines, so a change to pipelines can break pipelines.css, while a change to pipelines.css can't break pipelines.
- Position
- Below the diagonal: pipelines.css uses a module listed above it, which is the healthy direction.
24→3 pipelines.icon uses common.html_rewrite✕
- Connections
- 1 pair of types, where a type in pipelines.icon uses a type in common.html_rewrite.
- The types involved
trunk.pipelines.icon.IconOutput→trunk.common.html_rewrite.Document
- Direction
- pipelines.icon uses common.html_rewrite, so a change to common.html_rewrite can break pipelines.icon, while a change to pipelines.icon can't break common.html_rewrite.
- Position
- Below the diagonal: pipelines.icon uses a module listed above it, which is the healthy direction.
24→9 pipelines.icon uses processing.integrity✕
- Connections
- 2 pairs of types, where a type in pipelines.icon uses a type in processing.integrity.
- The types involved
trunk.pipelines.icon.Icon→trunk.processing.integrity.IntegrityTypetrunk.pipelines.icon.IconOutput→trunk.processing.integrity.OutputDigest
- Direction
- pipelines.icon uses processing.integrity, so a change to processing.integrity can break pipelines.icon, while a change to pipelines.icon can't break processing.integrity.
- Position
- Below the diagonal: pipelines.icon uses a module listed above it, which is the healthy direction.
24→15 pipelines.icon uses pipelines✕
- Connections
- 1 pair of types, where a type in pipelines.icon uses a type in pipelines.
- The types involved
trunk.pipelines.icon.Icon→trunk.pipelines.AssetFile
- Direction
- pipelines.icon uses pipelines, so a change to pipelines can break pipelines.icon, while a change to pipelines.icon can't break pipelines.
- Position
- Below the diagonal: pipelines.icon uses a module listed above it, which is the healthy direction.
25→3 pipelines.inline uses common.html_rewrite✕
- Connections
- 1 pair of types, where a type in pipelines.inline uses a type in common.html_rewrite.
- The types involved
trunk.pipelines.inline.InlineOutput→trunk.common.html_rewrite.Document
- Direction
- pipelines.inline uses common.html_rewrite, so a change to common.html_rewrite can break pipelines.inline, while a change to pipelines.inline can't break common.html_rewrite.
- Position
- Below the diagonal: pipelines.inline uses a module listed above it, which is the healthy direction.
25→15 pipelines.inline uses pipelines✕
- Connections
- 1 pair of types, where a type in pipelines.inline uses a type in pipelines.
- The types involved
trunk.pipelines.inline.Inline→trunk.pipelines.AssetFile
- Direction
- pipelines.inline uses pipelines, so a change to pipelines can break pipelines.inline, while a change to pipelines.inline can't break pipelines.
- Position
- Below the diagonal: pipelines.inline uses a module listed above it, which is the healthy direction.
26→3 pipelines.js uses common.html_rewrite✕
- Connections
- 1 pair of types, where a type in pipelines.js uses a type in common.html_rewrite.
- The types involved
trunk.pipelines.js.JsOutput→trunk.common.html_rewrite.Document
- Direction
- pipelines.js uses common.html_rewrite, so a change to common.html_rewrite can break pipelines.js, while a change to pipelines.js can't break common.html_rewrite.
- Position
- Below the diagonal: pipelines.js uses a module listed above it, which is the healthy direction.
26→9 pipelines.js uses processing.integrity✕
- Connections
- 2 pairs of types, where a type in pipelines.js uses a type in processing.integrity.
- The types involved
trunk.pipelines.js.Js→trunk.processing.integrity.IntegrityTypetrunk.pipelines.js.JsOutput→trunk.processing.integrity.OutputDigest
- Direction
- pipelines.js uses processing.integrity, so a change to processing.integrity can break pipelines.js, while a change to pipelines.js can't break processing.integrity.
- Position
- Below the diagonal: pipelines.js uses a module listed above it, which is the healthy direction.
26→15 pipelines.js uses pipelines✕
- Connections
- 1 pair of types, where a type in pipelines.js uses a type in pipelines.
- The types involved
trunk.pipelines.js.Js→trunk.pipelines.AssetFile
- Direction
- pipelines.js uses pipelines, so a change to pipelines can break pipelines.js, while a change to pipelines.js can't break pipelines.
- Position
- Below the diagonal: pipelines.js uses a module listed above it, which is the healthy direction.
27→3 pipelines.rust.output uses common.html_rewrite✕
- Connections
- 1 pair of types, where a type in pipelines.rust.output uses a type in common.html_rewrite.
- The types involved
trunk.pipelines.rust.output.RustAppOutput→trunk.common.html_rewrite.Document
- Direction
- pipelines.rust.output uses common.html_rewrite, so a change to common.html_rewrite can break pipelines.rust.output, while a change to pipelines.rust.output can't break common.html_rewrite.
- Position
- Below the diagonal: pipelines.rust.output uses a module listed above it, which is the healthy direction.
27→6 pipelines.rust.output uses config.types.cross_origin✕
- Connections
- 1 pair of types, where a type in pipelines.rust.output uses a type in config.types.cross_origin.
- The types involved
trunk.pipelines.rust.output.RustAppOutput→trunk.config.types.cross_origin.CrossOrigin
- Direction
- pipelines.rust.output uses config.types.cross_origin, so a change to config.types.cross_origin can break pipelines.rust.output, while a change to pipelines.rust.output can't break config.types.cross_origin.
- Position
- Below the diagonal: pipelines.rust.output uses a module listed above it, which is the healthy direction.
27→17 pipelines.rust.output uses pipelines.rust.sri✕
- Connections
- 1 pair of types, where a type in pipelines.rust.output uses a type in pipelines.rust.sri.
- The types involved
trunk.pipelines.rust.output.RustAppOutput→trunk.pipelines.rust.sri.SriBuilder
- Direction
- pipelines.rust.output uses pipelines.rust.sri, so a change to pipelines.rust.sri can break pipelines.rust.output, while a change to pipelines.rust.output can't break pipelines.rust.sri.
- Position
- Below the diagonal: pipelines.rust.output uses a module listed above it, which is the healthy direction.
27→18 pipelines.rust.output uses pipelines.rust.wasm_bindgen✕
- Connections
- 1 pair of types, where a type in pipelines.rust.output uses a type in pipelines.rust.wasm_bindgen.
- The types involved
trunk.pipelines.rust.output.RustAppOutput→trunk.pipelines.rust.wasm_bindgen.WasmBindgenFeatures
- Direction
- pipelines.rust.output uses pipelines.rust.wasm_bindgen, so a change to pipelines.rust.wasm_bindgen can break pipelines.rust.output, while a change to pipelines.rust.output can't break pipelines.rust.wasm_bindgen.
- Position
- Below the diagonal: pipelines.rust.output uses a module listed above it, which is the healthy direction.
27→31 pipelines.rust.output uses pipelines.rust part of a loop✕
- Connections
- 1 pair of types, where a type in pipelines.rust.output uses a type in pipelines.rust.
- The types involved
trunk.pipelines.rust.output.RustAppOutput→trunk.pipelines.rust.RustAppType
- Direction
- pipelines.rust.output uses pipelines.rust, so a change to pipelines.rust can break pipelines.rust.output, while a change to pipelines.rust.output can't break pipelines.rust.
- 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.
28→3 pipelines.sass uses common.html_rewrite✕
- Connections
- 1 pair of types, where a type in pipelines.sass uses a type in common.html_rewrite.
- The types involved
trunk.pipelines.sass.SassOutput→trunk.common.html_rewrite.Document
- Direction
- pipelines.sass uses common.html_rewrite, so a change to common.html_rewrite can break pipelines.sass, while a change to pipelines.sass can't break common.html_rewrite.
- Position
- Below the diagonal: pipelines.sass uses a module listed above it, which is the healthy direction.
28→9 pipelines.sass uses processing.integrity✕
- Connections
- 1 pair of types, where a type in pipelines.sass uses a type in processing.integrity.
- The types involved
trunk.pipelines.sass.Sass→trunk.processing.integrity.IntegrityType
- Direction
- pipelines.sass uses processing.integrity, so a change to processing.integrity can break pipelines.sass, while a change to pipelines.sass can't break processing.integrity.
- Position
- Below the diagonal: pipelines.sass uses a module listed above it, which is the healthy direction.
28→15 pipelines.sass uses pipelines✕
- Connections
- 1 pair of types, where a type in pipelines.sass uses a type in pipelines.
- The types involved
trunk.pipelines.sass.Sass→trunk.pipelines.AssetFile
- Direction
- pipelines.sass uses pipelines, so a change to pipelines can break pipelines.sass, while a change to pipelines.sass can't break pipelines.
- Position
- Below the diagonal: pipelines.sass uses a module listed above it, which is the healthy direction.
29→3 pipelines.tailwind_css_extra uses common.html_rewrite✕
- Connections
- 1 pair of types, where a type in pipelines.tailwind_css_extra uses a type in common.html_rewrite.
- The types involved
trunk.pipelines.tailwind_css_extra.TailwindCssExtraOutput→trunk.common.html_rewrite.Document
- Direction
- pipelines.tailwind_css_extra uses common.html_rewrite, so a change to common.html_rewrite can break pipelines.tailwind_css_extra, while a change to pipelines.tailwind_css_extra can't break common.html_rewrite.
- Position
- Below the diagonal: pipelines.tailwind_css_extra uses a module listed above it, which is the healthy direction.
29→9 pipelines.tailwind_css_extra uses processing.integrity✕
- Connections
- 1 pair of types, where a type in pipelines.tailwind_css_extra uses a type in processing.integrity.
- The types involved
trunk.pipelines.tailwind_css_extra.TailwindCssExtra→trunk.processing.integrity.IntegrityType
- Direction
- pipelines.tailwind_css_extra uses processing.integrity, so a change to processing.integrity can break pipelines.tailwind_css_extra, while a change to pipelines.tailwind_css_extra can't break processing.integrity.
- Position
- Below the diagonal: pipelines.tailwind_css_extra uses a module listed above it, which is the healthy direction.
29→15 pipelines.tailwind_css_extra uses pipelines✕
- Connections
- 1 pair of types, where a type in pipelines.tailwind_css_extra uses a type in pipelines.
- The types involved
trunk.pipelines.tailwind_css_extra.TailwindCssExtra→trunk.pipelines.AssetFile
- Direction
- pipelines.tailwind_css_extra uses pipelines, so a change to pipelines can break pipelines.tailwind_css_extra, while a change to pipelines.tailwind_css_extra can't break pipelines.
- Position
- Below the diagonal: pipelines.tailwind_css_extra uses a module listed above it, which is the healthy direction.
30→2 config.models uses cmd.tools✕
- Connections
- 1 pair of types, where a type in config.models uses a type in cmd.tools.
- The types involved
trunk.config.models.Configuration→trunk.cmd.tools.Tools
- Direction
- config.models uses cmd.tools, so a change to cmd.tools can break config.models, while a change to config.models can't break cmd.tools.
- Position
- Below the diagonal: config.models uses a module listed above it, which is the healthy direction.
30→11 config.models uses cmd.core✕
- Connections
- 1 pair of types, where a type in config.models uses a type in cmd.core.
- The types involved
trunk.config.models.Configuration→trunk.cmd.core.Core
- Direction
- config.models uses cmd.core, so a change to cmd.core can break config.models, while a change to config.models can't break cmd.core.
- Position
- Below the diagonal: config.models uses a module listed above it, which is the healthy direction.
30→12 config.models uses cmd.watch✕
- Connections
- 1 pair of types, where a type in config.models uses a type in cmd.watch.
- The types involved
trunk.config.models.Configuration→trunk.cmd.watch.Watch
- Direction
- config.models uses cmd.watch, so a change to cmd.watch can break config.models, while a change to config.models can't break cmd.watch.
- Position
- Below the diagonal: config.models uses a module listed above it, which is the healthy direction.
30→13 config.models uses config.models.node_package✕
- Connections
- 1 pair of types, where a type in config.models uses a type in config.models.node_package.
- The types involved
trunk.config.models.Configuration→trunk.config.models.node_package.NodePackages
- Direction
- config.models uses config.models.node_package, so a change to config.models.node_package can break config.models, while a change to config.models can't break config.models.node_package.
- Position
- Below the diagonal: config.models uses a module listed above it, which is the healthy direction.
30→14 config.models uses config.models.proxy✕
- Connections
- 1 pair of types, where a type in config.models uses a type in config.models.proxy.
- The types involved
trunk.config.models.Configuration→trunk.config.models.proxy.Proxies
- Direction
- config.models uses config.models.proxy, so a change to config.models.proxy can break config.models, while a change to config.models can't break config.models.proxy.
- Position
- Below the diagonal: config.models uses a module listed above it, which is the healthy direction.
30→19 config.models uses cmd.serve✕
- Connections
- 1 pair of types, where a type in config.models uses a type in cmd.serve.
- The types involved
trunk.config.models.Configuration→trunk.cmd.serve.Serve
- Direction
- config.models uses cmd.serve, so a change to cmd.serve can break config.models, while a change to config.models can't break cmd.serve.
- Position
- Below the diagonal: config.models uses a module listed above it, which is the healthy direction.
30→20 config.models uses config.models.hook✕
- Connections
- 1 pair of types, where a type in config.models uses a type in config.models.hook.
- The types involved
trunk.config.models.Configuration→trunk.config.models.hook.Hooks
- Direction
- config.models uses config.models.hook, so a change to config.models.hook can break config.models, while a change to config.models can't break config.models.hook.
- Position
- Below the diagonal: config.models uses a module listed above it, which is the healthy direction.
30→33 config.models uses cmd.clean part of a loop✕
- Connections
- 1 pair of types, where a type in config.models uses a type in cmd.clean.
- The types involved
trunk.config.models.Configuration→trunk.cmd.clean.Clean
- Direction
- config.models uses cmd.clean, so a change to cmd.clean can break config.models, while a change to config.models can't break cmd.clean.
- 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.
31→4 pipelines.rust uses config.manifest✕
- Connections
- 1 pair of types, where a type in pipelines.rust uses a type in config.manifest.
- The types involved
trunk.pipelines.rust.RustApp→trunk.config.manifest.CargoMetadata
- Direction
- pipelines.rust uses config.manifest, so a change to config.manifest can break pipelines.rust, while a change to pipelines.rust can't break config.manifest.
- Position
- Below the diagonal: pipelines.rust uses a module listed above it, which is the healthy direction.
31→6 pipelines.rust uses config.types.cross_origin✕
- Connections
- 1 pair of types, where a type in pipelines.rust uses a type in config.types.cross_origin.
- The types involved
trunk.pipelines.rust.RustApp→trunk.config.types.cross_origin.CrossOrigin
- Direction
- pipelines.rust uses config.types.cross_origin, so a change to config.types.cross_origin can break pipelines.rust, while a change to pipelines.rust can't break config.types.cross_origin.
- Position
- Below the diagonal: pipelines.rust uses a module listed above it, which is the healthy direction.
31→17 pipelines.rust uses pipelines.rust.sri✕
- Connections
- 1 pair of types, where a type in pipelines.rust uses a type in pipelines.rust.sri.
- The types involved
trunk.pipelines.rust.RustApp→trunk.pipelines.rust.sri.SriBuilder
- Direction
- pipelines.rust uses pipelines.rust.sri, so a change to pipelines.rust.sri can break pipelines.rust, while a change to pipelines.rust can't break pipelines.rust.sri.
- Position
- Below the diagonal: pipelines.rust uses a module listed above it, which is the healthy direction.
31→18 pipelines.rust uses pipelines.rust.wasm_bindgen✕
- Connections
- 1 pair of types, where a type in pipelines.rust uses a type in pipelines.rust.wasm_bindgen.
- The types involved
trunk.pipelines.rust.RustApp→trunk.pipelines.rust.wasm_bindgen.WasmBindgenTarget
- Direction
- pipelines.rust uses pipelines.rust.wasm_bindgen, so a change to pipelines.rust.wasm_bindgen can break pipelines.rust, while a change to pipelines.rust can't break pipelines.rust.wasm_bindgen.
- Position
- Below the diagonal: pipelines.rust uses a module listed above it, which is the healthy direction.
31→27 pipelines.rust uses pipelines.rust.output✕
- Connections
- 1 pair of types, where a type in pipelines.rust uses a type in pipelines.rust.output.
- The types involved
trunk.pipelines.rust.RustApp→trunk.pipelines.rust.output.RustAppOutput
- Direction
- pipelines.rust uses pipelines.rust.output, so a change to pipelines.rust.output can break pipelines.rust, while a change to pipelines.rust can't break pipelines.rust.output.
- Position
- Below the diagonal: pipelines.rust uses a module listed above it, which is the healthy direction.
32→3 pipelines.tailwind_css uses common.html_rewrite✕
- Connections
- 1 pair of types, where a type in pipelines.tailwind_css uses a type in common.html_rewrite.
- The types involved
trunk.pipelines.tailwind_css.TailwindCssOutput→trunk.common.html_rewrite.Document
- Direction
- pipelines.tailwind_css uses common.html_rewrite, so a change to common.html_rewrite can break pipelines.tailwind_css, while a change to pipelines.tailwind_css can't break common.html_rewrite.
- Position
- Below the diagonal: pipelines.tailwind_css uses a module listed above it, which is the healthy direction.
32→9 pipelines.tailwind_css uses processing.integrity✕
- Connections
- 1 pair of types, where a type in pipelines.tailwind_css uses a type in processing.integrity.
- The types involved
trunk.pipelines.tailwind_css.TailwindCss→trunk.processing.integrity.IntegrityType
- Direction
- pipelines.tailwind_css uses processing.integrity, so a change to processing.integrity can break pipelines.tailwind_css, while a change to pipelines.tailwind_css can't break processing.integrity.
- Position
- Below the diagonal: pipelines.tailwind_css uses a module listed above it, which is the healthy direction.
32→15 pipelines.tailwind_css uses pipelines✕
- Connections
- 1 pair of types, where a type in pipelines.tailwind_css uses a type in pipelines.
- The types involved
trunk.pipelines.tailwind_css.TailwindCss→trunk.pipelines.AssetFile
- Direction
- pipelines.tailwind_css uses pipelines, so a change to pipelines can break pipelines.tailwind_css, while a change to pipelines.tailwind_css can't break pipelines.
- Position
- Below the diagonal: pipelines.tailwind_css uses a module listed above it, which is the healthy direction.
32→28 pipelines.tailwind_css uses pipelines.sass✕
- Connections
- 1 pair of types, where a type in pipelines.tailwind_css uses a type in pipelines.sass.
- The types involved
trunk.pipelines.tailwind_css.TailwindCssOutput→trunk.pipelines.sass.CssRef
- Direction
- pipelines.tailwind_css uses pipelines.sass, so a change to pipelines.sass can break pipelines.tailwind_css, while a change to pipelines.tailwind_css can't break pipelines.sass.
- Position
- Below the diagonal: pipelines.tailwind_css uses a module listed above it, which is the healthy direction.
33→30 cmd.clean uses config.models✕
- Connections
- 1 pair of types, where a type in cmd.clean uses a type in config.models.
- The types involved
trunk.cmd.clean.Clean→trunk.config.models.Configuration
- Direction
- cmd.clean uses config.models, so a change to config.models can break cmd.clean, while a change to cmd.clean can't break config.models.
- Position
- Below the diagonal: cmd.clean uses a module listed above it, which is the healthy direction.
34→5 config.models.serve uses config.types.address_family✕
- Connections
- 1 pair of types, where a type in config.models.serve uses a type in config.types.address_family.
- The types involved
trunk.config.models.serve.Serve→trunk.config.types.address_family.AddressFamily
- Direction
- config.models.serve uses config.types.address_family, so a change to config.types.address_family can break config.models.serve, while a change to config.models.serve can't break config.types.address_family.
- Position
- Below the diagonal: config.models.serve uses a module listed above it, which is the healthy direction.
34→7 config.models.serve uses config.types.uri✕
- Connections
- 1 pair of types, where a type in config.models.serve uses a type in config.types.uri.
- The types involved
trunk.config.models.serve.Serve→trunk.config.types.uri.Uri
- Direction
- config.models.serve uses config.types.uri, so a change to config.types.uri can break config.models.serve, while a change to config.models.serve can't break config.types.uri.
- Position
- Below the diagonal: config.models.serve uses a module listed above it, which is the healthy direction.
34→8 config.models.serve uses config.types.ws✕
- Connections
- 1 pair of types, where a type in config.models.serve uses a type in config.types.ws.
- The types involved
trunk.config.models.serve.Serve→trunk.config.types.ws.WsProtocol
- Direction
- config.models.serve uses config.types.ws, so a change to config.types.ws can break config.models.serve, while a change to config.models.serve can't break config.types.ws.
- Position
- Below the diagonal: config.models.serve uses a module listed above it, which is the healthy direction.
34→30 config.models.serve uses config.models✕
- Connections
- 1 pair of types, where a type in config.models.serve uses a type in config.models.
- The types involved
trunk.config.models.serve.Serve→trunk.config.models.ConfigModel
- Direction
- config.models.serve uses config.models, so a change to config.models can break config.models.serve, while a change to config.models.serve can't break config.models.
- Position
- Below the diagonal: config.models.serve uses a module listed above it, which is the healthy direction.
35→30 config.rt uses config.models✕
- Connections
- 1 pair of types, where a type in config.rt uses a type in config.models.
- The types involved
trunk.config.rt.RtcBuilder→trunk.config.models.Configuration
- Direction
- config.rt uses config.models, so a change to config.models can break config.rt, while a change to config.rt can't break config.models.
- Position
- Below the diagonal: config.rt uses a module listed above it, which is the healthy direction.
36→21 config.rt.clean uses config.rt.core✕
- Connections
- 2 pairs of types, where a type in config.rt.clean uses a type in config.rt.core.
- The types involved
trunk.config.rt.clean.CleanOptions→trunk.config.rt.core.CoreOptionstrunk.config.rt.clean.RtcClean→trunk.config.rt.core.RtcCore
- Direction
- config.rt.clean uses config.rt.core, so a change to config.rt.core can break config.rt.clean, while a change to config.rt.clean can't break config.rt.core.
- Position
- Below the diagonal: config.rt.clean uses a module listed above it, which is the healthy direction.
36→30 config.rt.clean uses config.models✕
- Connections
- 1 pair of types, where a type in config.rt.clean uses a type in config.models.
- The types involved
trunk.config.rt.clean.RtcClean→trunk.config.models.Configuration
- Direction
- config.rt.clean uses config.models, so a change to config.models can break config.rt.clean, while a change to config.rt.clean can't break config.models.
- Position
- Below the diagonal: config.rt.clean uses a module listed above it, which is the healthy direction.
36→35 config.rt.clean uses config.rt✕
- Connections
- 1 pair of types, where a type in config.rt.clean uses a type in config.rt.
- The types involved
trunk.config.rt.clean.RtcClean→trunk.config.rt.RtcBuilder
- Direction
- config.rt.clean uses config.rt, so a change to config.rt can break config.rt.clean, while a change to config.rt.clean can't break config.rt.
- Position
- Below the diagonal: config.rt.clean uses a module listed above it, which is the healthy direction.
37→30 config.rt.watch uses config.models✕
- Connections
- 1 pair of types, where a type in config.rt.watch uses a type in config.models.
- The types involved
trunk.config.rt.watch.RtcWatch→trunk.config.models.Configuration
- Direction
- config.rt.watch uses config.models, so a change to config.models can break config.rt.watch, while a change to config.rt.watch can't break config.models.
- Position
- Below the diagonal: config.rt.watch uses a module listed above it, which is the healthy direction.
37→35 config.rt.watch uses config.rt✕
- Connections
- 1 pair of types, where a type in config.rt.watch uses a type in config.rt.
- The types involved
trunk.config.rt.watch.RtcWatch→trunk.config.rt.RtcBuilder
- Direction
- config.rt.watch uses config.rt, so a change to config.rt can break config.rt.watch, while a change to config.rt.watch can't break config.rt.
- Position
- Below the diagonal: config.rt.watch uses a module listed above it, which is the healthy direction.
38→5 config.rt.serve uses config.types.address_family✕
- Connections
- 1 pair of types, where a type in config.rt.serve uses a type in config.types.address_family.
- The types involved
trunk.config.rt.serve.serve$module→trunk.config.types.address_family.AddressFamily
- Direction
- config.rt.serve uses config.types.address_family, so a change to config.types.address_family can break config.rt.serve, while a change to config.rt.serve can't break config.types.address_family.
- Position
- Below the diagonal: config.rt.serve uses a module listed above it, which is the healthy direction.
38→8 config.rt.serve uses config.types.ws✕
- Connections
- 1 pair of types, where a type in config.rt.serve uses a type in config.types.ws.
- The types involved
trunk.config.rt.serve.RtcServe→trunk.config.types.ws.WsProtocol
- Direction
- config.rt.serve uses config.types.ws, so a change to config.types.ws can break config.rt.serve, while a change to config.rt.serve can't break config.types.ws.
- Position
- Below the diagonal: config.rt.serve uses a module listed above it, which is the healthy direction.
38→14 config.rt.serve uses config.models.proxy✕
- Connections
- 1 pair of types, where a type in config.rt.serve uses a type in config.models.proxy.
- The types involved
trunk.config.rt.serve.RtcServe→trunk.config.models.proxy.Proxy
- Direction
- config.rt.serve uses config.models.proxy, so a change to config.models.proxy can break config.rt.serve, while a change to config.rt.serve can't break config.models.proxy.
- Position
- Below the diagonal: config.rt.serve uses a module listed above it, which is the healthy direction.
38→30 config.rt.serve uses config.models✕
- Connections
- 1 pair of types, where a type in config.rt.serve uses a type in config.models.
- The types involved
trunk.config.rt.serve.RtcServe→trunk.config.models.Configuration
- Direction
- config.rt.serve uses config.models, so a change to config.models can break config.rt.serve, while a change to config.rt.serve can't break config.models.
- Position
- Below the diagonal: config.rt.serve uses a module listed above it, which is the healthy direction.
38→35 config.rt.serve uses config.rt✕
- Connections
- 1 pair of types, where a type in config.rt.serve uses a type in config.rt.
- The types involved
trunk.config.rt.serve.RtcServe→trunk.config.rt.RtcBuilder
- Direction
- config.rt.serve uses config.rt, so a change to config.rt can break config.rt.serve, while a change to config.rt.serve can't break config.rt.
- Position
- Below the diagonal: config.rt.serve uses a module listed above it, which is the healthy direction.
38→37 config.rt.serve uses config.rt.watch✕
- Connections
- 2 pairs of types, where a type in config.rt.serve uses a type in config.rt.watch.
- The types involved
trunk.config.rt.serve.RtcServe→trunk.config.rt.watch.RtcWatchtrunk.config.rt.serve.ServeOptions→trunk.config.rt.watch.WatchOptions
- Direction
- config.rt.serve uses config.rt.watch, so a change to config.rt.watch can break config.rt.serve, while a change to config.rt.serve can't break config.rt.watch.
- Position
- Below the diagonal: config.rt.serve uses a module listed above it, which is the healthy direction.
39→1 watch uses cmd.config✕
- Connections
- 1 pair of types, where a type in watch uses a type in cmd.config.
- The types involved
trunk.watch.watch$module→trunk.cmd.config.Config
- Direction
- watch uses cmd.config, so a change to cmd.config can break watch, while a change to watch can't break cmd.config.
- Position
- Below the diagonal: watch uses a module listed above it, which is the healthy direction.
39→8 watch uses config.types.ws✕
- Connections
- 1 pair of types, where a type in watch uses a type in config.types.ws.
- The types involved
trunk.watch.WatchSystem→trunk.config.types.ws.WsProtocol
- Direction
- watch uses config.types.ws, so a change to config.types.ws can break watch, while a change to watch can't break config.types.ws.
- Position
- Below the diagonal: watch uses a module listed above it, which is the healthy direction.
39→10 watch uses tools.retry✕
- Connections
- 1 pair of types, where a type in watch uses a type in tools.retry.
- The types involved
trunk.watch.watch$module→trunk.tools.retry.Error
- Direction
- watch uses tools.retry, so a change to tools.retry can break watch, while a change to watch can't break tools.retry.
- Position
- Below the diagonal: watch uses a module listed above it, which is the healthy direction.
39→37 watch uses config.rt.watch✕
- Connections
- 2 pairs of types, where a type in watch uses a type in config.rt.watch.
- The types involved
trunk.watch.WatchSystem→trunk.config.rt.watch.GlobMatchertrunk.watch.WatchSystem→trunk.config.rt.watch.RtcWatch
- Direction
- watch uses config.rt.watch, so a change to config.rt.watch can break watch, while a change to watch can't break config.rt.watch.
- Position
- Below the diagonal: watch uses a module listed above it, which is the healthy direction.
40→10 serve uses tools.retry✕
- Connections
- 1 pair of types, where a type in serve uses a type in tools.retry.
- The types involved
trunk.serve.ServerError→trunk.tools.retry.Error
- Direction
- serve uses tools.retry, so a change to tools.retry can break serve, while a change to serve can't break tools.retry.
- Position
- Below the diagonal: serve uses a module listed above it, which is the healthy direction.
40→38 serve uses config.rt.serve✕
- Connections
- 3 pairs of types, where a type in serve uses a type in config.rt.serve.
- The types involved
trunk.serve.ServeSystem→trunk.config.rt.serve.RtcServetrunk.serve.State→trunk.config.rt.serve.RtcServetrunk.serve.serve$module→trunk.config.rt.serve.RtcServe
- Direction
- serve uses config.rt.serve, so a change to config.rt.serve can break serve, while a change to serve can't break config.rt.serve.
- Position
- Below the diagonal: serve uses a module listed above it, which is the healthy direction.
40→39 serve uses watch✕
- Connections
- 1 pair of types, where a type in serve uses a type in watch.
- The types involved
trunk.serve.ServeSystem→trunk.watch.WatchSystem
- Direction
- serve uses watch, so a change to watch can break serve, while a change to serve can't break watch.
- Position
- Below the diagonal: serve 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 — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 42 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 18 | Medium |
| A07:2025 — Authentication Failures | 4 | High / Critical |
Roadmap
Immediately resolve the leaked secret in REDACTED and remove the single yanked dependency to secure the codebase. Strengthen system resilience by enforcing request timeouts on all HTTP clients and adding retry logic for transient failures. Finally, establish architectural decision records and enable automated dependency scanning tools to maintain long-term hygiene.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED. | +7.1 pts | Low | REDACTED Scanning |
| Resolve the 1 Yanked release finding(s) in Dependency Hygiene. | +3.9 pts | Low | Dependency Hygiene |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +2.9 pts | Low | ADR Quality |
| Give every client a whole-request bound: `reqwest::Client::builder().timeout(Duration::from_secs(10))` (never `reqwest::get` or `Client::new()`, which have none), ureq's `timeout_global`, or wrap the call in `tokio::time::timeout`; add retry with back-off (`reqwest-retry`'s `RetryTransientMiddleware`, `backoff`) around dependencies that fail. | +4.0 pts | Medium | Outbound HTTP resilience |
| Enable Dependabot/Renovate or a dependency-review gate. | +2.8 pts | Medium | Security & performance tooling |
| 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. | +2.6 pts | Medium | Architecture documentation |
| Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it. | +1.8 pts | Medium | Deployment & Rollback |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +1.8 pts | Medium | Release Hygiene |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 3.7 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.6 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.9 | Mixed | Dependency Vulnerabilities: Medium CVE: REDACTED |
| REDACTED | 6.1 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| src/pipelines/rust/mod.rs | 7.0 | Near-clean | Cyclomatic Complexity: RustApp::cargo_build (cyclomatic 18) |
| src/pipelines/tailwind_css.rs | 7.2 | Near-clean | Code Duplication: Duplicated block (20 lines × 2) |
| src/pipelines/css.rs | 7.2 | Near-clean | Code Duplication: Duplicated block (15 lines × 2) |
| src/tools.rs | 7.4 | Near-clean | Cyclomatic Complexity: Application::url (cyclomatic 25) |
| src/pipelines/sass.rs | 7.4 | Near-clean | Code Duplication: Duplicated block (21–22 lines × 2) |
| src/proxy.rs | 7.8 | Near-clean | Cyclomatic Complexity: ProxyHandlerWebSocket::proxy_ws_request (cyclomatic 21) |
| REDACTED | 7.9 | Near-clean | Static Analysis (SAST): Medium: REDACTED |
| examples/seed/src/main.rs | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/serve/mod.rs | 8.5 | Near-clean | Cognitive Complexity: trunk::serve::show_listening (cognitive 33) |
| guide/theme/pagetoc.js | 8.5 | Near-clean | Cognitive Complexity: pagetoc.updateFunction (cognitive 21) |
| src/ws.rs | 8.5 | Near-clean | Cognitive Complexity: trunk::ws::handle_ws (cognitive 16) |
| src/common/html_rewrite.rs | 8.5 | Near-clean | Code Duplication: Duplicated block (9 lines × 2) |
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. 62 of 62 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
What we checked — 62 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, 134 of 164 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 · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ 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.
- 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 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (Cargo.toml), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
- 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.
- AX6 Interface segregation — 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 is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing 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.
- AXR1 Runtime accessibility — 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. Render strategy: boot via ToolchainServer (.). the service exited before it opened a port — `cargo run --locked --bin 'trunk' -- serve`: Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.16s Running `target/debug/trunk serve` 2026-10-28T14:30:10.916394Z INFO 🚀 Starting trunk 0.22.0 2026-10-28T14:30:10.917255Z WARN…; runtime evidence skipped (launch chosen because 'axum' dependency in Cargo.toml, binary 'trunk', started with its 'serve' subcommand).
- 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.
- X4 Structured logging — 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. 40 further occurrence(s) are not listed individually; the score already reflects all 80.
- X5 Nullable reference types — 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 and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's Rust 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.
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.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D11 Test Reliability: Flakiness is inferred from history/markers — Watchdog runs the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- 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 REDACTED Scanning: REDACTED 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.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- 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.
- 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.
- M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
4 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was Application::url at 25.
What to do
- Bring the 4 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with Application::url (cyclomatic 25), ProxyHandlerWebSocket::proxy_ws_request (cyclomatic 21), RustApp::cargo_build (cyclomatic 18). — 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 4 together lifts Cyclomatic Complexity from 9.1 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- 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
9 method(s) exceeded the cognitive complexity threshold of 15; the worst was trunk::serve::show_listening at 33.
What to do
- Bring the 9 bodies over 15 down to 15 or less in Cognitive Complexity — start with trunk::serve::show_listening (cognitive 33), pagetoc.updateFunction (cognitive 21), updateFunction (cognitive 21). — 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 9 together lifts Cognitive Complexity from 8.4 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- 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 god class(es) detected.
What to do
- Resolve the 2 MethodTooLong finding(s) in God Classes — start with mod.rs (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 FileTooLong finding(s) in God Classes — start with mod.rs, tools.rs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 ClassTooLong finding(s) in God Classes — start with mod.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
13 duplicated block group(s) detected.
What to do
- Resolve the 2 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with html_rewrite.rs, tailwind_css.rs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Duplicated block (21–22 lines × 2) finding(s) in Code Duplication — start with sass.rs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (20 lines × 2) finding(s) in Code Duplication — start with tailwind_css.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.
D6 · Cohesion (LCOM4)
0 of 37 classes have LCOM4 above 3.
D9 · Test Distribution
53 test methods: 53 unit, 0 integration, 0 BDD, 0 e2e. The Rust suite contributes 53 `#[test]` function(s) across 17 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.
D11 · Test Reliability
0 flaky across 1 measured tier(s). Rust (repository root, 17 test files): measured (0 flaky).
D12 · Dependency Hygiene
10 outdated, 1 yanked direct Cargo dependencies. 73 of 87 direct crates were graded against crates.io (0 not published there, 14 not resolved by a committed REDACTED). 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.
What to do
- Resolve the 1 Yanked release finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D13 · REDACTED Scanning
1 secret(s) detected.
What to do
- Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Enforce REDACTED Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D14 · License Compliance
0 of 585 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. This repository publishes itself under MIT/Apache-2.0, which is its own choice and is not judged here.
D15 · Churn × Complexity Hotspots
Top hotspots: src/pipelines/rust/mod.rs (2×16=32)
What to do
- Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with mod.rs. — One of this dimension's main actionable groups (1 warning-level).
D16 · Bus Factor
2 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/tls.rs. Counted over 44 of the 74 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
1 deducted task-comment markers across 9955 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 1 TodoComment finding(s) in Explicit Debt — start with main.rs. — One of this dimension's main actionable groups (1 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
1 of 1 documentation facets pass in full. 3 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 1 build units (Cargo) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
2 finding(s): 0 critical, 2 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 2 REDACTED finding(s) in Secrets (history) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
42 finding(s): 0 critical, 36 high, 5 medium, 1 low. 24 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 3 file(s) — `REDACTED` (lines 1–7, lines 15–17, line 29, …), `REDACTED` (lines 1–7, line 8, lines 16–18, …), `site/templates/index.html` (lines 1–3, line 4, line 5, …) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 2 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
- No action in Static Analysis (SAST) — all 24 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 (24 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
5 finding(s): 0 critical, 0 high, 5 medium, 0 low.
What to do
- 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).
- Resolve the 2 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
D31 · IaC & Container Security
trivy and checkov found no infrastructure-as-code or container misconfigurations.
D34 · Knowledge Freshness
2 of 44 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/pipelines/inline.rs. Counted over 44 of the 74 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 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.
Frontend & cross-cutting dimensions
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
- 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 5 of 20 project(s) that lack one — worth up to 0.5 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
M4 · Documentation accuracy
P1 · CI/CD gates
P2 · Observability
What to do
- Consider OpenTelemetry tracing/metrics (opentelemetry with tracing-opentelemetry) and a health-check endpoint (a /health route on your axum/actix router) for operability.
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.
P4 · Deployment & Rollback
- The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
P7 · Outbound HTTP resilience
- `reqwest::get(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — src/pipelines/node_packages/mod.rs:72
- `Client::builder()` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — src/pipelines/node_packages/node_package_client.rs:15
- `reqwest::ClientBuilder::new(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — src/serve/proxy.rs:130
- `reqwest::Client::builder(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — src/version/enabled/mod.rs:86
What to do
- Give every client a whole-request bound: `reqwest::Client::builder().timeout(Duration::from_secs(10))` (never `reqwest::get` or `Client::new()`, which have none), ureq's `timeout_global`, or wrap the call in `tokio::time::timeout`; add retry with back-off (`reqwest-retry`'s `RetryTransientMiddleware`, `backoff`) around dependencies that fail.
PF3 · Async & latency hygiene
S1 · Web-Security Posture
- No handler of this repository's Rust server answers 400, 413 or 422 (`StatusCode::BAD_REQUEST`, `HttpResponse::BadRequest()`, `Status::BadRequest`, tonic `Status::invalid_argument`), and nothing declares validation — no `validator`/`garde` derive, no body limit (`DefaultBodyLimit::max`, `RequestBodyLimitLayer`, `JsonConfig::default().limit(…)`, Rocket `Limits`) — nothing shows inbound requests being checked, and refused, before a handler acts on them. A check that answers its failure with 200 and an error body is not seen. (−2.0 on this card.) The server: `axum_server::from_tcp_rustls(` (src/serve/mod.rs:330).
What to do
- Validate what the server reads from a request — path, query, headers, body size and shape — and answer what fails with 400 (413 for an oversized body) before a handler acts on it: derive `validator::Validate` (or `garde::Validate`) on the request types and reject with `StatusCode::BAD_REQUEST`, and cap bodies with `DefaultBodyLimit::max`/`RequestBodyLimitLayer` or actix's `JsonConfig::default().limit(…)`.
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
X2 · Cancellation propagation
- Only 0/1 async functions that make a cancellable request (fetch, axios, ky, ofetch) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
- `__trunkInitializer` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — src/pipelines/rust/initializer.js:1
What to do
- Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
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
X4 · Structured logging
- `info!` at line 71 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/build.rs:71
- `info!` at line 77 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/build.rs:77
- `error!` at line 132 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/build.rs:132
- `info!` at line 31 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/hooks.rs:31
- `info!` at line 45 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/hooks.rs:45
- `info!` at line 85 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/main.rs:85
- `error!` at line 94 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/main.rs:94
- `info!` at line 96 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/main.rs:96
- `error!` at line 320 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/proxy.rs:320
- `error!` at line 354 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/proxy.rs:354
- `debug!` at line 338 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/tools.rs:338
- `debug!` at line 351 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/tools.rs:351
- `debug!` at line 385 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/tools.rs:385
- `debug!` at line 414 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/tools.rs:414
- `debug!` at line 422 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/tools.rs:422
- `info!` at line 436 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/tools.rs:436
- `info!` at line 473 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/tools.rs:473
- `warn!` at line 487 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/tools.rs:487
- `debug!` at line 768 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/tools.rs:768
- `warn!` at line 822 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/tools.rs:822
- `debug!` at line 118 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/watch.rs:118
- `debug!` at line 226 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/watch.rs:226
- `error!` at line 239 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/watch.rs:239
- `trace!` at line 249 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/watch.rs:249
- `debug!` at line 309 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/watch.rs:309
- `warn!` at line 319 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/watch.rs:319
- `warn!` at line 325 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/watch.rs:325
- `info!` at line 369 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/watch.rs:369
- `debug!` at line 36 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/ws.rs:36
- `debug!` at line 46 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. (×2) — src/ws.rs:46, src/version/enabled/mod.rs:46
- `debug!` at line 49 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/ws.rs:49
- `trace!` at line 68 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/ws.rs:68
- `trace!` at line 83 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/ws.rs:83
- `info!` at line 88 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/ws.rs:88
- `debug!` at line 6 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/version/enforce.rs:6
- `debug!` at line 14 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/version/enforce.rs:14
- `debug!` at line 42 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/version/enabled/mod.rs:42
- `debug!` at line 73 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/version/enabled/mod.rs:73
- `info!` at line 76 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/version/enabled/mod.rs:76
What to do
- Interpolated log message defeats structured logging
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 65% | Adequate — gated by X4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 83% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 62% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 50% | Adequate — gated by P7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 67% | Adequate — gated by D29, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 56 check(s) not relevant to this codebase
- AC1 Text alternatives — Frontend below the scale floor (4 DOM element(s) < 25) — too little surface to assess accessibility.
- AC2 Forms & labels — Frontend below the scale floor (4 DOM element(s) < 25) — too little surface to assess accessibility.
- AC3 Page structure — Frontend below the scale floor (4 DOM element(s) < 25) — too little surface to assess accessibility.
- AC4 Keyboard semantics — Frontend below the scale floor (4 DOM element(s) < 25) — too little surface to assess accessibility.
- AC5 ARIA correctness — Frontend below the scale floor (4 DOM element(s) < 25) — too little surface to assess accessibility.
- AC6 Visual & motion safety — Frontend below the scale floor (4 DOM element(s) < 25) — too little surface to assess accessibility.
- AC7 A11y enforcement — Frontend below the scale floor (4 DOM element(s) < 25) — too little surface to assess accessibility.
- AX1 Captive dependencies — Not applicable: this repository's JavaScript 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; 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.
- 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 — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the service exited before it opened a port — `cargo run --locked --bin 'trunk' -- serve`: Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.16s Running `target/debug/trunk serve` 2026-10-28T14:30:10.916394Z INFO 🚀 Starting trunk 0.22.0 2026-10-28T14:30:10.917255Z WARN…; runtime evidence skipped (launch chosen because 'axum' dependency in Cargo.toml, binary 'trunk', started with its 'serve' subcommand) This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- 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 — ~2280 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.
- 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 not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- 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, 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.
- 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.
- D5 Coupling — Not applicable — this Cargo build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- 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
- 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'.
- 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.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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.
- X5 Nullable reference types — 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
- 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 — 39 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 56 finding(s)
- Outbound HTTP without resilience src/pipelines/node_packages/mod.rs:72
- Outbound HTTP without resilience src/pipelines/node_packages/node_package_client.rs:15
- Outbound HTTP without resilience src/serve/proxy.rs:130
- Outbound HTTP without resilience src/version/enabled/mod.rs:86
- trunk::serve::show_listening (cognitive 33) src/serve/mod.rs:210
- trunk::proxy::make_outbound_request (cognitive 18) src/proxy.rs:87
- trunk::ws::handle_ws (cognitive 16) src/ws.rs:25
- RustApp::cargo_build (cognitive 18) src/pipelines/rust/mod.rs:406
- RustApp::wasm_bindgen_build (cognitive 18) src/pipelines/rust/mod.rs:543
- RustApp::new (cognitive 16) src/pipelines/rust/mod.rs:131
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- RustApp::cargo_build (cyclomatic 18) src/pipelines/rust/mod.rs:406
- RustApp::wasm_bindgen_build (cyclomatic 16) src/pipelines/rust/mod.rs:543
- REDACTED
- REDACTED
- MethodTooLong: RustApp.wasm_bindgen_build src/pipelines/rust/mod.rs:543
- MethodTooLong: RustApp.new src/pipelines/rust/mod.rs:131
- FileTooLong: rust/mod.rs src/pipelines/rust/mod.rs
- FileTooLong: src/tools.rs src/tools.rs
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (9 lines × 2) src/common/html_rewrite.rs:65
- Duplicated block (9 lines × 2) src/pipelines/tailwind_css.rs:86
- Application::url (cyclomatic 25) src/tools.rs:116
- ProxyHandlerWebSocket::proxy_ws_request (cyclomatic 21) src/proxy.rs:306
- Yanked release: tokio
- Hotspot: src/pipelines/rust/mod.rs src/pipelines/rust/mod.rs:543
- TodoComment examples/seed/src/main.rs:52
- pagetoc.updateFunction (cognitive 21) guide/theme/pagetoc.js:61
- Application::url (cognitive 16) src/tools.rs:116
- ClassTooLong: RustApp src/pipelines/rust/mod.rs:45
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (21–22 lines × 2) src/pipelines/sass.rs:141
- Duplicated block (20 lines × 2) src/pipelines/tailwind_css.rs:53
- Duplicated block (18–19 lines × 3) src/pipelines/sass.rs:147
- Duplicated block (19 lines × 2) src/pipelines/tailwind_css.rs:95
- Duplicated block (15 lines × 2) src/pipelines/css.rs:48
- Duplicated block (13 lines × 2) src/pipelines/sass.rs:213
- Duplicated block (12 lines × 2) src/pipelines/tailwind_css.rs:199
- Duplicated block (10 lines × 3) src/pipelines/css.rs:79
- Duplicated block (8 lines × 2) src/pipelines/css.rs:94
- Duplicated block (5 lines × 2) src/cmd/serve.rs:148
- Duplicated block (8 lines × 3) src/pipelines/css.rs:94
- Async function without AbortSignal: __trunkInitializer src/pipelines/rust/initializer.js:1
Minor — 59 finding(s)
- Interpolated log message defeats structured logging src/build.rs:71
- Interpolated log message defeats structured logging src/build.rs:77
- Interpolated log message defeats structured logging src/build.rs:132
- Interpolated log message defeats structured logging src/hooks.rs:31
- Interpolated log message defeats structured logging src/hooks.rs:45
- Interpolated log message defeats structured logging src/main.rs:85
- Interpolated log message defeats structured logging src/main.rs:94
- Interpolated log message defeats structured logging src/main.rs:96
- Interpolated log message defeats structured logging src/proxy.rs:320
- Interpolated log message defeats structured logging src/proxy.rs:354
- Interpolated log message defeats structured logging src/tools.rs:338
- Interpolated log message defeats structured logging src/tools.rs:351
- Interpolated log message defeats structured logging src/tools.rs:385
- Interpolated log message defeats structured logging src/tools.rs:414
- Interpolated log message defeats structured logging src/tools.rs:422
- Interpolated log message defeats structured logging src/tools.rs:436
- Interpolated log message defeats structured logging src/tools.rs:473
- Interpolated log message defeats structured logging src/tools.rs:487
- Interpolated log message defeats structured logging src/tools.rs:768
- Interpolated log message defeats structured logging src/tools.rs:822
- Interpolated log message defeats structured logging src/watch.rs:118
- Interpolated log message defeats structured logging src/watch.rs:226
- Interpolated log message defeats structured logging src/watch.rs:239
- Interpolated log message defeats structured logging src/watch.rs:249
- Interpolated log message defeats structured logging src/watch.rs:309
- Orphaned file src/pipelines/inline.rs:1
- Orphaned file src/hooks.rs:1
- Off-boarding risk: anonymized user #1
- No ADRs found
- Projects may be oversized for their cohesion
- REDACTED
- REDACTED
- Orphaned files with no living knowledge
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- No release approval gate
- No changelog
- No inbound request validation detected
- Not all async functions that make a request accept an AbortSignal
Minor — 10 finding(s)
- Outdated: globset
- Outdated: lol_html
- Outdated: notify
- Outdated: open
- Outdated: swc_ecma_codegen
- Outdated: swc_ecma_minifier
- Outdated: swc_ecma_parser
- Outdated: swc_ecma_transforms_base
- Outdated: uuid
- Outdated: zip
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-5dee002a60604ba3b30b818ee30d64a3/history.json --exit-code 0 --source . | 2 | 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-5dee002a60604ba3b30b818ee30d64a3/tree.json --exit-code 0 --source . | 1 | 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 . | 42 | 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 . | 5 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 0 | artifacts/raw/trivy-config.json |
| 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 |