Executive summary
ducaale/xh falls short of our standard for a preview release, in part because we found no recorded design decisions and no architecture document or diagram. It scores 63 out of 100 and is rated Adequate, and 15 of its 16 critical findings are security problems in the build pipeline.
Maturity, at 51, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 12 points. Having someone learn and document the five files no active contributor knows is another step, worth about 3 points. Raising Maturity to 62 would lift the score to about 68.
Thirteen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. One pipeline step puts outside input straight into a shell command, so an attacker can run commands in the build pipeline, and one secret can leak from the build pipeline. Pinning each tool to an exact version, passing outside input through environment variables and limiting the secret to its own step would close these risks.
The product code is 9,206 lines, about €17,000 to rebuild.
If Maturity rose from 51 to 62, the lowest score rated Strong, the score would rise from 63 to about 68.
New since the last survey: 13 findings
- Code Coverage · Low coverage: src/auth.rs src/auth.rs
- Code Coverage · Low coverage: src/download.rs src/download.rs
- Code Coverage · Low coverage: src/error_reporting.rs src/error_reporting.rs
- Code Coverage · Low coverage: src/formatting/headers.rs src/formatting/headers.rs
- Code Coverage · Low coverage: src/formatting/mod.rs src/formatting/mod.rs
- Code Coverage · Low coverage: src/formatting/palette.rs src/formatting/palette.rs
- Code Coverage · Low coverage: src/generation.rs src/generation.rs
- Code Coverage · Low coverage: src/main.rs src/main.rs
- Code Coverage · Low coverage: src/middleware.rs src/middleware.rs
- Code Coverage · Low coverage: src/printer.rs src/printer.rs
- Code Coverage · Low coverage: src/redirect.rs src/redirect.rs
- Code Coverage · Low coverage: src/session.rs src/session.rs
- Dependency Vulnerabilities · REDACTED
Fixed since the last survey: 1 finding
- Dependency Vulnerabilities · Medium vulnerability: [GHSA redacted] REDACTED
Rebuild cost: about €17,000 · Estimate
| Cost to rebuild | €5,600 to €28,000, for 93 to 294 hours of work, about 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.9 at a score of 63. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 9,206 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 content_disposition | 2 decoder | 3 download | 4 error_reporting | 5 message_signature | 6 nested_json | 7 netrc | 8 redacted | 9 utils | 10 buffer.imp | 11 request_items | 12 to_curl | 13 cli | 14 xh | 15 formatting | 16 formatting.headers | 17 generation | 18 formatting.palette.util | 19 printer | 20 middleware | 21 auth | 22 redirect | 23 session |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 content_disposition | |||||||||||||||||||||||
| 2 decoder | |||||||||||||||||||||||
| 3 download | |||||||||||||||||||||||
| 4 error_reporting | |||||||||||||||||||||||
| 5 message_signature | |||||||||||||||||||||||
| 6 nested_json | |||||||||||||||||||||||
| 7 netrc | |||||||||||||||||||||||
| 8 redacted | |||||||||||||||||||||||
| 9 utils | |||||||||||||||||||||||
| 10 buffer.imp | 1 | ||||||||||||||||||||||
| 11 request_items | 1 | ||||||||||||||||||||||
| 12 to_curl | 1 | ||||||||||||||||||||||
| 13 cli | 1 | 1 | 1 | 1 | 2 | ||||||||||||||||||
| 14 xh | 1 | ||||||||||||||||||||||
| 15 formatting | 1 | 1 | |||||||||||||||||||||
| 16 formatting.headers | 2 | ||||||||||||||||||||||
| 17 generation | 1 | 1 | |||||||||||||||||||||
| 18 formatting.palette.util | 1 | 1 | |||||||||||||||||||||
| 19 printer | 1 | 3 | 1 | 1 | |||||||||||||||||||
| 20 middleware | 1 | ||||||||||||||||||||||
| 21 auth | 1 | 1 | 2 | ||||||||||||||||||||
| 22 redirect | 1 | 2 | |||||||||||||||||||||
| 23 session | 2 |
10→13 buffer.imp uses cli part of a loop✕
- Connections
- 1 pair of types, where a type in buffer.imp uses a type in cli.
- The types involved
xh.buffer.imp.Buffer→xh.cli.Pretty
- Direction
- buffer.imp uses cli, so a change to cli can break buffer.imp, while a change to buffer.imp can't break cli.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→13 request_items uses cli part of a loop✕
- Connections
- 1 pair of types, where a type in request_items uses a type in cli.
- The types involved
xh.request_items.RequestItems→xh.cli.BodyType
- Direction
- request_items uses cli, so a change to cli can break request_items, while a change to request_items can't break cli.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→13 to_curl uses cli part of a loop✕
- Connections
- 1 pair of types, where a type in to_curl uses a type in cli.
- The types involved
xh.to_curl.to_curl$module→xh.cli.Cli
- Direction
- to_curl uses cli, so a change to cli can break to_curl, while a change to to_curl can't break cli.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→7 cli uses netrc✕
- Connections
- 1 pair of types, where a type in cli uses a type in netrc.
- The types involved
xh.cli.Verify→xh.netrc.Parser
- Direction
- cli uses netrc, so a change to netrc can break cli, while a change to cli can't break netrc.
- Position
- Below the diagonal: cli uses a module listed above it, which is the healthy direction.
13→8 cli uses redacted✕
- Connections
- 1 pair of types, where a type in cli uses a type in redacted.
- The types involved
xh.cli.Cli→xh.redacted.SecretString
- Direction
- cli uses redacted, so a change to redacted can break cli, while a change to cli can't break redacted.
- Position
- Below the diagonal: cli uses a module listed above it, which is the healthy direction.
13→10 cli uses buffer.imp✕
- Connections
- 1 pair of types, where a type in cli uses a type in buffer.imp.
- The types involved
xh.cli.Print→xh.buffer.imp.Buffer
- Direction
- cli uses buffer.imp, so a change to buffer.imp can break cli, while a change to cli can't break buffer.imp.
- Position
- Below the diagonal: cli uses a module listed above it, which is the healthy direction.
13→11 cli uses request_items✕
- Connections
- 1 pair of types, where a type in cli uses a type in request_items.
- The types involved
xh.cli.Cli→xh.request_items.RequestItems
- Direction
- cli uses request_items, so a change to request_items can break cli, while a change to cli can't break request_items.
- Position
- Below the diagonal: cli uses a module listed above it, which is the healthy direction.
13→12 cli uses to_curl✕
- Connections
- 2 pairs of types, where a type in cli uses a type in to_curl.
- The types involved
xh.cli.Cli→xh.to_curl.Commandxh.cli.VerifyParser→xh.to_curl.Command
- Direction
- cli uses to_curl, so a change to to_curl can break cli, while a change to cli can't break to_curl.
- Position
- Below the diagonal: cli uses a module listed above it, which is the healthy direction.
14→13 xh uses cli✕
- Connections
- 1 pair of types, where a type in xh uses a type in cli.
- The types involved
xh.xh$module→xh.cli.Cli
- Direction
- xh uses cli, so a change to cli can break xh, while a change to xh can't break cli.
- Position
- Below the diagonal: xh uses a module listed above it, which is the healthy direction.
15→10 formatting uses buffer.imp✕
- Connections
- 1 pair of types, where a type in formatting uses a type in buffer.imp.
- The types involved
xh.formatting.Highlighter→xh.buffer.imp.Buffer
- Direction
- formatting uses buffer.imp, so a change to buffer.imp can break formatting, while a change to formatting can't break buffer.imp.
- Position
- Below the diagonal: formatting uses a module listed above it, which is the healthy direction.
15→13 formatting uses cli✕
- Connections
- 1 pair of types, where a type in formatting uses a type in cli.
- The types involved
xh.formatting.Highlighter→xh.cli.Theme
- Direction
- formatting uses cli, so a change to cli can break formatting, while a change to formatting can't break cli.
- Position
- Below the diagonal: formatting uses a module listed above it, which is the healthy direction.
16→13 formatting.headers uses cli✕
- Connections
- 2 pairs of types, where a type in formatting.headers uses a type in cli.
- The types involved
xh.formatting.headers.HeaderFormatter→xh.cli.Themexh.formatting.headers.HeaderPalette→xh.cli.Theme
- Direction
- formatting.headers uses cli, so a change to cli can break formatting.headers, while a change to formatting.headers can't break cli.
- Position
- Below the diagonal: formatting.headers uses a module listed above it, which is the healthy direction.
17→12 generation uses to_curl✕
- Connections
- 1 pair of types, where a type in generation uses a type in to_curl.
- The types involved
xh.generation.generation$module→xh.to_curl.Command
- Direction
- generation uses to_curl, so a change to to_curl can break generation, while a change to generation can't break to_curl.
- Position
- Below the diagonal: generation uses a module listed above it, which is the healthy direction.
17→13 generation uses cli✕
- Connections
- 1 pair of types, where a type in generation uses a type in cli.
- The types involved
xh.generation.generation$module→xh.cli.Generate
- Direction
- generation uses cli, so a change to cli can break generation, while a change to generation can't break cli.
- Position
- Below the diagonal: generation uses a module listed above it, which is the healthy direction.
18→13 formatting.palette.util uses cli✕
- Connections
- 1 pair of types, where a type in formatting.palette.util uses a type in cli.
- The types involved
xh.formatting.palette.util.util$module→xh.cli.Theme
- Direction
- formatting.palette.util uses cli, so a change to cli can break formatting.palette.util, while a change to formatting.palette.util can't break cli.
- Position
- Below the diagonal: formatting.palette.util uses a module listed above it, which is the healthy direction.
18→15 formatting.palette.util uses formatting✕
- Connections
- 1 pair of types, where a type in formatting.palette.util uses a type in formatting.
- The types involved
xh.formatting.palette.util.util$module→xh.formatting.Highlighter
- Direction
- formatting.palette.util uses formatting, so a change to formatting can break formatting.palette.util, while a change to formatting.palette.util can't break formatting.
- Position
- Below the diagonal: formatting.palette.util uses a module listed above it, which is the healthy direction.
19→10 printer uses buffer.imp✕
- Connections
- 1 pair of types, where a type in printer uses a type in buffer.imp.
- The types involved
xh.printer.Printer→xh.buffer.imp.Buffer
- Direction
- printer uses buffer.imp, so a change to buffer.imp can break printer, while a change to printer can't break buffer.imp.
- Position
- Below the diagonal: printer uses a module listed above it, which is the healthy direction.
19→13 printer uses cli✕
- Connections
- 3 pairs of types, where a type in printer uses a type in cli.
- The types involved
xh.printer.Printer→xh.cli.FormatOptionsxh.printer.Printer→xh.cli.Prettyxh.printer.Printer→xh.cli.Theme
- Direction
- printer uses cli, so a change to cli can break printer, while a change to printer can't break cli.
- Position
- Below the diagonal: printer uses a module listed above it, which is the healthy direction.
19→15 printer uses formatting✕
- Connections
- 1 pair of types, where a type in printer uses a type in formatting.
- The types involved
xh.printer.Printer→xh.formatting.Highlighter
- Direction
- printer uses formatting, so a change to formatting can break printer, while a change to printer can't break formatting.
- Position
- Below the diagonal: printer uses a module listed above it, which is the healthy direction.
19→16 printer uses formatting.headers✕
- Connections
- 1 pair of types, where a type in printer uses a type in formatting.headers.
- The types involved
xh.printer.Printer→xh.formatting.headers.HeaderFormatter
- Direction
- printer uses formatting.headers, so a change to formatting.headers can break printer, while a change to printer can't break formatting.headers.
- Position
- Below the diagonal: printer uses a module listed above it, which is the healthy direction.
20→19 middleware uses printer✕
- Connections
- 1 pair of types, where a type in middleware uses a type in printer.
- The types involved
xh.middleware.Context→xh.printer.Printer
- Direction
- middleware uses printer, so a change to printer can break middleware, while a change to middleware can't break printer.
- Position
- Below the diagonal: middleware uses a module listed above it, which is the healthy direction.
21→7 auth uses netrc✕
- Connections
- 1 pair of types, where a type in auth uses a type in netrc.
- The types involved
xh.auth.Auth→xh.netrc.Entry
- Direction
- auth uses netrc, so a change to netrc can break auth, while a change to auth can't break netrc.
- Position
- Below the diagonal: auth uses a module listed above it, which is the healthy direction.
21→13 auth uses cli✕
- Connections
- 1 pair of types, where a type in auth uses a type in cli.
- The types involved
xh.auth.Auth→xh.cli.AuthType
- Direction
- auth uses cli, so a change to cli can break auth, while a change to auth can't break cli.
- Position
- Below the diagonal: auth uses a module listed above it, which is the healthy direction.
21→20 auth uses middleware✕
- Connections
- 2 pairs of types, where a type in auth uses a type in middleware.
- The types involved
xh.auth.DigestAuthMiddleware→xh.middleware.Contextxh.auth.DigestAuthMiddleware→xh.middleware.Middleware
- Direction
- auth uses middleware, so a change to middleware can break auth, while a change to auth can't break middleware.
- Position
- Below the diagonal: auth uses a module listed above it, which is the healthy direction.
22→13 redirect uses cli✕
- Connections
- 1 pair of types, where a type in redirect uses a type in cli.
- The types involved
xh.redirect.RedirectFollower→xh.cli.MessageSignature
- Direction
- redirect uses cli, so a change to cli can break redirect, while a change to redirect can't break cli.
- Position
- Below the diagonal: redirect uses a module listed above it, which is the healthy direction.
22→20 redirect uses middleware✕
- Connections
- 2 pairs of types, where a type in redirect uses a type in middleware.
- The types involved
xh.redirect.RedirectFollower→xh.middleware.Contextxh.redirect.RedirectFollower→xh.middleware.Middleware
- Direction
- redirect uses middleware, so a change to middleware can break redirect, while a change to redirect can't break middleware.
- Position
- Below the diagonal: redirect uses a module listed above it, which is the healthy direction.
23→21 session uses auth✕
- Connections
- 2 pairs of types, where a type in session uses a type in auth.
- The types involved
xh.session.Content→xh.auth.Authxh.session.Session→xh.auth.Auth
- Direction
- session uses auth, so a change to auth can break session, while a change to session can't break auth.
- Position
- Below the diagonal: session 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
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 19 | Medium |
| A05:2025 — Injection | 15 | High / Critical |
Roadmap
Top priorities: Resolve the 1 No ADRs found finding(s) in ADR Quality — start with main.rs; 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; 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.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with main.rs. | +11.6 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. | +10.3 pts | Medium | Architecture documentation |
| Resolve the 5 Orphaned file finding(s) in Knowledge Freshness — start with netrc.rs, buffer.rs, headers.rs. | +3.2 pts | Low | Knowledge Freshness |
| Resolve the 1 Orphaned knowledge finding(s) in Knowledge Freshness — start with message_signature.rs. | +3.2 pts | Low | Knowledge Freshness |
| Resolve the 1 Off-boarding risk finding(s) in Bus Factor. | +2.3 pts | Low | Bus Factor |
| 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. | +3.8 pts | Medium | Documentation (README) |
| Resolve the 12 Low coverage finding(s) in Code Coverage — start with auth.rs, download.rs, error_reporting.rs. | +1.9 pts | Medium | Code Coverage |
| Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. | +0.9 pts | Low | Supply-chain Provenance & Signing |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| src/generation.rs | 5.5 | Mixed | Cyclomatic Complexity: xh::generation::generate_markdown (cyclomatic 22) |
| REDACTED | 5.8 | Mixed | Dependency Vulnerabilities: Medium advisory (unmaintained): REDACTED |
| src/download.rs | 5.9 | Mixed | Cyclomatic Complexity: xh::download::download_file (cyclomatic 18) |
| src/main.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/printer.rs | 6.0 | Mixed | Explicit Debt: FixmeComment |
| src/request_items.rs | 6.7 | Mixed | Explicit Debt: TodoComment |
| src/formatting/headers.rs | 7.0 | Near-clean | Cognitive Complexity: HeaderFormatter::print_headers (cognitive 20) |
| src/to_curl.rs | 7.4 | Near-clean | Cyclomatic Complexity: xh::to_curl::translate (cyclomatic 76) |
| src/cli.rs | 7.4 | Near-clean | Cyclomatic Complexity: Cli::process_relations (cyclomatic 18) |
| src/netrc.rs | 7.8 | Near-clean | Cyclomatic Complexity: Parser::parse (cyclomatic 18) |
| tests/cases/download.rs | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/message_signature.rs | 8.5 | Near-clean | Cognitive Complexity: xh::message_signature::resolve_components (cognitive 22) |
| src/decoder.rs | 8.5 | Near-clean | Cognitive Complexity: LazyZstdDecoder::read (cognitive 21) |
| src/nested_json.rs | 8.5 | Near-clean | Cognitive Complexity: xh::nested_json::parse_path (cognitive 20) |
| src/buffer.rs | 8.5 | Near-clean | Cohesion (LCOM4): Low cohesion: Buffer (LCOM4 8) |
| src/auth.rs | 8.5 | Near-clean | Code Coverage: Low coverage: src/auth.rs |
| src/error_reporting.rs | 8.5 | Near-clean | Code Coverage: Low coverage: src/error_reporting.rs |
| src/formatting/mod.rs | 8.5 | Near-clean | Code Coverage: Low coverage: src/formatting/mod.rs |
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
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 38 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 1.0, the weighted average across measured dimensions.
What we checked — 38 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, 84 of 101 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 or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
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 |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 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.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (Cargo.toml), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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.
- 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- 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 our 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.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- 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.
- 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
8 function(s) exceeded the cyclomatic complexity threshold of 15; the worst was xh::run at 113.
What to do
- Bring the 2 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with xh::run (cyclomatic 113), xh::to_curl::translate (cyclomatic 76). — 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 6.7 to about 8.4/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
D2 · Cognitive Complexity
13 function(s) exceeded the cognitive complexity threshold of 15; the worst was xh::run at 165.
What to do
- Bring the 2 bodies over 60 down to 60 or less in Cognitive Complexity — start with xh::run (cognitive 165), xh::to_curl::translate (cognitive 84). — 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 3.8 to about 6.0/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
D3 · God Classes
7 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 4 FunctionTooLong finding(s) in God Classes — start with main.rs, to_curl.rs, generation.rs. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 2 FileTooLong finding(s) in God Classes — start with cli.rs, main.rs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 TooManyFields finding(s) in God Classes — start with cli.rs. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
2 duplicated block group(s) detected. 0.4 % of the production lines (36 of 9,206) are in a reported copy.
What to do
- Resolve the 1 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with generation.rs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with generation.rs. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
1 of 12 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with buffer.rs. — One of this dimension's main actionable groups (1 warning-level).
D8 · Code Coverage
Line coverage 36.0% — 12 file(s) below 50%. Measured from the Rust suite (repository root: `cargo test --workspace` instrumented over 22 production file(s), 2 test binaries and 0 doc-test binaries).
What to do
- Resolve the 12 Low coverage finding(s) in Code Coverage — start with auth.rs, download.rs, error_reporting.rs. — One of this dimension's main actionable groups (12 warning-level).
D11 · Test Reliability
0 flaky across 1 measured tier(s). Rust (repository root, 23 test files): measured (0 flaky).
D12 · Dependency Hygiene
7 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 362 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
Top hotspots: src/download.rs (2×18=36)
What to do
- Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with download.rs. — One of this dimension's main actionable groups (1 warning-level).
D16 · Bus Factor
3 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/message_signature.rs. Counted over 21 of the 23 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 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
D17 · Explicit Debt
5 deducted task-comment markers across 9206 LoC (0.0/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 4 TodoComment finding(s) in Explicit Debt — start with download.rs, main.rs, printer.rs. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 1 FixmeComment finding(s) in Explicit Debt — start with printer.rs. — One of this dimension's main actionable groups (1 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 4 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 — start with main.rs. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
15 finding(s): 0 critical, 15 high, 0 medium, 0 low. 13 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 2 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 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 13 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 (13 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
11 finding(s): 0 critical, 0 high, 11 medium, 0 low.
What to do
- Resolve the 5 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (5). — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 3 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 Medium advisory (unmaintained) finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
D34 · Knowledge Freshness
6 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/message_signature.rs. Counted over 21 of the 23 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 5 Orphaned file finding(s) in Knowledge Freshness — start with netrc.rs, buffer.rs, headers.rs. — One of this dimension's main actionable groups (5 recommendation-level).
- Resolve the 1 Orphaned knowledge finding(s) in Knowledge Freshness — start with message_signature.rs. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Further orphaned files (smaller) 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.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
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.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
P1 · CI/CD gates
P2 · Observability
P3 · Security & performance tooling
What to do
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P6 · Release Hygiene
X14 · Bypassable address classification
X21 · Side-effecting pattern guard
X30 · Support guard that admits what it rejects
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 83% | Adequate — gated by D2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 98% | Exemplary | Strongest area. |
| Maturity | 51% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 70% | Strong | Solid. |
| Security | 68% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
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 — 76 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- 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 — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no data at rest for these controls to protect.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository starts no server another machine can reach (no actix-web HttpServer, axum::serve, Rocket launch, warp::serve, poem or salvo Server, tonic Server::builder, hyper or tiny_http server outside examples and tests, none bound beyond loopback). Access control is therefore N/A here — a crate is authorized by the application that serves it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~5612 lines of test source are present (.rs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (806 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — 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
- D26 Project Cohesion — This repository is one build unit, `(repository root)` (9206 LoC, 60 module-visible types across 2 directories), within the size bounds. Not scored: a single unit of this size gives project cohesion nothing to grade.
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D5 Coupling — Not applicable — this Cargo build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (4 value object(s))
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- M4 Documentation accuracy — Not applicable: the 4 current-state document(s) make no claim of a kind M4 checks. 11 claim(s) of kinds M4 does not check were not checked (environment variable 11); M4 checks only links and versions and artefact counts.
- 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 — coverage data present for 22 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
- 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 scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — No web surface: 23 Rust file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. This repository serves no HTTP of its own — no HTTP-server crate (actix-web, axum, Rocket, warp, poem, tide, salvo, tonic, a hyper server, …) among its Cargo manifests' run-time dependencies, and no server started in its production source — so HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library or worker. If this codebase starts serving HTTP, the dimension reactivates automatically.
- X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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.
- X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 16 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Orphaned knowledge src/message_signature.rs:1
Serious — 63 finding(s)
- Low coverage: src/auth.rs src/auth.rs:1
- Low coverage: src/download.rs src/download.rs:1
- Low coverage: src/error_reporting.rs src/error_reporting.rs:1
- Low coverage: src/formatting/headers.rs src/formatting/headers.rs:1
- Low coverage: src/formatting/mod.rs src/formatting/mod.rs:1
- Low coverage: src/formatting/palette.rs src/formatting/palette.rs:1
- Low coverage: src/generation.rs src/generation.rs:1
- Low coverage: src/main.rs src/main.rs:1
- Low coverage: src/middleware.rs src/middleware.rs:1
- Low coverage: src/printer.rs src/printer.rs:1
- Low coverage: src/redirect.rs src/redirect.rs:1
- Low coverage: src/session.rs src/session.rs:1
- xh::run (cognitive 165) src/main.rs:99
- xh::to_curl::translate (cognitive 84) src/to_curl.rs:83
- xh::generation::generate_manpages (cognitive 32) src/generation.rs:169
- xh::download::download_file (cognitive 31) src/download.rs:166
- xh::generation::generate_markdown (cognitive 27) src/generation.rs:59
- xh::generation::parse_help (cognitive 22) src/generation.rs:328
- xh::message_signature::resolve_components (cognitive 22) src/message_signature.rs:76
- xh::nested_json::parse_path (cognitive 20) src/nested_json.rs:100
- xh::run (cyclomatic 113) src/main.rs:99
- xh::to_curl::translate (cyclomatic 76) src/to_curl.rs:83
- xh::generation::generate_markdown (cyclomatic 22) src/generation.rs:59
- xh::generation::generate_manpages (cyclomatic 22) src/generation.rs:169
- xh::download::download_file (cyclomatic 18) src/download.rs:166
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- TodoComment tests/cases/download.rs:287
- TodoComment src/main.rs:574
- TodoComment src/printer.rs:460
- TodoComment src/request_items.rs:127
- FunctionTooLong: xh::run src/main.rs:99
- FunctionTooLong: xh::to_curl::translate src/to_curl.rs:83
- FunctionTooLong: xh::generation::generate_manpages src/generation.rs:169
- FunctionTooLong: xh::download::download_file src/download.rs:166
- REDACTED
- REDACTED
- REDACTED
- Printer::print_json_stream (cognitive 19) src/printer.rs:288
- Printer::print_response_body (cognitive 17) src/printer.rs:437
- FileTooLong: src/cli.rs src/cli.rs
- FileTooLong: src/main.rs src/main.rs
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Cli::process_relations (cyclomatic 18) src/cli.rs:606
- Parser::parse (cyclomatic 18) src/netrc.rs:125
- RequestItem::from_str (cyclomatic 17) src/request_items.rs:51
- Hotspot: src/download.rs src/download.rs:166
- FixmeComment src/printer.rs:379
- Parser::parse (cognitive 27) src/netrc.rs:125
- LazyZstdDecoder::read (cognitive 21) src/decoder.rs:238
- HeaderFormatter::print_headers (cognitive 20) src/formatting/headers.rs:144
- TooManyFields: Cli src/cli.rs:56
- REDACTED
- REDACTED
- Duplicated block (12 lines × 2) src/generation.rs:194
- Duplicated block (6 lines × 2) src/generation.rs:185
- Low cohesion: Buffer (LCOM4 8) src/buffer.rs:35
Minor — 15 finding(s)
- Orphaned file src/netrc.rs:1
- Orphaned file src/buffer.rs:1
- Orphaned file src/formatting/headers.rs:1
- Orphaned file src/formatting/mod.rs:1
- Orphaned file src/content_disposition.rs:1
- Off-boarding risk: anonymized user #1
- No ADRs found src/main.rs:1
- Further orphaned files (smaller)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
Minor — 7 finding(s)
- Outdated: cookie_store
- Outdated: encoding_rs
- Outdated: flate2
- Outdated: log
- Outdated: mime
- Outdated: rpassword
- Outdated: time
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-b53a41ce0a6d4475b3a0808f597c3234/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/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-b53a41ce0a6d4475b3a0808f597c3234/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/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 15 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 11 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |