Executive summary
svenstaro/genact falls short of our standard for production because its Testing dimensions are rated Critical, and the project has no automated tests. It scores 57 out of 100, which alone would earn Adequate, but it is rated Weak: a rating can't sit more than one step above its weakest group.
Production Readiness, at 38, is the weakest lens and counts most in the score. The best first step is adding automated tests, worth about 16 points. Recording design decisions is another step, worth about 9 points. Raising Production Readiness to 70 would lift the score to about 68.
Fifteen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Three secrets can leak from the build pipeline, and one automatic update takes new releases before a bad one can be spotted. Pinning each tool to an exact version, limiting each secret to its own step and setting a waiting period for automatic updates would close these risks. The pipeline step that installs packages without pinning their versions needs the packages it installs pinned to exact versions. The unsafe setting in infrastructure or container files needs changing to safe values.
The product code is 3,383 lines, about €3,500 to rebuild.
If Production Readiness rose from 38 to 70, the lowest score rated Strong, the score would rise from 57 to about 68.
New since the last survey: 6 findings
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
Fixed since the last survey: 2 findings
- Supply-chain Provenance & Signing · Unpinned build actions
- Supply-chain Provenance & Signing REDACTED
Rebuild cost: about €3,500 · Estimate
| Cost to rebuild | €1,100 to €5,800, for 19 to 61 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 57. 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: 3,383 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 args | 2 generators | 3 io | 4 main | 5 genact | 6 modules | 7 modules.ansible | 8 modules.bootlog | 9 modules.botnet | 10 modules.bruteforce | 11 modules.cargo | 12 modules.cc | 13 modules.composer | 14 modules.cryptomining | 15 modules.docker_build | 16 modules.docker_image_rm | 17 modules.download | 18 modules.julia | 19 modules.kernel_compile | 20 modules.memdump | 21 modules.mkinitcpio | 22 modules.rkhunter | 23 modules.simcity | 24 modules.terraform | 25 modules.uv | 26 modules.weblog | 27 modules.wpt |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 args | |||||||||||||||||||||||||||
| 2 generators | |||||||||||||||||||||||||||
| 3 io | |||||||||||||||||||||||||||
| 4 main | |||||||||||||||||||||||||||
| 5 genact | 1 | ||||||||||||||||||||||||||
| 6 modules | 1 | ||||||||||||||||||||||||||
| 7 modules.ansible | 1 | 1 | |||||||||||||||||||||||||
| 8 modules.bootlog | 1 | 1 | |||||||||||||||||||||||||
| 9 modules.botnet | 1 | 1 | |||||||||||||||||||||||||
| 10 modules.bruteforce | 1 | 1 | |||||||||||||||||||||||||
| 11 modules.cargo | 1 | 1 | |||||||||||||||||||||||||
| 12 modules.cc | 1 | 1 | |||||||||||||||||||||||||
| 13 modules.composer | 1 | 1 | |||||||||||||||||||||||||
| 14 modules.cryptomining | 1 | 1 | |||||||||||||||||||||||||
| 15 modules.docker_build | 1 | 1 | |||||||||||||||||||||||||
| 16 modules.docker_image_rm | 1 | 1 | |||||||||||||||||||||||||
| 17 modules.download | 1 | 1 | |||||||||||||||||||||||||
| 18 modules.julia | 1 | 1 | |||||||||||||||||||||||||
| 19 modules.kernel_compile | 1 | 1 | |||||||||||||||||||||||||
| 20 modules.memdump | 1 | 1 | |||||||||||||||||||||||||
| 21 modules.mkinitcpio | 2 | 1 | |||||||||||||||||||||||||
| 22 modules.rkhunter | 1 | 1 | |||||||||||||||||||||||||
| 23 modules.simcity | 1 | 1 | |||||||||||||||||||||||||
| 24 modules.terraform | 1 | 1 | |||||||||||||||||||||||||
| 25 modules.uv | 1 | 1 | |||||||||||||||||||||||||
| 26 modules.weblog | 1 | 1 | |||||||||||||||||||||||||
| 27 modules.wpt | 1 | 1 |
5→1 genact uses args✕
- Connections
- 1 pair of types, where a type in genact uses a type in args.
- The types involved
genact.genact$module→genact.args.AppConfig
- Direction
- genact uses args, so a change to args can break genact, while a change to genact can't break args.
- Position
- Below the diagonal: genact uses a module listed above it, which is the healthy direction.
6→1 modules uses args✕
- Connections
- 1 pair of types, where a type in modules uses a type in args.
- The types involved
genact.modules.Module→genact.args.AppConfig
- Direction
- modules uses args, so a change to args can break modules, while a change to modules can't break args.
- Position
- Below the diagonal: modules uses a module listed above it, which is the healthy direction.
7→1 modules.ansible uses args✕
- Connections
- 1 pair of types, where a type in modules.ansible uses a type in args.
- The types involved
genact.modules.ansible.Ansible→genact.args.AppConfig
- Direction
- modules.ansible uses args, so a change to args can break modules.ansible, while a change to modules.ansible can't break args.
- Position
- Below the diagonal: modules.ansible uses a module listed above it, which is the healthy direction.
7→6 modules.ansible uses modules✕
- Connections
- 1 pair of types, where a type in modules.ansible uses a type in modules.
- The types involved
genact.modules.ansible.Ansible→genact.modules.Module
- Direction
- modules.ansible uses modules, so a change to modules can break modules.ansible, while a change to modules.ansible can't break modules.
- Position
- Below the diagonal: modules.ansible uses a module listed above it, which is the healthy direction.
8→1 modules.bootlog uses args✕
- Connections
- 1 pair of types, where a type in modules.bootlog uses a type in args.
- The types involved
genact.modules.bootlog.Bootlog→genact.args.AppConfig
- Direction
- modules.bootlog uses args, so a change to args can break modules.bootlog, while a change to modules.bootlog can't break args.
- Position
- Below the diagonal: modules.bootlog uses a module listed above it, which is the healthy direction.
8→6 modules.bootlog uses modules✕
- Connections
- 1 pair of types, where a type in modules.bootlog uses a type in modules.
- The types involved
genact.modules.bootlog.Bootlog→genact.modules.Module
- Direction
- modules.bootlog uses modules, so a change to modules can break modules.bootlog, while a change to modules.bootlog can't break modules.
- Position
- Below the diagonal: modules.bootlog uses a module listed above it, which is the healthy direction.
9→1 modules.botnet uses args✕
- Connections
- 1 pair of types, where a type in modules.botnet uses a type in args.
- The types involved
genact.modules.botnet.Botnet→genact.args.AppConfig
- Direction
- modules.botnet uses args, so a change to args can break modules.botnet, while a change to modules.botnet can't break args.
- Position
- Below the diagonal: modules.botnet uses a module listed above it, which is the healthy direction.
9→6 modules.botnet uses modules✕
- Connections
- 1 pair of types, where a type in modules.botnet uses a type in modules.
- The types involved
genact.modules.botnet.Botnet→genact.modules.Module
- Direction
- modules.botnet uses modules, so a change to modules can break modules.botnet, while a change to modules.botnet can't break modules.
- Position
- Below the diagonal: modules.botnet uses a module listed above it, which is the healthy direction.
10→1 modules.bruteforce uses args✕
- Connections
- 1 pair of types, where a type in modules.bruteforce uses a type in args.
- The types involved
genact.modules.bruteforce.Bruteforce→genact.args.AppConfig
- Direction
- modules.bruteforce uses args, so a change to args can break modules.bruteforce, while a change to modules.bruteforce can't break args.
- Position
- Below the diagonal: modules.bruteforce uses a module listed above it, which is the healthy direction.
10→6 modules.bruteforce uses modules✕
- Connections
- 1 pair of types, where a type in modules.bruteforce uses a type in modules.
- The types involved
genact.modules.bruteforce.Bruteforce→genact.modules.Module
- Direction
- modules.bruteforce uses modules, so a change to modules can break modules.bruteforce, while a change to modules.bruteforce can't break modules.
- Position
- Below the diagonal: modules.bruteforce uses a module listed above it, which is the healthy direction.
11→1 modules.cargo uses args✕
- Connections
- 1 pair of types, where a type in modules.cargo uses a type in args.
- The types involved
genact.modules.cargo.Cargo→genact.args.AppConfig
- Direction
- modules.cargo uses args, so a change to args can break modules.cargo, while a change to modules.cargo can't break args.
- Position
- Below the diagonal: modules.cargo uses a module listed above it, which is the healthy direction.
11→6 modules.cargo uses modules✕
- Connections
- 1 pair of types, where a type in modules.cargo uses a type in modules.
- The types involved
genact.modules.cargo.Cargo→genact.modules.Module
- Direction
- modules.cargo uses modules, so a change to modules can break modules.cargo, while a change to modules.cargo can't break modules.
- Position
- Below the diagonal: modules.cargo uses a module listed above it, which is the healthy direction.
12→1 modules.cc uses args✕
- Connections
- 1 pair of types, where a type in modules.cc uses a type in args.
- The types involved
genact.modules.cc.Cc→genact.args.AppConfig
- Direction
- modules.cc uses args, so a change to args can break modules.cc, while a change to modules.cc can't break args.
- Position
- Below the diagonal: modules.cc uses a module listed above it, which is the healthy direction.
12→6 modules.cc uses modules✕
- Connections
- 1 pair of types, where a type in modules.cc uses a type in modules.
- The types involved
genact.modules.cc.Cc→genact.modules.Module
- Direction
- modules.cc uses modules, so a change to modules can break modules.cc, while a change to modules.cc can't break modules.
- Position
- Below the diagonal: modules.cc uses a module listed above it, which is the healthy direction.
13→1 modules.composer uses args✕
- Connections
- 1 pair of types, where a type in modules.composer uses a type in args.
- The types involved
genact.modules.composer.Composer→genact.args.AppConfig
- Direction
- modules.composer uses args, so a change to args can break modules.composer, while a change to modules.composer can't break args.
- Position
- Below the diagonal: modules.composer uses a module listed above it, which is the healthy direction.
13→6 modules.composer uses modules✕
- Connections
- 1 pair of types, where a type in modules.composer uses a type in modules.
- The types involved
genact.modules.composer.Composer→genact.modules.Module
- Direction
- modules.composer uses modules, so a change to modules can break modules.composer, while a change to modules.composer can't break modules.
- Position
- Below the diagonal: modules.composer uses a module listed above it, which is the healthy direction.
14→1 modules.cryptomining uses args✕
- Connections
- 1 pair of types, where a type in modules.cryptomining uses a type in args.
- The types involved
genact.modules.cryptomining.Crytomining→genact.args.AppConfig
- Direction
- modules.cryptomining uses args, so a change to args can break modules.cryptomining, while a change to modules.cryptomining can't break args.
- Position
- Below the diagonal: modules.cryptomining uses a module listed above it, which is the healthy direction.
14→6 modules.cryptomining uses modules✕
- Connections
- 1 pair of types, where a type in modules.cryptomining uses a type in modules.
- The types involved
genact.modules.cryptomining.Crytomining→genact.modules.Module
- Direction
- modules.cryptomining uses modules, so a change to modules can break modules.cryptomining, while a change to modules.cryptomining can't break modules.
- Position
- Below the diagonal: modules.cryptomining uses a module listed above it, which is the healthy direction.
15→1 modules.docker_build uses args✕
- Connections
- 1 pair of types, where a type in modules.docker_build uses a type in args.
- The types involved
genact.modules.docker_build.DockerBuild→genact.args.AppConfig
- Direction
- modules.docker_build uses args, so a change to args can break modules.docker_build, while a change to modules.docker_build can't break args.
- Position
- Below the diagonal: modules.docker_build uses a module listed above it, which is the healthy direction.
15→6 modules.docker_build uses modules✕
- Connections
- 1 pair of types, where a type in modules.docker_build uses a type in modules.
- The types involved
genact.modules.docker_build.DockerBuild→genact.modules.Module
- Direction
- modules.docker_build uses modules, so a change to modules can break modules.docker_build, while a change to modules.docker_build can't break modules.
- Position
- Below the diagonal: modules.docker_build uses a module listed above it, which is the healthy direction.
16→1 modules.docker_image_rm uses args✕
- Connections
- 1 pair of types, where a type in modules.docker_image_rm uses a type in args.
- The types involved
genact.modules.docker_image_rm.DockerImageRm→genact.args.AppConfig
- Direction
- modules.docker_image_rm uses args, so a change to args can break modules.docker_image_rm, while a change to modules.docker_image_rm can't break args.
- Position
- Below the diagonal: modules.docker_image_rm uses a module listed above it, which is the healthy direction.
16→6 modules.docker_image_rm uses modules✕
- Connections
- 1 pair of types, where a type in modules.docker_image_rm uses a type in modules.
- The types involved
genact.modules.docker_image_rm.DockerImageRm→genact.modules.Module
- Direction
- modules.docker_image_rm uses modules, so a change to modules can break modules.docker_image_rm, while a change to modules.docker_image_rm can't break modules.
- Position
- Below the diagonal: modules.docker_image_rm uses a module listed above it, which is the healthy direction.
17→1 modules.download uses args✕
- Connections
- 1 pair of types, where a type in modules.download uses a type in args.
- The types involved
genact.modules.download.Download→genact.args.AppConfig
- Direction
- modules.download uses args, so a change to args can break modules.download, while a change to modules.download can't break args.
- Position
- Below the diagonal: modules.download uses a module listed above it, which is the healthy direction.
17→6 modules.download uses modules✕
- Connections
- 1 pair of types, where a type in modules.download uses a type in modules.
- The types involved
genact.modules.download.Download→genact.modules.Module
- Direction
- modules.download uses modules, so a change to modules can break modules.download, while a change to modules.download can't break modules.
- Position
- Below the diagonal: modules.download uses a module listed above it, which is the healthy direction.
18→1 modules.julia uses args✕
- Connections
- 1 pair of types, where a type in modules.julia uses a type in args.
- The types involved
genact.modules.julia.Julia→genact.args.AppConfig
- Direction
- modules.julia uses args, so a change to args can break modules.julia, while a change to modules.julia can't break args.
- Position
- Below the diagonal: modules.julia uses a module listed above it, which is the healthy direction.
18→6 modules.julia uses modules✕
- Connections
- 1 pair of types, where a type in modules.julia uses a type in modules.
- The types involved
genact.modules.julia.Julia→genact.modules.Module
- Direction
- modules.julia uses modules, so a change to modules can break modules.julia, while a change to modules.julia can't break modules.
- Position
- Below the diagonal: modules.julia uses a module listed above it, which is the healthy direction.
19→1 modules.kernel_compile uses args✕
- Connections
- 1 pair of types, where a type in modules.kernel_compile uses a type in args.
- The types involved
genact.modules.kernel_compile.KernelCompile→genact.args.AppConfig
- Direction
- modules.kernel_compile uses args, so a change to args can break modules.kernel_compile, while a change to modules.kernel_compile can't break args.
- Position
- Below the diagonal: modules.kernel_compile uses a module listed above it, which is the healthy direction.
19→6 modules.kernel_compile uses modules✕
- Connections
- 1 pair of types, where a type in modules.kernel_compile uses a type in modules.
- The types involved
genact.modules.kernel_compile.KernelCompile→genact.modules.Module
- Direction
- modules.kernel_compile uses modules, so a change to modules can break modules.kernel_compile, while a change to modules.kernel_compile can't break modules.
- Position
- Below the diagonal: modules.kernel_compile uses a module listed above it, which is the healthy direction.
20→1 modules.memdump uses args✕
- Connections
- 1 pair of types, where a type in modules.memdump uses a type in args.
- The types involved
genact.modules.memdump.Memdump→genact.args.AppConfig
- Direction
- modules.memdump uses args, so a change to args can break modules.memdump, while a change to modules.memdump can't break args.
- Position
- Below the diagonal: modules.memdump uses a module listed above it, which is the healthy direction.
20→6 modules.memdump uses modules✕
- Connections
- 1 pair of types, where a type in modules.memdump uses a type in modules.
- The types involved
genact.modules.memdump.Memdump→genact.modules.Module
- Direction
- modules.memdump uses modules, so a change to modules can break modules.memdump, while a change to modules.memdump can't break modules.
- Position
- Below the diagonal: modules.memdump uses a module listed above it, which is the healthy direction.
21→1 modules.mkinitcpio uses args✕
- Connections
- 2 pairs of types, where a type in modules.mkinitcpio uses a type in args.
- The types involved
genact.modules.mkinitcpio.Mkinitcpio→genact.args.AppConfiggenact.modules.mkinitcpio.mkinitcpio$module→genact.args.AppConfig
- Direction
- modules.mkinitcpio uses args, so a change to args can break modules.mkinitcpio, while a change to modules.mkinitcpio can't break args.
- Position
- Below the diagonal: modules.mkinitcpio uses a module listed above it, which is the healthy direction.
21→6 modules.mkinitcpio uses modules✕
- Connections
- 1 pair of types, where a type in modules.mkinitcpio uses a type in modules.
- The types involved
genact.modules.mkinitcpio.Mkinitcpio→genact.modules.Module
- Direction
- modules.mkinitcpio uses modules, so a change to modules can break modules.mkinitcpio, while a change to modules.mkinitcpio can't break modules.
- Position
- Below the diagonal: modules.mkinitcpio uses a module listed above it, which is the healthy direction.
22→1 modules.rkhunter uses args✕
- Connections
- 1 pair of types, where a type in modules.rkhunter uses a type in args.
- The types involved
genact.modules.rkhunter.RkHunter→genact.args.AppConfig
- Direction
- modules.rkhunter uses args, so a change to args can break modules.rkhunter, while a change to modules.rkhunter can't break args.
- Position
- Below the diagonal: modules.rkhunter uses a module listed above it, which is the healthy direction.
22→6 modules.rkhunter uses modules✕
- Connections
- 1 pair of types, where a type in modules.rkhunter uses a type in modules.
- The types involved
genact.modules.rkhunter.RkHunter→genact.modules.Module
- Direction
- modules.rkhunter uses modules, so a change to modules can break modules.rkhunter, while a change to modules.rkhunter can't break modules.
- Position
- Below the diagonal: modules.rkhunter uses a module listed above it, which is the healthy direction.
23→1 modules.simcity uses args✕
- Connections
- 1 pair of types, where a type in modules.simcity uses a type in args.
- The types involved
genact.modules.simcity.Simcity→genact.args.AppConfig
- Direction
- modules.simcity uses args, so a change to args can break modules.simcity, while a change to modules.simcity can't break args.
- Position
- Below the diagonal: modules.simcity uses a module listed above it, which is the healthy direction.
23→6 modules.simcity uses modules✕
- Connections
- 1 pair of types, where a type in modules.simcity uses a type in modules.
- The types involved
genact.modules.simcity.Simcity→genact.modules.Module
- Direction
- modules.simcity uses modules, so a change to modules can break modules.simcity, while a change to modules.simcity can't break modules.
- Position
- Below the diagonal: modules.simcity uses a module listed above it, which is the healthy direction.
24→1 modules.terraform uses args✕
- Connections
- 1 pair of types, where a type in modules.terraform uses a type in args.
- The types involved
genact.modules.terraform.Terraform→genact.args.AppConfig
- Direction
- modules.terraform uses args, so a change to args can break modules.terraform, while a change to modules.terraform can't break args.
- Position
- Below the diagonal: modules.terraform uses a module listed above it, which is the healthy direction.
24→6 modules.terraform uses modules✕
- Connections
- 1 pair of types, where a type in modules.terraform uses a type in modules.
- The types involved
genact.modules.terraform.Terraform→genact.modules.Module
- Direction
- modules.terraform uses modules, so a change to modules can break modules.terraform, while a change to modules.terraform can't break modules.
- Position
- Below the diagonal: modules.terraform uses a module listed above it, which is the healthy direction.
25→1 modules.uv uses args✕
- Connections
- 1 pair of types, where a type in modules.uv uses a type in args.
- The types involved
genact.modules.uv.Uv→genact.args.AppConfig
- Direction
- modules.uv uses args, so a change to args can break modules.uv, while a change to modules.uv can't break args.
- Position
- Below the diagonal: modules.uv uses a module listed above it, which is the healthy direction.
25→6 modules.uv uses modules✕
- Connections
- 1 pair of types, where a type in modules.uv uses a type in modules.
- The types involved
genact.modules.uv.Uv→genact.modules.Module
- Direction
- modules.uv uses modules, so a change to modules can break modules.uv, while a change to modules.uv can't break modules.
- Position
- Below the diagonal: modules.uv uses a module listed above it, which is the healthy direction.
26→1 modules.weblog uses args✕
- Connections
- 1 pair of types, where a type in modules.weblog uses a type in args.
- The types involved
genact.modules.weblog.Weblog→genact.args.AppConfig
- Direction
- modules.weblog uses args, so a change to args can break modules.weblog, while a change to modules.weblog can't break args.
- Position
- Below the diagonal: modules.weblog uses a module listed above it, which is the healthy direction.
26→6 modules.weblog uses modules✕
- Connections
- 1 pair of types, where a type in modules.weblog uses a type in modules.
- The types involved
genact.modules.weblog.Weblog→genact.modules.Module
- Direction
- modules.weblog uses modules, so a change to modules can break modules.weblog, while a change to modules.weblog can't break modules.
- Position
- Below the diagonal: modules.weblog uses a module listed above it, which is the healthy direction.
27→1 modules.wpt uses args✕
- Connections
- 1 pair of types, where a type in modules.wpt uses a type in args.
- The types involved
genact.modules.wpt.WPT→genact.args.AppConfig
- Direction
- modules.wpt uses args, so a change to args can break modules.wpt, while a change to modules.wpt can't break args.
- Position
- Below the diagonal: modules.wpt uses a module listed above it, which is the healthy direction.
27→6 modules.wpt uses modules✕
- Connections
- 1 pair of types, where a type in modules.wpt uses a type in modules.
- The types involved
genact.modules.wpt.WPT→genact.modules.Module
- Direction
- modules.wpt uses modules, so a change to modules can break modules.wpt, while a change to modules.wpt can't break modules.
- Position
- Below the diagonal: modules.wpt 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 | 20 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 5 | Medium |
| A02:2025 — Security Misconfiguration | 1 | High / Critical |
Roadmap
Begin by establishing automated test coverage and ensuring tests are properly distributed across the codebase. Next, document significant design decisions using Architecture Decision Records to preserve institutional knowledge. Finally, implement detailed logging and diagnostic trails to improve observability and enable effective bug reproduction.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No automated tests finding(s) in Code Coverage. | +15.5 pts | Low | Code Coverage |
| Resolve the 1 No tests found finding(s) in Test Distribution. | +15.5 pts | Low | Test Distribution |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +9.1 pts | Low | ADR Quality |
| 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. | +7.2 pts | Medium | Architecture documentation |
| Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce. | +7.1 pts | Medium | Observability |
| Resolve the 3 Orphaned file finding(s) in Knowledge Freshness — start with julia.rs, wpt.rs, terraform.rs. | +1.4 pts | Low | Knowledge Freshness |
| 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. | +2.4 pts | Medium | Deployment & Rollback |
| Keep implementation types off the public surface (Rust: `pub(crate)`, or keep the module private) so internals can change without breaking consumers. | +1.7 pts | Medium | Library API & versioning |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.9 | Mixed | Dependency Vulnerabilities: Medium advisory (unmaintained): REDACTED |
| src/modules/uv.rs | 7.2 | Mixed | Cyclomatic Complexity: Uv::run (cyclomatic 17) |
| src/modules/wpt.rs | 7.2 | Mixed | Cognitive Complexity: WPT::run (cognitive 45) |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Mixed | IaC & Container Security: High IaC: REDACTED |
| src/modules/simcity.rs | 7.8 | Mixed | Cyclomatic Complexity: Simcity::run (cyclomatic 18) |
| src/modules/julia.rs | 7.8 | Mixed | Code Duplication: Duplicated block (14 lines × 2) |
| src/modules/botnet.rs | 8.5 | Near-clean | Cognitive Complexity: Botnet::run (cognitive 24) |
| src/modules/bruteforce.rs | 8.5 | Near-clean | Cognitive Complexity: Bruteforce::run (cognitive 19) |
| src/modules/rkhunter.rs | 8.5 | Near-clean | Cognitive Complexity: RkHunter::run (cognitive 18) |
| src/modules/bootlog.rs | 8.5 | Near-clean | Cognitive Complexity: Bootlog::run (cognitive 17) |
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. 46 of 46 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.8 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
What we checked — 46 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, 50 of 62 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
- D16 Bus Factor — 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. Single-maintainer repository — bus factor is not applicable (35 contributor(s) across 1187 commit(s) sampled, automation and bot accounts excluded). One of them holds 83% of the history; the other 34 hold 0.5% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- D44 Platform End-of-Life — 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 dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
- 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.
- AXB1 Runtime evidence locked — no reproducible boot — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Subject: 1 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. Watchdog then boots it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
- 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 no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala 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.
- 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 no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala 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.
- M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9). Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- X12 Unreachable branch — 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 JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, 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.
- X13 Undrained process stream — 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 JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, 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.
- X16 Unfloored truncation loop — 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 JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala or Kotlin was found in this repository, 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.
- X17 Uncapped recursion over a caller-supplied document — 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 JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, 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.
- X18 Disposal-pattern correctness — 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 JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP was found in this repository, 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.
- X19 Unrestored process-global state — 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 JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala or PHP was found in this repository, 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.
- X22 Contradicted release guard — 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 Java, TypeScript/JavaScript, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded, 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.
- X23 Unguarded diagnostic materialisation — 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 JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin or PHP was found in this repository, 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.
- X24 Document value interpolated into markup unescaped — 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 JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, 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.
- X25 Inert configuration knob — 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 JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart and Ruby source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart or Ruby was found in this repository, 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.
- X3 Exception handling — 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 PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go and JavaScript/TypeScript source only, and no C# was loaded and no PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go, JavaScript or TypeScript was found in this repository, 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.
- 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.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside Watchdog's isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- 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.
- 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
2 function(s) exceeded the cyclomatic complexity threshold of 15; the worst was Simcity::run at 18. A further 1 function(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being Terraform::run at 18 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: src/modules/terraform.rs (Terraform::run at 18). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 2 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with Simcity::run (cyclomatic 18), Uv::run (cyclomatic 17). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cyclomatic Complexity from 9.7 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
8 function(s) exceeded the cognitive complexity threshold of 15; the worst was WPT::run at 45.
What to do
- Bring the 2 bodies over 30 down to 30 or less in Cognitive Complexity — start with WPT::run (cognitive 45), Uv::run (cognitive 31). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 6.3 to about 7.4/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
2 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 2 MethodTooLong finding(s) in God Classes — start with uv.rs, wpt.rs. — One of this dimension's main actionable groups (2 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
4 duplicated block group(s) detected.
What to do
- Resolve the 1 Duplicated block (16–17 lines × 2) finding(s) in Code Duplication — start with wpt.rs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (14 lines × 2) finding(s) in Code Duplication — start with julia.rs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with uv.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 1 classes have LCOM4 above 3.
D8 · Code Coverage
No automated tests — no test code was found in this repository.
What to do
- Resolve the 1 No automated tests finding(s) in Code Coverage. — One of this dimension's main actionable groups (1 issue-level).
- Enforce Code Coverage in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
No test suite found.
What to do
- Resolve the 1 No tests found finding(s) in Test Distribution. — One of this dimension's main actionable groups (1 recommendation-level).
D12 · Dependency Hygiene
2 outdated, 0 yanked direct Cargo dependencies. Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from REDACTED there.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 212 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, which is its own choice and is not judged here.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
0 deducted task-comment markers across 3383 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.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 2 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
0 of 1 build units (Cargo) flagged as possibly oversized/incoherent.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
20 finding(s): 0 critical, 20 high, 0 medium, 0 low. 15 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. Separately, one or more rules could not re-parse an embedded snippet in 1 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 (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 15 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 (15 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 4 Medium advisory (unmaintained) finding(s) in Dependency Vulnerabilities — start with REDACTED (4). — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 1 Medium advisory (unsound) finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D31 · IaC & Container Security
1 finding(s): 0 critical, 1 high, 0 medium, 0 low.
What to do
- Resolve the 1 High IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D34 · Knowledge Freshness
3 of 21 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/modules/julia.rs. Counted over 21 of the 28 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 3 Orphaned file finding(s) in Knowledge Freshness — start with julia.rs, wpt.rs, terraform.rs. — One of this dimension's main actionable groups (3 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
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.
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
What to do
- Add `#[cfg(test)] mod tests` blocks beside the code they cover — the attribute keeps them out of the release build, a stronger separation than a folder — reserve `tests/` for black-box integration tests, and run `cargo test` in CI.
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
- 24/27 types (89%) declared in the published library are public. For a library, every public type is a stability contract — keep implementation types off the surface and expose only the intended API.
What to do
- Keep implementation types off the public surface (Rust: `pub(crate)`, or keep the module private) so internals can change without breaking consumers.
P2 · Observability
- No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
What to do
- Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
P3 · Security & performance tooling
What to do
- Dependabot is configured but does not watch `github-actions` — add that `package-ecosystem` entry to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
- 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
PF3 · Async & latency hygiene
S1 · Web-Security Posture
- `https://cdn.jsdelivr.net/npm/xterm@4.19.0/lib/xterm.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. 2 such include(s) across the repository's markup. — index.html:13
What to do
- Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
X1 · Async correctness
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X21 · Side-effecting pattern guard
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X30 · Support guard that admits what it rejects
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 93% | Exemplary | Solid. |
| Architecture | 99% | Exemplary | Solid. |
| Maturity | 54% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 38% | Weak — gated by D8, D9, P2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 83% | Strong | Solid. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 3 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 2 observation(s) recorded · The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 69 check(s) not relevant to this codebase
- AC1 Text alternatives — Frontend below the scale floor (15 DOM element(s) < 25) — too little surface to assess accessibility.
- AC2 Forms & labels — Frontend below the scale floor (15 DOM element(s) < 25) — too little surface to assess accessibility.
- AC3 Page structure — Frontend below the scale floor (15 DOM element(s) < 25) — too little surface to assess accessibility.
- AC4 Keyboard semantics — Frontend below the scale floor (15 DOM element(s) < 25) — too little surface to assess accessibility.
- AC5 ARIA correctness — Frontend below the scale floor (15 DOM element(s) < 25) — too little surface to assess accessibility.
- AC6 Visual & motion safety — Frontend below the scale floor (15 DOM element(s) < 25) — too little surface to assess accessibility.
- AC7 A11y enforcement — Frontend below the scale floor (15 DOM element(s) < 25) — too little surface to assess accessibility.
- AX1 Captive dependencies — Not applicable: Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one.
- 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.
- 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
- AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — 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 — No tests were found in the analyzed repository to assess for quality.
- D11 Test Reliability — No test suite was found to re-run, so reliability couldn't be assessed. Two searches produced that zero and both came back empty: the classifier that reads the loaded workspace recognised no suite it could run, and a walk of the source on disk — which covers the JS/TS `*.test.*` and `*.spec.*` conventions and probes for a Pester suite — found no test source in any other ecosystem either. Neither search reaches a suite that is missing from the loaded workspace and carries no name either walk recognises, so this is 'no suite found by those two searches', not a verdict that the repository has none.
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- 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; Rust not measured.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .rs, 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.
- D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
- 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
- DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
- 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'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Rust source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `#[bench]`, criterion's `bench_function`/`bench_with_input`, `#[divan::bench]` or `#[library_benchmark]` in any `.rs` file, or criterion, divan, iai or a `[[bench]]` target in a Cargo.toml, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not applicable: Rust spells out every heap allocation and makes borrowed slices (&[T], &str) its ordinary parameter types, so the allocation-aware style this card rewards elsewhere is the language's baseline rather than a rung to climb.
- X12 Unreachable branch — 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
- X13 Undrained process stream — 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
- X16 Unfloored truncation loop — 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
- X17 Uncapped recursion over a caller-supplied document — 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
- X18 Disposal-pattern correctness — 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
- X19 Unrestored process-global state — 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
- X2 Cancellation propagation — no C# was loaded; this repository's Rust was read, and no request in it can be cancelled by a caller — a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X22 Contradicted release guard — 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
- X23 Unguarded diagnostic materialisation — 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
- X24 Document value interpolated into markup unescaped — 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
- X25 Inert configuration knob — 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
- 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. Not a gap in the analyzer and not a finding about your code.
- X3 Exception handling — 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
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Rust was read, and it logs through none: the `log` crate's macros take one finished message (as log4net does in C#; its `kv` values are an opt-in its backends mostly drop), `println!`/`eprintln!` are not loggers, or it makes no log call outside its tests and examples at all. Calls through `tracing` (`tracing::info!`, or `info!` imported from it) would be judged.
- 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.
- 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 — 22 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No automated tests
Serious — 26 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- MethodTooLong: Uv.run src/modules/uv.rs:40
- MethodTooLong: WPT.run src/modules/wpt.rs:30
- REDACTED
- REDACTED
- Simcity::run (cyclomatic 18) src/modules/simcity.rs:24
- Uv::run (cyclomatic 17) src/modules/uv.rs:40
- WPT::run (cognitive 45) src/modules/wpt.rs:30
- Uv::run (cognitive 31) src/modules/uv.rs:40
- Simcity::run (cognitive 29) src/modules/simcity.rs:24
- genact::modules::wpt::generate_stack_trace (cognitive 25) src/modules/wpt.rs:235
- Botnet::run (cognitive 24) src/modules/botnet.rs:22
- Bruteforce::run (cognitive 19) src/modules/bruteforce.rs:29
- RkHunter::run (cognitive 18) src/modules/rkhunter.rs:26
- Bootlog::run (cognitive 17) src/modules/bootlog.rs:24
- REDACTED
- REDACTED
- Duplicated block (16–17 lines × 2) src/modules/wpt.rs:266
- Duplicated block (14 lines × 2) src/modules/julia.rs:486
- Duplicated block (12 lines × 2) src/modules/uv.rs:76
- Duplicated block (9 lines × 2) src/modules/julia.rs:339
- No structured logging
- Third-party script without Subresource Integrity index.html:13
Minor — 12 finding(s)
- Orphaned file src/modules/julia.rs:1
- Orphaned file src/modules/wpt.rs:1
- Orphaned file src/modules/terraform.rs:1
- No ADRs found
- Orphaned files with no living knowledge
- No tests found
- No ADRs
- No architecture diagram/doc
- Large public API surface
- No release approval gate
- Duplicated predicate src/modules/bootlog.rs:36
- Silent fallback default on Err src/args.rs:135
Minor — 2 finding(s)
- Outdated: sha2
- Outdated: tokio
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-1bae8f7d1be4447f9bd8ac6d1e58f8a5/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-1bae8f7d1be4447f9bd8ac6d1e58f8a5/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 20 | 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 . | 1 | 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 |