Executive summary
qishibo/AnotherRedisDesktopManager is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back in part because it has controls that only work with a mouse. It scores 30 out of 100, which the At risk rating leaves unchanged.
Accessibility, at 21, is the weakest lens and counts most in the score. The best first step is replacing the 22 deprecated dependencies, worth about 5 points. Making the controls keyboard-usable would lift Accessibility itself, also worth about 5. Raising Accessibility to 70 would lift the score to about 38.
Sixty-eight known security holes in the packages the code depends on can be used by attackers. Twenty-two controls can't be used without a mouse, and eighteen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Making the controls work with a keyboard, updating the vulnerable packages and pinning each tool to an exact version would close these risks. Limiting each secret to its own step would fix the five secrets exposed to more of the pipeline than needed, and switching the validation back on would deal with the security check on connections or logins switched off. The five buttons or links with no name need a name, even when they only show an icon.
The product code is 16,431 lines, about €14,000 to rebuild.
If Accessibility rose from 21 to 70, the lowest score rated Strong, the score would rise from 30 to about 38.
New since the last survey: 45 findings
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Exception handling · Swallowed exception (empty catch) src/util.js
- Exception handling · Swallowed exception (empty catch) src/util.js
- Exception handling · Swallowed exception (empty catch) src/util.js
- Exception handling · Swallowed exception (empty catch) src/util.js
- Exception handling · Swallowed exception (empty catch) src/util.js
- Exception handling · Swallowed exception (empty catch) src/components/ConnectionMenu.vue
- Exception handling · Swallowed exception (empty catch) src/components/ConnectionMenu.vue
- Exception handling · Swallowed exception (empty catch) src/components/ConnectionMenu.vue
- Exception handling · Swallowed exception (empty catch) src/components/ConnectionMenu.vue
- Exception handling · Swallowed exception (empty catch) src/components/ConnectionWrapper.vue
- Exception handling · Swallowed exception (empty catch) src/components/ConnectionWrapper.vue
- Exception handling · Swallowed exception (empty catch) src/components/KeyHeader.vue
- Exception handling · Swallowed exception (empty catch) src/components/KeyHeader.vue
- Exception handling · Swallowed exception (empty catch) src/components/KeyHeader.vue
- Exception handling · Swallowed exception (empty catch) src/components/OperateItem.vue
- Exception handling · Swallowed exception (empty catch) src/components/OperateItem.vue
- Exception handling · Swallowed exception (empty catch) src/components/SlowLog.vue
- Exception handling · Swallowed exception (empty catch) src/components/SlowLog.vue
- Exception handling · Swallowed exception (empty catch) src/components/contents/KeyContentHash.vue
- Exception handling · Swallowed exception (empty catch) src/components/contents/KeyContentHash.vue
- Exception handling · Swallowed exception (empty catch) src/components/contents/KeyContentList.vue
- Exception handling · Swallowed exception (empty catch) src/components/contents/KeyContentList.vue
- Exception handling · Swallowed exception (empty catch) src/components/contents/KeyContentSet.vue
- Exception handling · Swallowed exception (empty catch) src/components/contents/KeyContentSet.vue
- Exception handling · Swallowed exception (empty catch) src/components/contents/KeyContentZset.vue
- Exception handling · Swallowed exception (empty catch) src/components/contents/KeyContentZset.vue
- Exception handling · Swallowed exception (empty catch) pack/electron/update.js
- Exception handling · Swallowed exception (empty catch) pack/electron/update.js
- Exception handling · Swallowed exception (empty catch) pack/electron/win-state.js
- Exception handling · Swallowed exception (empty catch) pack/electron/win-state.js
- Visual & motion safety · Low contrast colour pair in CSS (2.8:1) static/theme/light/index.css
- Visual & motion safety · Low contrast colour pair in CSS (1.7:1) static/theme/light/index.css
- Visual & motion safety · Low contrast colour pair in CSS (2.8:1) static/theme/light/index.css
- Visual & motion safety · Low contrast colour pair in CSS (2.8:1) static/theme/light/index.css
- Visual & motion safety · Low contrast colour pair in CSS (1.7:1) static/theme/light/index.css
- Visual & motion safety · Low contrast colour pair in CSS (2.8:1) static/theme/light/index.css
- Visual & motion safety · Low contrast colour pair in CSS (3.1:1) static/theme/dark/index.css
- Visual & motion safety · Low contrast colour pair in CSS (3.1:1) static/theme/dark/index.css
- Visual & motion safety · Low contrast colour pair in CSS (3.1:1) static/theme/dark/index.css
- Visual & motion safety · Low contrast colour pair in CSS (3.1:1) src/components/Connections.vue
- Visual & motion safety · Low contrast colour pair in CSS (3.2:1) src/components/KeyListNormal.vue
- Visual & motion safety · Low contrast colour pair in CSS (2.2:1) src/components/viewers/ViewerOverSize.vue
Fixed since the last survey: 214 findings
- Secrets (history) · High secret: WD-SECRET-0005 REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
- Dead Code · Dead file (~61 LoC) src/components/RightClickMenu.vue
- Dead Code · Dead file (~57 LoC) src/components/KeyListNormal.vue
- Dead Code · Dead file (~56 LoC) src/components/viewers/ViewerText.vue
- Dead Code · Dead file (~55 LoC) src/components/HotKeys.vue
- Dead Code · Dead file (~55 LoC) src/components/PaginationTable.vue
- Dead Code · Dead file (~55 LoC) src/components/viewers/ViewerPHPSerialize.vue
- Dead Code · Dead file (~51 LoC) src/components/viewers/ViewerMsgpack.vue
- Dead Code · Dead file (~48 LoC) src/components/FileInput.vue
- Dead Code · Dead file (~48 LoC) src/components/InputPassword.vue
- Dead Code · Dead file (~45 LoC) src/components/viewers/ViewerJson.vue
- Dead Code · Dead file (~44 LoC) src/components/LanguageSelector.vue
- Dead Code · Dead file (~41 LoC) src/components/viewers/ViewerBrotli.vue
- Dead Code · Dead file (~41 LoC) src/components/viewers/ViewerDeflate.vue
- Dead Code · Dead file (~41 LoC) src/components/viewers/ViewerDeflateRaw.vue
- Dead Code · Dead file (~41 LoC) src/components/viewers/ViewerGzip.vue
- Dead Code · Dead file (~39 LoC) src/components/InputBinary.vue
- Dead Code · Dead file (~38 LoC) src/components/viewers/ViewerJavaSerialize.vue
- Dead Code · Dead file (~30 LoC) src/components/viewers/ViewerBinary.vue
- Dead Code · Dead file (~30 LoC) src/components/viewers/ViewerHex.vue
- Dead Code · Dead file (~30 LoC) src/components/viewers/ViewerPickle.vue
- Dead Code · Dead file (~29 LoC) src/components/viewers/ViewerOverSize.vue
- Dead Code · Dead file (~18 LoC) pack/scripts/notarize.js
- Dead Code · Dead file (~15 LoC) src/router/index.js
- Dead Code · Dead file (~7 LoC) config/dev.env.js
- Dead Code · Dead file (~4 LoC) config/prod.env.js
- Exception handling · Swallowed exception (empty catch) pack/electron/win-state.js
- Exception handling · Swallowed exception (empty catch) pack/electron/win-state.js
- Exception handling · Swallowed exception (empty catch) pack/electron/update.js
- Exception handling · Swallowed exception (empty catch) pack/electron/update.js
- Exception handling · Swallowed exception (empty catch) src/util.js
- Exception handling · Swallowed exception (empty catch) src/util.js
- Exception handling · Swallowed exception (empty catch) src/util.js
- Exception handling · Swallowed exception (empty catch) src/util.js
- Exception handling · Swallowed exception (empty catch) src/util.js
- Exception handling · Swallowed exception (empty catch) src/components/SlowLog.vue
- Exception handling · Swallowed exception (empty catch) src/components/SlowLog.vue
- Exception handling · Swallowed exception (empty catch) src/components/OperateItem.vue
- Exception handling · Swallowed exception (empty catch) src/components/OperateItem.vue
- Exception handling · Swallowed exception (empty catch) src/components/KeyHeader.vue
- Exception handling · Swallowed exception (empty catch) src/components/KeyHeader.vue
- Exception handling · Swallowed exception (empty catch) src/components/KeyHeader.vue
- Exception handling · Swallowed exception (empty catch) src/components/ConnectionWrapper.vue
- Exception handling · Swallowed exception (empty catch) src/components/ConnectionWrapper.vue
- Exception handling · Swallowed exception (empty catch) src/components/ConnectionMenu.vue
- Exception handling · Swallowed exception (empty catch) src/components/ConnectionMenu.vue
- Exception handling · Swallowed exception (empty catch) src/components/ConnectionMenu.vue
- Exception handling · Swallowed exception (empty catch) src/components/ConnectionMenu.vue
- Exception handling · Swallowed exception (empty catch) src/components/contents/KeyContentZset.vue
- Exception handling · Swallowed exception (empty catch) src/components/contents/KeyContentZset.vue
- Exception handling · Swallowed exception (empty catch) src/components/contents/KeyContentSet.vue
- Exception handling · Swallowed exception (empty catch) src/components/contents/KeyContentSet.vue
- Exception handling · Swallowed exception (empty catch) src/components/contents/KeyContentList.vue
- Exception handling · Swallowed exception (empty catch) src/components/contents/KeyContentList.vue
- Exception handling · Swallowed exception (empty catch) src/components/contents/KeyContentHash.vue
- Exception handling · Swallowed exception (empty catch) src/components/contents/KeyContentHash.vue
- Visual & motion safety · Low contrast colour pair in CSS (1.7:1) static/theme/light/index.css
- Visual & motion safety · Low contrast colour pair in CSS (3.1:1) static/theme/dark/index.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement static/theme/light/index.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement static/theme/light/index.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement static/theme/light/index.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement static/theme/dark/index.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement static/theme/dark/index.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement static/theme/dark/index.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement static/theme/dark/index.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement static/theme/dark/index.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement static/theme/dark/index.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement static/theme/dark/index.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement static/theme/dark/index.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement static/theme/dark/index.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement static/theme/dark/index.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement static/theme/dark/index.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement static/theme/dark/index.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement static/theme/dark/index.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement static/theme/dark/index.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement static/theme/dark/index.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement static/theme/dark/index.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement static/theme/dark/index.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement static/theme/dark/index.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement static/theme/dark/index.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement static/theme/dark/index.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement static/theme/dark/index.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement static/theme/dark/index.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement static/theme/dark/index.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement static/theme/dark/index.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement static/theme/dark/index.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement static/theme/dark/index.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement static/theme/dark/index.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement static/theme/dark/index.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement static/theme/dark/index.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement static/theme/dark/index.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement static/theme/dark/index.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement static/theme/dark/index.css
- Visual & motion safety · Focus outline removed in CSS without a :focus replacement static/theme/dark/index.css
- Visual & motion safety · Animation without a prefers-reduced-motion guard static/theme/light/index.css
- Visual & motion safety · Animation without a prefers-reduced-motion guard static/theme/light/index.css
- Visual & motion safety · Animation without a prefers-reduced-motion guard static/theme/light/index.css
Rebuild cost: about €14,000 · Estimate
| Cost to rebuild | €4,600 to €23,000, for 77 to 246 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 30. 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: 16,431 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
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 | 106 | High / Critical |
| A05:2025 — Injection | 29 | High / Critical |
Roadmap
Top priorities: Resolve the 1 No automated tests finding(s) in Code Coverage; Resolve the 22 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (22); Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 22 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (22). | +4.9 pts | Medium | Dependency Hygiene |
| Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href. | +4.8 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.8 pts | Medium | Visual & motion safety |
| Resolve the 1 No automated tests finding(s) in Code Coverage. | +7.5 pts | High | Code Coverage |
| Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh. | +3.5 pts | Medium | Page structure |
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with package.json. | +1.2 pts | Low | ADR Quality |
| Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label. | +2.4 pts | Medium | Forms & labels |
| Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/javascript`, or eslint-plugin-security — so a security regression fails the build instead of landing. | +2.3 pts | Medium | Security & performance tooling |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 1.4 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 1.6 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.1 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| package.json | 4.0 | Mixed | Platform End-of-Life: End-of-life framework: Vue 2 |
| REDACTED | 4.5 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 6.5 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/components/LanguageSelector.vue | 8.0 | Near-clean | Change Coupling: Boundary-crossing change coupling: LanguageSelector.vue ↔ i18n.js |
| src/components/FormatViewer.vue | 8.5 | Near-clean | Change Coupling: Change coupling: FormatViewer.vue ↔ util.js |
| src/redisClient.js | 9.5 | Near-clean | Comment Value: redundant comment |
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 58 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 — 58 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, 384 of 409 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
- D4 Code Duplication — 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. The language model for this repository listed its production source (.html) but exposed no token stream for any of it, so nothing reached the token comparison.
- 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 (41 contributor(s) across 897 commit(s) sampled, automation and bot accounts excluded). One of them holds 94% of the history; the other 40 hold 0.2% 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.
- D21 Naming 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. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
- AC6 Visual & motion safety — 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. 150 further occurrence(s) are not listed individually; the score already reflects all 190.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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. A program the dev server needs is not installed in our sandbox image. This is a limit of our sandbox, not of your repository. (rule: missing-tool). The renderer reported: the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): a program the dev server needs is not installed in our sandbox image. This is a limit of our sandbox, not of your repository. Last output: "> another-redis-desktop-manager@1.1.1 dev / > webpack serve --mode development --progress --config build/webpack.dev.conf.js / sh: 1: webpack: not found" 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): a program the dev server needs is not installed in our sandbox image. This is a limit of our sandbox, not of your repository. Last output: "> another-redis-desktop-manager@1.1.1 dev / > webpack serve --mode development --progress --config build/webpack.dev.conf.js / sh: 1: webpack: not found" No runtime evidence was gathered.
- 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 Vue components 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 Vue components 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.
- P1 CI/CD gates — 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. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
- R7 Dead Code — 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. 25 further occurrence(s) are not listed individually; the score already reflects all 65.
- 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.
- X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP make no call through a named logger, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X5 Nullable reference types — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's Vue components is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- 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.
- 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.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- 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.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
0 method(s) exceeded the cognitive complexity threshold of 15.
D3 · God Classes
0 god class(es) detected.
D5 · Coupling
2 production modules (npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations, and main-sequence distance (abstractness) is not computed for these modules yet.
D8 · Code Coverage
No automated tests — no test code was found in this repository.
What to do
- Resolve the 1 No automated tests finding(s) in Code Coverage. — One of this dimension's main actionable groups (1 issue-level).
D12 · Dependency Hygiene
12 outdated direct production npm dependency(ies) of 21 graded, 0 pinning defect(s), across 2 package.json (2 of them the product) and 1 committed lockfile(s). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 10 direct dependency(ies) — production, development or optional — are marked DEPRECATED by their publisher (the registry's per-version mark, or the lockfile's copy of it when the registry could not be asked); deprecated transitive packages are listed but not charged. Whether any is UNMAINTAINED is not graded — the registry publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, and the frontend dependency lens (R8) answers it in this same run. Known CVEs in this dependency graph are D30's question, read from the manifest there.
What to do
- Resolve the 22 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (22). — One of this dimension's main actionable groups (22 recommendation-level).
- Resolve the 10 Deprecated finding(s) in Dependency Hygiene — start with package.json (10). — One of this dimension's main actionable groups (10 warning-level).
- Resolve the 1 Outdated (npm) finding(s) in Dependency Hygiene — start with package.json. — One of this dimension's main actionable groups (1 recommendation-level).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 87 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 87 package(s) this repository's committed lockfile installs for a consumer — its 21 production, optional and peer dependency(ies), across 2 product package.json manifest(s), and everything those install in turn. Its 59 `devDependencies` declaration(s), and every package only they reach, are excluded: a consumer installs none of them. ★ Each licence is the one the registry publishes for the package's CURRENT release rather than for the pinned version, which is the same caveat the Hex and RubyGems arms carry. 1 of them publish no licence this pass can read on registry.npmjs.org — an absent field, `UNLICENSED`, or a `SEE LICENSE IN <file>` pointer into a tarball this pass does not download; that is missing data, not a violation, and none of them is charged.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 2 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 package.json. — One of this dimension's main actionable groups (1 recommendation-level).
D24 · Comment Value
3 of 59 judged comments only repeat the code they sit on (5.1 %). 5 comment(s) in another language or script were not judged.
What to do
- Resolve the 3 redundant comment finding(s) in Comment Value — start with REDACTED (2), redisClient.js. — One of this dimension's main actionable groups (3 recommendation-level).
D26 · Project Cohesion
0 of 2 build units (npm) flagged as possibly oversized/incoherent.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
29 finding(s): 0 critical, 24 high, 5 medium, 0 low. 18 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 5 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (5 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 18 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (18 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
96 finding(s): 11 critical, 57 high, 20 medium, 8 low.
What to do
- Resolve the 55 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (55). — One of this dimension's main actionable groups (55 issue-level).
- Resolve the 10 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (10). — One of this dimension's main actionable groups (10 issue-level).
- Resolve the 2 High vulnerability 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 58 of the 89 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
Strongest change-coupling: LanguageSelector.vue↔i18n.js 85%; FormatViewer.vue↔util.js 50%
What to do
- Resolve the 1 Boundary-crossing change coupling finding(s) in Change Coupling — start with LanguageSelector.vue. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Change coupling finding(s) in Change Coupling — start with FormatViewer.vue. — One of this dimension's main actionable groups (1 warning-level).
D36 · Supply-chain Provenance & Signing
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 5 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 1 end-of-life framework(s), read from 1 platform declaration(s) and 21 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
What to do
- Resolve the 1 End-of-life framework finding(s) in Platform End-of-Life — start with package.json. — One of this dimension's main actionable groups (1 warning-level).
Frontend & cross-cutting dimensions
AC2 · Forms & labels
- This <i> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label. — src/components/InputPassword.vue:3
- This <i> carries a click handler, which makes it a control, and its only name is a title attribute. A plain element maps to role="generic", which does not support a name from the author, so the title is announced as nothing at all — it is a mouse-only tooltip, unreachable on touch. Give it role="button" (which it needs anyway to be operable) so the title becomes a real name, or add an aria-label. (×3) — src/components/KeyHeader.vue:13, src/components/KeyHeader.vue:30, src/components/KeyHeader.vue:36
- This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label. — src/components/ScrollToTop.vue:3
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
- The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). — index.html:2
- 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="app">, so there is no content here to wrap — render the <main> from the component mounted into it. — index.html:2
- A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope). — src/components/CustomFormatter.vue:66
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. (×22) — src/components/InputPassword.vue:3, src/components/KeyHeader.vue:13, src/components/KeyHeader.vue:30, …
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
- `.el-pagination.is-background .el-pager li:not(.disabled).active` sets color: #fff on background-color: #409EFF — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. This is a MINIFIED, build-generated sheet — editing the literal here is undone by the next vendor drop or rebuild, so override the rule in your own stylesheet (or fix it upstream / in the source the bundle is built from). — static/theme/light/index.css:1
- `.el-select .el-tag__close.el-icon-close` sets color: #fff on background-color: #c0c4cc — 1.7:1, below the 4.5:1 WCAG AA minimum for normal text. This is a MINIFIED, build-generated sheet — editing the literal here is undone by the next vendor drop or rebuild, so override the rule in your own stylesheet (or fix it upstream / in the source the bundle is built from). — static/theme/light/index.css:1
- `.el-date-table td.current:not(.disabled) span` sets color: #fff on background-color: #409EFF — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. This is a MINIFIED, build-generated sheet — editing the literal here is undone by the next vendor drop or rebuild, so override the rule in your own stylesheet (or fix it upstream / in the source the bundle is built from). — static/theme/light/index.css:1
- `.el-date-table td.selected span` sets color: #fff on background-color: #409EFF — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. This is a MINIFIED, build-generated sheet — editing the literal here is undone by the next vendor drop or rebuild, so override the rule in your own stylesheet (or fix it upstream / in the source the bundle is built from). — static/theme/light/index.css:1
- `.el-tabs__item .el-icon-close:hover` sets color: #fff on background-color: #c0c4cc — 1.7:1, below the 4.5:1 WCAG AA minimum for normal text. This is a MINIFIED, build-generated sheet — editing the literal here is undone by the next vendor drop or rebuild, so override the rule in your own stylesheet (or fix it upstream / in the source the bundle is built from). — static/theme/light/index.css:1
- `.el-tag .el-icon-close:hover` sets color: #fff on background-color: #409EFF — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. This is a MINIFIED, build-generated sheet — editing the literal here is undone by the next vendor drop or rebuild, so override the rule in your own stylesheet (or fix it upstream / in the source the bundle is built from). — static/theme/light/index.css:1
- `.el-select .el-tag__close.el-icon-close` sets color: #263238 on background-color: #507fa9 — 3.1:1, below the 4.5:1 WCAG AA minimum for normal text. This is a MINIFIED, build-generated sheet — editing the literal here is undone by the next vendor drop or rebuild, so override the rule in your own stylesheet (or fix it upstream / in the source the bundle is built from). — static/theme/dark/index.css:1
- `.el-tabs__item .el-icon-close:hover` sets color: #263238 on background-color: #507fa9 — 3.1:1, below the 4.5:1 WCAG AA minimum for normal text. This is a MINIFIED, build-generated sheet — editing the literal here is undone by the next vendor drop or rebuild, so override the rule in your own stylesheet (or fix it upstream / in the source the bundle is built from). — static/theme/dark/index.css:1
- `.el-cascader__tags .el-tag .el-icon-close` sets color: #263238 on background-color: #507fa9 — 3.1:1, below the 4.5:1 WCAG AA minimum for normal text. This is a MINIFIED, build-generated sheet — editing the literal here is undone by the next vendor drop or rebuild, so override the rule in your own stylesheet (or fix it upstream / in the source the bundle is built from). — static/theme/dark/index.css:1
- `.connections-wrap .group-count` sets color: #909399 on background-color: #fff — 3.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/components/Connections.vue:409
- `.connection-menu .key-list .key-item.key-select` sets color: #0b7ff7 on background-color: #e7ebec — 3.2:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/components/KeyListNormal.vue:88
- `.size-too-large-viewer .el-alert` sets color: #f56c6c on background-color: #f9dbdb — 2.2:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/components/viewers/ViewerOverSize.vue:33
- `.el-dropdown .el-dropdown-selfdefine:focus:not(.focusing)` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — static/theme/light/index.css:1
- `.el-pagination button:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — static/theme/light/index.css:1
- `.el-dialog__headerbtn` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — static/theme/light/index.css:1
- `.el-menu--horizontal>.el-submenu:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — static/theme/light/index.css:1
- `.el-radio` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — static/theme/light/index.css:1
- `.el-radio__input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — static/theme/light/index.css:1
- `.el-radio__original` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — static/theme/light/index.css:1
- `.el-radio-button` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — static/theme/light/index.css:1
- `.el-radio-button__orig-radio` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — static/theme/light/index.css:1
- `.el-switch__core` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — static/theme/light/index.css:1
- `.el-select__input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — static/theme/light/index.css:1
- `.el-table-filter__bottom button:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — static/theme/light/index.css:1
- `.el-date-editor .el-range-input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — static/theme/light/index.css:1
- `.el-picker-panel__shortcut` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — static/theme/light/index.css:1
- `.el-picker-panel__btn` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — static/theme/light/index.css:1
- `.el-picker-panel__icon-btn` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — static/theme/light/index.css:1
- `.el-time-panel__btn` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — static/theme/light/index.css:1
- `.el-message-box__headerbtn` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — static/theme/light/index.css:1
- `.el-tabs__item:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — static/theme/light/index.css:1
- `.el-carousel__arrow` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — static/theme/light/index.css:1
- `.el-carousel__button` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — static/theme/light/index.css:1
- `.el-collapse-item__header` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — static/theme/light/index.css:1
- `.el-cascader-menu__item` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — static/theme/light/index.css:1
- `.el-color-dropdown__btn` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — static/theme/light/index.css:1
- `.el-input.is-active .el-input__inner` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — static/theme/light/index.css:1
- `.el-input-group__append:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — static/theme/light/index.css:1
- `.el-checkbox__input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — static/theme/light/index.css:1
- `.el-checkbox__original` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — static/theme/light/index.css:1
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
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
What to do
- Run the test suite in CI via an explicit runner step (`npm test` for the toolchain this pipeline already uses) and gate merges on it.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/javascript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 7 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.
- `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`. — package.json:28
What to do
- Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/javascript`, or eslint-plugin-security — 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.
P4 · Deployment & Rollback
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
- 0 typed · 89 plain JS — the untyped files are config/dev.env.js, config/index.js, config/prod.env.js, REDACTED, pack/electron/font-manager.js, pack/electron/update.js (+83 more).
What to do
- Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
R10 · Code Duplication
- src/components/contents/KeyContentArray.vue:113 · src/components/contents/KeyContentTimeSeries.vue:153 — the two spans are one implementation copied and then locally edited — 1052 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/components/contents/KeyContentArray.vue:113
- src/components/contents/KeyContentList.vue:97 · src/components/contents/KeyContentSet.vue:97 — the two spans are one implementation copied and then locally edited — 473 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/components/contents/KeyContentList.vue:97
- src/components/contents/KeyContentList.vue:152 · src/components/contents/KeyContentStream.vue:259 — the two spans are one implementation copied and then locally edited — 395 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/components/contents/KeyContentList.vue:152
- src/components/contents/KeyContentSet.vue:160 · src/components/contents/KeyContentZset.vue:200 — the two spans are one implementation copied and then locally edited — 427 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/components/contents/KeyContentSet.vue:160
- src/components/contents/KeyContentReJson.vue:25 · src/components/contents/KeyContentString.vue:25 — the two spans are one implementation copied and then locally edited — 391 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/components/contents/KeyContentReJson.vue:25
- src/components/contents/KeyContentHash.vue:269 · src/components/contents/KeyContentZset.vue:267 — the two spans are one implementation copied and then locally edited — 326 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/components/contents/KeyContentHash.vue:269
- src/components/contents/KeyContentHash.vue:190 · src/components/contents/KeyContentSet.vue:139 — the two spans are one implementation copied and then locally edited — 324 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/components/contents/KeyContentHash.vue:190
- src/components/contents/KeyContentHash.vue:138 · src/components/contents/KeyContentSet.vue:99 — the 2 copies are spread across 2 files, 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. — src/components/contents/KeyContentHash.vue:138
- src/components/contents/KeyContentVector.vue:169 · src/components/contents/KeyContentZset.vue:108 — the two spans are one implementation copied and then locally edited — 136 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/components/contents/KeyContentVector.vue:169
- src/components/ConnectionMenu.vue:280 · src/components/ConnectionMenu.vue:340 — 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. — src/components/ConnectionMenu.vue:280
- src/components/MemoryAnalysis.vue:234 · src/components/SlowLog.vue:140 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — src/components/MemoryAnalysis.vue:234
- src/components/contents/KeyContentSet.vue:256 · src/components/contents/KeyContentStream.vue:365 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — src/components/contents/KeyContentSet.vue:256
- src/components/contents/KeyContentStream.vue:168 · src/components/contents/KeyContentVector.vue:173 — the two spans are one implementation copied and then locally edited — 112 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/components/contents/KeyContentStream.vue:168
- src/components/viewers/ViewerBinary.vue:9 · src/components/viewers/ViewerHex.vue:9 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — src/components/viewers/ViewerBinary.vue:9
- src/components/viewers/ViewerMsgpack.vue:18 · src/components/viewers/ViewerPHPSerialize.vue:27 — the 2 copies are spread across 2 files, 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. — src/components/viewers/ViewerMsgpack.vue:18
- src/components/ConnectionMenu.vue:373 · src/components/KeyHeader.vue:159 — the two spans are one implementation copied and then locally edited — 136 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/components/ConnectionMenu.vue:373
- src/components/DeleteBatch.vue:88 · src/components/MemoryAnalysis.vue:139 — the two spans are one implementation copied and then locally edited — 109 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/components/DeleteBatch.vue:88
- src/components/viewers/ViewerBrotli.vue:7 · src/components/viewers/ViewerDeflate.vue:7 · src/components/viewers/ViewerDeflateRaw.vue:7 · src/components/viewers/ViewerGzip.vue:7 — the 4 copies are spread across 4 files, 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. — src/components/viewers/ViewerBrotli.vue:7
- src/components/ConnectionMenu.vue:240 · src/components/ConnectionMenu.vue:305 — 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. — src/components/ConnectionMenu.vue:240
- src/components/contents/KeyContentArray.vue:241 · src/components/contents/KeyContentList.vue:198 · src/components/contents/KeyContentSet.vue:197 — the 3 copies are spread across 3 files, 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. — src/components/contents/KeyContentArray.vue:241
- src/components/Connections.vue:242 · src/components/NewConnectionDialog.vue:313 — the two spans are one implementation copied and then locally edited — 92 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/components/Connections.vue:242
- src/components/DeleteBatch.vue:141 · src/components/DeleteBatch.vue:168 — the two spans are one implementation copied and then locally edited — 86 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/components/DeleteBatch.vue:141
- src/components/DeleteBatch.vue:204 · src/components/Status.vue:376 — the two spans are one implementation copied and then locally edited — 53 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/components/DeleteBatch.vue:204
- src/components/CliTab.vue:74 · src/components/OperateItem.vue:144 — the 2 copies are spread across 2 files, 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. — src/components/CliTab.vue:74
- src/components/KeyListVirtualTree.vue:194 · src/components/Tabs.vue:353 — the 2 copies are spread across 2 files, 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. — src/components/KeyListVirtualTree.vue:194
- src/components/contents/KeyContentVector.vue:498 · src/components/contents/KeyContentZset.vue:216 — the 2 copies are spread across 2 files, 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. — src/components/contents/KeyContentVector.vue:498
- src/components/CliTab.vue:412 · src/components/OperateItem.vue:375 — the two spans are one implementation copied and then locally edited — 92 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/components/CliTab.vue:412
- src/components/Tabs.vue:162 · src/components/Tabs.vue:174 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — src/components/Tabs.vue:162
- src/components/contents/KeyContentVector.vue:349 · src/components/contents/KeyContentVector.vue:474 — the two spans are one implementation copied and then locally edited — 78 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/components/contents/KeyContentVector.vue:349
- src/components/KeyHeader.vue:144 · src/components/contents/KeyContentVector.vue:417 — the 2 copies are spread across 2 files, 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. — src/components/KeyHeader.vue:144
- src/components/KeyListVirtualTree.vue:285 · src/components/KeyListVirtualTree.vue:298 — the two spans are one implementation copied and then locally edited — 54 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/components/KeyListVirtualTree.vue:285
- src/components/DeleteBatch.vue:70 · src/components/MemoryAnalysis.vue:110 — the 2 copies are spread across 2 files, 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. — src/components/DeleteBatch.vue:70
- src/components/contents/KeyContentTimeSeries.vue:250 · src/components/contents/KeyContentVector.vue:258 — the 2 copies are spread across 2 files, 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. — src/components/contents/KeyContentTimeSeries.vue:250
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.
R11 · Import Boundaries
- src/i18n/i18n.js:3 imports element-ui/lib/locale, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/i18n/i18n.js:3
- src/i18n/i18n.js:5 imports element-ui/lib/locale/lang/en, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/i18n/i18n.js:5
- src/i18n/i18n.js:6 imports element-ui/lib/locale/lang/zh-CN, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/i18n/i18n.js:6
- src/i18n/i18n.js:7 imports element-ui/lib/locale/lang/zh-TW, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/i18n/i18n.js:7
- src/i18n/i18n.js:8 imports element-ui/lib/locale/lang/tr-TR, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/i18n/i18n.js:8
- src/i18n/i18n.js:9 imports element-ui/lib/locale/lang/ru-RU, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/i18n/i18n.js:9
- src/i18n/i18n.js:10 imports element-ui/lib/locale/lang/pt-br, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/i18n/i18n.js:10
- src/i18n/i18n.js:11 imports element-ui/lib/locale/lang/de, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/i18n/i18n.js:11
- src/i18n/i18n.js:12 imports element-ui/lib/locale/lang/fr, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/i18n/i18n.js:12
- src/i18n/i18n.js:13 imports element-ui/lib/locale/lang/ua, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/i18n/i18n.js:13
- src/i18n/i18n.js:14 imports element-ui/lib/locale/lang/it, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/i18n/i18n.js:14
- src/i18n/i18n.js:15 imports element-ui/lib/locale/lang/es, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/i18n/i18n.js:15
- src/i18n/i18n.js:16 imports element-ui/lib/locale/lang/ko, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/i18n/i18n.js:16
- src/i18n/i18n.js:17 imports element-ui/lib/locale/lang/vi, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/i18n/i18n.js:17
What to do
- Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.
R2 · Cyclomatic Complexity
- multipleCheck has cyclomatic complexity 16 and cognitive complexity 20; 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 is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. 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. — src/components/KeyListVirtualTree.vue:319
- autoFormat has cyclomatic complexity 16 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. — src/components/FormatViewer.vue:172
- consoleExec has cyclomatic complexity 14 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 is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. 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. — src/components/CliTab.vue:189
- editLine has cyclomatic complexity 13 and cognitive complexity 12; 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. — src/components/contents/KeyContentVector.vue:345
- (anonymous) has cyclomatic complexity 11 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 is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. 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. — src/components/contents/KeyContentStream.vue:210
R3 · Large Files
- src/components/KeyListVirtualTree.vue has 555 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/components/KeyListVirtualTree.vue:1
- src/components/contents/KeyContentVector.vue has 496 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/components/contents/KeyContentVector.vue:1
- src/components/NewConnectionDialog.vue has 485 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/components/NewConnectionDialog.vue:1
- src/components/Connections.vue has 457 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/components/Connections.vue:1
- src/components/OperateItem.vue has 440 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/components/OperateItem.vue:1
- src/components/ConnectionMenu.vue has 407 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/components/ConnectionMenu.vue:1
- src/components/contents/KeyContentStream.vue has 404 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/components/contents/KeyContentStream.vue:1
- src/components/Tabs.vue has 403 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/components/Tabs.vue:1
- src/components/CliTab.vue has 401 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/components/CliTab.vue: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 86 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).
R5 · Dependency Freshness
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 type checking (adopt TypeScript, or type-check the existing JavaScript with `checkJs`) as package.json scripts and run them in CI.
R7 · Dead Code
- Unreachable from the 2 application, 1 tooling and 0 test entry point(s) detected in this repo. Gate removals on `npm run dev` — an undetected custom entry would make these reachable.
- no import path from any entry point (2 application, 1 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×39) — src/components/contents/KeyContentVector.vue, src/components/NewConnectionDialog.vue, src/components/CliTab.vue, …
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 the root 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. (×2)
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
S1 · Web-Security Posture
- `rejectUnauthorized: false` is set on a TLS client, so every peer certificate is accepted — including one an attacker presents. Chain, expiry, revocation and hostname are all skipped, so an attacker on the network path can present any certificate and read or rewrite the traffic — the connection is encrypted to the attacker, not to the intended host. Remove the option so Node validates the peer. If the server presents a self-signed or privately-issued certificate, trust THAT issuer rather than every certificate: pass its CA as `ca` (or set `NODE_EXTRA_CA_CERTS`), which keeps the chain and hostname checks on. A managed database or broker that documents `rejectUnauthorized: false` publishes a CA bundle for exactly this purpose. — src/redisClient.js:340
What to do
- Stop accepting every TLS certificate: delete `rejectUnauthorized: false` / `NODE_TLS_REJECT_UNAUTHORIZED=0` so the chain, hostname and expiry are verified, and trust a self-signed or private server by passing its CA (`ca`, or `NODE_EXTRA_CA_CERTS`) — never by switching verification off.
X1 · Async correctness
X12 · Unreachable branch
X16 · Unfloored truncation loop
X19 · Unrestored process-global state
X21 · Side-effecting pattern guard
X24 · Document value interpolated into markup unescaped
- `$t('message.font_faq')` is text this program did not author, and it is written into the text of an element through Vue's `v-html` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — src/components/Setting.vue:52
What to do
- Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×8) — src/util.js:85, src/util.js:95, src/util.js:125, …
- `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it. (×17) — src/components/ConnectionMenu.vue:161, src/components/ConnectionMenu.vue:169, src/components/ConnectionMenu.vue:203, …
- `.catch((e) => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it. (×11) — src/components/ConnectionMenu.vue:392, src/components/ConnectionWrapper.vue:103, src/components/ConnectionWrapper.vue:152, …
- `.catch((err) => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it. (×2) — pack/electron/update.js:16, pack/electron/update.js:24
What to do
- Swallowed exception (empty catch)
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 | 37% | Weak — gated by R1, R7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 67% | Adequate — gated by R11 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 55% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 23% | Critical — gated by D8, R4, R6, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 63% | Adequate — gated by D29, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 21% | Critical — gated by AC3, AC4, AC6 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 1 check(s) recorded observations but carry no score
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 68 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: this repository's JavaScript 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 — Not applicable: 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 — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- 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): a program the dev server needs is not installed in our sandbox image. This is a limit of our sandbox, not of your repository. Last output: "> another-redis-desktop-manager@1.1.1 dev / > webpack serve --mode development --progress --config build/webpack.dev.conf.js / sh: 1: webpack: not found" 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 — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no data at rest for these controls to protect. If it does persist personal data (through a hosted backend configured outside this repository, for instance), the controls belong to wherever that data is stored.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository stands up no server (no Express, Fastify, Koa, Hono, NestJS or similar app, no Next.js/SvelteKit/Nuxt server route, no edge function), creates no Supabase tables and talks to no hosted backend. Access control is therefore N/A here — a browser application or library is authorized by the server it calls, not by itself; a client-side route guard hides a page and authorizes nothing. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound. If it does (through a hosted backend configured outside this repository, for instance), the limit belongs wherever that data is stored.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over. If it does (through a hosted backend configured outside this repository, for instance), the rights are served wherever that data is stored.
- D10 Test Quality — No tests were found in the analyzed repository to assess for quality.
- D11 Test Reliability — No test suite was found to re-run, so reliability couldn't be assessed. Two searches produced that zero and both came back empty: the classifier that reads the loaded workspace recognised no suite it could run, and a walk of the source on disk — which covers the JS/TS `*.test.*` and `*.spec.*` conventions and probes for a Pester suite — found no test source in any other ecosystem either. Neither search reaches a suite that is missing from the loaded workspace and carries no name either walk recognises, so this is 'no suite found by those two searches', not a verdict that the repository has none.
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D17 Explicit Debt — explicit-debt markers are read through a C# workspace today, so they were not read for this repository's language — this asserts nothing about how many markers the code carries. Not scored — this is a gap in the analyzer, not a finding about this repository
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; JavaScript, html not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — symbol resolution incomplete — navigability not assessed
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D4 Code Duplication — Duplication not measured — .html not exposed to the token comparison
- 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.
- D6 Cohesion (LCOM4) — No production classes were analyzable, so cohesion (LCOM4) was not measured (the solution likely failed to load or has no production code).
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P2 Observability — This repository's JavaScript/TypeScript source (2 module(s), 38 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript 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 tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a package.json, 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.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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
- 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
- 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.
- 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
- 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: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
- X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. JavaScript and TypeScript have no iterator that a change can invalidate: an `Array` is walked by index against its live length, and a `Map` or `Set` by the ECMAScript specification's live entry list, so a body that adds to, removes from or empties what it walks raises nothing — every loop form (`for…of`, `for…in`, `forEach`, `map`, `filter`, `reduce`, `entries()`) on every built-in collection (`Array`, `Map`, `Set`, plain objects, `URLSearchParams`, `Headers`, `FormData`) runs to completion. Such a loop can still skip an element or never end, which is a different defect and not the one this check asks about. Not a gap in the analyzer and not a finding about your code.
- 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
- 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 — 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
- X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 123 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
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Click handler on a non-interactive <li> src/components/KeyListNormal.vue:10
- Click handler on a non-interactive <li> src/components/KeyListVirtualTree.vue:60
- Click handler on a non-interactive <li> src/components/KeyListVirtualTree.vue:61
- Click handler on a non-interactive <li> src/components/KeyListVirtualTree.vue:62
- Click handler on a non-interactive <li> src/components/KeyListVirtualTree.vue:63
- Click handler on a non-interactive <li> src/components/KeyListVirtualTree.vue:67
- Click handler on a non-interactive <li> src/components/KeyListVirtualTree.vue:68
- Click handler on a non-interactive <li> src/components/KeyListVirtualTree.vue:69
- Click handler on a non-interactive <li> src/components/KeyListVirtualTree.vue:70
- Click handler on a non-interactive <li> src/components/KeyListVirtualTree.vue:71
- Click handler on a non-interactive <li> src/components/MemoryAnalysis.vue:60
- Click handler on a non-interactive <li> src/components/Tabs.vue:24
- Click handler on a non-interactive <li> src/components/Tabs.vue:25
- Click handler on a non-interactive <li> src/components/Tabs.vue:26
- Click handler on a non-interactive <li> src/components/Tabs.vue:27
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Click handler on a non-interactive <i> src/components/InputPassword.vue:3
- Click handler on a non-interactive <i> src/components/KeyHeader.vue:13
- Click handler on a non-interactive <i> src/components/KeyHeader.vue:30
- Click handler on a non-interactive <i> src/components/KeyHeader.vue:36
- Custom control named only by title on <i> src/components/KeyHeader.vue:13
- Custom control named only by title on <i> src/components/KeyHeader.vue:30
- Custom control named only by title on <i> src/components/KeyHeader.vue:36
- Click handler on a non-interactive <span> src/components/MemoryAnalysis.vue:46
- Click handler on a non-interactive <span> src/components/SlowLog.vue:21
- REDACTED
- REDACTED
- Custom control with no accessible name on <i> src/components/InputPassword.vue:3
- Custom control with no accessible name on <div> src/components/ScrollToTop.vue:3
- <html> without a lang index.html:2
- Click handler on a non-interactive <div> src/components/ScrollToTop.vue:3
- REDACTED
- REDACTED
- Boundary-crossing change coupling: LanguageSelector.vue ↔ i18n.js src/components/LanguageSelector.vue:1
- No automated tests
- TLS certificate validation disabled src/redisClient.js:340
Serious — 231 finding(s)
- Swallowed exception (empty catch) src/util.js:85
- Swallowed exception (empty catch) src/util.js:95
- Swallowed exception (empty catch) src/util.js:125
- Swallowed exception (empty catch) src/util.js:160
- Swallowed exception (empty catch) src/util.js:180
- Swallowed exception (empty catch) src/components/ConnectionMenu.vue:161
- Swallowed exception (empty catch) src/components/ConnectionMenu.vue:169
- Swallowed exception (empty catch) src/components/ConnectionMenu.vue:203
- Swallowed exception (empty catch) src/components/ConnectionMenu.vue:392
- Swallowed exception (empty catch) src/components/ConnectionWrapper.vue:103
- Swallowed exception (empty catch) src/components/ConnectionWrapper.vue:152
- Swallowed exception (empty catch) src/components/Connections.vue:266
- Swallowed exception (empty catch) src/components/DeleteBatch.vue:170
- Swallowed exception (empty catch) src/components/KeyHeader.vue:149
- Swallowed exception (empty catch) src/components/KeyHeader.vue:186
- Swallowed exception (empty catch) src/components/KeyHeader.vue:203
- Swallowed exception (empty catch) src/components/NewConnectionDialog.vue:405
- Swallowed exception (empty catch) src/components/OperateItem.vue:219
- Swallowed exception (empty catch) src/components/OperateItem.vue:262
- Swallowed exception (empty catch) src/components/Setting.vue:298
- Swallowed exception (empty catch) src/components/SlowLog.vue:114
- Swallowed exception (empty catch) src/components/SlowLog.vue:117
- Swallowed exception (empty catch) src/components/contents/KeyContentArray.vue:317
- Swallowed exception (empty catch) src/components/contents/KeyContentHash.vue:170
- Swallowed exception (empty catch) src/components/contents/KeyContentHash.vue:333
- Focus outline removed in CSS without a :focus replacement static/theme/light/index.css:1
- Focus outline removed in CSS without a :focus replacement static/theme/light/index.css:1
- Focus outline removed in CSS without a :focus replacement static/theme/light/index.css:1
- Focus outline removed in CSS without a :focus replacement static/theme/light/index.css:1
- Focus outline removed in CSS without a :focus replacement static/theme/light/index.css:1
- Focus outline removed in CSS without a :focus replacement static/theme/light/index.css:1
- Focus outline removed in CSS without a :focus replacement static/theme/light/index.css:1
- Focus outline removed in CSS without a :focus replacement static/theme/light/index.css:1
- Focus outline removed in CSS without a :focus replacement static/theme/light/index.css:1
- Focus outline removed in CSS without a :focus replacement static/theme/light/index.css:1
- Focus outline removed in CSS without a :focus replacement static/theme/light/index.css:1
- Focus outline removed in CSS without a :focus replacement static/theme/light/index.css:1
- Focus outline removed in CSS without a :focus replacement static/theme/light/index.css:1
- Focus outline removed in CSS without a :focus replacement static/theme/light/index.css:1
- Focus outline removed in CSS without a :focus replacement static/theme/light/index.css:1
- Focus outline removed in CSS without a :focus replacement static/theme/light/index.css:1
- Focus outline removed in CSS without a :focus replacement static/theme/light/index.css:1
- Focus outline removed in CSS without a :focus replacement static/theme/light/index.css:1
- Focus outline removed in CSS without a :focus replacement static/theme/light/index.css:1
- Focus outline removed in CSS without a :focus replacement static/theme/light/index.css:1
- Focus outline removed in CSS without a :focus replacement static/theme/light/index.css:1
- Focus outline removed in CSS without a :focus replacement static/theme/light/index.css:1
- Focus outline removed in CSS without a :focus replacement static/theme/light/index.css:1
- Focus outline removed in CSS without a :focus replacement static/theme/light/index.css:1
- Focus outline removed in CSS without a :focus replacement static/theme/light/index.css:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Boundary violation [package:third-party-deep-import] src/i18n/i18n.js:3
- Boundary violation [package:third-party-deep-import] src/i18n/i18n.js:5
- Boundary violation [package:third-party-deep-import] src/i18n/i18n.js:6
- Boundary violation [package:third-party-deep-import] src/i18n/i18n.js:7
- Boundary violation [package:third-party-deep-import] src/i18n/i18n.js:8
- Boundary violation [package:third-party-deep-import] src/i18n/i18n.js:9
- Boundary violation [package:third-party-deep-import] src/i18n/i18n.js:10
- Boundary violation [package:third-party-deep-import] src/i18n/i18n.js:11
- Boundary violation [package:third-party-deep-import] src/i18n/i18n.js:12
- Boundary violation [package:third-party-deep-import] src/i18n/i18n.js:13
- Boundary violation [package:third-party-deep-import] src/i18n/i18n.js:14
- Boundary violation [package:third-party-deep-import] src/i18n/i18n.js:15
- Boundary violation [package:third-party-deep-import] src/i18n/i18n.js:16
- Boundary violation [package:third-party-deep-import] src/i18n/i18n.js:17
- Deprecated: vue package.json:47
- Deprecated: vue-i18n package.json:48
- Deprecated: @babel/plugin-proposal-class-properties package.json:53
- Deprecated: @babel/plugin-proposal-export-namespace-from package.json:55
- Deprecated: @babel/plugin-proposal-json-strings package.json:57
- Deprecated: @babel/plugin-proposal-numeric-separator package.json:58
- Deprecated: asar package.json:67
- Deprecated: eslint package.json:79
- Deprecated: friendly-errors-webpack-plugin package.json:85
- Deprecated: rimraf package.json:98
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Low contrast colour pair in CSS (2.8:1) static/theme/light/index.css:1
- Low contrast colour pair in CSS (2.8:1) static/theme/light/index.css:1
- Low contrast colour pair in CSS (2.8:1) static/theme/light/index.css:1
- Low contrast colour pair in CSS (2.8:1) static/theme/light/index.css:1
- Low contrast colour pair in CSS (3.1:1) static/theme/dark/index.css:1
- Low contrast colour pair in CSS (3.1:1) static/theme/dark/index.css:1
- Low contrast colour pair in CSS (3.1:1) static/theme/dark/index.css:1
- Low contrast colour pair in CSS (3.1:1) src/components/Connections.vue:409
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (12 lines × 2 locations) src/components/CliTab.vue:74
- Duplicated block (12 lines × 2 locations) src/components/KeyListVirtualTree.vue:194
- Duplicated block (12 lines × 2 locations) src/components/contents/KeyContentVector.vue:498
- Low contrast colour pair in CSS (1.7:1) static/theme/light/index.css:1
- Low contrast colour pair in CSS (1.7:1) static/theme/light/index.css:1
- REDACTED
- REDACTED
- Duplicated block (22 lines × 2 locations) src/components/MemoryAnalysis.vue:234
- Duplicated block (22 lines × 2 locations) src/components/contents/KeyContentSet.vue:256
- Duplicated block (21 lines × 2 locations) src/components/viewers/ViewerBinary.vue:9
- Duplicated block (21 lines × 2 locations) src/components/viewers/ViewerMsgpack.vue:18
- Duplicated block with local edits (19 matched lines × 2 locations) src/components/ConnectionMenu.vue:373
- Duplicated block with local edits (19 matched lines × 2 locations) src/components/DeleteBatch.vue:88
- Duplicated block with local edits (11 matched lines × 2 locations) src/components/CliTab.vue:412
- Duplicated block with local edits (11 matched lines × 2 locations) src/components/contents/KeyContentVector.vue:349
- Dead file (~398 LoC) src/components/ConnectionMenu.vue
- Dead file (~398 LoC) src/components/Tabs.vue
- Dead file (~260 LoC) src/components/KeyHeader.vue
- Dead file (~260 LoC) src/components/MemoryAnalysis.vue
- Page without a main landmark index.html:2
- Data table has no header cells src/components/CustomFormatter.vue:66
- Low contrast colour pair in CSS (3.2:1) src/components/KeyListNormal.vue:88
- Low contrast colour pair in CSS (2.2:1) src/components/viewers/ViewerOverSize.vue:33
- Change coupling: FormatViewer.vue ↔ util.js src/components/FormatViewer.vue:1
- REDACTED
- REDACTED
- End-of-life framework: Vue 2 package.json:1
- Type Safety
- Duplicated block with local edits (162 matched lines × 2 locations) src/components/contents/KeyContentArray.vue:113
- Duplicated block with local edits (69 matched lines × 2 locations) src/components/contents/KeyContentList.vue:97
- Duplicated block with local edits (63 matched lines × 2 locations) src/components/contents/KeyContentList.vue:152
- Duplicated block with local edits (62 matched lines × 2 locations) src/components/contents/KeyContentSet.vue:160
- Duplicated block with local edits (61 matched lines × 2 locations) src/components/contents/KeyContentReJson.vue:25
- Duplicated block with local edits (51 matched lines × 2 locations) src/components/contents/KeyContentHash.vue:269
- Duplicated block with local edits (47 matched lines × 2 locations) src/components/contents/KeyContentHash.vue:190
- Duplicated block (37 lines × 2 locations) src/components/contents/KeyContentHash.vue:138
- Duplicated block with local edits (24 matched lines × 2 locations) src/components/contents/KeyContentVector.vue:169
- Duplicated block (23 lines × 2 locations) src/components/ConnectionMenu.vue:280
- Duplicated block with local edits (21 matched lines × 2 locations) src/components/contents/KeyContentStream.vue:168
- Duplicated block (18 lines × 4 locations) src/components/viewers/ViewerBrotli.vue:7
- Duplicated block (16 lines × 2 locations) src/components/ConnectionMenu.vue:240
- Duplicated block (16 lines × 3 locations) src/components/contents/KeyContentArray.vue:241
- Duplicated block with local edits (15 matched lines × 2 locations) src/components/Connections.vue:242
- Duplicated block with local edits (14 matched lines × 2 locations) src/components/DeleteBatch.vue:141
- Duplicated block with local edits (13 matched lines × 2 locations) src/components/DeleteBatch.vue:204
- Duplicated block (11 lines × 2 locations) src/components/Tabs.vue:162
- Duplicated block (8 lines × 2 locations) src/components/KeyHeader.vue:144
- Duplicated block with local edits (8 matched lines × 2 locations) src/components/KeyListVirtualTree.vue:285
- Duplicated block (7 lines × 2 locations) src/components/DeleteBatch.vue:70
- Duplicated block (6 lines × 2 locations) src/components/contents/KeyContentTimeSeries.vue:250
- Complex function multipleCheck (cyclomatic 16, cognitive 20) src/components/KeyListVirtualTree.vue:319
- Complex function autoFormat (cyclomatic 16, cognitive 15) src/components/FormatViewer.vue:172
- Complex function consoleExec (cyclomatic 14, cognitive 15) src/components/CliTab.vue:189
- Complex function editLine (cyclomatic 13, cognitive 12) src/components/contents/KeyContentVector.vue:345
- Complex function (anonymous) (cyclomatic 11, cognitive 13) src/components/contents/KeyContentStream.vue:210
- src/components/KeyListVirtualTree.vue: 555 lines of code src/components/KeyListVirtualTree.vue:1
- src/components/contents/KeyContentVector.vue: 496 lines of code src/components/contents/KeyContentVector.vue:1
- src/components/NewConnectionDialog.vue: 485 lines of code src/components/NewConnectionDialog.vue:1
- src/components/Connections.vue: 457 lines of code src/components/Connections.vue:1
- src/components/OperateItem.vue: 440 lines of code src/components/OperateItem.vue:1
- src/components/ConnectionMenu.vue: 407 lines of code src/components/ConnectionMenu.vue:1
- src/components/contents/KeyContentStream.vue: 404 lines of code src/components/contents/KeyContentStream.vue:1
- src/components/Tabs.vue: 403 lines of code src/components/Tabs.vue:1
- src/components/CliTab.vue: 401 lines of code src/components/CliTab.vue:1
- Test Coverage
- No test or typecheck script
- Dead file (~522 LoC) src/components/contents/KeyContentVector.vue
- Dead file (~495 LoC) src/components/NewConnectionDialog.vue
- Dead file (~437 LoC) src/components/CliTab.vue
- Dead file (~433 LoC) src/components/contents/KeyContentStream.vue
- Dead file (~432 LoC) src/components/KeyListVirtualTree.vue
- Dead file (~411 LoC) src/components/OperateItem.vue
- Dead file (~395 LoC) src/components/Status.vue
- Dead file (~389 LoC) src/components/contents/KeyContentTimeSeries.vue
- Dead file (~380 LoC) src/redisClient.js
- Dead file (~339 LoC) src/components/contents/KeyContentHash.vue
- Dead file (~333 LoC) src/components/KeyList.vue
- Dead file (~331 LoC) src/components/Connections.vue
- Dead file (~327 LoC) src/components/contents/KeyContentZset.vue
- Dead file (~323 LoC) src/components/contents/KeyContentArray.vue
- Dead file (~309 LoC) src/components/Setting.vue
- Dead file (~294 LoC) src/components/contents/KeyContentList.vue
- Dead file (~282 LoC) src/components/contents/KeyContentSet.vue
- Dead file (~258 LoC) src/components/viewers/ViewerProtobuf.vue
- Dead file (~256 LoC) src/components/FormatViewer.vue
- Dead file (~242 LoC) src/commands.js
- Dead file (~225 LoC) src/components/ConnectionWrapper.vue
- Dead file (~223 LoC) src/components/DeleteBatch.vue
- Dead file (~175 LoC) src/components/CustomFormatter.vue
- Dead file (~165 LoC) src/components/SlowLog.vue
- Dead file (~156 LoC) src/components/viewers/ViewerCustom.vue
- Dead file (~152 LoC) src/components/JsonEditor.vue
- Dead file (~148 LoC) src/components/UpdateCheck.vue
- Dead file (~110 LoC) src/components/KeyDetail.vue
- Dead file (~107 LoC) src/components/CommandLog.vue
- Dead file (~101 LoC) src/components/contents/KeyContentString.vue
- Dead file (~100 LoC) src/components/contents/KeyContentReJson.vue
- Dead file (~94 LoC) src/components/CliContent.vue
- Dead file (~85 LoC) src/components/ScrollToTop.vue
- Dead file (~83 LoC) src/Aside.vue
- Dead file (~70 LoC) config/index.js
- Unused dependency 'element-theme-chalk'
- Unused dependency 'js-yaml'
- JavaScript dependencies are not locked pack/electron/package.json:8
- Untrusted text written into markup unescaped src/components/Setting.vue:52
Minor — 43 finding(s)
- Deprecated: asar REDACTED:2738
- Deprecated: browserslist REDACTED:5298
- Deprecated: browserslist REDACTED:5809
- Deprecated: core-js REDACTED:6711
- Deprecated: svgo REDACTED:7944
- Deprecated: browserslist REDACTED:8051
- Deprecated: electron-osx-sign REDACTED:9178
- Deprecated: debug REDACTED:9803
- Deprecated: flatten REDACTED:10583
- Deprecated: browserslist REDACTED:15895
- Deprecated: querystring REDACTED:17722
- Deprecated: resolve-url REDACTED:18421
- Deprecated: uuid REDACTED:19172
- Deprecated: source-map-resolve REDACTED:19214
- Deprecated: source-map-url REDACTED:19238
- Deprecated: stable REDACTED:19411
- Deprecated: svgo REDACTED:19798
- Deprecated: urix REDACTED:21089
- Deprecated: uuid REDACTED:21220
- Deprecated: debug REDACTED:21301
- Deprecated: fsevents REDACTED:21527
- Deprecated: fsevents REDACTED:22055
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- redundant comment REDACTED:55
- redundant comment REDACTED:58
- redundant comment src/redisClient.js:134
- Outdated (npm): vue-i18n package.json:48
- No ADRs found package.json:8
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- No SAST
- No dependency-update automation package.json:28
- No changelog
Minor — 12 finding(s)
- Outdated (npm): element-ui
- Outdated (npm): ioredis
- Outdated (npm): java-object-serialization
- Outdated (npm): monaco-editor
- Outdated (npm): php-serialize
- Outdated (npm): protobufjs
- Outdated (npm): rawproto
- Outdated (npm): sortablejs
- Outdated (npm): tunnel-ssh
- Outdated (npm): vue
- Outdated (npm): vxe-table
- doc comments repeat the names config/index.js:50
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-24a5337b14e44779bc83181c31160dd3/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-24a5337b14e44779bc83181c31160dd3/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 . | 29 | 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/** . | 96 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| 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 |