Executive summary
stephenleo/cship falls short of our standard for production because it has pipeline tools referenced by a changeable name. It scores 61.9 out of 100 and is rated Adequate, and all 31 of its critical findings are security problems in the build pipeline and in the packages it uses.
Security and Compliance, at 49.2, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 4.2 points. Stopping the two pipeline steps that hand secrets to unpinned tools would lift Security and Compliance itself, worth about 2.0 points. Raising Security and Compliance to 70 would lift the score to about 71.1.
Twenty-six pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Two pipeline steps run downloads nobody checks, and two secrets can leak from the build pipeline. Pinning each tool to an exact version, checking each download against a checksum and limiting each secret to its own step would close these risks. Updating the vulnerable packages would fix the package with a known security hole.
The product code is 13,396 lines, about €16,000 to rebuild.
If Security and Compliance rose from 49.2 to 70, the lowest score rated Strong, the score would rise from 61.9 to about 71.1.
Rebuild cost: about €16,000 · Estimate
| Cost to rebuild | €5,300 to €27,000, for 89 to 282 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.8 at a score of 62. 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: 13,396 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 account | 2 ansi | 3 config | 4 context | 5 main | 6 platform | 7 terminal.unix_impl | 8 terminal.unix_impl.os | 9 uninstall | 10 usage_limits | 11 cache | 12 explain | 13 format | 14 modules | 15 modules.account | 16 modules.agent | 17 modules.context_bar | 18 modules.context_window | 19 modules.cost | 20 modules.effort | 21 modules.model | 22 modules.peak_usage | 23 modules.session | 24 modules.usage_limits | 25 modules.vim | 26 modules.workspace | 27 passthrough | 28 renderer | 29 terminal |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 account | |||||||||||||||||||||||||||||
| 2 ansi | |||||||||||||||||||||||||||||
| 3 config | |||||||||||||||||||||||||||||
| 4 context | |||||||||||||||||||||||||||||
| 5 main | |||||||||||||||||||||||||||||
| 6 platform | |||||||||||||||||||||||||||||
| 7 terminal.unix_impl | |||||||||||||||||||||||||||||
| 8 terminal.unix_impl.os | |||||||||||||||||||||||||||||
| 9 uninstall | |||||||||||||||||||||||||||||
| 10 usage_limits | |||||||||||||||||||||||||||||
| 11 cache | 2 | 2 | |||||||||||||||||||||||||||
| 12 explain | 1 | 1 | |||||||||||||||||||||||||||
| 13 format | 1 | ||||||||||||||||||||||||||||
| 14 modules | 1 | 1 | |||||||||||||||||||||||||||
| 15 modules.account | 1 | 2 | 1 | ||||||||||||||||||||||||||
| 16 modules.agent | 1 | 1 | |||||||||||||||||||||||||||
| 17 modules.context_bar | 1 | 1 | |||||||||||||||||||||||||||
| 18 modules.context_window | 1 | 1 | |||||||||||||||||||||||||||
| 19 modules.cost | 3 | 1 | |||||||||||||||||||||||||||
| 20 modules.effort | 2 | 1 | |||||||||||||||||||||||||||
| 21 modules.model | 2 | 1 | |||||||||||||||||||||||||||
| 22 modules.peak_usage | 2 | 1 | |||||||||||||||||||||||||||
| 23 modules.session | 1 | 1 | |||||||||||||||||||||||||||
| 24 modules.usage_limits | 2 | 1 | 1 | ||||||||||||||||||||||||||
| 25 modules.vim | 1 | 1 | |||||||||||||||||||||||||||
| 26 modules.workspace | 1 | 1 | |||||||||||||||||||||||||||
| 27 passthrough | 1 | 1 | |||||||||||||||||||||||||||
| 28 renderer | 1 | 1 | |||||||||||||||||||||||||||
| 29 terminal | 1 |
11→1 cache uses account✕
- Connections
- 2 pairs of types, where a type in cache uses a type in account.
- The types involved
cship.cache.AccountProfileCacheEnvelope→cship.account.AccountProfilecship.cache.cache$module→cship.account.AccountProfile
- Direction
- cache uses account, so a change to account can break cache, while a change to cache can't break account.
- Position
- Below the diagonal: cache uses a module listed above it, which is the healthy direction.
11→10 cache uses usage_limits✕
- Connections
- 2 pairs of types, where a type in cache uses a type in usage_limits.
- The types involved
cship.cache.UsageLimitsCacheEnvelope→cship.usage_limits.UsageLimitsDatacship.cache.cache$module→cship.usage_limits.UsageLimitsData
- Direction
- cache uses usage_limits, so a change to usage_limits can break cache, while a change to cache can't break usage_limits.
- Position
- Below the diagonal: cache uses a module listed above it, which is the healthy direction.
12→3 explain uses config✕
- Connections
- 1 pair of types, where a type in explain uses a type in config.
- The types involved
cship.explain.explain$module→cship.config.CshipConfig
- Direction
- explain uses config, so a change to config can break explain, while a change to explain can't break config.
- Position
- Below the diagonal: explain uses a module listed above it, which is the healthy direction.
12→4 explain uses context✕
- Connections
- 1 pair of types, where a type in explain uses a type in context.
- The types involved
cship.explain.explain$module→cship.context.Context
- Direction
- explain uses context, so a change to context can break explain, while a change to explain can't break context.
- Position
- Below the diagonal: explain uses a module listed above it, which is the healthy direction.
13→3 format uses config✕
- Connections
- 1 pair of types, where a type in format uses a type in config.
- The types involved
cship.format.format$module→cship.config.SubfieldConfig
- Direction
- format uses config, so a change to config can break format, while a change to format can't break config.
- Position
- Below the diagonal: format uses a module listed above it, which is the healthy direction.
14→3 modules uses config✕
- Connections
- 1 pair of types, where a type in modules uses a type in config.
- The types involved
cship.modules.modules$module→cship.config.CshipConfig
- Direction
- modules uses config, so a change to config can break modules, while a change to modules can't break config.
- Position
- Below the diagonal: modules uses a module listed above it, which is the healthy direction.
14→4 modules uses context✕
- Connections
- 1 pair of types, where a type in modules uses a type in context.
- The types involved
cship.modules.modules$module→cship.context.Context
- Direction
- modules uses context, so a change to context can break modules, while a change to modules can't break context.
- Position
- Below the diagonal: modules uses a module listed above it, which is the healthy direction.
15→1 modules.account uses account✕
- Connections
- 1 pair of types, where a type in modules.account uses a type in account.
- The types involved
cship.modules.account.account$module→cship.account.AccountProfile
- Direction
- modules.account uses account, so a change to account can break modules.account, while a change to modules.account can't break account.
- Position
- Below the diagonal: modules.account uses a module listed above it, which is the healthy direction.
15→3 modules.account uses config✕
- Connections
- 2 pairs of types, where a type in modules.account uses a type in config.
- The types involved
cship.modules.account.account$module→cship.config.AccountConfigcship.modules.account.account$module→cship.config.CshipConfig
- Direction
- modules.account uses config, so a change to config can break modules.account, while a change to modules.account can't break config.
- Position
- Below the diagonal: modules.account uses a module listed above it, which is the healthy direction.
15→4 modules.account uses context✕
- Connections
- 1 pair of types, where a type in modules.account uses a type in context.
- The types involved
cship.modules.account.account$module→cship.context.Context
- Direction
- modules.account uses context, so a change to context can break modules.account, while a change to modules.account can't break context.
- Position
- Below the diagonal: modules.account uses a module listed above it, which is the healthy direction.
16→3 modules.agent uses config✕
- Connections
- 1 pair of types, where a type in modules.agent uses a type in config.
- The types involved
cship.modules.agent.agent$module→cship.config.CshipConfig
- Direction
- modules.agent uses config, so a change to config can break modules.agent, while a change to modules.agent can't break config.
- Position
- Below the diagonal: modules.agent uses a module listed above it, which is the healthy direction.
16→4 modules.agent uses context✕
- Connections
- 1 pair of types, where a type in modules.agent uses a type in context.
- The types involved
cship.modules.agent.agent$module→cship.context.Context
- Direction
- modules.agent uses context, so a change to context can break modules.agent, while a change to modules.agent can't break context.
- Position
- Below the diagonal: modules.agent uses a module listed above it, which is the healthy direction.
17→3 modules.context_bar uses config✕
- Connections
- 1 pair of types, where a type in modules.context_bar uses a type in config.
- The types involved
cship.modules.context_bar.context_bar$module→cship.config.CshipConfig
- Direction
- modules.context_bar uses config, so a change to config can break modules.context_bar, while a change to modules.context_bar can't break config.
- Position
- Below the diagonal: modules.context_bar uses a module listed above it, which is the healthy direction.
17→4 modules.context_bar uses context✕
- Connections
- 1 pair of types, where a type in modules.context_bar uses a type in context.
- The types involved
cship.modules.context_bar.context_bar$module→cship.context.Context
- Direction
- modules.context_bar uses context, so a change to context can break modules.context_bar, while a change to modules.context_bar can't break context.
- Position
- Below the diagonal: modules.context_bar uses a module listed above it, which is the healthy direction.
18→3 modules.context_window uses config✕
- Connections
- 1 pair of types, where a type in modules.context_window uses a type in config.
- The types involved
cship.modules.context_window.context_window$module→cship.config.CshipConfig
- Direction
- modules.context_window uses config, so a change to config can break modules.context_window, while a change to modules.context_window can't break config.
- Position
- Below the diagonal: modules.context_window uses a module listed above it, which is the healthy direction.
18→4 modules.context_window uses context✕
- Connections
- 1 pair of types, where a type in modules.context_window uses a type in context.
- The types involved
cship.modules.context_window.context_window$module→cship.context.Context
- Direction
- modules.context_window uses context, so a change to context can break modules.context_window, while a change to modules.context_window can't break context.
- Position
- Below the diagonal: modules.context_window uses a module listed above it, which is the healthy direction.
19→3 modules.cost uses config✕
- Connections
- 3 pairs of types, where a type in modules.cost uses a type in config.
- The types involved
cship.modules.cost.cost$module→cship.config.CostConfigcship.modules.cost.cost$module→cship.config.CshipConfigcship.modules.cost.cost$module→cship.config.SubfieldConfig
- Direction
- modules.cost uses config, so a change to config can break modules.cost, while a change to modules.cost can't break config.
- Position
- Below the diagonal: modules.cost uses a module listed above it, which is the healthy direction.
19→4 modules.cost uses context✕
- Connections
- 1 pair of types, where a type in modules.cost uses a type in context.
- The types involved
cship.modules.cost.cost$module→cship.context.Context
- Direction
- modules.cost uses context, so a change to context can break modules.cost, while a change to modules.cost can't break context.
- Position
- Below the diagonal: modules.cost uses a module listed above it, which is the healthy direction.
20→3 modules.effort uses config✕
- Connections
- 2 pairs of types, where a type in modules.effort uses a type in config.
- The types involved
cship.modules.effort.effort$module→cship.config.CshipConfigcship.modules.effort.effort$module→cship.config.EffortConfig
- Direction
- modules.effort uses config, so a change to config can break modules.effort, while a change to modules.effort can't break config.
- Position
- Below the diagonal: modules.effort uses a module listed above it, which is the healthy direction.
20→4 modules.effort uses context✕
- Connections
- 1 pair of types, where a type in modules.effort uses a type in context.
- The types involved
cship.modules.effort.effort$module→cship.context.Context
- Direction
- modules.effort uses context, so a change to context can break modules.effort, while a change to modules.effort can't break context.
- Position
- Below the diagonal: modules.effort uses a module listed above it, which is the healthy direction.
21→3 modules.model uses config✕
- Connections
- 2 pairs of types, where a type in modules.model uses a type in config.
- The types involved
cship.modules.model.model$module→cship.config.CshipConfigcship.modules.model.model$module→cship.config.ModelConfig
- Direction
- modules.model uses config, so a change to config can break modules.model, while a change to modules.model can't break config.
- Position
- Below the diagonal: modules.model uses a module listed above it, which is the healthy direction.
21→4 modules.model uses context✕
- Connections
- 1 pair of types, where a type in modules.model uses a type in context.
- The types involved
cship.modules.model.model$module→cship.context.Context
- Direction
- modules.model uses context, so a change to context can break modules.model, while a change to modules.model can't break context.
- Position
- Below the diagonal: modules.model uses a module listed above it, which is the healthy direction.
22→3 modules.peak_usage uses config✕
- Connections
- 2 pairs of types, where a type in modules.peak_usage uses a type in config.
- The types involved
cship.modules.peak_usage.peak_usage$module→cship.config.CshipConfigcship.modules.peak_usage.peak_usage$module→cship.config.PeakUsageConfig
- Direction
- modules.peak_usage uses config, so a change to config can break modules.peak_usage, while a change to modules.peak_usage can't break config.
- Position
- Below the diagonal: modules.peak_usage uses a module listed above it, which is the healthy direction.
22→4 modules.peak_usage uses context✕
- Connections
- 1 pair of types, where a type in modules.peak_usage uses a type in context.
- The types involved
cship.modules.peak_usage.peak_usage$module→cship.context.Context
- Direction
- modules.peak_usage uses context, so a change to context can break modules.peak_usage, while a change to modules.peak_usage can't break context.
- Position
- Below the diagonal: modules.peak_usage uses a module listed above it, which is the healthy direction.
23→3 modules.session uses config✕
- Connections
- 1 pair of types, where a type in modules.session uses a type in config.
- The types involved
cship.modules.session.session$module→cship.config.CshipConfig
- Direction
- modules.session uses config, so a change to config can break modules.session, while a change to modules.session can't break config.
- Position
- Below the diagonal: modules.session uses a module listed above it, which is the healthy direction.
23→4 modules.session uses context✕
- Connections
- 1 pair of types, where a type in modules.session uses a type in context.
- The types involved
cship.modules.session.session$module→cship.context.Context
- Direction
- modules.session uses context, so a change to context can break modules.session, while a change to modules.session can't break context.
- Position
- Below the diagonal: modules.session uses a module listed above it, which is the healthy direction.
24→3 modules.usage_limits uses config✕
- Connections
- 2 pairs of types, where a type in modules.usage_limits uses a type in config.
- The types involved
cship.modules.usage_limits.usage_limits$module→cship.config.CshipConfigcship.modules.usage_limits.usage_limits$module→cship.config.UsageLimitsConfig
- Direction
- modules.usage_limits uses config, so a change to config can break modules.usage_limits, while a change to modules.usage_limits can't break config.
- Position
- Below the diagonal: modules.usage_limits uses a module listed above it, which is the healthy direction.
24→4 modules.usage_limits uses context✕
- Connections
- 1 pair of types, where a type in modules.usage_limits uses a type in context.
- The types involved
cship.modules.usage_limits.usage_limits$module→cship.context.Context
- Direction
- modules.usage_limits uses context, so a change to context can break modules.usage_limits, while a change to modules.usage_limits can't break context.
- Position
- Below the diagonal: modules.usage_limits uses a module listed above it, which is the healthy direction.
24→10 modules.usage_limits uses usage_limits✕
- Connections
- 1 pair of types, where a type in modules.usage_limits uses a type in usage_limits.
- The types involved
cship.modules.usage_limits.usage_limits$module→cship.usage_limits.UsageLimitsData
- Direction
- modules.usage_limits uses usage_limits, so a change to usage_limits can break modules.usage_limits, while a change to modules.usage_limits can't break usage_limits.
- Position
- Below the diagonal: modules.usage_limits uses a module listed above it, which is the healthy direction.
25→3 modules.vim uses config✕
- Connections
- 1 pair of types, where a type in modules.vim uses a type in config.
- The types involved
cship.modules.vim.vim$module→cship.config.CshipConfig
- Direction
- modules.vim uses config, so a change to config can break modules.vim, while a change to modules.vim can't break config.
- Position
- Below the diagonal: modules.vim uses a module listed above it, which is the healthy direction.
25→4 modules.vim uses context✕
- Connections
- 1 pair of types, where a type in modules.vim uses a type in context.
- The types involved
cship.modules.vim.vim$module→cship.context.Context
- Direction
- modules.vim uses context, so a change to context can break modules.vim, while a change to modules.vim can't break context.
- Position
- Below the diagonal: modules.vim uses a module listed above it, which is the healthy direction.
26→3 modules.workspace uses config✕
- Connections
- 1 pair of types, where a type in modules.workspace uses a type in config.
- The types involved
cship.modules.workspace.workspace$module→cship.config.CshipConfig
- Direction
- modules.workspace uses config, so a change to config can break modules.workspace, while a change to modules.workspace can't break config.
- Position
- Below the diagonal: modules.workspace uses a module listed above it, which is the healthy direction.
26→4 modules.workspace uses context✕
- Connections
- 1 pair of types, where a type in modules.workspace uses a type in context.
- The types involved
cship.modules.workspace.workspace$module→cship.context.Context
- Direction
- modules.workspace uses context, so a change to context can break modules.workspace, while a change to modules.workspace can't break context.
- Position
- Below the diagonal: modules.workspace uses a module listed above it, which is the healthy direction.
27→3 passthrough uses config✕
- Connections
- 1 pair of types, where a type in passthrough uses a type in config.
- The types involved
cship.passthrough.passthrough$module→cship.config.CshipConfig
- Direction
- passthrough uses config, so a change to config can break passthrough, while a change to passthrough can't break config.
- Position
- Below the diagonal: passthrough uses a module listed above it, which is the healthy direction.
27→4 passthrough uses context✕
- Connections
- 1 pair of types, where a type in passthrough uses a type in context.
- The types involved
cship.passthrough.passthrough$module→cship.context.Context
- Direction
- passthrough uses context, so a change to context can break passthrough, while a change to passthrough can't break context.
- Position
- Below the diagonal: passthrough uses a module listed above it, which is the healthy direction.
28→3 renderer uses config✕
- Connections
- 1 pair of types, where a type in renderer uses a type in config.
- The types involved
cship.renderer.renderer$module→cship.config.CshipConfig
- Direction
- renderer uses config, so a change to config can break renderer, while a change to renderer can't break config.
- Position
- Below the diagonal: renderer uses a module listed above it, which is the healthy direction.
28→4 renderer uses context✕
- Connections
- 1 pair of types, where a type in renderer uses a type in context.
- The types involved
cship.renderer.renderer$module→cship.context.Context
- Direction
- renderer uses context, so a change to context can break renderer, while a change to renderer can't break context.
- Position
- Below the diagonal: renderer uses a module listed above it, which is the healthy direction.
29→3 terminal uses config✕
- Connections
- 1 pair of types, where a type in terminal uses a type in config.
- The types involved
cship.terminal.terminal$module→cship.config.CshipConfig
- Direction
- terminal uses config, so a change to config can break terminal, while a change to terminal can't break config.
- Position
- Below the diagonal: terminal 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 |
|---|---|---|
| A05:2025 — Injection | 31 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 14 | 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; Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with main.rs. | +4.2 pts | Low | ADR Quality |
| Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. | +2.0 pts | Low | Static Analysis (SAST) |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +1.9 pts | Low | Static Analysis (SAST) |
| Resolve the 1 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. | +1.9 pts | Low | Dependency Vulnerabilities |
| 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. | +3.6 pts | Medium | Architecture documentation |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. | +1.1 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +1.1 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. | +1.1 pts | Low | Supply-chain Provenance & Signing |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.5 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.3 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/account.rs | 6.3 | Mixed | Code Duplication: Edited copy of a member (25 corresponding lines) |
| src/passthrough.rs | 7.1 | Mixed | God Classes: FunctionTooLong: cship::passthrough::render_starship_prompt |
| src/modules/context_window.rs | 7.1 | Mixed | Code Duplication: Members sharing a duplicated core (7 members, 50+ identical tokens) |
| src/ansi.rs | 7.2 | Mixed | Cyclomatic Complexity: cship::ansi::apply_style (cyclomatic 16) |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/renderer.rs | 7.4 | Mixed | Cyclomatic Complexity: cship::renderer::parse_line (cyclomatic 16) |
| src/modules/session.rs | 7.4 | Mixed | Code Duplication: Members sharing a duplicated core (7 members, 50+ identical tokens) |
| src/config.rs | 7.8 | Mixed | Cognitive Complexity: cship::config::load_with_source (cognitive 21) |
| src/modules/usage_limits.rs | 7.8 | Mixed | God Classes: TooManyFunctions: cship::modules::usage_limits |
| src/modules/agent.rs | 7.8 | Mixed | Code Duplication: Edited copy of a member (30 corresponding lines) |
| src/modules/effort.rs | 7.8 | Mixed | Code Duplication: Edited copies of one member (3 members, 25+ corresponding lines) |
| src/cache.rs | 7.8 | Mixed | Code Duplication: Edited copy of a member (16 corresponding lines) |
| src/explain.rs | 8.0 | Near-clean | Cyclomatic Complexity: cship::explain::error_hint_for (cyclomatic 22) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
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 44 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 — 44 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, 121 of 140 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
- D14 License Compliance — 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. This repository declares package.json, but the licence verdict published here was taken over its crate dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- 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 (16 contributor(s) across 336 commit(s) sampled, automation and bot accounts excluded). One of them holds 83% of the history; the other 15 hold 1.1% 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 — 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.
- 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. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- 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's deterministic call-shape rules are gated per language (docs/plans/deterministic-engine.md, P5; C# and each NeutralApiArms arm pass): 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 — 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. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D44 Platform End-of-Life — 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 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 — 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.
- M4 Documentation accuracy — 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. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. 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.
- 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.
- 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.
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.
- 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.
- 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.
- 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: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- 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
3 function(s) exceeded the cyclomatic complexity threshold of 15; the worst was cship::explain::error_hint_for at 22. 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 cship::modules::render_module at 46 — 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/mod.rs (cship::modules::render_module at 46). 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 3 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with cship::explain::error_hint_for (cyclomatic 22), cship::ansi::apply_style (cyclomatic 16), cship::renderer::parse_line (cyclomatic 16). — 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 3 together lifts Cyclomatic Complexity from 9.4 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
6 function(s) exceeded the cognitive complexity threshold of 15; the worst was cship::renderer::parse_line at 28.
What to do
- Bring the 6 bodies over 15 down to 15 or less in Cognitive Complexity — start with cship::renderer::parse_line (cognitive 28), cship::config::load_with_source (cognitive 21), cship::ansi::apply_style (cognitive 18). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 6 together lifts Cognitive Complexity from 8.6 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
2 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 1 TooManyFunctions finding(s) in God Classes — start with usage_limits.rs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 FunctionTooLong finding(s) in God Classes — start with passthrough.rs. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
15 duplicated block group(s) detected. 6.4 % of the production lines (861 of 13,396) are in a reported copy. A further 13 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 2 Members sharing a duplicated core (7 members, 50+ identical tokens) finding(s) in Code Duplication — start with context_window.rs, session.rs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Edited copy of a member (17 corresponding lines) finding(s) in Code Duplication — start with mod.rs, cache.rs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (13–14 lines × 2) finding(s) in Code Duplication — start with model.rs, passthrough.rs. — One of this dimension's main actionable groups (2 warning-level).
D8 · Code Coverage
Line coverage 85.0% — 2 file(s) below 50%. Measured from the Rust suite (repository root: `cargo nextest run` and the doc tests instrumented, 3 run(s), 27 production file(s)). Taken over 3 runs of the suite: a line counts as covered only when every run executed it. 18 line(s) in 1 file(s) were executed in some runs and not in others, so they are not counted.
What to do
- Resolve the 2 Low coverage finding(s) in Code Coverage — start with account.rs, main.rs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Tests reach code only in some runs finding(s) in Code Coverage — start with explain.rs. — One of this dimension's main actionable groups (1 recommendation-level).
D11 · Test Reliability
0 flaky across 1 measured tier(s). Rust (repository root, 27 test files): measured (0 flaky).
D12 · Dependency Hygiene
11 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 190 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 Apache-2.0, which is its own choice and is not judged here. ★ COVERAGE OF THIS VERDICT: it grades this repository's crate dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D15 · Churn × Complexity Hotspots
Top hotspots: src/explain.rs (6×22=132)
What to do
- Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with explain.rs. — One of this dimension's main actionable groups (1 warning-level).
D17 · Explicit Debt
0 deducted task-comment markers across 13396 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. 8 document(s) read across 2 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)
31 finding(s): 0 critical, 30 high, 1 medium, 0 low. 26 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 1 file(s) — `src/terminal.rs` (line 117) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 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, REDACTED. — 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 26 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 (26 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
5 finding(s): 0 critical, 1 high, 4 medium, 0 low.
What to do
- Resolve the 1 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 2 Medium advisory (unsound) finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 27 of the 28 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 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 — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX9 · CQS / query purity
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
- `proc_info` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — src/terminal.rs:193
What to do
- Finish or delete the unfinished stubs (functions that throw "not implemented", or whose body is empty or a bare constant) — they are dead surface that looks live.
M1 · Documentation (README)
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
P3 · Security & performance tooling
- `docs/package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — docs/package.json:10
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
X12 · Unreachable branch
X13 · Undrained process stream
X16 · Unfloored truncation loop
X21 · Side-effecting pattern guard
X23 · Unguarded diagnostic materialisation
X25 · Inert configuration knob
- `ModelConfig.label` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — src/config.rs:64
- `CostConfig.label` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — src/config.rs:82
- `ContextBarConfig.label` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — src/config.rs:191
- `ContextWindowConfig.label` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — src/config.rs:216
- `VimConfig.label` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — src/config.rs:266
- `VimConfig.normal_style` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — src/config.rs:267
- `VimConfig.insert_style` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — src/config.rs:268
- `AgentConfig.label` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — src/config.rs:279
- `EffortConfig.label` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — src/config.rs:293
- `SessionConfig.label` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — src/config.rs:309
- `WorkspaceConfig.label` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — src/config.rs:320
What to do
- Each finding names the spans that disagree — the knob the caller supplies and the site that ignores it, whether by re-spelling its default, by falling back under the wrong key, by parsing with no format provider at all, or by printing under whatever culture the host supplies. Confirm from those spans, then decide which of the two the type meant: read the knob at the named site, or drop the knob so the signature stops advertising something the type cannot feel. Leaving both is the one option that cannot be right.
X4 · Structured logging
- `warn!` at line 477 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/config.rs:477
- `warn!` at line 497 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/config.rs:497
- `warn!` at line 508 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/config.rs:508
- `warn!` at line 528 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/config.rs:528
- `warn!` at line 539 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/config.rs:539
- `debug!` at line 589 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/config.rs:589
- `debug!` at line 607 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/config.rs:607
- `debug!` at line 613 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/config.rs:613
- `warn!` at line 116 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/explain.rs:116
- `error!` at line 62 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/main.rs:62
- `error!` at line 78 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/main.rs:78
- `warn!` at line 98 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/passthrough.rs:98
- `warn!` at line 186 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/passthrough.rs:186
- `debug!` at line 75 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/terminal.rs:75
- `warn!` at line 81 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/modules/account.rs:81
- `warn!` at line 107 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/modules/account.rs:107
- `warn!` at line 153 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/modules/mod.rs:153
- `warn!` at line 181 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/modules/mod.rs:181
- `warn!` at line 185 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/modules/mod.rs:185
- `warn!` at line 60 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/modules/peak_usage.rs:60
- `warn!` at line 67 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/modules/peak_usage.rs:67
- `warn!` at line 76 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/modules/usage_limits.rs:76
- `warn!` at line 373 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/modules/usage_limits.rs:373
What to do
- Interpolated log message defeats structured logging
X5 · Nullable reference types
- `serde_json::to_string_pretty(&schema)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `schema_json` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/config.rs:578
- `serde_json::from_str(SAMPLE_CONTEXT)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `load_context` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/explain.rs:148
- `remaining.chars().next()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `render_fmt` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — src/format.rs:170
What to do
- Each row is a forced `Option`/`Result` no guard on its path proves present. Handle the absent case where it arises rather than forcing it: `?` to hand it to the caller, `if let` / `match` / `let … else` to branch on it, `unwrap_or` / `unwrap_or_default` / `unwrap_or_else` where a default is right. Where the value genuinely cannot be absent, say so in a way a reader can check from the line: test it first (`if x.is_none() { return … }`), look the key up with `contains_key` or the index against `len()`, or construct the value so it cannot be absent.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 75.9 | Strong | Solid. |
| Architecture | 97.4 | Exemplary | Strongest area. |
| Maturity | 66.9 | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 76.8 | Strong | Solid. |
| Security | 49.2 | Weak — 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 — 72 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 — ~1073 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.
- 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 — N/A — too few peers to establish a naming convention (803 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — API consistency is measured on C#, TypeScript, Go 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+ 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; comments in this repository's .rs source were not judged.
- D25 ADR Conformance — no ADRs to check
- D26 Project Cohesion — This repository is one build unit, `(repository root)` (13337 LoC, 62 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 — symbol resolution incomplete — too few calls resolved to assess navigability
- 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.
- 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.)
- D6 Cohesion (LCOM4) — Cohesion (LCOM4) was not measured: of the 42 type(s) found, none both holds instance state and has two or more methods whose shared use of it could be read (41 with fewer than two methods, 1 stub-like), so LCOM4 is undefined for every type in this repository. Not scored — the metric does not apply here, and this is not a finding about this repository.
- 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
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript, Rust source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage data present for 27 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: 28 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.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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.
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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 applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. Rust's compiler refuses the unsynchronised version: a collection shared between a callback's thread and the waiting body must be `Sync`, which a `Vec`, `VecDeque` or `HashMap` is only behind a `Mutex`/`RwLock`, so the race this check looks for cannot be written in safe Rust. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
- 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
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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 — 31 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 65 finding(s)
- Configuration option is read nowhere src/config.rs:64
- Configuration option is read nowhere src/config.rs:82
- Configuration option is read nowhere src/config.rs:191
- Configuration option is read nowhere src/config.rs:216
- Configuration option is read nowhere src/config.rs:266
- Configuration option is read nowhere src/config.rs:267
- Configuration option is read nowhere src/config.rs:268
- Configuration option is read nowhere src/config.rs:279
- Configuration option is read nowhere src/config.rs:293
- Configuration option is read nowhere src/config.rs:309
- Configuration option is read nowhere src/config.rs:320
- cship::renderer::parse_line (cognitive 28) src/renderer.rs:13
- cship::config::load_with_source (cognitive 21) src/config.rs:470
- cship::ansi::apply_style (cognitive 18) src/ansi.rs:6
- cship::renderer::render_line (cognitive 18) src/renderer.rs:99
- cship::format::render_fmt (cognitive 17) src/format.rs:124
- cship::ansi::strip_ansi (cognitive 16) src/ansi.rs:121
- cship::explain::error_hint_for (cyclomatic 22) src/explain.rs:199
- cship::ansi::apply_style (cyclomatic 16) src/ansi.rs:6
- cship::renderer::parse_line (cyclomatic 16) src/renderer.rs:13
- Symbol treated as nullable, then dereferenced unguarded src/config.rs:578
- Symbol treated as nullable, then dereferenced unguarded src/explain.rs:148
- Symbol treated as nullable, then dereferenced unguarded src/format.rs:170
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Members sharing a duplicated core (7 members, 50+ identical tokens) src/modules/context_window.rs:153
- Members sharing a duplicated core (7 members, 50+ identical tokens) src/modules/session.rs:10
- Edited copy of a member (17 corresponding lines) src/modules/mod.rs:173
- Edited copy of a member (17 corresponding lines) src/cache.rs:140
- Duplicated block (13–14 lines × 2) src/modules/model.rs:71
- Duplicated block (13–14 lines × 2) src/passthrough.rs:85
- Low coverage: src/account.rs src/account.rs:1
- Low coverage: src/main.rs src/main.rs:1
- Hotspot: src/explain.rs src/explain.rs:199
- REDACTED
- TooManyFunctions: cship::modules::usage_limits src/modules/usage_limits.rs:35
- FunctionTooLong: cship::passthrough::render_starship_prompt src/passthrough.rs:216
- REDACTED
- REDACTED
- REDACTED
- Near-duplicate member pair (95 shared lines) src/passthrough.rs:80
- Edited copy of a member (30 corresponding lines) src/modules/agent.rs:16
- Edited copies of one member (3 members, 25+ corresponding lines) src/modules/effort.rs:38
- Edited copy of a member (28 corresponding lines) src/modules/context_window.rs:21
- Edited copy of a member (25 corresponding lines) src/account.rs:84
- Edited copies of one member (5 members, 16+ corresponding lines) src/modules/cost.rs:88
- Edited copy of a member (16 corresponding lines) src/cache.rs:172
- Edited copy of a member (13 corresponding lines) src/ansi.rs:61
- Edited copies of one member (4 members, 7+ corresponding lines) src/modules/usage_limits.rs:196
- Duplicated block (64 lines × 2) src/passthrough.rs:115
- Duplicated block (18 lines × 2) src/passthrough.rs:187
- Duplicated block (15–19 lines × 2) src/modules/context_bar.rs:69
- Duplicated block (13 lines × 2) src/account.rs:96
- Duplicated block (9 lines × 2) src/modules/agent.rs:37
- Duplicated block (7 lines × 4) src/modules/context_window.rs:273
- Duplicated block (7 lines × 7) src/modules/session.rs:29
- Duplicated block (3–6 lines × 5) src/modules/session.rs:23
- Duplicated block (6 lines × 3) src/modules/effort.rs:61
- Duplicated block (6 lines × 2) src/modules/workspace.rs:27
- Duplicated block (11 lines × 7) src/modules/context_window.rs:167
- Duplicated block (11 lines × 2) src/modules/context_window.rs:35
- Duplicated block (10 lines × 2) src/config.rs:495
- Hollow method — returns a constant without doing the work src/terminal.rs:193
Minor — 33 finding(s)
- Interpolated log message defeats structured logging src/config.rs:477
- Interpolated log message defeats structured logging src/config.rs:497
- Interpolated log message defeats structured logging src/config.rs:508
- Interpolated log message defeats structured logging src/config.rs:528
- Interpolated log message defeats structured logging src/config.rs:539
- Interpolated log message defeats structured logging src/config.rs:589
- Interpolated log message defeats structured logging src/config.rs:607
- Interpolated log message defeats structured logging src/config.rs:613
- Interpolated log message defeats structured logging src/explain.rs:116
- Interpolated log message defeats structured logging src/main.rs:62
- Interpolated log message defeats structured logging src/main.rs:78
- Interpolated log message defeats structured logging src/passthrough.rs:98
- Interpolated log message defeats structured logging src/passthrough.rs:186
- Interpolated log message defeats structured logging src/terminal.rs:75
- Interpolated log message defeats structured logging src/modules/account.rs:81
- Interpolated log message defeats structured logging src/modules/account.rs:107
- Interpolated log message defeats structured logging src/modules/mod.rs:153
- Interpolated log message defeats structured logging src/modules/mod.rs:181
- Interpolated log message defeats structured logging src/modules/mod.rs:185
- Interpolated log message defeats structured logging src/modules/peak_usage.rs:60
- Interpolated log message defeats structured logging src/modules/peak_usage.rs:67
- Interpolated log message defeats structured logging src/modules/usage_limits.rs:76
- Interpolated log message defeats structured logging src/modules/usage_limits.rs:373
- No ADRs found src/main.rs:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Tests reach code only in some runs: src/explain.rs src/explain.rs:96
- No ADRs
- No dependency-update automation docs/package.json:10
Minor — 11 finding(s)
- Outdated: anyhow
- Outdated: clap
- Outdated: libc
- Outdated: schemars
- Outdated: serde
- Outdated: serde_json
- Outdated: thiserror
- Outdated: toml
- Outdated: tracing-subscriber
- Outdated: unicode-width
- Outdated: ureq
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 --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-7fdcdfe07f67465e9cc9815b678db6d2/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=136" --report-format json --report-path /tmp/watchdog-gitleaks-7fdcdfe07f67465e9cc9815b678db6d2/history-1.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-1.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-7fdcdfe07f67465e9cc9815b678db6d2/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 . | 31 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 5 | artifacts/raw/trivy-fs.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 | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |