Public report — VelociRust, published 30 Jul 2026.
Concrete security findings (CVE IDs, secret matches, dependency versions) are hidden in this version;
ask the repo owner for the full report.
214findings with an exact file:lineof 225 — the remainder are repo-wide signals (a dimension-level measurement, not a single line); open any file:line and verify
28/101dimensions across the health lenses61963 LoC — wide & deep
Executive summary
Read through the Preview lens: this repo is pre-1.0 / in development, so the colour bands are relaxed to what a preview needs — *green* means good enough for a preview, not yet production-stable. Code correctness and security stay near-strict even here; the score itself is absolute and comparable across repos.
AabhaJahagirdar/VelociRust is sound in substance but carries real gaps (63%). It is not in crisis, but the issues below raise the cost of changing it — friction its consumers ultimately inherit.
It is strongest in Architecture (100%) — the structure is clean and changes stay contained. Event Sourcing (100%) is solid too.
The area that most needs attention is Maturity (55%) — onboarding is slow — key decisions and the architecture aren't written down, so contributors have to reverse-engineer the intent. Code Health (61%) is the next concern — changes there are slower and more error-prone.
Leadership focus, highest impact first: Start an ADR log (docs/adr/) recording significant decisions… (Architecture documentation); Reconcile the README with reality (Documentation accuracy); 'Testing' section to the root README (Documentation (README)).
For scale: Medium (~61,963 production lines); rebuilding it from scratch would take roughly ~0.6 person-years (~1–2 engineers). Approximate, ±~30%.
It builds on a genuinely strong Architecture foundation (100%); the priorities above are the highest-leverage way to bring the rest up to that level.
How the score is built — each lens's share of the headlineWidth is the lens's weight in the worst-heaviest fold (the weakest area pulls hardest); colour is that lens's own band. A lens fixes the score in proportion to its width.
D38 · Medium vulnerability: [GHSA redacted] Cargo.lock
A full-fidelity diff against the previous run's complete recorded findings — line-move tolerant: a finding that only shifted line counts as unchanged, only genuinely new titles/files surface here.
0.9× (at 63% quality) — the last 20% of quality is most of the work
Size & shape
Medium · effort split not classified (source measured from disk; the effort-tier breakdown is a C#-only syntax walk)
This codebase represents roughly ~0.6 person-years of build effort (about ~€82,000 to rebuild). Its weakest lens is Maturity at 55% — the part of that asset most exposed by the findings below.
How we model this: boilerplate at a scaffolding rate + logic × domain Standard (×1.2) — domain model × a 0.9× quality factor, at €60–95/h; indicative, ±~30% · size measured directly from source · effort from total production LoC as straight-line logic (the tier split is a C#-only syntax walk), a conservative lower bound. Indicative only — most sensitive to the hourly rate and the domain tier (both tunable in config).
Top priorities
The highest-leverage moves; the full ranked list is in the Roadmap below.
1
Start an ADR log (docs/adr/) recording significant decisions and their rationale.
Reconcile the README with reality: Hybrid AI Autocompletion System claimed but no local DeepSeek-R1 model or Ollama pipeline is present; Cloud Reasoning Bridge claimed with Gemini via ADK-Gemini crate not shown.
Value concentrated against a weak lens · Medium · Value at risk
This is a Medium asset (~0.6 person-years to rebuild), and its weakest lens is Maturity at 55%. The operational and business risk on an asset this size concentrates there — that's where remediation buys the most protection.
→ Direct remediation budget at Maturity first — highest risk-reduction per euro on an asset this size.
Highest-leverage move · Medium · Leverage
Of everything flagged, the best return on effort is: Start an ADR log (docs/adr/) recording significant decisions and their rationale. The rest can wait behind it.
Evidence: priority ranking: top of 5 ranked by impact/effort
→ Start an ADR log (docs/adr/) recording significant decisions and their rationale.
A velocity tax on every change · Medium · Economics
The code-quality signals (complexity, duplication, cohesion) average 5.5/10, which acts as a tax on every change in the weaker areas: modifications there plausibly cost on the order of 6–14% more than in clean code, and the tax compounds as the codebase grows. (A modelled estimate, not a measured fact.)
Evidence: D1/D2 complexity, D4 duplication, D6 cohesion: averaging 5.5/10 across the code-quality signals
→ Pay it down where churn is highest — the hotspots — not everywhere; that's where the tax is actually paid.
At a glance — Code Health · 61% · Adequate · gated by D2
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A06:2021 — Vulnerable & Outdated Components
23
High / Critical
A05:2021 — Security Misconfiguration
5
High / Critical
A03:2021 — Injection
4
High / Critical
Roadmap
Begin by establishing an ADR log to record significant architectural decisions and their rationale. Reconcile the README with reality by removing claims about local models and missing pipelines, and add a testing section to explain how to run the test suite. Resolve the four high-priority static analysis findings, focusing on the release and dependabot configuration files. Finally, implement a manual approval gate for releases to ensure bad builds are stopped before users can download them.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Start an ADR log (docs/adr/) recording significant decisions and their rationale.
Reconcile the README with reality: Hybrid AI Autocompletion System claimed but no local DeepSeek-R1 model or Ollama pipeline is present; Cloud Reasoning Bridge claimed with Gemini via ADK-Gemini crate not shown.
Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 27 of 28 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 1 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.4 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 28 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
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, 214 of 225 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D19 Documentation Quality — LLM provider failed — The model provider returned an unusable result, so this LLM-assisted dimension fell back to a measurement gap (confidence 0) rather than a penalty. Re-run with a reachable provider to score it.
D30 Dependency Vulnerabilities — scanner not present in this environment — The backing tool was not installed where this scan ran, so this dimension was not scored. Install the tool (or run in the hosted environment, where it is always present) for a graded result.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
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 (jscpd) — 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.
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").
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.
D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
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").
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
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.
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.
DM4 Rich vs anemic domain model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
The LLM boundary
LLM-set scores this run (2): D21, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score (documentation, ADR quality, naming, comment value, onboarding) — D25 sets the ADR-conformance fraction over sampled code, D22 judges API accuracy over a sample. These are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
49 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was KeyMapKey::fmt at 240. A further 6 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being KeyMapKey::from_str at 139 — they are counted neither in the figure above nor in this dimension's score.
+ 27 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 7 app finding(s) in Cyclomatic Complexity — start with app.rs (7). — One of this dimension's main actionable groups (7 warning-level).
Resolve the 3 WindowTabData finding(s) in Cyclomatic Complexity — start with window_tab.rs (3). — One of this dimension's main actionable groups (3 warning-level).
Resolve the 3 MainSplitData finding(s) in Cyclomatic Complexity — start with main_split.rs (3). — One of this dimension's main actionable groups (3 warning-level).
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 50 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 8 app finding(s) in Cognitive Complexity — start with app.rs (8). — One of this dimension's main actionable groups (8 warning-level).
Resolve the 6 view finding(s) in Cognitive Complexity — start with view.rs (6). — One of this dimension's main actionable groups (6 warning-level).
Resolve the 5 MainSplitData finding(s) in Cognitive Complexity — start with main_split.rs (5). — One of this dimension's main actionable groups (5 warning-level).
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes7.9 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 26 FileTooLong finding(s) in God Classes — start with view.rs (2), app.rs, editor.rs. — One of this dimension's main actionable groups (26 warning-level).
Resolve the 9 TooManyMethods finding(s) in God Classes — start with editor.rs, proxy.rs, doc.rs. — One of this dimension's main actionable groups (9 warning-level).
Resolve the 1 TooManyFunctions finding(s) in God Classes — start with app.rs. — One of this dimension's main actionable groups (1 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Copy-pasted code that should be shared instead.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Git-history secret scan via gitleaks detect over full history in an isolated checkout; each match flagged High. Exhaustive; degrades cleanly when tool absent.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
High: dependabot-missing-cooldown · ×4.github/dependabot.yml:3detected by semgrep finding
What to do
Resolve the 4 High finding(s) in Static Analysis (SAST) — start with release.yml (3), dependabot.yml. — One of this dimension's main actionable groups (4 issue-level).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
High IaC: DS-0029 · ×2extra/linux/docker/debian/Dockerfiledetected by trivy finding
Medium IaC: DS-0001 · ×3extra/linux/docker/alpine/Dockerfiledetected by trivy finding
What to do
Resolve the 2 High IaC finding(s) in IaC & Container Security — start with Dockerfile (2). — One of this dimension's main actionable groups (2 issue-level).
Resolve the 3 Medium IaC finding(s) in IaC & Container Security — start with Dockerfile (3). — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling; coupling through a build step, config, or non-source file isn't seen.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
Resolve the 1 No build provenance finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 No SBOM finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether dependencies have known published vulnerabilities (CVEs) per the OSV database — read natively from whatever lockfile the repository ships (Cargo, npm, Go, Python, Maven, RubyGems, …). D33 and D30 add ecosystem-specific scanners on top for npm and .NET.
Method: Multi-ecosystem dependency-CVE scan via osv-scanner --recursive (queries the osv.dev database + parses lockfiles natively across ecosystems: npm package-lock/yarn/pnpm/bun, Go go.mod, Rust Cargo.lock, Maven/Gradle pom.xml/gradle.lockfile, PyPI requirements.txt/poetry.lock/Pipfile.lock, Composer composer.lock, RubyGems Gemfile.lock, Hex mix.lock, pub pubspec.lock, Swift Package.resolved); severity tally (Critical/High/Medium/Low) to 0-10 tight normalizer (8.0). NotApplicable only when the repo declares no supported non-.NET dependency lockfile (a NuGet-only repo stays NotApplicable — .NET CVEs are D30's domain); coverage needs a resolved lockfile. Additive to D33 (trivy fs); exhaustive + deterministic, DB kept fresh.
High CVE: [GHSA redacted] · ×2Cargo.lockdetected by osv-scanner finding
Medium advisory (unmaintained): RUSTSEC-2025-0141 · ×7Cargo.lockdetected by osv-scanner finding
Medium CVE: RUSTSEC-2024-0445 · ×6Cargo.lockdetected by osv-scanner finding
Medium advisory (unsound): RUSTSEC-2026-0190 · ×4Cargo.lockdetected by osv-scanner finding
Medium vulnerability: RUSTSEC-2026-0204 · ×4Cargo.lockdetected by osv-scanner finding
What to do
Resolve the 2 High CVE finding(s) in OSV Dependency Vulnerabilities — start with Cargo.lock (2). — One of this dimension's main actionable groups (2 issue-level).
Resolve the 7 Medium advisory (unmaintained) finding(s) in OSV Dependency Vulnerabilities — start with Cargo.lock (7). — One of this dimension's main actionable groups (7 warning-level).
Resolve the 6 Medium CVE finding(s) in OSV Dependency Vulnerabilities — start with Cargo.lock (6). — One of this dimension's main actionable groups (6 warning-level).
Detailed fixes: d38_recommendation.md · top locations in Appendix A, every location in findings.md.
Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.
Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.
Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.
Other · Domain Modelling — Whether domain identifiers are strongly typed (a newtype wrapper) rather than raw primitives — consistency once an idiom exists.
Method: Roslyn (DDD-gated): strongly-typed id adoption on domain entities/events; raw Guid/int/string ids counted versus wrapped types. Deterministic, adoption percentage.
Coverage: Population: id-like members by *Id/*Key NAME suffix; strongly-typed-ID shape then checked semantically — non-suffixed identifiers are not seen.
`Dispatcher.window_id` is a raw primitive id while the repo already defines newtype typed-ids — an inconsistently-adopted typed-id idiom. Give this identity its own newtype so it can't be confused with another entity's id or a plain value. — dispatch.rs:63
`Dispatcher.tab_id` is a raw primitive id while the repo already defines newtype typed-ids — an inconsistently-adopted typed-id idiom. Give this identity its own newtype so it can't be confused with another entity's id or a plain value. — dispatch.rs:64
What to do
Adopt the repo's newtype typed-id idiom consistently — wrap every entity identity in its own newtype.
Do you agree with this assessment?
DM4 · Rich vs anemic domain model10.0 / 10Exemplary✓ Tool-verified
Other · Domain Modelling — Whether domain entities own their behaviour (invariant-enforcing commands) rather than being data-only structs driven by a foreign service.
Method: Roslyn (DDD-gated): entity method BODIES classified mutator-vs-query — only methods that mutate the entity's own declared state count as invariant-protecting behaviour, so a getter/passthrough doesn't rescue an anemic class. Deterministic, exhaustive over domain-layer entities.
Coverage: Population: entities by name/base convention; rich-vs-anemic judged by classifying each method body mutator-vs-query — logic-bearing domain types outside the convention are invisible.
Other · Domain Modelling — Whether a domain type's identity-bearing field stays immutable — a `pub` mutable field under a hand-rolled Hash/PartialEq breaks the value-identity invariant.
Method: Roslyn (DDD-gated): public setters on entities detected; score softened when Marten/EF rehydration frameworks present. Deterministic, framework-aware.
Coverage: Population: entities by convention; encapsulation (setter shape) checked exhaustively within the set.
Other · Domain Modelling — Whether the domain layer stays free of infrastructure dependencies — a domain aggregate fused to a persistence ORM (diesel/sea-orm/sqlx) on its own declaration (active-record) couples the domain to infrastructure. The clean-architecture dependency rule.
Method: Roslyn (DDD-gated): domain-layer types scanned for infrastructure usage in member SIGNATURES and inside method/accessor BODIES — resolved calls and object-creations into EF/Marten/HTTP/Mongo/Redis/message-bus types (not just a namespace allowlist). Deterministic, symbol-resolved, exhaustive over domain-layer bodies, DDD-native.
Coverage: Domain layer identified by NAMESPACE heuristic; infrastructure then resolved by symbol in member SIGNATURES and method/accessor BODIES — rename the layer and the check evaporates.
Other · Event Sourcing — Whether the recovery-replay fold is deterministic — state derived purely from each event's own fields, no clock/random/IO on the replay path.
Method: Roslyn syntax scan (event-sourcing gated): Apply/When folds checked for forbidden tokens (DateTime.Now, Guid.NewGuid, Random, IO), stripped of comments/strings. Deterministic, hard fact per fold.
Other · Event Sourcing — Whether domain events stay immutable (private fields, set once) rather than carrying mutable state.
Method: Roslyn scan (event-sourcing gated): persisted events checked for public setters; immutability verified per property/field. Deterministic, hard fact.
Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Add a 'Testing' section to the root README — how to run the test suite.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 4 of 4 project(s) that lack one — worth up to 2 pts.
Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).
Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.
Hybrid AI Autocompletion System claimed but no local DeepSeek-R1 model or Ollama pipeline is present
Cloud Reasoning Bridge claimed with Gemini via ADK-Gemini crate not shown
What to do
Reconcile the README with reality: Hybrid AI Autocompletion System claimed but no local DeepSeek-R1 model or Ollama pipeline is present; Cloud Reasoning Bridge claimed with Gemini via ADK-Gemini crate not shown.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
What to do
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
What to do
Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.
Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.
Do you agree with this assessment?
Reference — by lens
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Not included — 73 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
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.
AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
AX1 Captive dependencies — no DI registrations detected
AX10 Code composition — not assessed — code composition is computed by ROLE over the .NET document set and none was loaded for this repository, because it is written in another language or the solution failed to load. This is a gap in the analyzer, not a finding about this repository
AX2 Stateful singletons — no singleton implementations detected
AX3 Project dependency cycles — not assessed — project cycles and dependency direction are computed over the .NET project-reference graph and none was loaded for this repository, because it is written in another language or the solution failed to load. This is a gap in the analyzer, not a finding about this repository
AX4 Dependency direction — not assessed — project cycles and dependency direction are computed over the .NET project-reference graph and none was loaded for this repository, because it is written in another language or the solution failed to load. This is a gap in the analyzer, not a finding about this repository
AX5 Architecture & structure — not assessed — architecture style/structure is computed from the .NET project graph (projects, types, namespaces) and no such graph was loaded for this repository, because it is written in another language or the solution 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 the .NET type surface and none was loaded for this repository, because it is written in another language or the solution 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 — not assessed — test isolation is computed from the .NET project graph (which projects are test projects, and what they reference) and no such graph was loaded for this repository, because it is written in another language or the solution failed to load. This is a gap in the analyzer, not a finding about this repository
AXB2 Runtime readiness — no data
C1 Data Protection — Not assessed: these personal data controls are read from C# source (attributes, middleware, entity/column names, guard methods) and no C# source was loaded for this repository — because it is written in another language, or the solution failed to load. Absence of a .NET idiom is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C2 Access Controls — Not assessed: these authorization controls are read from C# source (attributes, middleware, entity/column names, guard methods) and no C# source was loaded for this repository — because it is written in another language, or the solution failed to load. Absence of a .NET idiom is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C3 Audit Trail — Not assessed: these audit controls are read from C# source (attributes, middleware, entity/column names, guard methods) and no C# source was loaded for this repository — because it is written in another language, or the solution failed to load. Absence of a .NET idiom is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C4 Data Retention — Not assessed: these retention controls are read from C# source (attributes, middleware, entity/column names, guard methods) and no C# source was loaded for this repository — because it is written in another language, or the solution failed to load. Absence of a .NET idiom is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from C# source (attributes, middleware, entity/column names, guard methods) and no C# source was loaded for this repository — because it is written in another language, or the solution failed to load. Absence of a .NET idiom is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
D10 Test Quality — ~545 lines of test source are present (.rs) but the test-quality collector reads C# only, so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
D11 Test Reliability — Test reliability not included
D12 Dependency Hygiene — Dependency hygiene not measured — dependency manifest found but not parsed for hygiene
D14 License Compliance — Not scored — this repository's package manifest is not parsed for licence data yet. A gap in the analyzer's language coverage, NOT a finding that the repository's licenses are compliant (a Cargo manifest), which this pass does not parse yet — so this dimension asserts nothing about this repository's licensing in either direction.
D16 Bus Factor — single-maintainer — knowledge-concentration (bus factor) risk
D17 Explicit Debt — explicit-debt markers are read through a C# workspace today, so they were not read for this repository's language — this asserts nothing about how many markers the code carries. Not scored — this is a gap in the analyzer, not a finding about this repository
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D19 Documentation Quality — LLM evaluation failed
D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
D22 Internal API Consistency — No exposed public API
D23 Boundary Type-Coupling — Production source is present (.rs) but bounded contexts are resolved over the C#/VB project set, which exposed none, so context scope could not be assessed. Not scored — this is a gap in the analyzer, not a verdict about this repository. Declaring the codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed — see the recommendation on this dimension for where. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["Acme.Billing"]`, `Catalog: ["Acme.Catalog"]`.
D24 Comment Value — No inline comments to assess — comment value is not applicable here.
D25 ADR Conformance — no ADRs to check
D26 Project Cohesion — Project cohesion is assessed over the .NET project set; this target exposed no projects, so project size and spread could not be assessed. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
D27 Navigability — No calls could be sampled, so navigability was not assessed — tracing effort is measured over resolved call sites and this target exposed none. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Cargo manifest — not scanned yet) — where an OSV-supported manifest exists, dependency vulnerabilities for this repository are reported under D38 instead.
D32 Data Compliance (PII/GDPR) — No PII/GDPR ruleset is bundled (the public p/gdpr semgrep pack was retired) — data compliance is not assessed in this scan.
D33 JS/npm Dependency Vulnerabilities — No JS/npm manifest or lockfile found outside build output (package.json, package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb); no JS dependencies to scan.
D34 Knowledge Freshness — early-stage repository — too little history to judge knowledge freshness
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D5 Coupling — Inter-project coupling could not be assessed — no analyzable project graph was found for this repository. Not scored: a gap in the analyzer's reach, not a verdict about this repository. (Coupling here is Martin afferent/efferent/instability plus reference cycles across a project-reference graph, read today from .NET project files; other ecosystems' module graphs are not read yet.)
D6 Cohesion (LCOM4) — Cohesion (LCOM4) is measured over a C#/VB class graph, and this repository's production source is .rs, which this pass does not read — so no class could be assessed. Not scored — this is a gap in the analyzer, not a finding about this repository.
D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
D8 Code Coverage — Coverage not included — suite not readable by the collector
D9 Test Distribution — Test source is present (.rs) but the test-pyramid classifier reads C# only, so its unit/integration/BDD/E2E split couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
DM1 Aggregate boundaries — not scored for Rust: aggregate-vs-value-object classification cannot be told apart in source (every struct-holding-struct reads alike), and a child COLLECTION (legitimate membership) vs a single embedded aggregate is indistinguishable — advisory (the Swift/Dart parity)
DM3 Integration-event coupling — not scored for Rust: a cross-crate domain leak cannot be told apart in source from a legitimate shared-kernel crate, and most repositories ship a single crate — reported as guidance rather than measured
DM7 Repository granularity — not scored for Rust: 'a repository per CHILD entity' needs the aggregate-root structure, which is not source-resolvable — reported as guidance rather than measured
ED2 Event/command shape — not gated in Rust source-only: a command with >1 competing handler needs a dispatch/call graph the source-only frontend cannot resolve (inferred/generic call owners decline) — advisory
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
GD1 Unfinished & placeholder code — no source files
IC1 Incompleteness & stubs — not analysed — these correctness checks are read from C# source and none was loaded for this repository, because it is written in another language or the solution failed to load. This is a gap in the analyzer, not a finding about this repository
P12 CI test-gate honesty — no data
P2 Observability — Observability was not assessed: this check reads a source model that does not carry this repository's product — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of a logging idiom this check recognises is NOT evidence that this repo lacks structured logging (it may log through its own ecosystem's logger). This is a gap in the analyzer, not a finding about this repository.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
P7 Outbound HTTP resilience — not applicable — this isn't a service/API/worker
P8 Schema migrations — not assessed — schema-migration practice is read from 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
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `cargo llvm-cov --lcov --output-path lcov.info`) into the repo working tree before the scan — a CI step is the usual place, since the artefact is commonly gitignored, or wire coverage collection into CI, to enable this cross-layer check
PF1 Benchmark discipline — Performance was not assessed: this lens reads a source model that was not loaded for this repository, because the repository is written in a language this lens does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository — in particular it is NOT a statement that this repo is unpackaged or performance-careless.
PF2 Allocation hygiene — Performance was not assessed: this lens reads a source model that was not loaded for this repository, because the repository is written in a language this lens does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository — in particular it is NOT a statement that this repo is unpackaged or performance-careless.
PF3 Async & latency hygiene — Performance was not assessed: this lens reads a source model that was not loaded for this repository, because the repository is written in a language this lens does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository — in particular it is NOT a statement that this repo is unpackaged or performance-careless.
S1 Web-Security Posture — Not assessed: these web-security controls are read from C# source (attributes, middleware, entity/column names, guard methods) and no C# source was loaded for this repository — because it is written in another language, or the solution failed to load. Absence of a .NET idiom is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
X1 Async correctness — not analysed — these correctness checks are read from C# source and none was loaded for this repository, because it is written in another language or the solution failed to load. This is a gap in the analyzer, not a finding about this repository
X2 Cancellation propagation — not analysed — these correctness checks are read from C# source and none was loaded for this repository, because it is written in another language or the solution failed to load. This is a gap in the analyzer, not a finding about this repository
X3 Exception handling — not analysed — these correctness checks are read from C# source and none was loaded for this repository, because it is written in another language or the solution failed to load. This is a gap in the analyzer, not a finding about this repository
X4 Structured logging — not analysed — these correctness checks are read from C# source and none was loaded for this repository, because it is written in another language or the solution failed to load. This is a gap in the analyzer, not a finding about this repository
X5 Nullable reference types — not analysed — these correctness checks are read from C# source and none was loaded for this repository, because it is written in another language or the solution failed to load. This is a gap in the analyzer, not a finding about this repository
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
High: dependabot-missing-cooldown .github/dependabot.yml:3— This Dependabot configuration does not set a cooldown period. Newly published packages can be malicious or unstable. Add a `cooldown` block with `default-days: 7` to each `package-ecosystem` entry under `updates` to wait 7 days before proposing updates to newly published package versions. Reference: https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#cooldown. This is a semgrep security-AUDIT rule reporting a POLICY that is absent or weaker than its recommendation, not an exploitable defect. Confirm whether the current setting is a deliberate decision for this repository — and apply the change where it is not; where it is (a policy your release process already enforces elsewhere, or one this repository has consciously opted out of), record the decision and leave the configuration as it is. This configuration file has 2 such entries; one cooldown decision clears them all — reported once.
High: gha-workflow-env-secret .github/workflows/release.yml:24— A secret is exposed in the workflow-level `env:` block, making it available to every job and step in this workflow — including any untrusted code run in pull-request workflows. Scope secrets as narrowly as possible: prefer step-level `env:` so the secret is only available where it is actually needed. This is a semgrep security-AUDIT rule reporting a POLICY that is absent or weaker than its recommendation, not an exploitable defect. Confirm whether the current setting is a deliberate decision for this repository — and apply the change where it is not; where it is (a policy your release process already enforces elsewhere, or one this repository has consciously opted out of), record the decision and leave the configuration as it is.
High: run-shell-injection .github/workflows/release.yml:40— Using variable interpolation `${{...}}` with `github` context data in a `run:` step could allow an attacker to inject their own code into the runner. This would allow them to steal secrets and code. `github` context data can have arbitrary user input and should be treated as untrusted. Instead, use an intermediate environment variable with `env:` to store the data and use the environment variable in the `run:` script. Reference it as a shell VARIABLE rather than a `${{ }}` interpolation, using your shell's own syntax (`"$ENVVAR"` in bash, `$env:ENVVAR` in PowerShell), so the value is passed as data and never re-expanded as code.
High: run-shell-injection .github/workflows/release.yml:336— Using variable interpolation `${{...}}` with `github` context data in a `run:` step could allow an attacker to inject their own code into the runner. This would allow them to steal secrets and code. `github` context data can have arbitrary user input and should be treated as untrusted. Instead, use an intermediate environment variable with `env:` to store the data and use the environment variable in the `run:` script. Reference it as a shell VARIABLE rather than a `${{ }}` interpolation, using your shell's own syntax (`"$ENVVAR"` in bash, `$env:ENVVAR` in PowerShell), so the value is passed as data and never re-expanded as code.
High IaC: DS-0029 extra/linux/docker/debian/Dockerfile— 'apt-get' missing '--no-install-recommends'
High IaC: DS-0029 extra/linux/docker/ubuntu/Dockerfile— 'apt-get' missing '--no-install-recommends'
D38 · OSV Dependency Vulnerabilities· High CVE · ×2
High CVE: [GHSA redacted] Cargo.lock— quinn-proto 0.11.14: [GHSA redacted] — quinn-proto is not declared in this repo's manifests: it is pulled in transitively by quinn 0.11.9, so upgrade the dependency that requires it (or force it with `cargo update -p quinn-proto@0.11.14 --precise 0.11.15`, or a `[patch.crates-io]` entry).
High CVE: [GHSA redacted] Cargo.lock— wasmtime-wasi 14.0.4: [GHSA redacted] — upgrade to 24.0.9. This is 1 of 4 advisories this scan raises against wasmtime-wasi 14.0.4, and their fixed versions do not agree — anything below 24.0.11 still leaves at least one of them open. Take this package to 24.0.11 or later: that is the floor for the package, not this row's target alone. One upgrade of wasmtime-wasi 14.0.4 clears all 3 advisories it raises: [GHSA redacted], RUSTSEC-2026-0182, RUSTSEC-2026-0188.
FileTooLong: src/app.rs velocirust-app/src/app.rs:0— FileTooLong — 3220 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted).
FileTooLong: src/editor.rs velocirust-app/src/editor.rs:0— FileTooLong — 2374 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted).
FileTooLong: src/main_split.rs velocirust-app/src/main_split.rs:0— FileTooLong — 2202 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted).
FileTooLong: src/window_tab.rs velocirust-app/src/window_tab.rs:0— FileTooLong — 2075 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted).
FileTooLong: editor/view.rs velocirust-app/src/editor/view.rs:0— FileTooLong — 1925 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted).
FileTooLong: src/language.rs velocirust-core/src/language.rs:0— FileTooLong — 1671 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted).
FileTooLong: src/doc.rs velocirust-app/src/doc.rs:0— FileTooLong — 1464 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted).
FileTooLong: plugin/mod.rs velocirust-proxy/src/plugin/mod.rs:0— FileTooLong — 1353 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted).
FileTooLong: src/dispatch.rs velocirust-proxy/src/dispatch.rs:0— FileTooLong — 1246 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted).
FileTooLong: src/palette.rs velocirust-app/src/palette.rs:0— FileTooLong — 1190 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted).
FileTooLong: plugin/psp.rs velocirust-proxy/src/plugin/psp.rs:0— FileTooLong — 1053 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted).
FileTooLong: src/settings.rs velocirust-app/src/settings.rs:0— FileTooLong — 1036 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted).
FileTooLong: src/proxy.rs velocirust-rpc/src/proxy.rs:0— FileTooLong — 821 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted).
FileTooLong: src/plugin.rs velocirust-app/src/plugin.rs:0— FileTooLong — 725 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted).
FileTooLong: src/config.rs velocirust-app/src/config.rs:0— FileTooLong — 716 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted).
FileTooLong: src/dap_types.rs velocirust-rpc/src/dap_types.rs:0— FileTooLong — 698 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted).
FileTooLong: src/command.rs velocirust-app/src/command.rs:0— FileTooLong — 592 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted).
FileTooLong: keypress/keymap.rs velocirust-app/src/keypress/keymap.rs:0— FileTooLong — 581 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted).
FileTooLong: terminal/data.rs velocirust-app/src/terminal/data.rs:0— FileTooLong — 576 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted).
FileTooLong: terminal/panel.rs velocirust-app/src/terminal/panel.rs:0— FileTooLong — 570 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted).
FileTooLong: plugin/dap.rs velocirust-proxy/src/plugin/dap.rs:0— FileTooLong — 568 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted).
FileTooLong: src/text_input.rs velocirust-app/src/text_input.rs:0— FileTooLong — 566 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted).
FileTooLong: panel/debug_view.rs velocirust-app/src/panel/debug_view.rs:0— FileTooLong — 555 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted).
FileTooLong: terminal/view.rs velocirust-app/src/terminal/view.rs:0— FileTooLong — 542 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted).
FileTooLong: plugin/catalog.rs velocirust-proxy/src/plugin/catalog.rs:0— FileTooLong — 526 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted).
app::editor_tab_content (cognitive 60) velocirust-app/src/app.rs:1222— app::editor_tab_content has cognitive complexity 60 (threshold 15). Drivers by points: if/else 56, boolean chains 3, match/switch 1 (nesting depth added 30). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
app::split_resize_border (cognitive 58) velocirust-app/src/app.rs:1633— app::split_resize_border has cognitive complexity 58 (threshold 15). Drivers by points: if/else 38, match/switch 12, loops 8 (nesting depth added 27). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
app::launch (cognitive 57) velocirust-app/src/app.rs:3715— app::launch has cognitive complexity 57 (threshold 15). Drivers by points: if/else 38, loops 10, match/switch 9 (nesting depth added 22). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
app::editor_tab_header (cognitive 46) velocirust-app/src/app.rs:683— app::editor_tab_header has cognitive complexity 46 (threshold 15). Drivers by points: if/else 42, boolean chains 2, loops 1, match/switch 1 (nesting depth added 9). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
app::palette_item (cognitive 37) velocirust-app/src/app.rs:2219— app::palette_item has cognitive complexity 37 (threshold 15). Drivers by points: if/else 34, match/switch 3 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
app::workspace_tab_header (cognitive 37) velocirust-app/src/app.rs:3375— app::workspace_tab_header has cognitive complexity 37 (threshold 15). Drivers by points: if/else 34, boolean chains 2, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
app::editor_tab (cognitive 29) velocirust-app/src/app.rs:1429— app::editor_tab has cognitive complexity 29 (threshold 15). Drivers by points: if/else 19, match/switch 10 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
app::listen_local_socket (cognitive 16) velocirust-app/src/app.rs:4131— app::listen_local_socket has cognitive complexity 16 (threshold 15). Drivers by points: if/else 13, loops 3 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
app::editor_tab (cyclomatic 36) velocirust-app/src/app.rs:1429— app::editor_tab has cyclomatic complexity 36 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
app::launch (cyclomatic 36) velocirust-app/src/app.rs:3715— app::launch has cyclomatic complexity 36 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
app::editor_tab_header (cyclomatic 26) velocirust-app/src/app.rs:683— app::editor_tab_header has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
app::split_resize_border (cyclomatic 24) velocirust-app/src/app.rs:1633— app::split_resize_border has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
app::editor_tab_content (cyclomatic 23) velocirust-app/src/app.rs:1222— app::editor_tab_content has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
app::workspace_tab_header (cyclomatic 21) velocirust-app/src/app.rs:3375— app::workspace_tab_header has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
app::palette_item (cyclomatic 19) velocirust-app/src/app.rs:2219— app::palette_item has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D38 · OSV Dependency Vulnerabilities· Medium advisory (unmaintained) · ×7
Medium advisory (unmaintained): RUSTSEC-2025-0141 Cargo.lock— bincode 1.3.3: RUSTSEC-2025-0141 — no fixed version exists: the advisory reports the package as unmaintained. bincode is not declared in this repo's manifests: it is pulled in transitively by wasmtime 14.0.4 and wasmtime-cache 14.0.4 and 1 other, so the action is on the dependency that requires it — upgrade or replace that dependent.
Medium advisory (unmaintained): RUSTSEC-2025-0057 Cargo.lock— fxhash 0.2.1: RUSTSEC-2025-0057 — no fixed version exists: the advisory reports the package as unmaintained. fxhash is not declared in this repo's manifests: it is pulled in transitively by fxprof-processed-profile 0.6.0, so the action is on the dependency that requires it — upgrade or replace that dependent.
Medium advisory (unmaintained): RUSTSEC-2020-0168 Cargo.lock— mach 0.3.2: RUSTSEC-2020-0168 — no fixed version exists: the advisory reports the package as unmaintained. mach is not declared in this repo's manifests: it is pulled in transitively by wasmtime-runtime 14.0.4, so the action is on the dependency that requires it — upgrade or replace that dependent.
Medium advisory (unmaintained): RUSTSEC-2024-0436 Cargo.lock— paste 1.0.15: RUSTSEC-2024-0436 — no fixed version exists: the advisory reports the package as unmaintained. paste is not declared in this repo's manifests: it is pulled in transitively by metal 0.31.0 and wasmtime 14.0.4 and 1 other, so the action is on the dependency that requires it — upgrade or replace that dependent.
Medium advisory (unmaintained): RUSTSEC-2025-0134 Cargo.lock— rustls-pemfile 1.0.4: RUSTSEC-2025-0134 — no fixed version exists: the advisory reports the package as unmaintained. rustls-pemfile is not declared in this repo's manifests: it is pulled in transitively by reqwest 0.11.27, so the action is on the dependency that requires it — upgrade or replace that dependent.
Medium advisory (unmaintained): RUSTSEC-2026-0206 Cargo.lock— rustybuzz 0.14.1: RUSTSEC-2026-0206 — no fixed version exists: the advisory reports the package as unmaintained. rustybuzz is not declared in this repo's manifests: it is pulled in transitively by cosmic-text 0.14.2, so the action is on the dependency that requires it — and every route to it here runs through floem-vger 0.3.1, which is pinned to a git revision, so `cargo update` cannot reach rustybuzz at all: that pinned `rev` has to move (or the dependent be replaced) first.
Medium advisory (unmaintained): RUSTSEC-2026-0192 Cargo.lock— ttf-parser 0.20.0: RUSTSEC-2026-0192 — no fixed version exists: the advisory reports the package as unmaintained. ttf-parser is not declared in this repo's manifests: it is pulled in transitively by fontdb 0.16.2, so the action is on the dependency that requires it — and every route to it here runs through floem-vger 0.3.1, which is pinned to a git revision, so `cargo update` cannot reach ttf-parser at all: that pinned `rev` has to move (or the dependent be replaced) first.
view::get_sticky_header_info (cognitive 40) velocirust-app/src/editor/view.rs:1164— view::get_sticky_header_info has cognitive complexity 40 (threshold 15). Drivers by points: if/else 38, boolean chains 2 (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
view::panel_container_view (cognitive 34) velocirust-app/src/panel/view.rs:210— view::panel_container_view has cognitive complexity 34 (threshold 15). Drivers by points: if/else 27, match/switch 4, boolean chains 3 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
view::editor_view (cognitive 21) velocirust-app/src/editor/view.rs:148— view::editor_view has cognitive complexity 21 (threshold 15). Drivers by points: if/else 20, boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
view::file_explorer_view (cognitive 19) velocirust-app/src/file_explorer/view.rs:307— view::file_explorer_view has cognitive complexity 19 (threshold 15). Drivers by points: if/else 17, match/switch 2 (nesting depth added 4). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
view::editor_gutter_breakpoint_view (cognitive 19) velocirust-app/src/editor/view.rs:1378— view::editor_gutter_breakpoint_view has cognitive complexity 19 (threshold 15). Drivers by points: if/else 17, loops 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
view::panel_picker (cognitive 16) velocirust-app/src/panel/view.rs:535— view::panel_picker has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 13, if/else 2, match/switch 1. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D38 · OSV Dependency Vulnerabilities· Medium CVE · ×6
Medium CVE: RUSTSEC-2024-0445 Cargo.lock— cap-primitives 2.0.2: RUSTSEC-2024-0445 — cap-primitives is not declared in this repo's manifests: it is pulled in transitively by cap-fs-ext 2.0.2 and cap-net-ext 2.0.2 and 2 others, so upgrade the dependency that requires it (or add a `[patch.crates-io]` entry for cap-primitives — 3.4.1 is not semver-compatible with the resolved 2.0.2, so `cargo update --precise` cannot select it).
Medium CVE: [GHSA redacted] Cargo.lock— grid 0.17.0: [GHSA redacted] — grid is not declared in this repo's manifests: it is pulled in transitively by taffy 0.8.3, so upgrade the dependency that requires it (or add a `[patch.crates-io]` entry for grid — 1.0.1 is not semver-compatible with the resolved 0.17.0, so `cargo update --precise` cannot select it).
Medium CVE: [GHSA redacted] Cargo.lock— openssl 0.10.79: [GHSA redacted] — openssl is not declared in this repo's manifests: it is pulled in transitively by native-tls 0.2.18, so upgrade the dependency that requires it (or force it with `cargo update -p openssl@0.10.79 --precise 0.10.80`, or a `[patch.crates-io]` entry).
Medium CVE: [GHSA redacted] Cargo.lock— time 0.3.45: [GHSA redacted] — time is not declared in this repo's manifests: it is pulled in transitively by adk-gemini 0.5.0 and plist 1.8.0 and 1 other, so upgrade the dependency that requires it (or force it with `cargo update -p time@0.3.45 --precise 0.3.47`, or a `[patch.crates-io]` entry). Note that tracing-appender 0.2.0 also requires time and is itself pinned to a git revision, so it has to move first — which is why an in-place `cargo update` fails here.
Medium CVE: RUSTSEC-2025-0055 Cargo.lock— tracing-subscriber 0.3.0: RUSTSEC-2025-0055 — tracing-subscriber is not a crates.io dependency here: it is pinned to git revision 908cc432a599, so the "0.3.0" beside it is that branch's own version string and there is no registry version to upgrade to. Move the pinned `rev` to a revision carrying the fix (the advisory is resolved in 0.3.20 upstream), together with any sibling crates pinned to the same revision.
Medium CVE: [GHSA redacted] Cargo.lock— wasmtime 14.0.4: [GHSA redacted] — upgrade to 24.0.6. This is 1 of 17 advisories this scan raises against wasmtime 14.0.4, and their fixed versions do not agree — anything below 36.0.7 still leaves at least one of them open. Take this package to 36.0.7 or later: that is the floor for the package, not this row's target alone. One upgrade of wasmtime 14.0.4 clears all 17 advisories it raises: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], RUSTSEC-2024-0438, RUSTSEC-2025-0046, RUSTSEC-2025-0118, RUSTSEC-2026-0086, RUSTSEC-2026-0088, RUSTSEC-2026-0089, RUSTSEC-2026-0094, RUSTSEC-2026-0095, RUSTSEC-2026-0096.
MainSplitData::get_editor_tab_child (cognitive 132) velocirust-app/src/main_split.rs:768— MainSplitData::get_editor_tab_child has cognitive complexity 132 (threshold 15). Drivers by points: if/else 107, match/switch 16, boolean chains 5, loops 4 (nesting depth added 67). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MainSplitData::editor_tab_child_close (cognitive 27) velocirust-app/src/main_split.rs:2006— MainSplitData::editor_tab_child_close has cognitive complexity 27 (threshold 15). Drivers by points: if/else 23, match/switch 4 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MainSplitData::split_move (cognitive 25) velocirust-app/src/main_split.rs:1605— MainSplitData::split_move has cognitive complexity 25 (threshold 15). Drivers by points: if/else 12, loops 8, boolean chains 4, match/switch 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MainSplitData::editor_tab_remove (cognitive 21) velocirust-app/src/main_split.rs:1778— MainSplitData::editor_tab_remove has cognitive complexity 21 (threshold 15). Drivers by points: if/else 20, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MainSplitData::editor_tab_child_close_by_kind (cognitive 18) velocirust-app/src/main_split.rs:1952— MainSplitData::editor_tab_child_close_by_kind has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11, loops 5, boolean chains 1, match/switch 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EditorData::run_multi_selection_command (cognitive 81) velocirust-app/src/editor.rs:611— EditorData::run_multi_selection_command has cognitive complexity 81 (threshold 15). Drivers by points: if/else 58, loops 18, boolean chains 4, match/switch 1 (nesting depth added 56). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EditorData::run_focus_command (cognitive 71) velocirust-app/src/editor.rs:856— EditorData::run_focus_command has cognitive complexity 71 (threshold 15). Drivers by points: if/else 62, loops 6, boolean chains 2, match/switch 1 (nesting depth added 31). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EditorData::go_to_definition (cognitive 33) velocirust-app/src/editor.rs:1317— EditorData::go_to_definition has cognitive complexity 33 (threshold 15). Drivers by points: if/else 29, match/switch 4 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EditorData::pointer_move (cognitive 17) velocirust-app/src/editor.rs:2805— EditorData::pointer_move has cognitive complexity 17 (threshold 15). Drivers by points: if/else 15, boolean chains 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EditorData::pointer_down (cognitive 16) velocirust-app/src/editor.rs:2649— EditorData::pointer_down has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9, match/switch 4, boolean chains 3 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D38 · OSV Dependency Vulnerabilities· Medium advisory (unsound) · ×4
Medium advisory (unsound): RUSTSEC-2026-0190 Cargo.lock— anyhow 1.0.102: RUSTSEC-2026-0190 — upgrade to 1.0.103. Note that floem_tiny_skia_renderer 0.2.0 also requires anyhow and is itself pinned to a git revision, so it has to move first — which is why an in-place `cargo update` fails here.
Medium advisory (unsound): RUSTSEC-2026-0183 Cargo.lock— git2 0.20.4: RUSTSEC-2026-0183 — upgrade to 0.21.0
Medium advisory (unsound): RUSTSEC-2026-0184 Cargo.lock— git2 0.20.4: RUSTSEC-2026-0184 — upgrade to 0.21.0
Medium advisory (unsound): RUSTSEC-2026-0186 Cargo.lock— memmap2 0.9.10: RUSTSEC-2026-0186 — memmap2 is not declared in this repo's manifests: it is pulled in transitively by fontdb 0.16.2 and fontdb 0.23.0 and 6 others, so upgrade the dependency that requires it (or force it with `cargo update -p memmap2@0.9.10 --precise 0.9.11`, or a `[patch.crates-io]` entry). Note that winit 0.30.7 also requires memmap2 and is itself pinned to a git revision, so it has to move first — which is why an in-place `cargo update` fails here.
D38 · OSV Dependency Vulnerabilities· Medium vulnerability · ×4
Medium vulnerability: RUSTSEC-2026-0204 Cargo.lock— crossbeam-epoch 0.9.18: RUSTSEC-2026-0204 — crossbeam-epoch is not declared in this repo's manifests: it is pulled in transitively by crossbeam-deque 0.8.6, so upgrade the dependency that requires it (or force it with `cargo update -p crossbeam-epoch@0.9.18 --precise 0.9.20`, or a `[patch.crates-io]` entry).
Medium vulnerability: RUSTSEC-2026-0194 Cargo.lock— quick-xml 0.38.4: RUSTSEC-2026-0194 — quick-xml is not declared in this repo's manifests: it is pulled in transitively by plist 1.8.0, so upgrade the dependency that requires it (or add a `[patch.crates-io]` entry for quick-xml — 0.41.0 is not semver-compatible with the resolved 0.38.4, so `cargo update --precise` cannot select it). One upgrade of quick-xml 0.38.4 clears all 2 advisories it raises: RUSTSEC-2026-0194, RUSTSEC-2026-0195.
Medium vulnerability: [GHSA redacted] Cargo.lock— tar 0.4.45: [GHSA redacted] — upgrade to 0.4.46
Medium vulnerability: [GHSA redacted] Cargo.lock— wasmtime-jit-debug 14.0.4: [GHSA redacted] — wasmtime-jit-debug is not declared in this repo's manifests: it is pulled in transitively by wasmtime-jit 14.0.4 and wasmtime-runtime 14.0.4, so upgrade the dependency that requires it (or add a `[patch.crates-io]` entry for wasmtime-jit-debug — 24.0.0 is not semver-compatible with the resolved 14.0.4, so `cargo update --precise` cannot select it).
WindowTabData::run_workbench_command (cyclomatic 194) velocirust-app/src/window_tab.rs:716— WindowTabData::run_workbench_command has cyclomatic complexity 194 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
WindowTabData::run_internal_command (cyclomatic 81) velocirust-app/src/window_tab.rs:1580— WindowTabData::run_internal_command has cyclomatic complexity 81 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
WindowTabData::handle_core_notification (cyclomatic 47) velocirust-app/src/window_tab.rs:2076— WindowTabData::handle_core_notification has cyclomatic complexity 47 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MainSplitData::get_editor_tab_child (cyclomatic 78) velocirust-app/src/main_split.rs:768— MainSplitData::get_editor_tab_child has cyclomatic complexity 78 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MainSplitData::editor_tab_child_close (cyclomatic 17) velocirust-app/src/main_split.rs:2006— MainSplitData::editor_tab_child_close has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MainSplitData::split_move (cyclomatic 16) velocirust-app/src/main_split.rs:1605— MainSplitData::split_move has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
PaletteData::select (cyclomatic 29) velocirust-app/src/palette.rs:1124— PaletteData::select has cyclomatic complexity 29 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
PaletteData::preview (cyclomatic 23) velocirust-app/src/palette.rs:1349— PaletteData::preview has cyclomatic complexity 23 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
PaletteData::new (cyclomatic 16) velocirust-app/src/palette.rs:119— PaletteData::new has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
WindowTabData::run_workbench_command (cognitive 223) velocirust-app/src/window_tab.rs:716— WindowTabData::run_workbench_command has cognitive complexity 223 (threshold 15). Drivers by points: if/else 212, match/switch 9, loops 2 (nesting depth added 128). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WindowTabData::run_internal_command (cognitive 72) velocirust-app/src/window_tab.rs:1580— WindowTabData::run_internal_command has cognitive complexity 72 (threshold 15). Drivers by points: if/else 52, match/switch 17, loops 3 (nesting depth added 38). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WindowTabData::handle_core_notification (cognitive 54) velocirust-app/src/window_tab.rs:2076— WindowTabData::handle_core_notification has cognitive complexity 54 (threshold 15). Drivers by points: if/else 38, loops 11, match/switch 5 (nesting depth added 35). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
remote::start_remote (cognitive 37) velocirust-app/src/proxy/remote.rs:76— remote::start_remote has cognitive complexity 37 (threshold 15). Drivers by points: if/else 24, match/switch 10, loops 2, boolean chains 1 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
remote::host_specification (cognitive 25) velocirust-app/src/proxy/remote.rs:394— remote::host_specification has cognitive complexity 25 (threshold 15). Drivers by points: match/switch 21, if/else 4 (nesting depth added 17). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
remote::download_remote (cognitive 22) velocirust-app/src/proxy/remote.rs:249— remote::download_remote has cognitive complexity 22 (threshold 15). Drivers by points: if/else 13, match/switch 9 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TerminalPanelData::terminal_stopped (cognitive 33) velocirust-app/src/terminal/panel.rs:384— TerminalPanelData::terminal_stopped has cognitive complexity 33 (threshold 15). Drivers by points: if/else 31, boolean chains 2 (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TerminalPanelData::get_stopped_run_debug_terminal (cognitive 30) velocirust-app/src/terminal/panel.rs:429— TerminalPanelData::get_stopped_run_debug_terminal has cognitive complexity 30 (threshold 15). Drivers by points: if/else 21, match/switch 5, loops 3, boolean chains 1 (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TerminalPanelData::run_debug_process (cognitive 20) velocirust-app/src/terminal/panel.rs:595— TerminalPanelData::run_debug_process has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10, loops 10 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TerminalView::paint_content (cognitive 33) velocirust-app/src/terminal/view.rs:326— TerminalView::paint_content has cognitive complexity 33 (threshold 15). Drivers by points: if/else 27, boolean chains 5, loops 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TerminalView::event_before_children (cognitive 21) velocirust-app/src/terminal/view.rs:499— TerminalView::event_before_children has cognitive complexity 21 (threshold 15). Drivers by points: if/else 17, match/switch 3, boolean chains 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TerminalView::paint (cognitive 21) velocirust-app/src/terminal/view.rs:629— TerminalView::paint has cognitive complexity 21 (threshold 15). Drivers by points: if/else 17, boolean chains 2, loops 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
settings::settings_item_view (cognitive 25) velocirust-app/src/settings.rs:547— settings::settings_item_view has cognitive complexity 25 (threshold 15). Drivers by points: if/else 22, match/switch 3 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
settings::color_section_list (cognitive 20) velocirust-app/src/settings.rs:818— settings::color_section_list has cognitive complexity 20 (threshold 15). Drivers by points: if/else 16, match/switch 4 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
settings::settings_view (cognitive 16) velocirust-app/src/settings.rs:325— settings::settings_view has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10, loops 4, boolean chains 2 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Syntax::parse (cognitive 20) velocirust-core/src/syntax/mod.rs:952— Syntax::parse has cognitive complexity 20 (threshold 15). Drivers by points: if/else 14, match/switch 4, loops 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Syntax::find_enclosing_parentheses (cognitive 18) velocirust-core/src/syntax/mod.rs:1171— Syntax::find_enclosing_parentheses has cognitive complexity 18 (threshold 15). Drivers by points: if/else 16, boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Syntax::find_enclosing_pair (cognitive 18) velocirust-core/src/syntax/mod.rs:1206— Syntax::find_enclosing_pair has cognitive complexity 18 (threshold 15). Drivers by points: if/else 17, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EditorData::run_focus_command (cyclomatic 71) velocirust-app/src/editor.rs:856— EditorData::run_focus_command has cyclomatic complexity 71 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
EditorData::run_multi_selection_command (cyclomatic 26) velocirust-app/src/editor.rs:611— EditorData::run_multi_selection_command has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Dispatcher::handle_notification (cyclomatic 70) velocirust-proxy/src/dispatch.rs:68— Dispatcher::handle_notification has cyclomatic complexity 70 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Dispatcher::handle_request (cyclomatic 65) velocirust-proxy/src/dispatch.rs:404— Dispatcher::handle_request has cyclomatic complexity 65 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TerminalData::resolve_key_event (cyclomatic 51) velocirust-app/src/terminal/data.rs:452— TerminalData::resolve_key_event has cyclomatic complexity 51 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
TerminalData::run_command (cyclomatic 44) velocirust-app/src/terminal/data.rs:64— TerminalData::run_command has cyclomatic complexity 44 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
view::panel_picker (cyclomatic 25) velocirust-app/src/panel/view.rs:535— view::panel_picker has cyclomatic complexity 25 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
view::panel_container_view (cyclomatic 19) velocirust-app/src/panel/view.rs:210— view::panel_container_view has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
settings::settings_item_view (cyclomatic 21) velocirust-app/src/settings.rs:547— settings::settings_item_view has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
settings::color_section_list (cyclomatic 21) velocirust-app/src/settings.rs:818— settings::color_section_list has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
editor::compute_screen_lines (cognitive 120) velocirust-app/src/editor.rs:3103— editor::compute_screen_lines has cognitive complexity 120 (threshold 15). Drivers by points: if/else 104, loops 12, match/switch 4 (nesting depth added 89). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
editor::find_hint (cognitive 19) velocirust-app/src/editor.rs:3274— editor::find_hint has cognitive complexity 19 (threshold 15). Drivers by points: if/else 14, boolean chains 2, loops 2, match/switch 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
HighlightIter::next (cognitive 116) velocirust-core/src/syntax/highlight.rs:487— HighlightIter::next has cognitive complexity 116 (threshold 15). Drivers by points: if/else 90, loops 22, boolean chains 4 (nesting depth added 72). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
HighlightIter::sort_layers (cognitive 20) velocirust-core/src/syntax/highlight.rs:450— HighlightIter::sort_layers has cognitive complexity 20 (threshold 15). Drivers by points: if/else 16, loops 4 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PluginCatalog::handle_notification (cognitive 85) velocirust-proxy/src/plugin/catalog.rs:476— PluginCatalog::handle_notification has cognitive complexity 85 (threshold 15). Drivers by points: if/else 63, loops 13, match/switch 9 (nesting depth added 49). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PluginCatalog::check_unactivated_volts (cognitive 29) velocirust-proxy/src/plugin/catalog.rs:223— PluginCatalog::check_unactivated_volts has cognitive complexity 29 (threshold 15). Drivers by points: if/else 14, loops 8, match/switch 7 (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Dispatcher::handle_notification (cognitive 84) velocirust-proxy/src/dispatch.rs:68— Dispatcher::handle_notification has cognitive complexity 84 (threshold 15). Drivers by points: if/else 60, match/switch 22, loops 2 (nesting depth added 46). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Dispatcher::handle_request (cognitive 74) velocirust-proxy/src/dispatch.rs:404— Dispatcher::handle_request has cognitive complexity 74 (threshold 15). Drivers by points: if/else 57, match/switch 11, loops 6 (nesting depth added 40). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
dispatch::git_diff_new (cognitive 33) velocirust-proxy/src/dispatch.rs:1517— dispatch::git_diff_new has cognitive complexity 33 (threshold 15). Drivers by points: if/else 15, loops 12, match/switch 5, boolean chains 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
dispatch::search_in_path (cognitive 20) velocirust-proxy/src/dispatch.rs:1677— dispatch::search_in_path has cognitive complexity 20 (threshold 15). Drivers by points: if/else 19, loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PaletteData::select (cognitive 31) velocirust-app/src/palette.rs:1124— PaletteData::select has cognitive complexity 31 (threshold 15). Drivers by points: if/else 15, match/switch 15, boolean chains 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PaletteData::new (cognitive 19) velocirust-app/src/palette.rs:119— PaletteData::new has cognitive complexity 19 (threshold 15). Drivers by points: if/else 16, boolean chains 3 (nesting depth added 3). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
FileExplorerData::reveal_in_file_tree (cognitive 30) velocirust-app/src/file_explorer/data.rs:407— FileExplorerData::reveal_in_file_tree has cognitive complexity 30 (threshold 15). Drivers by points: if/else 26, loops 4 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FileExplorerData::secondary_click (cognitive 18) velocirust-app/src/file_explorer/data.rs:482— FileExplorerData::secondary_click has cognitive complexity 18 (threshold 15). Drivers by points: if/else 18 (nesting depth added 4). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Doc::phantom_text (cognitive 29) velocirust-app/src/doc.rs:1622— Doc::phantom_text has cognitive complexity 29 (threshold 15). Drivers by points: if/else 26, boolean chains 2, match/switch 1 (nesting depth added 6). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Doc::get_semantic_styles (cognitive 17) velocirust-app/src/doc.rs:861— Doc::get_semantic_styles has cognitive complexity 17 (threshold 15). Drivers by points: if/else 15, loops 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BracketParser::update_code (cognitive 25) velocirust-core/src/syntax/mod.rs:176— BracketParser::update_code has cognitive complexity 25 (threshold 15). Drivers by points: if/else 17, match/switch 4, loops 3, boolean chains 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BracketParser::parse_bracket (cognitive 16) velocirust-core/src/syntax/mod.rs:262— BracketParser::parse_bracket has cognitive complexity 16 (threshold 15). Drivers by points: if/else 14, boolean chains 1, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
KeyMapKey::fmt (cyclomatic 240) velocirust-app/src/keypress/keymap.rs:349— KeyMapKey::fmt has cyclomatic complexity 240 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
buffer::language_id_from_path (cyclomatic 66) velocirust-proxy/src/buffer.rs:213— buffer::language_id_from_path has cyclomatic complexity 66 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
PluginCatalog::handle_notification (cyclomatic 57) velocirust-proxy/src/plugin/catalog.rs:476— PluginCatalog::handle_notification has cyclomatic complexity 57 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
HighlightIter::next (cyclomatic 41) velocirust-core/src/syntax/highlight.rs:487— HighlightIter::next has cyclomatic complexity 41 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PluginHostHandler::method_registered (cyclomatic 41) velocirust-proxy/src/plugin/psp.rs:698— PluginHostHandler::method_registered has cyclomatic complexity 41 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
SyntaxLayers::update (cyclomatic 38) velocirust-core/src/syntax/mod.rs:502— SyntaxLayers::update has cyclomatic complexity 38 (threshold 15). Of this number, 36 points are the body's own statements and 2 belong to 2 function items declared inside it. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
editor::compute_screen_lines (cyclomatic 30) velocirust-app/src/editor.rs:3103— editor::compute_screen_lines has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
status::status (cyclomatic 28) velocirust-app/src/status.rs:31— status::status has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
markdown::parse_markdown (cyclomatic 26) velocirust-app/src/markdown.rs:19— markdown::parse_markdown has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
DapClient::handle_host_event (cyclomatic 26) velocirust-proxy/src/plugin/dap.rs:214— DapClient::handle_host_event has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
WindowData::run_window_command (cyclomatic 24) velocirust-app/src/window.rs:202— WindowData::run_window_command has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
remote::start_remote (cyclomatic 23) velocirust-app/src/proxy/remote.rs:76— remote::start_remote has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Find::next (cyclomatic 22) velocirust-app/src/find.rs:196— Find::next has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
dispatch::git_diff_new (cyclomatic 22) velocirust-proxy/src/dispatch.rs:1517— dispatch::git_diff_new has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
Doc::phantom_text (cyclomatic 20) velocirust-app/src/doc.rs:1622— Doc::phantom_text has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TerminalView::paint_content (cyclomatic 18) velocirust-app/src/terminal/view.rs:326— TerminalView::paint_content has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Terminal::run (cyclomatic 18) velocirust-proxy/src/terminal.rs:105— Terminal::run has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
EditorTabChild::view_info (cyclomatic 17) velocirust-app/src/editor_tab.rs:201— EditorTabChild::view_info has cyclomatic complexity 17 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
terminal_view::terminal_tab_header (cyclomatic 17) velocirust-app/src/panel/terminal_view.rs:47— terminal_view::terminal_tab_header has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
LspClient::new (cyclomatic 17) velocirust-proxy/src/plugin/lsp.rs:174— LspClient::new has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
velocirust_proxy::mainloop (cyclomatic 17) velocirust-proxy/src/lib.rs:46— velocirust_proxy::mainloop has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AppData::create_windows (cyclomatic 16) velocirust-app/src/app.rs:304— AppData::create_windows has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
VelocirustDb::new (cyclomatic 16) velocirust-app/src/db.rs:49— VelocirustDb::new has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
LLM evaluation failed — JSON parse error: Expected end of string, but instead reached end of data. Path: $.findings[1] | LineNumber: 0 | BytePositionInLine: 1083.
SyntaxLayers::update (cognitive 116) velocirust-core/src/syntax/mod.rs:502— SyntaxLayers::update has cognitive complexity 116 (threshold 15). Drivers by points: if/else 76, loops 27, match/switch 11, boolean chains 2 (nesting depth added 77). Of this number, 112 points are the body's own statements and 4 belong to 2 function items declared inside it. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Terminal::run (cognitive 53) velocirust-proxy/src/terminal.rs:105— Terminal::run has cognitive complexity 53 (threshold 15). Drivers by points: if/else 44, match/switch 6, loops 3 (nesting depth added 37). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Find::next (cognitive 50) velocirust-app/src/find.rs:196— Find::next has cognitive complexity 50 (threshold 15). Drivers by points: if/else 36, loops 10, boolean chains 4 (nesting depth added 28). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
highlight::intersect_ranges (cognitive 49) velocirust-core/src/syntax/highlight.rs:744— highlight::intersect_ranges has cognitive complexity 49 (threshold 15). Drivers by points: if/else 40, loops 6, match/switch 3 (nesting depth added 34). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TerminalData::run_command (cognitive 45) velocirust-app/src/terminal/data.rs:64— TerminalData::run_command has cognitive complexity 45 (threshold 15). Drivers by points: if/else 33, match/switch 12 (nesting depth added 28). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
markdown::parse_markdown (cognitive 44) velocirust-app/src/markdown.rs:19— markdown::parse_markdown has cognitive complexity 44 (threshold 15). Drivers by points: if/else 37, match/switch 6, loops 1 (nesting depth added 29). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
main_split::next_in_file_errors_offset (cognitive 42) velocirust-app/src/main_split.rs:3041— main_split::next_in_file_errors_offset has cognitive complexity 42 (threshold 15). Drivers by points: if/else 34, loops 6, boolean chains 2 (nesting depth added 27). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WindowData::run_window_command (cognitive 40) velocirust-app/src/window.rs:202— WindowData::run_window_command has cognitive complexity 40 (threshold 15). Drivers by points: if/else 37, boolean chains 2, match/switch 1 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
status::status (cognitive 40) velocirust-app/src/status.rs:31— status::status has cognitive complexity 40 (threshold 15). Drivers by points: if/else 29, match/switch 8, loops 3 (nesting depth added 12). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
DapClient::handle_host_event (cognitive 38) velocirust-proxy/src/plugin/dap.rs:214— DapClient::handle_host_event has cognitive complexity 38 (threshold 15). Drivers by points: if/else 24, loops 10, match/switch 4 (nesting depth added 23). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
event::terminal_update_process (cognitive 33) velocirust-app/src/terminal/event.rs:27— event::terminal_update_process has cognitive complexity 33 (threshold 15). Drivers by points: if/else 27, match/switch 5, loops 1 (nesting depth added 22). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LspClient::new (cognitive 33) velocirust-proxy/src/plugin/lsp.rs:174— LspClient::new has cognitive complexity 33 (threshold 15). Drivers by points: if/else 25, match/switch 5, loops 3 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AppData::create_windows (cognitive 32) velocirust-app/src/app.rs:304— AppData::create_windows has cognitive complexity 32 (threshold 15). Drivers by points: if/else 21, loops 5, boolean chains 4, match/switch 2 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
velocirust_proxy::mainloop (cognitive 28) velocirust-proxy/src/lib.rs:46— velocirust_proxy::mainloop has cognitive complexity 28 (threshold 15). Drivers by points: if/else 19, match/switch 7, loops 2 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FileNodeItem::append_children_view_slice (cognitive 28) velocirust-rpc/src/file.rs:513— FileNodeItem::append_children_view_slice has cognitive complexity 28 (threshold 15). Drivers by points: if/else 26, boolean chains 1, loops 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
KeyMapLoader::load_from_str (cognitive 27) velocirust-app/src/keypress/loader.rs:21— KeyMapLoader::load_from_str has cognitive complexity 27 (threshold 15). Drivers by points: if/else 15, loops 7, match/switch 4, boolean chains 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
KeyPressData::handle_keymatch (cognitive 27) velocirust-app/src/keypress.rs:331— KeyPressData::handle_keymatch has cognitive complexity 27 (threshold 15). Drivers by points: if/else 24, loops 2, match/switch 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
wasi::start_volt (cognitive 27) velocirust-proxy/src/plugin/wasi.rs:416— wasi::start_volt has cognitive complexity 27 (threshold 15). Drivers by points: if/else 25, loops 1, match/switch 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
VelocirustDb::new (cognitive 25) velocirust-app/src/db.rs:49— VelocirustDb::new has cognitive complexity 25 (threshold 15). Drivers by points: if/else 22, match/switch 2, loops 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
keymap::keyboard_picker_view (cognitive 25) velocirust-app/src/keymap.rs:374— keymap::keyboard_picker_view has cognitive complexity 25 (threshold 15). Drivers by points: if/else 24, boolean chains 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ExpandedRunDebug::expand (cognitive 23) velocirust-app/src/terminal/data.rs:771— ExpandedRunDebug::expand has cognitive complexity 23 (threshold 15). Drivers by points: if/else 21, loops 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TerminalConfig::get_indexed_colors (cognitive 22) velocirust-app/src/config/terminal.rs:47— TerminalConfig::get_indexed_colors has cognitive complexity 22 (threshold 15). Drivers by points: if/else 15, loops 7 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
lsp::path_from_url (cognitive 22) velocirust-app/src/lsp.rs:10— lsp::path_from_url has cognitive complexity 22 (threshold 15). Drivers by points: if/else 14, match/switch 7, boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FocusText::set_text_layout (cognitive 21) velocirust-app/src/focus_text.rs:79— FocusText::set_text_layout has cognitive complexity 21 (threshold 15). Drivers by points: if/else 18, loops 3 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
terminal_view::terminal_tab_header (cognitive 21) velocirust-app/src/panel/terminal_view.rs:47— terminal_view::terminal_tab_header has cognitive complexity 21 (threshold 15). Drivers by points: if/else 17, match/switch 3, loops 1 (nesting depth added 5). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
DapData::stopped (cognitive 18) velocirust-app/src/debug.rs:250— DapData::stopped has cognitive complexity 18 (threshold 15). Drivers by points: if/else 17, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DocStyling::apply_layout_styles (cognitive 18) velocirust-app/src/doc.rs:2016— DocStyling::apply_layout_styles has cognitive complexity 18 (threshold 15). Drivers by points: if/else 12, match/switch 4, boolean chains 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
text_input::text_input_full (cognitive 18) velocirust-app/src/text_input.rs:135— text_input::text_input_full has cognitive complexity 18 (threshold 15). Drivers by points: if/else 18 (nesting depth added 3). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
DapRpcHandler::mainloop (cognitive 18) velocirust-proxy/src/plugin/dap.rs:465— DapRpcHandler::mainloop has cognitive complexity 18 (threshold 15). Drivers by points: if/else 15, match/switch 2, loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PluginHostHandler::method_registered (cognitive 18) velocirust-proxy/src/plugin/psp.rs:698— PluginHostHandler::method_registered has cognitive complexity 18 (threshold 15). Drivers by points: match/switch 18 (nesting depth added 8). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
EditorView::paint_current_line (cognitive 17) velocirust-app/src/editor/view.rs:404— EditorView::paint_current_line has cognitive complexity 17 (threshold 15). Drivers by points: if/else 12, loops 3, boolean chains 1, match/switch 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EditorTabData::get_unconfirmed_editor_tab_child (cognitive 17) velocirust-app/src/editor_tab.rs:443— EditorTabData::get_unconfirmed_editor_tab_child has cognitive complexity 17 (threshold 15). Drivers by points: if/else 14, match/switch 2, loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FileWatchNotifier::handle_workspace_fs_event (cognitive 17) velocirust-proxy/src/dispatch.rs:1314— FileWatchNotifier::handle_workspace_fs_event has cognitive complexity 17 (threshold 15). Drivers by points: if/else 15, loops 1, match/switch 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
problem_view::file_view (cognitive 16) velocirust-app/src/panel/problem_view.rs:83— problem_view::file_view has cognitive complexity 16 (threshold 15). Drivers by points: if/else 14, match/switch 2 (nesting depth added 2). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
plugin::plugin_info_view (cognitive 16) velocirust-app/src/plugin.rs:713— plugin::plugin_info_view has cognitive complexity 16 (threshold 15). Drivers by points: if/else 12, match/switch 4 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FileWatcher::unwatch (cognitive 16) velocirust-proxy/src/watcher.rs:159— FileWatcher::unwatch has cognitive complexity 16 (threshold 15). Drivers by points: if/else 12, loops 3, boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D11 · Test Reliability· Test reliability not included · ×1
Test reliability not included — Test source is present (.rs) but the built-in reliability runner does not support this repository's ecosystem, so flakiness couldn't be assessed. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
early-stage repository — too little history to judge knowledge freshness — early-stage repository — too little history to judge knowledge freshness (10 commit(s) sampled).
No build provenance — No SLSA provenance generation or build attestation found in CI (e.g. slsa-github-generator, actions/attest-build-provenance).
D36 · Supply-chain Provenance & Signing· No SBOM · ×1
No SBOM — No SBOM generation or committed SBOM found — produce one with what your ecosystem ships (`cargo sbom` or `cargo cyclonedx` for the Cargo dependency graph — or `cargo auditable build`, which embeds it in the shipped binary, `syft` (or `anchore/sbom-action` in CI) over the source tree or released image). Publish it as a release asset (`*.spdx.json` / `*.cdx.json`) so consumers can see what they are installing.
Coverage not included — suite not readable by the collector — Coverage NOT MEASURED: test source is present (.rs) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (lcov — `cargo llvm-cov --lcov --output-path lcov.info`) into the repo working tree before the scan — a CI step is the usual place, since the artefact is commonly gitignored.
Info — 4 finding(s)
D12 · Dependency Hygiene· Dependency hygiene not measured · ×1
Dependency hygiene not measured — dependency manifest found but not parsed for hygiene — This repository's dependency manifest (a Cargo manifest) was found, but this pass cannot parse it for hygiene, so no package was assessed. Zero packages read is NOT a clean dependency tree, so this is NOT SCORED — a gap in the analyzer, not a verdict about this repository. This row is about dependency HYGIENE — outdated, deprecated or unmaintained direct dependencies; known CVEs in the same dependency graph are a separate question, reported under D38 wherever the manifest is OSV-readable.
git history depth insufficient — git history depth insufficient — install a full clone for reliable trend signal.
D22 · Internal API Consistency· No exposed public API · ×1
No exposed public API — No intentionally-exposed types (IsPackable or .Contracts) to evaluate.
D35 · Change Coupling· git history depth insufficient · ×1
git history depth insufficient — git history depth insufficient — a full clone gives reliable change-coupling.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
trivy: not applicable — No JS/npm manifest or lockfile found outside build output (package.json, package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb); no JS dependencies to scan.
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.
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.
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.
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
—
Run 019fb0a0-6556-7c2d-a508-743624801fbd · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 8 · Warnings: 208 · Recommendations: 5 · Info: 4 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 30-07-2026 @ 01:25 UTC.
Downloadable artifacts
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.