Executive summary
Qetesh/logi-options-plus-mini is rated At risk because critical security findings are open, all of them in the packages it uses. Its score is held back because we found no working pipeline that builds or tests changes to the code and no automated security scanning of the code, its secrets or its dependencies. It scores 40 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 24, is the weakest lens and counts most in the score. The best first steps are making the controls keyboard-usable and fixing focus, motion and contrast, each worth about 5 points. Raising Production Readiness to 70 would lift the score to about 51.
Ten known security holes in the packages the code depends on can be used by attackers. Two controls can't be used without a mouse, and two form fields can't be read by a screen reader. Making the controls work with a keyboard, updating the vulnerable packages and labelling the form fields would close these risks.
The product code is 6,549 lines, about €5,600 to rebuild.
If Production Readiness rose from 24 to 70, the lowest score rated Strong, the score would rise from 40 to about 51.
New since the last survey: 16 findings
- Code Duplication · Edited copy of a member (52 corresponding lines) Logi Options Plus Mini For Windows/src-tauri/src/backup.rs
- Code Duplication · Edited copy of a member (48 corresponding lines) Logi Options Plus Mini For Windows/src-tauri/src/installer.rs
- Code Duplication · Edited copy of a member (37 corresponding lines) Logi Options Plus Mini/Logi Options+ mini/logi_options_plus_installer/InstallerController.swift
- Code Duplication · Edited copies of one member (3 members, 14+ corresponding lines) Logi Options Plus Mini For Windows/src-tauri/src/backup.rs
- Code Duplication · Edited copy of a member (11 corresponding lines) Logi Options Plus Mini/Logi Options+ mini/common/LogLevel.swift
- Code Duplication · Edited copy of a member (6 corresponding lines) Logi Options Plus Mini/Logi Options+ mini/common/AboutView.swift
- Code Duplication · Duplicated block (18–19 lines × 2) Logi Options Plus Mini For Windows/src-tauri/src/backup.rs
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Hygiene · Unused dependency '@tauri-apps/plugin-shell'
- Dependency Hygiene · Unused dependency '@tauri-apps/plugin-updater'
- Visual & motion safety · Low contrast colour pair in CSS (2.6:1) Logi Options Plus Mini For Windows/src/App.css
- Visual & motion safety · Low contrast colour pair in CSS (4.0:1) Logi Options Plus Mini For Windows/src/App.css
- Visual & motion safety · Low contrast colour pair in CSS (4.4:1) Logi Options Plus Mini For Windows/src/App.css
Fixed since the last survey: 5 findings
- Code Duplication · Duplicated block (18–19 lines × 2) Logi Options Plus Mini For Windows/src-tauri/src/backup.rs
- Dependency Vulnerabilities · Critical CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Critical CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium vulnerability: [GHSA redacted] REDACTED
- A11y enforcement · Accessibility enforcement below the top rung
Rebuild cost: about €5,600 · Estimate
| Cost to rebuild | €1,900 to €9,400, for 31 to 99 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 40. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 6,549 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 Logi Options Plus Mini For Windows.src.components | 2 Logi Options Plus Mini For Windows.src.components.UpdatePage | 3 Logi Options Plus Mini For Windows.src.config | 4 Logi Options Plus Mini For Windows.src.types | 5 logi_options_plus_mini | 6 logi_options_plus_mini.backup | 7 logi_options_plus_mini.downloader | 8 logi_options_plus_mini.exe_version | 9 logi_options_plus_mini.main | 10 logi_options_plus_mini.models | 11 logi_options_plus_mini.version | 12 repository | 13 Logi Options Plus Mini For Windows.src | 14 logi_options_plus_mini.installer | 15 logi_options_plus_mini.commands |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Logi Options Plus Mini For Windows.src.components | |||||||||||||||
| 2 Logi Options Plus Mini For Windows.src.components.UpdatePage | |||||||||||||||
| 3 Logi Options Plus Mini For Windows.src.config | |||||||||||||||
| 4 Logi Options Plus Mini For Windows.src.types | |||||||||||||||
| 5 logi_options_plus_mini | |||||||||||||||
| 6 logi_options_plus_mini.backup | |||||||||||||||
| 7 logi_options_plus_mini.downloader | |||||||||||||||
| 8 logi_options_plus_mini.exe_version | |||||||||||||||
| 9 logi_options_plus_mini.main | |||||||||||||||
| 10 logi_options_plus_mini.models | |||||||||||||||
| 11 logi_options_plus_mini.version | |||||||||||||||
| 12 repository | |||||||||||||||
| 13 Logi Options Plus Mini For Windows.src | 2 | ||||||||||||||
| 14 logi_options_plus_mini.installer | 1 | 1 | |||||||||||||
| 15 logi_options_plus_mini.commands | 1 | 1 |
13→4 Logi Options Plus Mini For Windows.src uses Logi Options Plus Mini For Windows.src.types✕
- Connections
- 2 pairs of types, where a type in Logi Options Plus Mini For Windows.src uses a type in Logi Options Plus Mini For Windows.src.types.
- The types involved
Logi Options Plus Mini For Windows.src.api→Logi Options Plus Mini For Windows.src.types.InstallResultLogi Options Plus Mini For Windows.src.api→Logi Options Plus Mini For Windows.src.types.VersionInfo
- Direction
- Logi Options Plus Mini For Windows.src uses Logi Options Plus Mini For Windows.src.types, so a change to Logi Options Plus Mini For Windows.src.types can break Logi Options Plus Mini For Windows.src, while a change to Logi Options Plus Mini For Windows.src can't break Logi Options Plus Mini For Windows.src.types.
- Position
- Below the diagonal: Logi Options Plus Mini For Windows.src uses a module listed above it, which is the healthy direction.
14→6 logi_options_plus_mini.installer uses logi_options_plus_mini.backup✕
- Connections
- 1 pair of types, where a type in logi_options_plus_mini.installer uses a type in logi_options_plus_mini.backup.
- The types involved
logi_options_plus_mini.installer.Installer→logi_options_plus_mini.backup.BackupManager
- Direction
- logi_options_plus_mini.installer uses logi_options_plus_mini.backup, so a change to logi_options_plus_mini.backup can break logi_options_plus_mini.installer, while a change to logi_options_plus_mini.installer can't break logi_options_plus_mini.backup.
- Position
- Below the diagonal: logi_options_plus_mini.installer uses a module listed above it, which is the healthy direction.
14→7 logi_options_plus_mini.installer uses logi_options_plus_mini.downloader✕
- Connections
- 1 pair of types, where a type in logi_options_plus_mini.installer uses a type in logi_options_plus_mini.downloader.
- The types involved
logi_options_plus_mini.installer.Installer→logi_options_plus_mini.downloader.Downloader
- Direction
- logi_options_plus_mini.installer uses logi_options_plus_mini.downloader, so a change to logi_options_plus_mini.downloader can break logi_options_plus_mini.installer, while a change to logi_options_plus_mini.installer can't break logi_options_plus_mini.downloader.
- Position
- Below the diagonal: logi_options_plus_mini.installer uses a module listed above it, which is the healthy direction.
15→10 logi_options_plus_mini.commands uses logi_options_plus_mini.models✕
- Connections
- 1 pair of types, where a type in logi_options_plus_mini.commands uses a type in logi_options_plus_mini.models.
- The types involved
logi_options_plus_mini.commands.commands$module→logi_options_plus_mini.models.FeatureInfo
- Direction
- logi_options_plus_mini.commands uses logi_options_plus_mini.models, so a change to logi_options_plus_mini.models can break logi_options_plus_mini.commands, while a change to logi_options_plus_mini.commands can't break logi_options_plus_mini.models.
- Position
- Below the diagonal: logi_options_plus_mini.commands uses a module listed above it, which is the healthy direction.
15→14 logi_options_plus_mini.commands uses logi_options_plus_mini.installer✕
- Connections
- 1 pair of types, where a type in logi_options_plus_mini.commands uses a type in logi_options_plus_mini.installer.
- The types involved
logi_options_plus_mini.commands.AppState→logi_options_plus_mini.installer.Installer
- Direction
- logi_options_plus_mini.commands uses logi_options_plus_mini.installer, so a change to logi_options_plus_mini.installer can break logi_options_plus_mini.commands, while a change to logi_options_plus_mini.commands can't break logi_options_plus_mini.installer.
- Position
- Below the diagonal: logi_options_plus_mini.commands uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 50 | High / Critical |
Roadmap
Top priorities: Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href; Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1; Add a CI workflow that builds and runs the test suite on every push/PR.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href. | +4.7 pts | Medium | Keyboard semantics |
| Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1. | +4.7 pts | Medium | Visual & motion safety |
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with main.rs. | +2.1 pts | Low | ADR Quality |
| Add a CI workflow that builds and runs the test suite on every push/PR. | +2.7 pts | Medium | CI/CD gates |
| Add tests that import the unreached modules (directly or through their public entry). | +2.7 pts | Medium | Test Coverage |
| Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh. | +2.1 pts | Medium | Page structure |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +1.9 pts | Medium | Architecture documentation |
| Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label. | +1.7 pts | Medium | Forms & labels |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.6 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 1.7 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| Logi Options Plus Mini For Windows/src/App.tsx | 7.1 | Mixed | Cyclomatic Complexity: App.App (cyclomatic 115) |
| Logi Options Plus Mini For Windows/src-tauri/src/installer.rs | 7.1 | Mixed | Cyclomatic Complexity: Installer::install_internal (cyclomatic 27) |
| Logi Options Plus Mini/Logi Options+ mini/logi_options_plus_installer/logiOptionsPlusView.swift | 7.4 | Mixed | Cyclomatic Complexity: LogiOptionsPlusView.body (cyclomatic 23) |
| Logi Options Plus Mini For Windows/src/components/UpdatePage.tsx | 7.4 | Mixed | Cyclomatic Complexity: UpdatePage.UpdatePage (cyclomatic 18) |
| Logi Options Plus Mini For Windows/src-tauri/src/backup.rs | 7.4 | Mixed | Code Duplication: Edited copy of a member (52 corresponding lines) |
| Logi Options Plus Mini/Logi Options+ mini/logi_options_plus_installer/InstallationProgress.swift | 7.8 | Mixed | Cyclomatic Complexity: ProgressNode.body (cyclomatic 18) |
| Logi Options Plus Mini For Windows/src-tauri/src/exe_version.rs | 7.8 | Mixed | Cognitive Complexity: logi_options_plus_mini::exe_version::get_file_version_string (cognitive 23) |
| Logi Options Plus Mini/Logi Options+ mini/logi_options_plus_installer/InstallerController.swift | 7.8 | Mixed | Code Duplication: Edited copy of a member (37 corresponding lines) |
| Logi Options Plus Mini/Logi Options+ mini/common/AgentManager.swift | 7.8 | Mixed | Code Duplication: Duplicated block (10 lines × 2) |
| Logi Options Plus Mini For Windows/src-tauri/src/commands.rs | 7.8 | Mixed | Code Duplication: Duplicated block (9 lines × 2) |
| Logi Options Plus Mini For Windows/src/components/Settings.tsx | 8.5 | Near-clean | God Classes: FunctionTooLong: Settings.Settings |
| Logi Options Plus Mini/Logi Options+ mini/common/LogLevel.swift | 8.5 | Near-clean | Code Duplication: Edited copy of a member (11 corresponding lines) |
| Logi Options Plus Mini/Logi Options+ mini/common/AboutView.swift | 8.5 | Near-clean | Code Duplication: Edited copy of a member (6 corresponding lines) |
| Logi Options Plus Mini For Windows/src-tauri/src/downloader.rs | 8.5 | Near-clean | Code Duplication: Duplicated block (13–14 lines × 2) |
| Logi Options Plus Mini/Logi Options+ mini/common/PermissionChecker.swift | 8.5 | Near-clean | Cohesion (LCOM4): Low cohesion: PermissionChecker (LCOM4 4) |
| Logi Options Plus Mini For Windows/src-tauri/src/main.rs | 9.5 | Near-clean | ADR Quality: No ADRs found |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 51 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 51 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 118 of 146 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the Rust half could not be measured — the Cargo suite in Logi Options Plus Mini For Windows/src-tauri did not build, so it was never run. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo.
- D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its crate dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (3 contributor(s) across 64 commit(s) sampled, automation and bot accounts excluded). One of them holds 97% of the history; the other 2 hold 1.5% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D24 compares a comment's words with the identifiers, literals and constructs of the code it annotates, using English function-word and rationale lexicons. Comments in another script or language were left unread rather than counted as clean.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D27 Navigability — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Tracing effort is measured over resolved call sites, and all 78 sampled here came from .swift files. This repository's .rs, .tsx source is a material share of its production lines and contributed none, so the score above is a verdict about the part that was read. Not a finding that the unread half navigates well — it is unmeasured.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `Logi Options Plus Mini/Logi Options+ mini/ContentView.swift`, `Logi Options Plus Mini/Logi Options+ mini/common/BottomStatusBar.swift`, `Logi Options Plus Mini/Logi Options+ mini/common/DownloadSourcePreferencePaneView.swift`, `Logi Options Plus Mini/Logi Options+ mini/common/GeneralPreferencePane/GeneralPreferencePaneView.swift`, `Logi Options Plus Mini/Logi Options+ mini/common/PermissionAlertView.swift`, … (+5 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- D44 Platform End-of-Life — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
- AXB2 Runtime readiness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. (rule: no-root-manifest). The renderer reported: the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (dev). the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
- C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
- C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Rust, Swift is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Rust, Swift is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X21 Side-effecting pattern guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X3 Exception handling — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
5 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was App.App at 115.
What to do
- Bring the 1 body over 30 down to 30 or less in Cyclomatic Complexity — start with App.App (cyclomatic 115). — Refactoring it lifts Cyclomatic Complexity from 7.5 to about 8.9/10.
D2 · Cognitive Complexity
6 method(s) exceeded the cognitive complexity threshold of 15; the worst was App.App at 100.
What to do
- Bring the 1 body over 60 down to 60 or less in Cognitive Complexity — start with App.App (cognitive 100). — Refactoring it lifts Cognitive Complexity from 7.5 to about 8.1/10.
D3 · God Classes
8 god class(es) detected.
What to do
- Resolve the 4 FunctionTooLong finding(s) in God Classes — start with App.tsx, Settings.tsx, UpdatePage.tsx. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 2 MethodTooLong finding(s) in God Classes — start with logiOptionsPlusView.swift, installer.rs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 ClassTooLong finding(s) in God Classes — start with App.tsx. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
8 duplicated block group(s) detected. 6.1 % of the production lines (399 of 6,549) are in a reported copy. A further 6 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. Measured on part of this repository only: .tsx (17% of production source) was not exposed to THIS dimension's token comparison and is not in this count; duplication there is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream.
What to do
- Resolve the 3 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with commands.rs (2), AgentManager.swift. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 Edited copy of a member (52 corresponding lines) finding(s) in Code Duplication — start with backup.rs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Edited copy of a member (48 corresponding lines) finding(s) in Code Duplication — start with installer.rs. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
4 production modules (Cargo+npm+Xcode), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; a workspace's implicit (product-name) dependency is not visible there; 0 module(s) off the main sequence.
D6 · Cohesion (LCOM4)
1 of 10 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with PermissionChecker.swift. — One of this dimension's main actionable groups (1 warning-level).
D12 · Dependency Hygiene
15 outdated, 0 yanked direct Cargo dependencies. Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from REDACTED there.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 596 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's REDACTED closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. ★ COVERAGE OF THIS VERDICT: it grades this repository's crate dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D15 · Churn × Complexity Hotspots
Top hotspots: Logi Options Plus Mini For Windows/src/App.tsx (2×115=230); Logi Options Plus Mini/Logi Options+ mini/logi_options_plus_installer/logiOptionsPlusView.swift (2×23=46)
What to do
- Resolve the 2 Hotspot finding(s) in Churn × Complexity Hotspots — start with App.tsx, logiOptionsPlusView.swift. — One of this dimension's main actionable groups (2 warning-level).
D17 · Explicit Debt
0 deducted task-comment markers across 6549 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 3 document(s) read across 2 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with main.rs. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
0 of 3 build units (Cargo, Xcode, npm) flagged as possibly oversized/incoherent.
D27 · Navigability
0 % of calls cross a namespace and 0 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated. Measured over the .swift source only — this repository's .rs, .tsx was not sampled for call sites, so this score covers part of the tree, not all of it.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
semgrep found no security issues.
D30 · Dependency Vulnerabilities
50 finding(s): 2 critical, 8 high, 39 medium, 1 low.
What to do
- Resolve the 16 Medium advisory (unsound) finding(s) in Dependency Vulnerabilities — start with REDACTED (16). — One of this dimension's main actionable groups (16 warning-level).
- Resolve the 8 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (6), REDACTED (2). — One of this dimension's main actionable groups (8 issue-level).
- Resolve the 2 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 29 of the 53 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
Frontend & cross-cutting dimensions
AC2 · Forms & labels
- This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×2) — Logi Options Plus Mini For Windows/src/components/Settings.tsx:113, Logi Options Plus Mini For Windows/src/components/Settings.tsx:132
What to do
- Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
AC3 · Page structure
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="root">, so there is no content here to wrap — render the <main> from the component mounted into it. (×3) — Logi Options Plus Mini For Windows/index.html:2, Logi Options Plus Mini For Windows/settings.html:2, Logi Options Plus Mini For Windows/update.html:2
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC4 · Keyboard semantics
- A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler. (×2) — Logi Options Plus Mini For Windows/src/App.tsx:641, Logi Options Plus Mini For Windows/src/App.tsx:653
What to do
- Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC6 · Visual & motion safety
- `.btn-primary` sets color: white on background-color: #4da6ff — 2.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — Logi Options Plus Mini For Windows/src/App.css:260
- `.log-level-info .log-level-badge` sets color: #1976d2 on background-color: #e3f2fd — 4.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — Logi Options Plus Mini For Windows/src/App.css:953
- `.log-level-warn .log-level-badge` sets color: #f57c00 on background-color: #fff3e0 — 2.5:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — Logi Options Plus Mini For Windows/src/App.css:958
- `.log-level-error .log-level-badge` sets color: #d32f2f on background-color: #ffebee — 4.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — Logi Options Plus Mini For Windows/src/App.css:963
- `.step-icon.spinning` moves (`animation: spin 1s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — Logi Options Plus Mini For Windows/src/App.css:325
- `.progress-fill` moves (`transition: width 0.4s cubic-bezier(0.4, 0, 0.2, 1)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — Logi Options Plus Mini For Windows/src/App.css:359
- `.progress-fill::after` moves (`animation: shimmer 1.5s infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — Logi Options Plus Mini For Windows/src/App.css:380
- `.spinning` moves (`animation: spin 1s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — Logi Options Plus Mini For Windows/src/App.css:453
- `.update-progress-fill` moves (`transition: width 0.2s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — Logi Options Plus Mini For Windows/src/App.css:928
What to do
- Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX8 · Test isolation
AX9 · CQS / query purity
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
- No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
What to do
- Add a CI workflow that builds and runs the test suite on every push/PR.
P10 · Library API & versioning
P2 · Observability
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add CodeQL's Swift pack (Swift/Xcode) (or `semgrep --config=auto`, which runs on any language) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
- `Logi Options Plus Mini For Windows/package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — Logi Options Plus Mini For Windows/package.json:12
What to do
- Run what this repository's stack ships: CodeQL's Swift pack (Swift/Xcode) — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF3 · Async & latency hygiene
R1 · Type Safety
R10 · Code Duplication
- Logi Options Plus Mini For Windows/src/App.tsx:320 · Logi Options Plus Mini For Windows/src/App.tsx:398 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — Logi Options Plus Mini For Windows/src/App.tsx:320
- Logi Options Plus Mini For Windows/src/components/Settings.tsx:150 · Logi Options Plus Mini For Windows/src/components/Settings.tsx:171 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — Logi Options Plus Mini For Windows/src/components/Settings.tsx:150
- Logi Options Plus Mini For Windows/src/components/Settings.tsx:117 · Logi Options Plus Mini For Windows/src/components/Settings.tsx:138 · Logi Options Plus Mini For Windows/src/components/Settings.tsx:159 · Logi Options Plus Mini For Windows/src/components/Settings.tsx:180 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. — Logi Options Plus Mini For Windows/src/components/Settings.tsx:117
- Logi Options Plus Mini For Windows/src/components/Settings.tsx:106 · Logi Options Plus Mini For Windows/src/components/Settings.tsx:124 · Logi Options Plus Mini For Windows/src/components/Settings.tsx:145 · Logi Options Plus Mini For Windows/src/components/Settings.tsx:166 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. — Logi Options Plus Mini For Windows/src/components/Settings.tsx:106
What to do
- Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R2 · Cyclomatic Complexity
- App has cyclomatic complexity 19 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — Logi Options Plus Mini For Windows/src/App.tsx:39
- (anonymous) has cyclomatic complexity 14 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — Logi Options Plus Mini For Windows/src/App.tsx:153
R3 · Large Files
- Logi Options Plus Mini For Windows/src/App.tsx has 682 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — Logi Options Plus Mini For Windows/src/App.tsx:1
What to do
- Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R4 · Test Coverage
- 0% of 10 production file(s) reachable from 0 test file(s) via the import graph — 'production' here is the RESIDUE: every source file left once tests, tooling, generated output, config, declarations and declaration-only modules, fixture corpora, type fixtures, behaviour-free data modules, re-export barrels, registration/constant data modules and service workers are set aside, so the percentage is taken over a smaller denominator than the workspace's file count
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R6 · Tooling
- test ✗ · lint ✗ · typecheck ✓ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
What to do
- Add a test runner (vitest / jest / playwright) and eslint as package.json scripts and run them in CI.
R7 · Dead Code
- Nothing imports this binding — it is safe to review for removal. (×4) — Logi Options Plus Mini For Windows/src/api.ts:4, Logi Options Plus Mini For Windows/src/config/updateSource.ts:19, Logi Options Plus Mini For Windows/src/i18n.ts:39, …
What to do
- Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene
- Declared in Logi Options Plus Mini For Windows/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×5)
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
X3 · Exception handling
X5 · Nullable reference types
- 1/2 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
- ~1.4 `!` null assertions per 1k TypeScript source lines — 2 assertion(s) across the 1399 source line(s) of the 11 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: Logi Options Plus Mini For Windows/src/settings.tsx (1), Logi Options Plus Mini For Windows/src/update.tsx (1). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
What to do
- The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC4 · Keyboard semantics | 2.1.1, 2.4.3 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 67% | Adequate | Acceptable, with room to improve. |
| Architecture | 99% | Exemplary | Solid. |
| Maturity | 72% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 24% | Critical — gated by R4, R6, P1, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 100% | Checked 2 of 9 | Strongest area. |
| Accessibility | 25% | Critical — gated by AC4, AC6 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Solid. |
Unscored — 2 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 5 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises 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 a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises 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 a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises 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.
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 72 check(s) not relevant to this codebase
- AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
- AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
- AX1 Captive dependencies — Not applicable: Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one; this repository's Swift imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's TypeScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No Swift request handler (a Vapor, Hummingbird, Kitura, Swifter or Perfect route handler, as a method or a registered closure) is declared, so no state is shared between request threads. Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — no exported interface declares behaviour
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises 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 a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises 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.
- D10 Test Quality — ~44 lines of test source are present (.rs, .swift) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test source is present (.rs, .swift) and this repository's suite is reachable only from an Apple platform: it ships Logi Options+ mini.xcodeproj and no SwiftPM manifest, so it is built by Xcode rather than by `swift test`. The analyzer runs on Linux, where no simulator exists, so the suite was not re-run. Not scored: nothing was exercised.
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (685 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — 63 of 80 comment blocks were not judged (63 in a non-Latin script): redundancy is judged by word overlap with the code's identifiers, which cannot be measured across languages.
- D25 ADR Conformance — no ADRs to check
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 10 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not measured — Rust suite
- DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and this analysis resolves a call's owner only where the receiver's type is written down in the source. Reported as guidance rather than measured
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — no CI workflow found
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript, Rust, Swift source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `Benchmark("…")` in a file importing package-benchmark, or package-benchmark in Package.swift, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- R5 Dependency Freshness — uses a pnpm lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises 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.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X1 Async correctness — X1 reached only 45% of this repository's production lines — swift (3,619 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X12 Unreachable branch — X12 reached only 19% of this repository's production lines — swift (3,619 lines), rust (1,685 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X16 Unfloored truncation loop — X16 reached only 19% of this repository's production lines — swift (3,619 lines), rust (1,685 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X21 Side-effecting pattern guard — X21 reached only 45% of this repository's production lines — swift (3,619 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Rust was read, and it logs through none: the `log` crate's macros take one finished message (as log4net does in C#; its `kv` values are an opt-in its backends mostly drop), `println!`/`eprintln!` are not loggers, or it makes no log call outside its tests and examples at all. Calls through `tracing` (`tracing::info!`, or `info!` imported from it) would be judged.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 14 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <select> without a programmatic label Logi Options Plus Mini For Windows/src/components/Settings.tsx:113
- <select> without a programmatic label Logi Options Plus Mini For Windows/src/components/Settings.tsx:132
- Click handler on a non-interactive <span> Logi Options Plus Mini For Windows/src/App.tsx:641
- Click handler on a non-interactive <span> Logi Options Plus Mini For Windows/src/App.tsx:653
- REDACTED
- REDACTED
Serious — 102 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Animation without a prefers-reduced-motion guard Logi Options Plus Mini For Windows/src/App.css:325
- Animation without a prefers-reduced-motion guard Logi Options Plus Mini For Windows/src/App.css:359
- Animation without a prefers-reduced-motion guard Logi Options Plus Mini For Windows/src/App.css:380
- Animation without a prefers-reduced-motion guard Logi Options Plus Mini For Windows/src/App.css:453
- Animation without a prefers-reduced-motion guard Logi Options Plus Mini For Windows/src/App.css:928
- FunctionTooLong: App.App Logi Options Plus Mini For Windows/src/App.tsx:39
- FunctionTooLong: Settings.Settings Logi Options Plus Mini For Windows/src/components/Settings.tsx:10
- FunctionTooLong: UpdatePage.UpdatePage Logi Options Plus Mini For Windows/src/components/UpdatePage.tsx:13
- FunctionTooLong: logi_options_plus_mini::exe_version::get_file_version_string Logi Options Plus Mini For Windows/src-tauri/src/exe_version.rs:76
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Page without a main landmark Logi Options Plus Mini For Windows/index.html:2
- Page without a main landmark Logi Options Plus Mini For Windows/settings.html:2
- Page without a main landmark Logi Options Plus Mini For Windows/update.html:2
- Duplicated block (9 lines × 2) Logi Options Plus Mini/Logi Options+ mini/common/AgentManager.swift:73
- Duplicated block (9 lines × 2) Logi Options Plus Mini For Windows/src-tauri/src/commands.rs:80
- Duplicated block (9 lines × 2) Logi Options Plus Mini For Windows/src-tauri/src/commands.rs:93
- Hotspot: Logi Options Plus Mini For Windows/src/App.tsx Logi Options Plus Mini For Windows/src/App.tsx:39
- Hotspot: Logi Options Plus Mini/Logi Options+ mini/logi_options_plus_installer/logiOptionsPlusView.swift Logi Options Plus Mini/Logi Options+ mini/logi_options_plus_installer/logiOptionsPlusView.swift:28
- MethodTooLong: LogiOptionsPlusView.body Logi Options Plus Mini/Logi Options+ mini/logi_options_plus_installer/logiOptionsPlusView.swift:28
- MethodTooLong: Installer.install_internal Logi Options Plus Mini For Windows/src-tauri/src/installer.rs:407
- Low contrast colour pair in CSS (2.6:1) Logi Options Plus Mini For Windows/src/App.css:260
- Low contrast colour pair in CSS (4.0:1) Logi Options Plus Mini For Windows/src/App.css:953
- Low contrast colour pair in CSS (2.5:1) Logi Options Plus Mini For Windows/src/App.css:958
- Low contrast colour pair in CSS (4.4:1) Logi Options Plus Mini For Windows/src/App.css:963
- App.App (cyclomatic 115) Logi Options Plus Mini For Windows/src/App.tsx:39
- Installer::install_internal (cyclomatic 27) Logi Options Plus Mini For Windows/src-tauri/src/installer.rs:407
- LogiOptionsPlusView.body (cyclomatic 23) Logi Options Plus Mini/Logi Options+ mini/logi_options_plus_installer/logiOptionsPlusView.swift:28
- ProgressNode.body (cyclomatic 18) Logi Options Plus Mini/Logi Options+ mini/logi_options_plus_installer/InstallationProgress.swift:104
- UpdatePage.UpdatePage (cyclomatic 18) Logi Options Plus Mini For Windows/src/components/UpdatePage.tsx:13
- App.App (cognitive 100) Logi Options Plus Mini For Windows/src/App.tsx:39
- Installer::install_internal (cognitive 51) Logi Options Plus Mini For Windows/src-tauri/src/installer.rs:407
- LogiOptionsPlusView.body (cognitive 31) Logi Options Plus Mini/Logi Options+ mini/logi_options_plus_installer/logiOptionsPlusView.swift:28
- logi_options_plus_mini::exe_version::get_file_version_string (cognitive 23) Logi Options Plus Mini For Windows/src-tauri/src/exe_version.rs:76
- ProgressNode.body (cognitive 20) Logi Options Plus Mini/Logi Options+ mini/logi_options_plus_installer/InstallationProgress.swift:104
- UpdatePage.UpdatePage (cognitive 18) Logi Options Plus Mini For Windows/src/components/UpdatePage.tsx:13
- ClassTooLong: App Logi Options Plus Mini For Windows/src/App.tsx:1
- FileTooLong: src/App.tsx Logi Options Plus Mini For Windows/src/App.tsx
- Edited copy of a member (52 corresponding lines) Logi Options Plus Mini For Windows/src-tauri/src/backup.rs:70
- Edited copy of a member (48 corresponding lines) Logi Options Plus Mini For Windows/src-tauri/src/installer.rs:137
- Edited copy of a member (37 corresponding lines) Logi Options Plus Mini/Logi Options+ mini/logi_options_plus_installer/InstallerController.swift:135
- Edited copies of one member (3 members, 14+ corresponding lines) Logi Options Plus Mini For Windows/src-tauri/src/backup.rs:31
- Edited copy of a member (11 corresponding lines) Logi Options Plus Mini/Logi Options+ mini/common/LogLevel.swift:36
- Edited copy of a member (6 corresponding lines) Logi Options Plus Mini/Logi Options+ mini/common/AboutView.swift:12
- Duplicated block (15–16 lines × 3) Logi Options Plus Mini/Logi Options+ mini/logi_options_plus_installer/InstallerController.swift:114
- Duplicated block (10 lines × 2) Logi Options Plus Mini/Logi Options+ mini/common/AgentManager.swift:40
- Duplicated block (28 lines × 2) Logi Options Plus Mini For Windows/src-tauri/src/installer.rs:149
- Duplicated block (18–19 lines × 2) Logi Options Plus Mini For Windows/src-tauri/src/backup.rs:98
- Duplicated block (13–14 lines × 2) Logi Options Plus Mini For Windows/src-tauri/src/downloader.rs:8
- Low cohesion: PermissionChecker (LCOM4 4) Logi Options Plus Mini/Logi Options+ mini/common/PermissionChecker.swift:13
- No CI pipeline
- Duplicated block (38 lines × 2 locations) Logi Options Plus Mini For Windows/src/App.tsx:320
- Duplicated block (17 lines × 2 locations) Logi Options Plus Mini For Windows/src/components/Settings.tsx:150
- Duplicated block (14 lines × 4 locations) Logi Options Plus Mini For Windows/src/components/Settings.tsx:117
- Duplicated block (9 lines × 4 locations) Logi Options Plus Mini For Windows/src/components/Settings.tsx:106
- Complex function App (cyclomatic 19, cognitive 15) Logi Options Plus Mini For Windows/src/App.tsx:39
- Complex function (anonymous) (cyclomatic 14, cognitive 13) Logi Options Plus Mini For Windows/src/App.tsx:153
- Logi Options Plus Mini For Windows/src/App.tsx: 682 lines of code Logi Options Plus Mini For Windows/src/App.tsx:1
- Test Coverage
- No test or lint script
- Unused dependency '@tauri-apps/plugin-dialog'
- Unused dependency '@tauri-apps/plugin-fs'
- Unused dependency '@tauri-apps/plugin-opener'
- Unused dependency '@tauri-apps/plugin-shell'
- Unused dependency '@tauri-apps/plugin-updater'
Minor — 15 finding(s)
- Duplicated predicate Logi Options Plus Mini For Windows/src/App.tsx:54
- Duplicated predicate Logi Options Plus Mini For Windows/src/App.tsx:51
- No ADRs found Logi Options Plus Mini For Windows/src-tauri/src/main.rs:1
- REDACTED
- No ADRs
- No SAST
- No dependency-update automation Logi Options Plus Mini For Windows/package.json:12
- No changelog
- Unused export 'getFeatures' Logi Options Plus Mini For Windows/src/api.ts:4
- Unused export 'DEFAULT_UPDATE_SOURCE' Logi Options Plus Mini For Windows/src/config/updateSource.ts:19
- Unused export 'default' Logi Options Plus Mini For Windows/src/i18n.ts:39
- Unused export 'LogMessage' Logi Options Plus Mini For Windows/src/types.ts:31
- Strict null checking is not enabled everywhere the repository type-checks
- Null assertions (`!`) override strict null checking
- Silent fallback default on Err Logi Options Plus Mini For Windows/src-tauri/src/exe_version.rs:33
Minor — 15 finding(s)
- Outdated: env_logger
- Outdated: futures-util
- Outdated: log
- Outdated: serde
- Outdated: serde_json
- Outdated: tauri
- Outdated: tauri-build
- Outdated: tauri-plugin-dialog
- Outdated: tauri-plugin-fs
- Outdated: tauri-plugin-opener
- Outdated: tauri-plugin-process
- Outdated: tauri-plugin-shell
- Outdated: tauri-plugin-updater
- Outdated: tokio
- Outdated: uuid
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-a9f2714d066043f0ab3eba14fbaf61fe/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-a9f2714d066043f0ab3eba14fbaf61fe/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 0 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 50 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 10 file(s) — `Logi Options Plus Mini/Logi Options+ mini/ContentView.swift`, `Logi Options Plus Mini/Logi Options+ mini/common/BottomStatusBar.swift`, `Logi Options Plus Mini/Logi Options+ mini/common/DownloadSourcePreferencePaneView.swift`, `Logi Options Plus Mini/Logi Options+ mini/common/GeneralPreferencePane/GeneralPreferencePaneView.swift`, `Logi Options Plus Mini/Logi Options+ mini/common/PermissionAlertView.swift`, … (+5 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D36 · Supply-chain Provenance & Signing | provenance | — | provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |