Public report of thebaselab/codeapp, published 14 November 2026. It has the same score, grades and number of findings as the full report. The details of security findings (where they are in the code, which known vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive report Measured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey → Signed and filed in the standard's public register, 14 November 2026, 22:37 UTC · Survey ID cd_50929a2a72a0445396bdabb6f10a55f6

thebaselab/codeapp

Measured 14 November 2026, 22:36 UTC, at code version ef33ee5

Test reliability is not measured: The suite could not be re-run, but the repository declares tests of its own unreliable.

Supply-chain provenance & signing is not measured: Supply-chain provenance is not scored (this pipeline releases no artifact), but its build steps or GitHub Actions workflows have integrity defects, or nothing watches its dependency set for published advisories.

CAI score 46out of 100 At risk Up 1 since the last survey

The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.

A medium codebase: 23,365 lines of product code in 4 projects, tests not counted · Estimated rebuild effort: about 0.2 person-years · Weakest lens: Accessibility, 24

Findings by how serious they are

37 critical 235 serious 40 minor

17 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.

This survey was produced by

Assert small markCanine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
14 November 2026, 22:36 UTC

A measurement, not a certificate. The Code Assurance Index records a number together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that implements it, and today the Canine Code Analyzer is the only one that does.

A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.

The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸

43of 43 dimensions measured by tools.
289of 312 findings point to an exact file and line, so you can open each one in the code. The other 23 concern the repository as a whole, such as missing documentation.
43dimensions across 7 lenses, read from 23,365 lines of product code in 4 projects.
Chapters

Executive summary

thebaselab/codeapp 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 pages that don't say their language. It scores 46 out of 100, which the At risk rating leaves unchanged.

Accessibility, at 24, is the weakest lens and counts most in the score. The best first step is fixing focus, motion and contrast, worth about 12 points. Fixing the password or key in the code comes next, worth about 4 points. Raising Accessibility to 70 would lift the score to about 63.

Nineteen known security holes in the packages the code depends on can be used by attackers. Four pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and two images have no description for people who can't see them. Updating the vulnerable packages, pinning each tool to an exact version and describing the images would close these risks. The five pages that don't say their language need their language set.

The product code is 23,365 lines, about €22,000 to rebuild.

A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.

How the score is built: what each lens counts for The lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
Accessibility 24 · counts for 46%Production Readiness 53 · counts for 25%Maturity 64 · counts for 14%Code Health 72 · counts for 8%Architecture 89 · counts for 4%Security and Compliance 98 · counts for 2%Performance 100 · counts for 1%

If Accessibility rose from 24 to 70, the lowest score rated Strong, the score would rise from 46 to about 63.

Code composition: what the lines of code are
Product code 93%Tests 7%
New since the last survey: 61 findings

These 61 critical or serious findings weren't in the previous survey, on 28 October 2026.

  • Cyclomatic Complexity · node.swift.tokenizeCommand (cyclomatic 17) CodeApp/Utilities/node.swift
  • Cyclomatic Complexity · node.swift.splitScriptLine (cyclomatic 16) CodeApp/Utilities/node.swift
  • Cognitive Complexity · node.swift.tokenizeCommand (cognitive 24) CodeApp/Utilities/node.swift
  • Cognitive Complexity · node.swift.splitScriptLine (cognitive 21) CodeApp/Utilities/node.swift
  • Cognitive Complexity · node.swift.runScriptCommand (cognitive 18) CodeApp/Utilities/node.swift
  • Code Duplication · Edited copy of a member (36 corresponding lines) CodeApp/Managers/FileSystem/SFTP/SFTPFileSystemProvider.swift
  • Code Duplication · Edited copy of a member (27 corresponding lines) SwiftGit2/SwiftGit2/Repository.swift
  • Code Duplication · Edited copy of a member (27 corresponding lines) Extensions/ImageEditor/ImageEditorExtension.swift
  • Code Duplication · Edited copy of a member (32 corresponding lines) Extensions/MonacoEditor/Views/VimKeyBufferLabel.swift
  • Code Duplication · Edited copy of a member (20 corresponding lines) CodeApp/Views/ActivityBar.swift
  • Code Duplication · Edited copy of a member (21 corresponding lines) SwiftGit2/SwiftGit2/Repository.swift
  • Code Duplication · Edited copy of a member (25 corresponding lines) CodeApp/Containers/SourceControlContainer.swift
  • Code Duplication · Edited copy of a member (27 corresponding lines) CodeApp/Containers/SourceControlContainer.swift
  • Code Duplication · Edited copy of a member (18 corresponding lines) SwiftGit2/SwiftGit2/Repository.swift
  • Code Duplication · Edited copies of one member (3 members, 19+ corresponding lines) CodeApp/Managers/FileSystem/WorkSpaceStorage.swift
  • Code Duplication · Edited copy of a member (19 corresponding lines) CodeApp/Views/SourceControlAuthenticationConfiguration.swift
  • Code Duplication · Edited copy of a member (22 corresponding lines) CodeApp/Views/SourceControlSection.swift
  • Code Duplication · Edited copy of a member (9 corresponding lines) CodeApp/Views/FileTreeView.swift
  • Code Duplication · Edited copy of a member (14 corresponding lines) SwiftGit2/SwiftGit2/Repository.swift
  • Code Duplication · Edited copy of a member (9 corresponding lines) SwiftGit2/SwiftGit2/Repository.swift
  • Code Duplication · Edited copies of one member (3 members, 17+ corresponding lines) CodeApp/Containers/SourceControlContainer.swift
  • Code Duplication · Edited copy of a member (13 corresponding lines) SwiftGit2/SwiftGit2/Repository.swift
  • Code Duplication · Edited copy of a member (12 corresponding lines) SwiftGit2/SwiftGit2/Repository.swift
  • Code Duplication · Edited copy of a member (10 corresponding lines) SwiftGit2/SwiftGit2/Repository.swift
  • Code Duplication · Edited copies of one member (3 members, 13+ corresponding lines) CodeApp/Managers/FileSystem/WorkSpaceStorage.swift
  • Code Duplication · Edited copy of a member (13 corresponding lines) CodeApp/Managers/FileSystem/SFTP/SFTPFileSystemProvider.swift
  • Code Duplication · Edited copy of a member (18 corresponding lines) CodeApp/Utilities/KeychainWrapper/KeychainWrapper.swift
  • Code Duplication · Edited copy of a member (22 corresponding lines) CodeApp/Managers/EditorImplementation/MonacoImplementation.swift
  • Code Duplication · Edited copy of a member (9 corresponding lines) CodeApp/Managers/FileSystem/Local/LocalGitCredentialsHelper.swift
  • Code Duplication · Edited copies of one member (4 members, 8+ corresponding lines) CodeApp/Managers/NotificationManager.swift
  • Code Duplication · Edited copies of one member (3 members, 10+ corresponding lines) CodeApp/Managers/FileSystem/Local/LocalGitServiceProvider.swift
  • Code Duplication · Edited copy of a member (12 corresponding lines) CodeApp/Managers/TerminalInstance.swift
  • Code Duplication · Edited copy of a member (11 corresponding lines) SwiftGit2/SwiftGit2/Repository.swift
  • Code Duplication · Edited copy of a member (16 corresponding lines) Extensions/ImageEditor/ImageEditorExtension.swift
  • Code Duplication · Edited copy of a member (13 corresponding lines) CodeApp/Types/EditorInstance.swift
  • Code Duplication · Edited copies of one member (3 members, 7+ corresponding lines) SwiftGit2/SwiftGit2/Repository.swift
  • Code Duplication · Edited copy of a member (6 corresponding lines) CodeApp/Containers/ExplorerContainer.swift
  • Code Duplication · Edited copy of a member (15 corresponding lines) CodeApp/Containers/SourceControlContainer.swift
  • Code Duplication · Edited copies of one member (3 members, 11+ corresponding lines) CodeApp/Views/SourceControlAuthenticationConfiguration.swift
  • Code Duplication · Edited copies of one member (3 members, 10+ corresponding lines) CodeApp/Managers/FileSystem/SFTP/SFTPFileSystemProvider.swift
  • Code Duplication · Edited copy of a member (13 corresponding lines) CodeApp/Containers/SourceControlContainer.swift
  • Code Duplication · Edited copy of a member (9 corresponding lines) CodeApp/Managers/FileSystem/Local/LocalFileSystemProvider.swift
  • Code Duplication · Edited copies of one member (6 members, 11+ corresponding lines) CodeApp/Managers/FileSystem/WorkSpaceStorage.swift
  • Code Duplication · Edited copy of a member (8 corresponding lines) Extensions/MonacoLanguageService/MonacoIntellisenseExtension.swift
  • Code Duplication · Edited copy of a member (9 corresponding lines) CodeApp/Views/DocumentPickerView.swift
  • Code Duplication · Edited copy of a member (6 corresponding lines) CodeApp/Views/EditorTab.swift
  • Code Duplication · Duplicated block (13 lines × 2) Extensions/ImageEditor/ImageEditorExtension.swift
  • Code Duplication · Duplicated block (6 lines × 2) CodeApp/Managers/FileSystem/WorkSpaceStorage.swift
  • Code Duplication · Duplicated block (5 lines × 2) CodeApp/Views/ActivityBar.swift
  • Dependency Vulnerabilities · REDACTED
  • Visual & motion safety · Low contrast colour pair in CSS (4.4:1) LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css
  • Visual & motion safety · Low contrast colour pair in CSS (1.4:1) LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css
  • Visual & motion safety · Low contrast colour pair in CSS (2.7:1) LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css
  • Visual & motion safety · Low contrast colour pair in CSS (1.4:1) LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css
  • Visual & motion safety · Low contrast colour pair in CSS (4.2:1) LanguageResources/Library/share/jupyter/nbconvert/templates/classic/static/style.css
  • Visual & motion safety · Low contrast colour pair in CSS (4.1:1) LanguageResources/Library/share/jupyter/nbconvert/templates/classic/static/style.css
  • Visual & motion safety · Low contrast colour pair in CSS (4.3:1) LanguageResources/Library/share/jupyter/nbconvert/templates/classic/static/style.css
  • Visual & motion safety · Low contrast colour pair in CSS (3.9:1) LanguageResources/Library/share/jupyter/nbconvert/templates/classic/static/style.css
  • Visual & motion safety · Low contrast colour pair in CSS (3.3:1) LanguageResources/Library/share/jupyter/nbconvert/templates/classic/static/style.css
  • Visual & motion safety · Low contrast colour pair in CSS (2.8:1) LanguageResources/Library/share/jupyter/nbconvert/templates/classic/static/style.css
  • Visual & motion safety · Low contrast colour pair in CSS (4.3:1) LanguageResources/Library/lib/python3.9/site-packages/docutils/writers/s5_html/themes/default/pretty.css

We compare every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.

Fixed since the last survey: 117 findings

These 117 critical or serious findings were in the previous survey, on 28 October 2026, and are gone from this one. The first 100 are listed here.

  • Cyclomatic Complexity · node.swift.npm (cyclomatic 23) CodeApp/Utilities/node.swift
  • Cognitive Complexity · node.swift.npm (cognitive 86) CodeApp/Utilities/node.swift
  • Code Duplication · Edited copy of a member (36 corresponding lines) CodeApp/Managers/FileSystem/SFTP/SFTPFileSystemProvider.swift
  • Code Duplication · Duplicated block (13 lines × 2) Extensions/ImageEditor/ImageEditorExtension.swift
  • Code Duplication · Duplicated block (8–11 lines × 2) CodeApp/Utilities/node.swift
  • Code Duplication · Duplicated block (8 lines × 2) CodeApp/Views/SourceControlSection.swift
  • Code Duplication · Duplicated block (6 lines × 4) CodeApp/Utilities/node.swift
  • Code Duplication · Duplicated block (6 lines × 2) CodeApp/Managers/FileSystem/WorkSpaceStorage.swift
  • Code Duplication · Duplicated block (5 lines × 2) CodeApp/Views/ActivityBar.swift
  • Code Duplication · Duplicated block (9 lines × 2) CodeApp/Views/SearchUnsupportedSection.swift
  • Code Duplication · Duplicated block (5 lines × 2) CodeApp/Managers/TerminalInstance.swift
  • Explicit Debt · TodoComment SwiftGit2/SwiftGit2/Repository.swift
  • Explicit Debt · FixmeComment SwiftGit2/SwiftGit2/Repository.swift
  • Secrets (history) · High secret: WD-SECRET-0005 CodeApp/Framework/MarkdownView/webassets/package-lock.json
  • Secrets (history) · Secret: http-basic-credential Library/lib/python3.9/site-packages/Cython/Compiler/ParseTreeTransforms.py
  • Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
  • Supply-chain Provenance & Signing · Unpinned build actions
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement LanguageResources/Library/share/jupyter/nbconvert/templates/classic/static/style.css
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement LanguageResources/Library/share/jupyter/nbconvert/templates/classic/static/style.css
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement LanguageResources/Library/share/jupyter/nbconvert/templates/classic/static/style.css
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement LanguageResources/Library/share/jupyter/nbconvert/templates/classic/static/style.css
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement LanguageResources/Library/share/jupyter/nbconvert/templates/classic/static/style.css
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement LanguageResources/Library/share/jupyter/nbconvert/templates/classic/static/style.css
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement LanguageResources/Library/share/jupyter/nbconvert/templates/classic/static/style.css
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement LanguageResources/Library/share/jupyter/nbconvert/templates/classic/static/style.css
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement LanguageResources/Library/share/jupyter/nbconvert/templates/classic/static/style.css
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement LanguageResources/Library/share/jupyter/nbconvert/templates/classic/static/style.css
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement LanguageResources/Library/share/jupyter/nbconvert/templates/classic/static/style.css
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement LanguageResources/Library/share/jupyter/nbconvert/templates/classic/static/style.css
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement LanguageResources/Library/share/jupyter/nbconvert/templates/classic/static/style.css
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement LanguageResources/Library/share/jupyter/nbconvert/templates/classic/static/style.css
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement LanguageResources/Library/share/jupyter/nbconvert/templates/classic/static/style.css
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement Dependencies/terminal.bundle/xterm.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css
Rebuild cost: about €22,000 · Estimate
Cost to rebuild€7,400 to €37,000, for 124 to 393 hours of work, about 0.2 person-years for one engineer
Difficulty of the problemStandard, 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 46. 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.
SizeMedium: 23,365 lines of product code
What it is notNot 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.

How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.

Top priorities

The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.

1
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.
Raises the score by about 12 points · Medium effort · Visual & motion safety
2
Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED.
Raises the score by about 4 points · Low effort · Secret Scanning
3
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Raises the score by about 9 points · Medium effort · Page structure

Diagnosis: what the measurements show together

Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.

Where the investment is most exposed · Value at risk
This code would cost about €22,000 to build again, about 0.2 person-years of work. Its weakest lens is Accessibility, at 24 (Critical). Accessibility is about whether the interface is built so that everyone can use it, including people who can't see the screen or can't use a mouse. Because the weakest lens counts most in the score, work on Accessibility also moves the score most.
Based on: the rebuild estimate · the Accessibility grade · how much each lens counts
What to do: Start with the Accessibility actions in Top priorities.
If you do one thing first · First action
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. Of all the actions in this report, it raises the score most for the work it takes: about 12 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 6.7 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 3% to 7% on every change. The history of the code shows how much it changes: about 2,343 lines over the last 90 days, which is about 9,502 lines a year. At that pace, the extra work comes to an estimated 0.8 to 4.6 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.

Architecture — module dependency graph

Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.

arch SwiftGit2 SwiftGit2 SwiftWS SwiftWS extension extension extension->SwiftWS testfield testfield testfield->SwiftGit2

Architecture: which parts of the code depend on which

The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.

605 modules, with 37 dependencies between them. Every module uses only modules listed above it, so there are no loops.

The table shows the 40 modules with the most connections; 565 more are left out to keep it readable.

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →1 Dependencies2 LanguageResources.Library.lib.python3.9.asyncore3 LanguageResources.Library.lib.python3.9.idlelib.delegator4 LanguageResources.Library.lib.python3.9.idlelib.editor5 LanguageResources.Library.lib.python3.9.idlelib.filelist6 LanguageResources.Library.lib.python3.9.idlelib.rpc7 LanguageResources.Library.lib.python3.9.idlelib.scrolledlist8 LanguageResources.Library.lib.python3.9.idlelib.searchbase9 LanguageResources.Library.lib.python3.9.idlelib.tooltip10 LanguageResources.Library.lib.python3.9.idlelib.tree11 LanguageResources.Library.lib.python3.9.tkinter12 LanguageResources.Library.lib.python3.9.tkinter.ttk13 SwiftWS~SwiftWS14 LanguageResources.Library.lib.python3.9.asynchat15 LanguageResources.Library.lib.python3.9.idlelib.browser16 LanguageResources.Library.lib.python3.9.idlelib.calltip_w17 LanguageResources.Library.lib.python3.9.idlelib.colorizer18 LanguageResources.Library.lib.python3.9.idlelib.config_key19 LanguageResources.Library.lib.python3.9.idlelib.configdialog20 LanguageResources.Library.lib.python3.9.idlelib.debugger21 LanguageResources.Library.lib.python3.9.idlelib.debugobj22 LanguageResources.Library.lib.python3.9.idlelib.dynoption23 LanguageResources.Library.lib.python3.9.idlelib.grep24 LanguageResources.Library.lib.python3.9.idlelib.help25 LanguageResources.Library.lib.python3.9.idlelib.help_about26 LanguageResources.Library.lib.python3.9.idlelib.outwin27 LanguageResources.Library.lib.python3.9.idlelib.query28 LanguageResources.Library.lib.python3.9.idlelib.replace29 LanguageResources.Library.lib.python3.9.idlelib.run30 LanguageResources.Library.lib.python3.9.idlelib.search31 LanguageResources.Library.lib.python3.9.idlelib.sidebar32 LanguageResources.Library.lib.python3.9.idlelib.squeezer33 LanguageResources.Library.lib.python3.9.idlelib.statusbar34 LanguageResources.Library.lib.python3.9.idlelib.textview35 LanguageResources.Library.lib.python3.9.idlelib.undo36 LanguageResources.Library.lib.python3.9.idlelib.window37 repository38 LanguageResources.Library.lib.python3.9.idlelib.pathbrowser39 LanguageResources.Library.lib.python3.9.idlelib.pyshell40 LanguageResources.Library.lib.python3.9.idlelib.stackviewer
1 Dependencies
2 LanguageResources.Library.lib.python3.9.asyncore
3 LanguageResources.Library.lib.python3.9.idlelib.delegator
4 LanguageResources.Library.lib.python3.9.idlelib.editor
5 LanguageResources.Library.lib.python3.9.idlelib.filelist
6 LanguageResources.Library.lib.python3.9.idlelib.rpc
7 LanguageResources.Library.lib.python3.9.idlelib.scrolledlist
8 LanguageResources.Library.lib.python3.9.idlelib.searchbase
9 LanguageResources.Library.lib.python3.9.idlelib.tooltip
10 LanguageResources.Library.lib.python3.9.idlelib.tree
11 LanguageResources.Library.lib.python3.9.tkinter
12 LanguageResources.Library.lib.python3.9.tkinter.ttk
13 SwiftWS~SwiftWS
14 LanguageResources.Library.lib.python3.9.asynchat1
15 LanguageResources.Library.lib.python3.9.idlelib.browser2
16 LanguageResources.Library.lib.python3.9.idlelib.calltip_w1
17 LanguageResources.Library.lib.python3.9.idlelib.colorizer1
18 LanguageResources.Library.lib.python3.9.idlelib.config_key1
19 LanguageResources.Library.lib.python3.9.idlelib.configdialog15
20 LanguageResources.Library.lib.python3.9.idlelib.debugger1
21 LanguageResources.Library.lib.python3.9.idlelib.debugobj1
22 LanguageResources.Library.lib.python3.9.idlelib.dynoption1
23 LanguageResources.Library.lib.python3.9.idlelib.grep1
24 LanguageResources.Library.lib.python3.9.idlelib.help21
25 LanguageResources.Library.lib.python3.9.idlelib.help_about1
26 LanguageResources.Library.lib.python3.9.idlelib.outwin1
27 LanguageResources.Library.lib.python3.9.idlelib.query1
28 LanguageResources.Library.lib.python3.9.idlelib.replace1
29 LanguageResources.Library.lib.python3.9.idlelib.run2
30 LanguageResources.Library.lib.python3.9.idlelib.search1
31 LanguageResources.Library.lib.python3.9.idlelib.sidebar1
32 LanguageResources.Library.lib.python3.9.idlelib.squeezer1
33 LanguageResources.Library.lib.python3.9.idlelib.statusbar1
34 LanguageResources.Library.lib.python3.9.idlelib.textview13
35 LanguageResources.Library.lib.python3.9.idlelib.undo1
36 LanguageResources.Library.lib.python3.9.idlelib.window1
37 repository2
38 LanguageResources.Library.lib.python3.9.idlelib.pathbrowser21
39 LanguageResources.Library.lib.python3.9.idlelib.pyshell111111
40 LanguageResources.Library.lib.python3.9.idlelib.stackviewer21
Uses a module listed above itPart of a loopThe module itself
1 Dependencies2 LanguageResources.Library.lib.python3.9.asyncore3 LanguageResources.Library.lib.python3.9.idlelib.delegator4 LanguageResources.Library.lib.python3.9.idlelib.editor5 LanguageResources.Library.lib.python3.9.idlelib.filelist6 LanguageResources.Library.lib.python3.9.idlelib.rpc7 LanguageResources.Library.lib.python3.9.idlelib.scrolledlist8 LanguageResources.Library.lib.python3.9.idlelib.searchbase9 LanguageResources.Library.lib.python3.9.idlelib.tooltip10 LanguageResources.Library.lib.python3.9.idlelib.tree11 LanguageResources.Library.lib.python3.9.tkinter12 LanguageResources.Library.lib.python3.9.tkinter.ttk13 SwiftWS~SwiftWS14 LanguageResources.Library.lib.python3.9.asynchat15 LanguageResources.Library.lib.python3.9.idlelib.browser16 LanguageResources.Library.lib.python3.9.idlelib.calltip_w17 LanguageResources.Library.lib.python3.9.idlelib.colorizer18 LanguageResources.Library.lib.python3.9.idlelib.config_key19 LanguageResources.Library.lib.python3.9.idlelib.configdialog20 LanguageResources.Library.lib.python3.9.idlelib.debugger21 LanguageResources.Library.lib.python3.9.idlelib.debugobj22 LanguageResources.Library.lib.python3.9.idlelib.dynoption23 LanguageResources.Library.lib.python3.9.idlelib.grep24 LanguageResources.Library.lib.python3.9.idlelib.help25 LanguageResources.Library.lib.python3.9.idlelib.help_about26 LanguageResources.Library.lib.python3.9.idlelib.outwin27 LanguageResources.Library.lib.python3.9.idlelib.query28 LanguageResources.Library.lib.python3.9.idlelib.replace29 LanguageResources.Library.lib.python3.9.idlelib.run30 LanguageResources.Library.lib.python3.9.idlelib.search31 LanguageResources.Library.lib.python3.9.idlelib.sidebar32 LanguageResources.Library.lib.python3.9.idlelib.squeezer33 LanguageResources.Library.lib.python3.9.idlelib.statusbar34 LanguageResources.Library.lib.python3.9.idlelib.textview35 LanguageResources.Library.lib.python3.9.idlelib.undo36 LanguageResources.Library.lib.python3.9.idlelib.window37 repository38 LanguageResources.Library.lib.python3.9.idlelib.pathbrowser39 LanguageResources.Library.lib.python3.9.idlelib.pyshell40 LanguageResources.Library.lib.python3.9.idlelib.stackviewerDependencies1LanguageResources.Library.lib.python3.9.asyncore2LanguageResources.Library.lib.python3.9.idlelib.delegator3LanguageResources.Library.lib.python3.9.idlelib.editor4LanguageResources.Library.lib.python3.9.idlelib.filelist5LanguageResources.Library.lib.python3.9.idlelib.rpc6LanguageResources.Library.lib.python3.9.idlelib.scrolledlist7LanguageResources.Library.lib.python3.9.idlelib.searchbase8LanguageResources.Library.lib.python3.9.idlelib.tooltip9LanguageResources.Library.lib.python3.9.idlelib.tree10LanguageResources.Library.lib.python3.9.tkinter11LanguageResources.Library.lib.python3.9.tkinter.ttk12SwiftWS~SwiftWS13LanguageResources.Library.lib.python3.9.asynchat14LanguageResources.Library.lib.python3.9.idlelib.browser15LanguageResources.Library.lib.python3.9.idlelib.calltip_w16LanguageResources.Library.lib.python3.9.idlelib.colorizer17LanguageResources.Library.lib.python3.9.idlelib.config_key18LanguageResources.Library.lib.python3.9.idlelib.configdialog19LanguageResources.Library.lib.python3.9.idlelib.debugger20LanguageResources.Library.lib.python3.9.idlelib.debugobj21LanguageResources.Library.lib.python3.9.idlelib.dynoption22LanguageResources.Library.lib.python3.9.idlelib.grep23LanguageResources.Library.lib.python3.9.idlelib.help24LanguageResources.Library.lib.python3.9.idlelib.help_about25LanguageResources.Library.lib.python3.9.idlelib.outwin26LanguageResources.Library.lib.python3.9.idlelib.query27LanguageResources.Library.lib.python3.9.idlelib.replace28LanguageResources.Library.lib.python3.9.idlelib.run29LanguageResources.Library.lib.python3.9.idlelib.search30LanguageResources.Library.lib.python3.9.idlelib.sidebar31LanguageResources.Library.lib.python3.9.idlelib.squeezer32LanguageResources.Library.lib.python3.9.idlelib.statusbar33LanguageResources.Library.lib.python3.9.idlelib.textview34LanguageResources.Library.lib.python3.9.idlelib.undo35LanguageResources.Library.lib.python3.9.idlelib.window36repository37LanguageResources.Library.lib.python3.9.idlelib.pathbrowser38LanguageResources.Library.lib.python3.9.idlelib.pyshell39LanguageResources.Library.lib.python3.9.idlelib.stackviewer401211115111121111121111131122111111121+565 more modules (most-connected shown)

At a glance — Code Health · 72% · Strong ·

At a glance — Architecture · 89% · Adequate · gated by D26 ·

At a glance — Maturity · 64% · Adequate · gated by M2 ·

At a glance — Readiness · 53% · Adequate · gated by P3 ·

At a glance — Security · 98% · Exemplary ·

At a glance — Accessibility · 24% · Critical · gated by AC3, AC6 ·

At a glance — Performance · 100% · Exemplary ·

Security & Compliance — OWASP Top-10 mapping

Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).

OWASP categoryFindingsSeverity
A03:2025 — Software Supply Chain Failures29High / Critical
A05:2025 — Injection5High / Critical
A07:2025 — Authentication Failures1High / Critical

Roadmap

Top priorities: 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; Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh; Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.

Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.

Do thisHelpsEffortDimension
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.+12.1 ptsMediumVisual & motion safety
Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED.+4.3 ptsLowSecret Scanning
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.+8.5 ptsMediumPage structure
Resolve the 1 Assertions commented out finding(s) in Test Quality — start with SwiftWSTests.swift.+4.0 ptsLowTest Quality
Resolve the 1 Test project verifies nothing finding(s) in Test Quality — start with SwiftWSTests.swift.+4.0 ptsLowTest Quality
Resolve the 5 Floating branch dependency finding(s) in Dependency Hygiene.+3.3 ptsLowDependency Hygiene
Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.+6.3 ptsMediumText alternatives
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with project.pbxproj.+2.8 ptsLowADR Quality

File quality

Per-file score 0–10 — a quality signature. Of 60 files carrying findings, judged against the Production bar: 5% slop · 62% mixed · 33% near-clean.

FileScoreBandWorst signal
REDACTED0.0SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED1.3SlopDependency Vulnerabilities: High CVE: REDACTED
REDACTED2.7SlopStatic Analysis (SAST): High: REDACTED
REDACTED5.1MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.1MixedStatic Analysis (SAST): High: REDACTED
CodeApp/Views/ExplorerFileTreeSection.swift5.6MixedCyclomatic Complexity: ExplorerFileTree.buildContextMenu (cyclomatic 20)
CodeApp/Managers/EditorImplementation/RunestoneImplementation.swift5.9MixedCyclomatic Complexity: RunestoneImplementation.detectLangauge (cyclomatic 38)
CodeApp/Views/EditorView.swift6.0MixedExplicit Debt: TodoComment
SwiftGit2/SwiftGit2/Repository.swift6.0MixedExplicit Debt: TodoComment
CodeApp/Views/SettingsView.swift6.0MixedExplicit Debt: TodoComment
CodeApp/Managers/MainApp.swift6.0MixedExplicit Debt: TodoComment
CodeApp/Managers/FileSystem/SFTP/SFTPFileSystemProvider.swift6.0MixedExplicit Debt: TodoComment
Extensions/ImageEditor/ImageEditorExtension.swift6.0MixedExplicit Debt: TodoComment
CodeApp/Managers/FileSystem/Local/LocalGitCredentialsHelper.swift6.0MixedExplicit Debt: TodoComment
CodeApp/Views/EditorTab.swift6.0MixedExplicit Debt: TodoComment
CodeApp/Views/FileTreeView.swift6.3MixedCognitive Complexity: TableViewDelegate.tableView (cognitive 22)
CodeApp/Managers/FileSystem/Local/LocalFileSystemProvider.swift7.0MixedCode Duplication: Edited copy of a member (9 corresponding lines)
SwiftWS/Tests/SwiftWSTests/SwiftWSTests.swift7.0MixedTest Quality: Assertions commented out: testExample
CodeApp/Utilities/wasm.swift7.0MixedCyclomatic Complexity: wasmWebViewDelegate.webView (cyclomatic 88)
CodeApp/Managers/TerminalInstance.swift7.0MixedCyclomatic Complexity: TerminalInstance.userContentController (cyclomatic 44)

How the grades work

Every finding carries one of four grades. Three say how serious it is. The fourth says this survey could not settle it — and it is a grade, not a gap.

Critical — 37

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.

Serious — 235

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.

Minor — 40

Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.

Could not be resolved — 17

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 43 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.

Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.

What we checked — 43 dimensions across the health lenses
D1D2D3D4D5D6D10D12D13D14D15D17D20D21D26D27D28D29D30D34D35D43D44AC1AC3AC6AX10AX3AX4AX8AX9M1M2M3P1P10P2P3P4P6PF3X28X3

Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.

How to trust any code-health report — three questions
  1. 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, 289 of 312 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
  2. Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
  3. Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.

This report answers yes to all three. That's the bar to hold any assessment to.

Tools & methods

The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.

MethodBacksVersionEvaluator
Roslyn static analysisComplexity, cohesion, coupling, dead code, API surface, layering5.3.0✓ deterministic
Native secret scannerHardcoded secrets / credentials1.0.0✓ deterministic
Canine Code Analyzer duplication detector (in-process)Code duplication1.0.0✓ deterministic
Coverage (coverlet / dotnet-coverage)Line & branch coverage10.0.400✓ deterministic
NuGet / dotnetOutdated, vulnerable & deprecated dependencies10.0.400✓ deterministic
git / LibGit2SharpChurn hotspots, knowledge concentration, history2.43.0 · 0.31.0✓ deterministic
gitleaks · semgrep · trivySecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3✓ deterministic

Every finding is locatable in findings.md. Run 01a1dc34-516c-7083-8d73-123228266ba1.

The exact command behind every deep-scan dimension — tool, version, invocation and retained raw output — is in Appendix B — Reproduction & audit trail.

Run transparency — what happened this run

What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.

  • D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the Swift half could not be measured — the Swift suite in SwiftGit2 produced no coverage export. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo.
  • D11 Test Reliability — 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 repository declares 1 of its own test(s) unreliable. The built-in reliability runner does not support this repository's ecosystem (.swift), so the suite was not re-run and no reliability score is given — these are the repository's own declarations, not our measurement.
  • D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Swift Package.swift/Package.resolved, but the licence verdict published here was taken over its gem dependencies. Nothing was read about its SwiftPM dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
  • D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (17 contributor(s) across 878 commit(s) sampled, automation and bot accounts excluded). One of them holds 96% of the history; the other 16 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.
  • D19 Documentation Quality — 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 kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
  • D21 Naming Consistency — 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. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
  • D21 Naming Consistency — 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. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
  • D21 Naming Consistency — 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. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these 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's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
  • D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
  • D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `CodeApp/Managers/AppExtensionService.swift`, `CodeApp/Managers/FileSystem/Local/LocalGitCredentialsHelper.swift`, `CodeApp/Managers/FileSystem/WorkSpaceStorage.swift`, `CodeApp/Managers/SearchManager.swift`, `CodeApp/Managers/TerminalInstance.swift`, … (+1 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
  • 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. 99 further occurrence(s) are not listed individually; the score already reflects all 139.
  • AX1 Captive dependencies — 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 Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository defines its own container in CodeApp/Managers/FileSystem/SFTP/SFTPTerminalServiceProvider.swift, whose lifetimes are not modelled 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.
  • 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.
  • AXB1 Runtime evidence locked — no reproducible boot — 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. Subject: 11 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
  • C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
  • C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
  • C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
  • 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 Swift, c, groovy, objectivec 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 Swift, c, groovy, objectivec 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.
  • P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
  • S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
  • 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.
  • X27 Collection changed while being enumerated — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded, no Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala or Kotlin was found, and this repository's Groovy, Objective-C, Swift (Foundation mutable collections) 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.
  • 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 C, Groovy, Objectivec, Swift 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.

Repo exclusion declarations: 10 pattern(s) declared (.gitattributes linguist-generated/vendored, .editorconfig generated_code) excluded 0 source file(s) from code-quality scoring. Declarations are the repo's own visible statement that a tree is machine-written or vendored — auditable in any diff, honored by GitHub the same way.

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

For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
  • D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
  • D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • 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.
  • D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
  • D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
  • 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.
  • AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
  • 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.
  • AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
  • AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
  • AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
  • 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 Complexity7.0 / 10Strong✓ Tool-verified

What it measures: How tangled the control flow is — methods with many branches are hard to test and change.

Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.

Maturity: Documented → Verified → Prevented · effective 7.0 / 10 · rule-coverage 100% · ceiling Prevented

14 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was wasmWebViewDelegate.webView at 88.

wasmWebViewDelegate.webView (cyclomatic 88)CodeApp/Utilities/wasm.swift:63
TerminalInstance.userContentController (cyclomatic 44)CodeApp/Managers/TerminalInstance.swift:237
RunestoneImplementation.detectLangauge (cyclomatic 38)CodeApp/Managers/EditorImplementation/RunestoneImplementation.swift:415
CodeApp.swift.createCSDK (cyclomatic 22)CodeApp/CodeApp.swift:85
wasm.swift.executeWebAssembly (cyclomatic 21)CodeApp/Utilities/wasm.swift:550

+ 9 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Bring the 1 body over 60 down to 60 or less in Cyclomatic Complexity — start with wasmWebViewDelegate.webView (cyclomatic 88). — Refactoring it lifts Cyclomatic Complexity from 7.0 to about 7.4/10.

Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.

D2 · Cognitive Complexity5.0 / 10Adequate✓ Tool-verified

What it measures: How hard the code is for a person to follow, beyond raw branching.

Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.

Maturity: Documented → Verified → Prevented · effective 5.0 / 10 · rule-coverage 100% · ceiling Prevented

23 method(s) exceeded the cognitive complexity threshold of 15; the worst was wasmWebViewDelegate.webView at 299.

wasmWebViewDelegate.webView (cognitive 299)CodeApp/Utilities/wasm.swift:63
TerminalInstance.userContentController (cognitive 63)CodeApp/Managers/TerminalInstance.swift:237
CodeApp.swift.createCSDK (cognitive 41)CodeApp/CodeApp.swift:85
RunestoneImplementation.detectLangauge (cognitive 37)CodeApp/Managers/EditorImplementation/RunestoneImplementation.swift:415
wasm.swift.executeWebAssembly (cognitive 37)CodeApp/Utilities/wasm.swift:550

+ 18 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Bring the 1 body over 120 down to 120 or less in Cognitive Complexity — start with wasmWebViewDelegate.webView (cognitive 299). — Refactoring it lifts Cognitive Complexity from 5.0 to about 6.0/10.

Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.

D3 · God Classes6.6 / 10Adequate✓ Tool-verified

What it measures: Over-large classes that try to do too much ("god classes").

Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.

Maturity: Documented → Verified → Prevented · effective 6.6 / 10 · rule-coverage 100% · ceiling Prevented

22 god class(es) detected.

MethodTooLong: wasmWebViewDelegate.webView · ×10CodeApp/Utilities/wasm.swift:63
TooManyMethods: Repository · ×7SwiftGit2/SwiftGit2/Repository.swift:179
ClassTooLong: Repository · ×2SwiftGit2/SwiftGit2/Repository.swift:179
FileTooLong: SwiftGit2/Repository.swift · ×2SwiftGit2/SwiftGit2/Repository.swift
FunctionTooLong: CodeApp.swift.createCSDKCodeApp/CodeApp.swift:85

What to do

  1. Resolve the 10 MethodTooLong finding(s) in God Classes — start with wasm.swift, SettingsView.swift, TerminalInstance.swift. — One of this dimension's main actionable groups (10 warning-level).
  2. Resolve the 7 TooManyMethods finding(s) in God Classes — start with Repository.swift, MainApp.swift, MonacoImplementation.swift. — One of this dimension's main actionable groups (7 warning-level).
  3. Resolve the 2 ClassTooLong finding(s) in God Classes — start with Repository.swift, MainApp.swift. — One of this dimension's main actionable groups (2 warning-level).

Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.

D4 · Code Duplication6.8 / 10Adequate✓ Tool-verified

What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.

Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.

Maturity: Documented → Verified → Prevented · effective 6.8 / 10 · rule-coverage 100% · ceiling Verified

31 duplicated block group(s) detected. 8.0 % of the production lines (1,869 of 23,365) are in a reported copy. A further 42 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.

Edited copy of a member (13 corresponding lines) · ×5CodeApp/Managers/NotificationManager.swift:23
Edited copy of a member (9 corresponding lines) · ×5CodeApp/Views/FileTreeView.swift:213
Duplicated block (13 lines × 2) · ×5CodeApp/Managers/FileSystem/Local/LocalGitServiceProvider.swift:268
Duplicated block (5 lines × 2) · ×4CodeApp/Views/PanelView.swift:24
Edited copy of a member (27 corresponding lines) · ×3SwiftGit2/SwiftGit2/Repository.swift:73

+ 43 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Resolve the 5 Edited copy of a member (13 corresponding lines) finding(s) in Code Duplication — start with NotificationManager.swift, Repository.swift, SFTPFileSystemProvider.swift. — One of this dimension's main actionable groups (5 warning-level).
  2. Resolve the 5 Edited copy of a member (9 corresponding lines) finding(s) in Code Duplication — start with FileTreeView.swift, Repository.swift, LocalGitCredentialsHelper.swift. — One of this dimension's main actionable groups (5 warning-level).
  3. Resolve the 5 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with ImageEditorExtension.swift (2), LocalGitServiceProvider.swift, EditorKeyboardToolBar.swift. — One of this dimension's main actionable groups (5 warning-level).

Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.

D5 · Coupling6.0 / 10Adequate✓ Tool-verified

What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.

Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.

Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.

Maturity: Documented → Verified → Prevented · effective 6.0 / 10 · rule-coverage 100% · ceiling Prevented

4 production modules (SwiftPM+Xcode), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; a workspace's implicit (product-name) dependency is not visible there; 2 module(s) off the main sequence, with abstractness counted on 2 of the 4 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).

Off the main sequence: SwiftWS · ×2

What to do

  1. Resolve the 2 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (2 warning-level).

Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.

D6 · Cohesion (LCOM4)8.0 / 10Strong✓ Tool-verified

What it measures: Whether a class's methods are focused on a single responsibility.

Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.

Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.

Maturity: Documented → Verified → Prevented · effective 8.0 / 10 · rule-coverage 100% · ceiling Verified

7 of 41 classes have LCOM4 above 3.

Low cohesion: RunestoneImplementation (LCOM4 18) · ×7CodeApp/Managers/EditorImplementation/RunestoneImplementation.swift:308

What to do

  1. Resolve the 7 Low cohesion finding(s) in Cohesion (LCOM4) — start with RunestoneImplementation.swift, LocalFileSystemProvider.swift, MainApp.swift. — One of this dimension's main actionable groups (7 warning-level).

Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.

D10 · Test Quality8.2 / 10Adequategated by 2 critical findings✓ Tool-verified

What it measures: Whether the tests truly assert behaviour rather than just running the code.

Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.

Maturity: Documented → Verified → Prevented · effective 8.2 / 10 · rule-coverage 100% · ceiling Prevented

0 skipped, 1 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 17 tests.

Assertions commented out: testExampleSwiftWS/Tests/SwiftWSTests/SwiftWSTests.swift:5
Test project verifies nothing: SwiftWSTestsSwiftWS/Tests/SwiftWSTests/SwiftWSTests.swift:5

What to do

  1. Resolve the 1 Assertions commented out finding(s) in Test Quality — start with SwiftWSTests.swift. — One of this dimension's main actionable groups (1 issue-level).
  2. Resolve the 1 Test project verifies nothing finding(s) in Test Quality — start with SwiftWSTests.swift. — One of this dimension's main actionable groups (1 issue-level).

Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.

D12 · Dependency Hygiene7.8 6.3 / 10Adequate✓ Tool-verified

What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.

Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.

Maturity: Documented → Verified → Prevented · effective 6.3 / 10 · rule-coverage 80% · ceiling Verified

13 outdated direct SwiftPM dependencies, 6 pinning defect(s). 20 of 25 direct dependencies had their releases listed (0 naming no readable repository, 5 pinned to a branch or a revision rather than a version). SwiftPM has no package registry: a dependency is a repository URL and its releases are that repository's semver tags, so currency is answered by listing tags rather than by querying an index. Only a newer tag on the SAME MAJOR is reported — a `from:` requirement admits everything below the next major and nothing above it, so a major crossing needs a Package.swift edit rather than an update, and naming the update as its remedy would be wrong. Whether any dependency is DEPRECATED or ABANDONED is not graded and cannot be: a repository publishes no such marker, and there is no registry that could carry one. Known CVEs in this dependency graph are D30's question.

Floating branch dependency: libgit2-on-ios · ×5
Dependency not covered by the committed resolution: libgit2-on-ios
Outdated: cwlcatchexception · ×11

What to do

  1. Resolve the 5 Floating branch dependency finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (5 warning-level).
  2. Resolve the 1 Dependency not covered by the committed resolution finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.

D13 · Secret Scanning5.0 / 10Adequate✓ Tool-verified

What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.

Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.

Maturity: Documented → Verified → Prevented · effective 5.0 / 10 · rule-coverage 100% · ceiling Prevented

1 secret(s) detected.

REDACTED

What to do

  1. Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).

Detailed fixes: d13_recommendation.md · top locations in Appendix A, every location in findings.md.

D14 · License Compliance10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether the licenses of third-party packages are compatible with your policy.

Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

0 of 90 shipped gem(s) use a banned license. Licences were resolved from rubygems.org over the 90 gem(s) a consumer installs — this repository's runtime declarations closed transitively over its committed REDACTED. Development-group and `add_development_dependency` gems are excluded: they are not distributed with this repository. 1 of them publish no licence on rubygems.org; that is missing data, not a violation, and none of them is charged. ★ COVERAGE OF THIS VERDICT: it grades this repository's gem dependencies and nothing else. The repository also declares a Swift Package.swift/Package.resolved, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

D15 · Churn × Complexity Hotspots10.0 / 10Exemplary✓ Tool-verified

What it measures: Files that change often and are also complex — the riskiest hotspots.

Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No churn × complexity hotspots in the window.

✓ On the Gold path — maintain.

Detailed fixes: d15_recommendation.md.

D17 · Explicit Debt9.8 / 10Stronggated by 24 serious findings✓ Tool-verified

What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.

Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.

Maturity: Documented → Verified → Prevented · effective 9.8 / 10 · rule-coverage 100% · ceiling Prevented

24 deducted task-comment markers across 23365 LoC (0.1/KLoC) → score 9.8. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.

TodoComment · ×24SwiftGit2/SwiftGit2/Repository.swift:341

What to do

  1. Resolve the 24 TodoComment finding(s) in Explicit Debt — start with MainApp.swift (6), SFTPFileSystemProvider.swift (3), Repository.swift (2). — One of this dimension's main actionable groups (24 warning-level).

Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.

D20 · ADR Quality0.0 / 10Critical✓ Tool-verified

What it measures: Whether architecture decisions are recorded well (context, decision, consequences).

Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

No architecture decision records were found.

No ADRs foundCode.xcodeproj/project.pbxproj:1

What to do

  1. Resolve the 1 No ADRs found finding(s) in ADR Quality — start with project.pbxproj. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.

D21 · Naming Consistency8.3 / 10Strong✓ Tool-verified

What it measures: Whether names — types, methods, variables — are clear and consistent.

Method: Seven vocabulary-free rules (N1-N7) mine each naming convention from the repository and flag a name that breaks a convention its structural peers in the same unit follow; production C# and TypeScript, each its own population. Deterministic, no model, no sample. Advisory.

Maturity: Documented → Verified → Prevented · effective 8.3 / 10 · rule-coverage 100% · ceiling Verified

1 naming inconsistencies among 60 declarations measured against a convention their peers follow.

`__sFILE` spells `FILE` where 59 names in the project spell it `File`LanguageResources/Library/lib/python3.9/lib2to3/tests/data/infinite_recursion.py:2032

What to do

  1. Resolve the 1 `__sFILE` spells `FILE` where 59 names in the project spell it `File` finding(s) in Naming Consistency — start with infinite_recursion.py. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d21_recommendation.md · top locations in Appendix A, every location in findings.md.

D26 · Project Cohesion3.3 / 10Weak✓ Tool-verified

What it measures: Whether each project is a focused, coherent unit rather than an oversized grab-bag.

Method: Project size overshoot penalties (LoC / public-type count / namespace count, 2-of-3 flag) weighted by log magnitude. Exhaustive across projects, deterministic.

Maturity: Documented → Verified → Prevented · effective 3.3 / 10 · rule-coverage 100% · ceiling Documented

1 of 3 build units (Bundler, SwiftPM) flagged as possibly oversized/incoherent.

Projects may be oversized for their cohesion

What to do

  1. Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.

D27 · Navigability9.7 / 10Exemplary✓ Tool-verified

What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.

Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.

Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.

Maturity: Documented → Verified → Prevented · effective 9.7 / 10 · rule-coverage 100% · ceiling Documented

1 % of calls cross a namespace and 6 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.

✓ On the Gold path — maintain.

Detailed fixes: d27_recommendation.md.

D28 · Secrets (history)10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.

Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

gitleaks scanned the full history AND the current working tree and found no secrets.

✓ On the Gold path — maintain.

Detailed fixes: d28_recommendation.md.

D29 · Static Analysis (SAST)9.5 / 10Adequategated by 4 critical findings✓ Tool-verified

What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.

Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.

Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).

Maturity: Documented → Verified → Prevented · effective 9.5 / 10 · rule-coverage 100% · ceiling Documented

5 finding(s): 0 critical, 4 high, 1 medium, 0 low. 4 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 2 file(s) — `CodeApp/Utilities/KBWebViewBase.h` (lines 38–39), `CodeUITests/CodeUITests.swift` (line 151, line 159, line 175) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.

REDACTED
REDACTED

What to do

  1. Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
  2. No action in Static Analysis (SAST) — all 4 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 (4 issue-level, 0 of them charged here).

Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.

D30 · Dependency Vulnerabilities0.0 / 10Critical✓ Tool-verified

What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.

Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no REDACTED is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

29 finding(s): 3 critical, 16 high, 7 medium, 3 low.

REDACTED
REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 16 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (8), REDACTED (8). — One of this dimension's main actionable groups (16 issue-level).
  2. Resolve the 7 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (5), REDACTED (2). — One of this dimension's main actionable groups (7 warning-level).
  3. Resolve the 3 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).

Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.

D34 · Knowledge Freshness10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.

Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

Every significant source file has living knowledge — recently and meaningfully worked. Counted over 92 of the 195 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

✓ On the Gold path — maintain.

Detailed fixes: d34_recommendation.md.

D35 · Change Coupling9.9 / 10Stronggated by 1 serious finding✓ Tool-verified

What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.

Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.

Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.

Maturity: Documented → Verified → Prevented · effective 9.9 / 10 · rule-coverage 100% · ceiling Documented

Strongest change-coupling: ExplorerFileTreeSection.swift↔FileTreeView.swift 50%

Change coupling: ExplorerFileTreeSection.swift ↔ FileTreeView.swiftCodeApp/Views/ExplorerFileTreeSection.swift:1

What to do

  1. Resolve the 1 Change coupling finding(s) in Change Coupling — start with ExplorerFileTreeSection.swift. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.

D43 · Malicious Dependencies10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.

Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No dependency in any ecosystem this repository declares is published as malicious.

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

D44 · Platform End-of-Life10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.

Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 0 platform declaration(s) and 1 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.

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Frontend & cross-cutting dimensions

R = React/JS · M = Maturity · P = Readiness.

AC1 · Text alternatives4.3 / 10Weak✓ Tool-verified

Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.

Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.

  • An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. (×2) — LanguageResources/Library/share/jupyter/nbconvert/templates/classic/base.html.j2:121, LanguageResources/Library/share/jupyter/nbconvert/templates/lab/base.html.j2:129

What to do

  • Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
AC3 · Page structure2.8 / 10Weak✓ Tool-verified

Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.

Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

  • The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). (×5) — Dependencies/terminal.bundle/index.html:2, LanguageResources/ClangLib/wasm.html:2, LanguageResources/Library/share/jupyter/nbconvert/templates/classic/index.html.j2:7, …
  • 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="overlay">, so there is no content here to wrap — render the <main> from the component mounted into it. — Dependencies/terminal.bundle/index.html:2
  • user-scalable=no/0 or a maximum-scale below 2 stops low-vision users zooming to 200%. Remove the zoom restriction from the viewport meta. (×2) — Dependencies/terminal.bundle/index.html:5, LanguageResources/ClangLib/wasm.html:6
  • 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="terminal">, so there is no content here to wrap — render the <main> from the component mounted into it. — LanguageResources/ClangLib/wasm.html:2
  • No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×3) — LanguageResources/Library/share/jupyter/nbconvert/templates/classic/index.html.j2:7, LanguageResources/Library/share/jupyter/nbconvert/templates/lab/index.html.j2:7, LanguageResources/Library/share/jupyter/nbconvert/templates/reveal/index.html.j2:12

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.
AC6 · Visual & motion safety1.0 / 10Critical✓ Tool-verified

Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.

Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.

Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

  • `.bp3-dark .bp3-running-text kbd, .bp3-running-text .bp3-dark kbd, .bp3-dark .bp3-key` sets color: #a7b6c2 on background-color: #394b59 — 4.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css:1033
  • `.cm-s-base16-light span.cm-error` sets color: #505050 on background-color: #ac4142 — 1.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css:11373
  • `.cm-s-base16-dark span.cm-error` sets color: #b0b0b0 on background-color: #ac4142 — 2.7:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css:11412
  • `.cm-s-hopscotch span.cm-error` sets color: #989498 on background-color: #dd464c — 1.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css:11485
  • `.cm-s-mdn-like.CodeMirror` sets color: #999 on background-color: #fff — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css:11540
  • `a.list-group-item-success:hover, button.list-group-item-success:hover, a.list-group-item-success:focus, button.list-group-item-success:focus` sets color: #3c763d on background-color: #d0e9c6 — 4.2:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — LanguageResources/Library/share/jupyter/nbconvert/templates/classic/static/style.css:5317
  • `a.list-group-item-info:hover, button.list-group-item-info:hover, a.list-group-item-info:focus, button.list-group-item-info:focus` sets color: #31708f on background-color: #c4e3f3 — 4.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — LanguageResources/Library/share/jupyter/nbconvert/templates/classic/static/style.css:5346
  • `a.list-group-item-warning:hover, button.list-group-item-warning:hover, a.list-group-item-warning:focus, button.list-group-item-warning:focus` sets color: #8a6d3b on background-color: #faf2cc — 4.3:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — LanguageResources/Library/share/jupyter/nbconvert/templates/classic/static/style.css:5375
  • `a.list-group-item-danger:hover, button.list-group-item-danger:hover, a.list-group-item-danger:focus, button.list-group-item-danger:focus` sets color: #a94442 on background-color: #ebcccc — 3.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — LanguageResources/Library/share/jupyter/nbconvert/templates/classic/static/style.css:5404
  • `div.unrecognized_cell .inner_cell` sets color: red on background-color: #eaeaea — 3.3:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — LanguageResources/Library/share/jupyter/nbconvert/templates/classic/static/style.css:10560
  • `.rendered_html hr` sets color: black on background-color: black — 1.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — LanguageResources/Library/share/jupyter/nbconvert/templates/classic/static/style.css:11190
  • `.pulse, .dropdown-menu > li > a.pulse, li.pulse > a.dropdown-toggle, li.pulse.open > a.dropdown-toggle` sets color: white on background-color: #F37626 — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — LanguageResources/Library/share/jupyter/nbconvert/templates/classic/static/style.css:12669
  • `#controls #navLinks a` sets color: #779 on background-color: #005 — 4.3:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — LanguageResources/Library/lib/python3.9/site-packages/docutils/writers/s5_html/themes/default/pretty.css:44
  • `.bp3-focus-disabled :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. — LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css:1074
  • `.bp3-focus-disabled :focus ~ .bp3-control-indicator` 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. — LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css:1076
  • `.bp3-button:not([class*="bp3-intent-"]).bp3-disabled` 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. — LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css:1277
  • `.bp3-dialog: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. — LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css:2211
  • `.bp3-drawer: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. — LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css:2299
  • `.bp3-editable-text-input: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. — LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css:2749
  • `.bp3-html-select select.bp3-disabled` 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. — LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css:4085
  • `.bp3-menu-item.bp3-disabled` 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. — LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css:6333
  • `.bp3-overlay-backdrop: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. — LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css:6676
  • `.bp3-transition-container: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. — LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css:7062
  • `.bp3-slider` 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. — LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css:7167
  • `.bp3-slider-handle.bp3-disabled` 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. — LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css:7236
  • `.bp3-input-ghost: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. — LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css:8045
  • `.lm-CommandPalette-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. — LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css:9800
  • `.jp-MainAreaWidget > :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. — LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css:10088
  • `.jp-Spinner` 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. — LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css:10387
  • `button.jp-mod-styled` 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. — LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css:10466
  • `select.jp-mod-styled` 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. — LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css:10527
  • `div.jp-ToolbarButton` 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. — LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css:10590
  • `button.jp-ToolbarButtonComponent` 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. — LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css:10602
  • `.CodeMirror-scroll` 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. — LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css:10900
  • `.CodeMirror-code` 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. — LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css:11012
  • `.CodeMirror-dialog 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. — LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css:11101
  • `.jp-MimeDocument` 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. — LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css:12688
  • `.jp-DirListing` 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. — LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css:12792
  • `.jp-DirListing-editor` 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. — LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css:12894
  • `.jp-Document` 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. — LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css:12931

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 composition9.4 / 10Exemplary✓ Tool-verified

Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.

Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.

Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.

AX3 · Project dependency cycles10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).

Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.

AX4 · Dependency direction10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.

Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.

AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.

Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.

AX9 · CQS / query purity9.7 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.

Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.

Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.

  • `LocalGitServiceProvider.lookupCommit` is a read-named query yet it performs a durable write on the read path (a persist to a store/client). A query must stay side-effect-free so reads are safe to retry, cache, and route to a read replica; move the write into a command. — CodeApp/Managers/FileSystem/Local/LocalGitServiceProvider.swift:399

What to do

  • Keep query handlers read-only — move the writes/event-publishes into a command handler so reads stay safe to retry, cache, and route to a read replica.
M1 · Documentation (README)7.7 / 10Strong✓ Tool-verified

Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.

Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.

What to do

  • 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 documentation2.0 / 10Critical✓ Tool-verified

Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.

Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.

  • No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.

What to do

  • Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.

Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.

P1 · CI/CD gates10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — Whether an automated pipeline builds and tests every change.

Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.

P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.

Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.

P2 · Observability7.0 / 10Strong✓ Tool-verified

Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.

Method: Filesystem/Roslyn scan: structured-logging frameworks (Serilog, NLog), OpenTelemetry, and health-check endpoint patterns. Exhaustive, deterministic.

P3 · Security & performance tooling0.0 / 10Critical✓ Tool-verified

Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).

Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.

  • No static application security testing detected. For this repository's stack, add CodeQL's Swift pack (Swift/Xcode) (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 3 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. — REDACTED:3
  • `Dependencies/npm.bundle/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`. — Dependencies/npm.bundle/package.json:2

What to do

  • Add a SAST step to CI running what this repository's stack ships: CodeQL's Swift pack (Swift/Xcode) — or `semgrep --config=auto`, which runs on any language — 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 & Rollback7.0 / 10Strong✓ Tool-verified

Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.

Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.

P6 · Release Hygiene8.0 / 10Strong✓ Tool-verified

Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.

Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.

  • The changelog this check read carries 0 versioned entries, against a bar of 3. Counted as either the distinct `x.y.z` versions it names (a link's target is not counted) or its version-shaped section headings (`## [1.2.0]`, `## V14.x.x`, `## Updates in 8.0.x`), whichever is the larger — so a log sectioned by minor series counts its sections, not its individual patch numbers. Entries recorded somewhere this check does not read — release notes generated at tag time from a generator config it did not recognise, or a log kept outside the repository — are not counted here, and this row is about what is re-findable in the tree rather than about how often you release.

What to do

  • Keep the changelog current — add a versioned entry (Keep-a-Changelog ## [x.y.z]) for each release so the history isn't a stub.
PF3 · Async & latency hygiene10.0 / 10Exemplary✓ Tool-verified

Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.

Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.

X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.

Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.

X3 · Exception handling6.3 / 10Adequate✓ Tool-verified

Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.

Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.

  • `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×4) — Extensions/RemoteExecution/CloudCodeExecutionManager.swift:164, CodeApp/Types/Shared/AppExtensionError.swift:15, CodeApp/Managers/FileSystem/SFTP/SFTPFileSystemProvider.swift:76, …
  • 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. — CodeApp/Utilities/wasm.swift:196

What to do

  • Swallowed exception (caught, then discarded)

WCAG coverage — what static analysis assessed

Statically assessed 11 of 55 WCAG 2.2 Level A/AA success criteria (20%; ≈22% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 44 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).

DimensionWCAG 2.2 A/AA criteriaCoverage
AC1 · Text alternatives1.1.1, 1.2.2, 1.2.5Partial signal
AC3 · Page structure1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2Partial signal
AC6 · Visual & motion safety1.4.3, 2.4.7Partial — literal CSS only

Not statically assessed — these 44 Level A/AA criteria need runtime or manual evaluation (WCAG-EM): 1.2.1, 1.2.3, 1.2.4, 1.3.1, 1.3.2, 1.3.3, 1.3.4, 1.3.5, 1.4.1, 1.4.2, 1.4.5, 1.4.10, 1.4.11, 1.4.12, 1.4.13, 2.1.1, 2.1.2, 2.1.4, 2.2.2, 2.3.1, 2.4.3, 2.4.4, 2.4.5, 2.4.6, 2.4.11, 2.5.1, 2.5.2, 2.5.3, 2.5.4, 2.5.7, 2.5.8, 3.1.2, 3.2.1, 3.2.2, 3.2.3, 3.2.4, 3.2.6, 3.3.1, 3.3.2, 3.3.3, 3.3.4, 3.3.7, 3.3.8, 4.1.3.

Reference — by lens

The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.

LensScoreRatingImpact
Code Health72%StrongSolid.
Architecture89%Adequate — gated by D26Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity64%Adequate — gated by M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness53%Adequate — gated by P3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security98%ExemplarySolid.
Accessibility24%Critical — gated by AC3, AC6Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance100%ExemplaryStrongest area.
Unscored — 5 check(s) recorded observations but carry no score

These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.

  • D11 Test Reliability — 1 observation(s) recorded · This repository declares 1 of its own test(s) unreliable. The built-in reliability runner does not support this repository's ecosystem (.swift), so the suite was not re-run and no reliability score is given — these are the repository's own declarations, not our measurement.
  • D36 Supply-chain Provenance & Signing — 3 observation(s) recorded · The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
  • SC1 Supply-chain hygiene — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X10 Duplicated predicate — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X7 Silent fallback defaults — 16 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 control(s) we could not find positive evidence for

These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.

  • C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • 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

These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.

  • AC2 Forms & labels — No form control/button found in the parsed markup — AC2 not applicable here.
  • AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
  • AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
  • AX1 Captive dependencies — 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
  • AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. No Swift request handler (a Vapor, Hummingbird, Kitura, Swifter or Perfect route handler, as a method or a registered closure) is declared, so no state is shared between request threads. 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
  • AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • C4 Data Retention — No personal data detected in a persisted data model — no PII-named property (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a SwiftData @Model, a Core Data, Realm, GRDB or Fluent type, a GRDB or SQLite.swift column, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (CoreData, SwiftData, GRDB, RealmSwift, SQLite, Firebase, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
  • C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named property (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a SwiftData @Model, a Core Data, Realm, GRDB or Fluent type, a GRDB or SQLite.swift column, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (CoreData, SwiftData, GRDB, RealmSwift, SQLite, Firebase, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
  • D16 Bus Factor — single-maintainer repository — bus factor is not applicable
  • D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
  • D19 Documentation Quality — D19 withholds "Documentation: empty section": 1 candidate(s) were measured and not published.
  • D22 Internal API Consistency — API consistency is measured on C# only; the exposed Swift surface was not measured.
  • D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
  • D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .swift source were not judged.
  • D25 ADR Conformance — no ADRs to check
  • D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
  • D32 Data Compliance (PII/GDPR) — 6 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
  • D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
  • D8 Code Coverage — Coverage not measured — Swift suite
  • DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (11 value object(s))
  • ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and this analysis resolves a call's owner only where the receiver's type is written down in the source. Reported as guidance rather than measured
  • ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
  • IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • M4 Documentation accuracy — Not applicable: the 6 current-state document(s) make no claim of a kind M4 checks. 5 claim(s) of kinds M4 does not check were not checked (path 4, command argument 1); M4 checks only links and versions and artefact counts.
  • P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
  • P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript, Swift source, so there is no service whose uptime a failing dependency could take down
  • P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
  • P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
  • PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for a pytest-benchmark or pytest-codspeed dependency with tests taking the `benchmark` fixture, an asv.conf.json with its `time_`/`mem_`/`peakmem_` benchmarks, or a pyperf Runner, 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.
  • S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X12 Unreachable branch — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X16 Unfloored truncation loop — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • X21 Side-effecting pattern guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X27 Collection changed while being enumerated — not 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
  • X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • X4 Structured logging — 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.
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.

Critical — 37 finding(s)
D30 · Dependency Vulnerabilities · High CVE · ×16
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AC3 · Page structure · <html> without a lang · ×5
  • <html> without a lang Dependencies/terminal.bundle/index.html:2 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang LanguageResources/ClangLib/wasm.html:2 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang LanguageResources/Library/share/jupyter/nbconvert/templates/classic/index.html.j2:7 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang LanguageResources/Library/share/jupyter/nbconvert/templates/lab/index.html.j2:7 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang LanguageResources/Library/share/jupyter/nbconvert/templates/reveal/index.html.j2:12 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D30 · Dependency Vulnerabilities · Critical CVE · ×3
  • REDACTED
  • REDACTED
  • REDACTED
AC1 · Text alternatives · <img> without a text alternative · ×2
  • <img> without a text alternative LanguageResources/Library/share/jupyter/nbconvert/templates/classic/base.html.j2:121 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative LanguageResources/Library/share/jupyter/nbconvert/templates/lab/base.html.j2:129 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
AC3 · Page structure · Viewport restricts zoom · ×2
  • Viewport restricts zoom Dependencies/terminal.bundle/index.html:5 — user-scalable=no/0 or a maximum-scale below 2 stops low-vision users zooming to 200%. Remove the zoom restriction from the viewport meta.
  • Viewport restricts zoom LanguageResources/ClangLib/wasm.html:6 — user-scalable=no/0 or a maximum-scale below 2 stops low-vision users zooming to 200%. Remove the zoom restriction from the viewport meta.
AX9 · CQS / query purity · Query writes persistent state on the read path · ×1
  • Query writes persistent state on the read path: LocalGitServiceProvider.lookupCommit CodeApp/Managers/FileSystem/Local/LocalGitServiceProvider.swift:399 — `LocalGitServiceProvider.lookupCommit` is a read-named query yet it performs a durable write on the read path (a persist to a store/client). A query must stay side-effect-free so reads are safe to retry, cache, and route to a read replica; move the write into a command.
D10 · Test Quality · Assertions commented out · ×1
  • Assertions commented out: testExample SwiftWS/Tests/SwiftWSTests/SwiftWSTests.swift:5 — The test body contains commented-out assertion calls and no live one — it runs, verifies nothing, and still passes. Restore the assertions or delete the test; a green test that checks nothing is worse than an absent one.
D10 · Test Quality · Test project verifies nothing · ×1
  • Test project verifies nothing: SwiftWSTests SwiftWS/Tests/SwiftWSTests/SwiftWSTests.swift:5 — No conventional assertion call was detected in 1 of 1 tests in `SwiftWSTests` — the project as a whole, not one method. 1 of them has its assertions commented out, so this suite did verify conventionally and was switched off — it is not an approval/verifier harness.
D11 · Test Reliability · Test declared unreliable · ×1
  • Test declared unreliable: test_f2py LanguageResources/Library/lib/python3.9/site-packages/numpy/tests/test_scripts.py:36 — This test is disabled or skipped with a reason naming unreliability — the repository's own words: "Test is unreliable". A test that is skipped for flakiness is neither passing nor protecting the code it covers; either stabilise it or delete it, but do not leave it disabled indefinitely. (Found by reading the repository's own test source — the suite itself was not re-run, since the reliability runner does not support this ecosystem.)
D13 · Secret Scanning · Leaked secret · ×1
  • REDACTED
Serious — 235 finding(s)
AC6 · Visual & motion safety · Focus outline removed in CSS without a · ×27
  • Focus outline removed in CSS without a :focus replacement LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css:1074 — `.bp3-focus-disabled :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.
  • Focus outline removed in CSS without a :focus replacement LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css:1076 — `.bp3-focus-disabled :focus ~ .bp3-control-indicator` 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.
  • Focus outline removed in CSS without a :focus replacement LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css:1277 — `.bp3-button:not([class*="bp3-intent-"]).bp3-disabled` 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.
  • Focus outline removed in CSS without a :focus replacement LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css:2211 — `.bp3-dialog: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.
  • Focus outline removed in CSS without a :focus replacement LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css:2299 — `.bp3-drawer: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.
  • Focus outline removed in CSS without a :focus replacement LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css:2749 — `.bp3-editable-text-input: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.
  • Focus outline removed in CSS without a :focus replacement LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css:4085 — `.bp3-html-select select.bp3-disabled` 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.
  • Focus outline removed in CSS without a :focus replacement LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css:6333 — `.bp3-menu-item.bp3-disabled` 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.
  • Focus outline removed in CSS without a :focus replacement LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css:6676 — `.bp3-overlay-backdrop: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.
  • Focus outline removed in CSS without a :focus replacement LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css:7062 — `.bp3-transition-container: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.
  • Focus outline removed in CSS without a :focus replacement LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css:7167 — `.bp3-slider` 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.
  • Focus outline removed in CSS without a :focus replacement LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css:7236 — `.bp3-slider-handle.bp3-disabled` 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.
  • Focus outline removed in CSS without a :focus replacement LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css:8045 — `.bp3-input-ghost: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.
  • Focus outline removed in CSS without a :focus replacement LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css:9800 — `.lm-CommandPalette-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.
  • Focus outline removed in CSS without a :focus replacement LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css:10088 — `.jp-MainAreaWidget > :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.
  • Focus outline removed in CSS without a :focus replacement LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css:10387 — `.jp-Spinner` 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.
  • Focus outline removed in CSS without a :focus replacement LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css:10466 — `button.jp-mod-styled` 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.
  • Focus outline removed in CSS without a :focus replacement LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css:10527 — `select.jp-mod-styled` 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.
  • Focus outline removed in CSS without a :focus replacement LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css:10590 — `div.jp-ToolbarButton` 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.
  • Focus outline removed in CSS without a :focus replacement LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css:10602 — `button.jp-ToolbarButtonComponent` 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.
  • Focus outline removed in CSS without a :focus replacement LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css:10900 — `.CodeMirror-scroll` 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.
  • Focus outline removed in CSS without a :focus replacement LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css:11012 — `.CodeMirror-code` 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.
  • Focus outline removed in CSS without a :focus replacement LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css:11101 — `.CodeMirror-dialog 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.
  • Focus outline removed in CSS without a :focus replacement LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css:12688 — `.jp-MimeDocument` 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.
  • Focus outline removed in CSS without a :focus replacement LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css:12792 — `.jp-DirListing` 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.
  • + 2 more in this group — see findings.md.
D17 · Explicit Debt · TodoComment · ×24
  • TodoComment SwiftGit2/SwiftGit2/Repository.swift:341 — // TODO: Evaluate whether this is a memory-safe code — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment SwiftGit2/SwiftGit2/Repository.swift:379 — // TODO: Handle local branch — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment Extensions/VideoViewer/VideoViewerExtension.swift:41 — // TODO: Support OutputStream — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment CodeApp/Managers/FileSystem/SFTP/SFTPFileSystemProvider.swift:358 — // TODO: Support OutputStream — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment Extensions/MarkdownViewer/MarkdownViewerExtension.swift:11 — // TODO: Localization — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment Extensions/ImageEditor/ImageEditorExtension.swift:14 — // TODO: Localization — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment CodeApp/Views/EditorTab.swift:15 — // TODO: Don't use ObservedObject because it leaks memory — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment CodeApp/Views/EditorTab.swift:35 — // TODO: File Icons for extensions — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment CodeApp/Views/EditorView.swift:28 — // TODO: Determine whether file is directory — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment CodeApp/Views/SettingsView.swift:45 — // TODO: Rework Editor / Terminal settings to support multiple scenes — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment CodeApp/Utilities/Utilities.swift:33 — // TODO: Track programmer error — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment CodeApp/Utilities/Utilities.swift:44 — // TODO: Track programmer error — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment CodeApp/Managers/AppExtensionService.swift:107 — // TODO: send real signal instead — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment CodeApp/Managers/MainApp.swift:248 — // TODO: Support deleted files detection for remote files — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment CodeApp/Managers/MainApp.swift:519 — // TODO: Modify SceneStorage? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment CodeApp/Managers/MainApp.swift:1021 — // TODO: A more efficient way to determine whether file is supported — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment CodeApp/Managers/MainApp.swift:1039 — // TODO: Update using updateUIView? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment CodeApp/Managers/MainApp.swift:1121 — // TODO: Avoid reading the same file twice — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment CodeApp/Managers/MainApp.swift:1285 — // TODO: This can be made more robust — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment CodeApp/Managers/FileSystem/SFTP/SFTPFileSystemProvider.swift:16 — // TODO: Expose libssh2_sftp_last_error — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment CodeApp/Managers/FileSystem/SFTP/SFTPFileSystemProvider.swift:264 — // TODO: Evaluate the performance penalty — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment CodeApp/Managers/FileSystem/Local/LocalGitCredentialsHelper.swift:24 — // TODO: Localize this using LocalizedError — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment CodeApp/Managers/FileSystem/Local/LocalGitCredentialsHelper.swift:295 — // TODO: Global SSH Key — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment CodeApp/Errors/AppError.swift:10 — // TODO: Add localization entries — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
D3 · God Classes · MethodTooLong · ×10
  • MethodTooLong: wasmWebViewDelegate.webView CodeApp/Utilities/wasm.swift:63 — MethodTooLong — webView runs 342 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 242 over it, 3.42× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: SettingsView.body CodeApp/Views/SettingsView.swift:42 — MethodTooLong — body runs 224 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 124 over it, 2.24× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: TerminalInstance.userContentController CodeApp/Managers/TerminalInstance.swift:237 — MethodTooLong — userContentController runs 161 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 61 over it, 1.61× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: ExplorerFileTree.buildContextMenu CodeApp/Views/ExplorerFileTreeSection.swift:91 — MethodTooLong — buildContextMenu runs 144 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 44 over it, 1.44× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: RemoteCreateSection.body CodeApp/Views/RemoteCreateSection.swift:119 — MethodTooLong — body runs 137 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 37 over it, 1.37× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: MainSection.body CodeApp/Views/SourceControlSection.swift:116 — MethodTooLong — body runs 125 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 25 over it, 1.25× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: TerminalKeyboardToolBar.body CodeApp/Views/TerminalKeyboardToolbar.swift:129 — MethodTooLong — body runs 116 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 16 over it, 1.16× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: EditorView.body CodeApp/Views/EditorView.swift:33 — MethodTooLong — body runs 109 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 9 over it, 1.09× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: TopBar.body CodeApp/Views/TopBar.swift:24 — MethodTooLong — body runs 109 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 9 over it, 1.09× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: MainView.body CodeApp/Containers/MainScene.swift:160 — MethodTooLong — body runs 108 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 8 over it, 1.08× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D3 · God Classes · TooManyMethods · ×7
  • TooManyMethods: Repository SwiftGit2/SwiftGit2/Repository.swift:179 — TooManyMethods — 74 methods. The bar is 30 methods; this is 44 over it, 2.47× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: MainApp CodeApp/Managers/MainApp.swift:141 — TooManyMethods — 46 methods. The bar is 30 methods; this is 16 over it, 1.53× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: MonacoImplementation CodeApp/Managers/EditorImplementation/MonacoImplementation.swift:50 — TooManyMethods — 44 methods. The bar is 30 methods; this is 14 over it, 1.47× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: RunestoneImplementation CodeApp/Managers/EditorImplementation/RunestoneImplementation.swift:308 — TooManyMethods — 44 methods. The bar is 30 methods; this is 14 over it, 1.47× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: LocalGitServiceProvider CodeApp/Managers/FileSystem/Local/LocalGitServiceProvider.swift:28 — TooManyMethods — 34 methods. The bar is 30 methods; this is 4 over it, 1.13× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: WorkSpaceStorage CodeApp/Managers/FileSystem/WorkSpaceStorage.swift:12 — TooManyMethods — 34 methods. The bar is 30 methods; this is 4 over it, 1.13× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: TerminalInstance CodeApp/Managers/TerminalInstance.swift:21 — TooManyMethods — 32 methods. The bar is 30 methods; this is 2 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D30 · Dependency Vulnerabilities · Medium CVE · ×7
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D6 · Cohesion (LCOM4) · Low cohesion · ×7
  • Low cohesion: RunestoneImplementation (LCOM4 18) CodeApp/Managers/EditorImplementation/RunestoneImplementation.swift:308 — RunestoneImplementation's methods fall into 18 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 18 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: LocalFileSystemProvider (LCOM4 9) CodeApp/Managers/FileSystem/Local/LocalFileSystemProvider.swift:10 — LocalFileSystemProvider's methods fall into 9 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 9 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: MainApp (LCOM4 7) CodeApp/Managers/MainApp.swift:141 — MainApp's methods fall into 7 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 7 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: SFTPTerminalServiceProvider (LCOM4 5) CodeApp/Managers/FileSystem/SFTP/SFTPTerminalServiceProvider.swift:11 — SFTPTerminalServiceProvider's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: WebViewBase (LCOM4 4) CodeApp/Managers/WebViewBase.swift:38 — WebViewBase's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: TableViewDelegate (LCOM4 4) CodeApp/Views/FileTreeView.swift:28 — TableViewDelegate's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: String (LCOM4 4) CodeApp/Extensions/String+base64EncodedDecoded.swift:10 — String's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
AC3 · Page structure · Page without a main landmark · ×5
  • Page without a main landmark Dependencies/terminal.bundle/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="overlay">, so there is no content here to wrap — render the <main> from the component mounted into it.
  • Page without a main landmark LanguageResources/ClangLib/wasm.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="terminal">, so there is no content here to wrap — render the <main> from the component mounted into it.
  • Page without a main landmark LanguageResources/Library/share/jupyter/nbconvert/templates/classic/index.html.j2:7 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark LanguageResources/Library/share/jupyter/nbconvert/templates/lab/index.html.j2:7 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark LanguageResources/Library/share/jupyter/nbconvert/templates/reveal/index.html.j2:12 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
D12 · Dependency Hygiene · Floating branch dependency · ×5
  • Floating branch dependency: libgit2-on-ios — Dependency `libgit2-on-ios` is declared in SwiftGit2/Package.swift against branch `master` — the declaration pins no immutable point, so `swift package update` moves this dependency to whatever that branch holds at the time, which is code nobody reviewed. Pin it to a version requirement (`from:`, `.upToNextMajor(from:)`, `exact:`) or to a `revision:` commit SHA.
  • Floating branch dependency: fileprovider — Dependency `fileprovider` is resolved in Code.xcodeproj/project.xcworkspace/xcshareddata/swiftpm/Package.resolved against branch `master` rather than a released version — the project pins no immutable point, so resolving the packages again moves this dependency to whatever that branch holds at the time. Change the dependency rule in Xcode to a version requirement, or to an exact commit.
  • Floating branch dependency: gcdwebserver — Dependency `gcdwebserver` is resolved in Code.xcodeproj/project.xcworkspace/xcshareddata/swiftpm/Package.resolved against branch `master` rather than a released version — the project pins no immutable point, so resolving the packages again moves this dependency to whatever that branch holds at the time. Change the dependency rule in Xcode to a version requirement, or to an exact commit.
  • Floating branch dependency: libgit2-on-ios — Dependency `libgit2-on-ios` is resolved in Code.xcodeproj/project.xcworkspace/xcshareddata/swiftpm/Package.resolved against branch `master` rather than a released version — the project pins no immutable point, so resolving the packages again moves this dependency to whatever that branch holds at the time. Change the dependency rule in Xcode to a version requirement, or to an exact commit.
  • Floating branch dependency: markdownview — Dependency `markdownview` is resolved in Code.xcodeproj/project.xcworkspace/xcshareddata/swiftpm/Package.resolved against branch `master` rather than a released version — the project pins no immutable point, so resolving the packages again moves this dependency to whatever that branch holds at the time. Change the dependency rule in Xcode to a version requirement, or to an exact commit.
D4 · Code Duplication · Edited copy of a member (13 corresponding lines) · ×5
  • Edited copy of a member (13 corresponding lines) CodeApp/Managers/NotificationManager.swift:23 — CodeApp/Managers/NotificationManager.swift:23-37 | CodeApp/Managers/NotificationManager.swift:39-57 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) SwiftGit2/SwiftGit2/Repository.swift:617 — SwiftGit2/SwiftGit2/Repository.swift:617-629 | SwiftGit2/SwiftGit2/Repository.swift:636-648 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) CodeApp/Managers/FileSystem/SFTP/SFTPFileSystemProvider.swift:101 — CodeApp/Managers/FileSystem/SFTP/SFTPFileSystemProvider.swift:101-113 | CodeApp/Managers/FileSystem/SFTP/SFTPTerminalServiceProvider.swift:20-38 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) CodeApp/Types/EditorInstance.swift:94 — CodeApp/Types/EditorInstance.swift:94-130 | CodeApp/Types/EditorInstance.swift:136-148 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) CodeApp/Containers/SourceControlContainer.swift:20 — CodeApp/Containers/SourceControlContainer.swift:20-34 | Extensions/SourceControlAuxiliary/Views/CheckoutMenu.swift:16-28 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (9 corresponding lines) · ×5
  • Edited copy of a member (9 corresponding lines) CodeApp/Views/FileTreeView.swift:213 — CodeApp/Views/FileTreeView.swift:213-221 | CodeApp/Views/FileTreeView.swift:228-236 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) SwiftGit2/SwiftGit2/Repository.swift:286 — SwiftGit2/SwiftGit2/Repository.swift:286-294 | SwiftGit2/SwiftGit2/Repository.swift:296-306 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) CodeApp/Managers/FileSystem/Local/LocalGitCredentialsHelper.swift:71 — CodeApp/Managers/FileSystem/Local/LocalGitCredentialsHelper.swift:71-79 | CodeApp/Managers/FileSystem/Local/LocalGitCredentialsHelper.swift:81-92 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) CodeApp/Managers/FileSystem/Local/LocalFileSystemProvider.swift:33 — CodeApp/Managers/FileSystem/Local/LocalFileSystemProvider.swift:33-41 | CodeApp/Managers/FileSystem/Local/LocalFileSystemProvider.swift:109-118 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) CodeApp/Views/DocumentPickerView.swift:44 — CodeApp/Views/DocumentPickerView.swift:44-53 | CodeApp/Views/DirectoryPickerView.swift:46-54 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (13 lines × 2) · ×5
  • Duplicated block (13 lines × 2) CodeApp/Managers/FileSystem/Local/LocalGitServiceProvider.swift:268 — CodeApp/Managers/FileSystem/Local/LocalGitServiceProvider.swift:268-280 | CodeApp/Managers/FileSystem/Local/LocalGitServiceProvider.swift:283-295 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (13 lines × 2) CodeApp/Views/EditorKeyboardToolBar.swift:133 — CodeApp/Views/EditorKeyboardToolBar.swift:133-145 | CodeApp/Views/TerminalKeyboardToolbar.swift:245-257 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `CodeApp/Views/EditorKeyboardToolBar.swift:133` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (13 lines × 2) Extensions/ImageEditor/ImageEditorExtension.swift:19 — Extensions/ImageEditor/ImageEditorExtension.swift:19-31 | Extensions/ImageViewer/ImageViewerExtension.swift:18-30 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (13 lines × 2) Extensions/ImageEditor/ImageEditorExtension.swift:39 — Extensions/ImageEditor/ImageEditorExtension.swift:39-51 | Extensions/ImageViewer/ImageViewerExtension.swift:38-50 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Extensions/ImageEditor/ImageEditorExtension.swift:39` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 2) SwiftGit2/SwiftGit2/Repository.swift:740 — SwiftGit2/SwiftGit2/Repository.swift:740-752 | SwiftGit2/SwiftGit2/Repository.swift:778-790 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `SwiftGit2/SwiftGit2/Repository.swift:740` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×4
  • Duplicated block (5 lines × 2) CodeApp/Views/PanelView.swift:24 — CodeApp/Views/PanelView.swift:24-28 | CodeApp/Views/SourceControlSection.swift:273-277 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `CodeApp/Views/PanelView.swift:24` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 2) Extensions/ImageEditor/ImageEditorExtension.swift:64 — Extensions/ImageEditor/ImageEditorExtension.swift:64-68 | Extensions/VideoViewer/VideoViewerExtension.swift:39-43 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Extensions/ImageEditor/ImageEditorExtension.swift:64` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 2) CodeApp/Managers/FileSystem/SFTP/SFTPFileSystemProvider.swift:236 — CodeApp/Managers/FileSystem/SFTP/SFTPFileSystemProvider.swift:236-240 | CodeApp/Managers/FileSystem/SFTP/SFTPTerminalServiceProvider.swift:136-140 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (5 lines × 2) CodeApp/Views/ActivityBar.swift:75 — CodeApp/Views/ActivityBar.swift:75-79 | CodeApp/Views/CompactSidebar.swift:19-23 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
X3 · Exception handling · Swallowed exception (caught, then discarded) · ×4
  • Swallowed exception (caught, then discarded) Extensions/RemoteExecution/CloudCodeExecutionManager.swift:164 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) CodeApp/Types/Shared/AppExtensionError.swift:15 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) CodeApp/Managers/FileSystem/SFTP/SFTPFileSystemProvider.swift:76 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) CodeApp/Managers/EditorImplementation/MonacoImplementation.swift:568 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
D36 · Supply-chain Provenance & Signing · REDACTED · ×3
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Edited copy of a member (27 corresponding lines) · ×3
  • Edited copy of a member (27 corresponding lines) SwiftGit2/SwiftGit2/Repository.swift:73 — SwiftGit2/SwiftGit2/Repository.swift:73-104 | SwiftGit2/SwiftGit2/Repository.swift:150-176 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (27 corresponding lines) Extensions/ImageEditor/ImageEditorExtension.swift:60 — Extensions/ImageEditor/ImageEditorExtension.swift:60-87 | Extensions/ImageViewer/ImageViewerExtension.swift:70-96 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (27 corresponding lines) CodeApp/Containers/SourceControlContainer.swift:304 — CodeApp/Containers/SourceControlContainer.swift:304-330 | CodeApp/Containers/SourceControlContainer.swift:358-388 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (1.4 · ×2
  • Low contrast colour pair in CSS (1.4:1) LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css:11373 — `.cm-s-base16-light span.cm-error` sets color: #505050 on background-color: #ac4142 — 1.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
  • Low contrast colour pair in CSS (1.4:1) LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css:11485 — `.cm-s-hopscotch span.cm-error` sets color: #989498 on background-color: #dd464c — 1.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (2.8 · ×2
  • Low contrast colour pair in CSS (2.8:1) LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css:11540 — `.cm-s-mdn-like.CodeMirror` sets color: #999 on background-color: #fff — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
  • Low contrast colour pair in CSS (2.8:1) LanguageResources/Library/share/jupyter/nbconvert/templates/classic/static/style.css:12669 — `.pulse, .dropdown-menu > li > a.pulse, li.pulse > a.dropdown-toggle, li.pulse.open > a.dropdown-toggle` sets color: white on background-color: #F37626 — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (4.3 · ×2
  • Low contrast colour pair in CSS (4.3:1) LanguageResources/Library/share/jupyter/nbconvert/templates/classic/static/style.css:5375 — `a.list-group-item-warning:hover, button.list-group-item-warning:hover, a.list-group-item-warning:focus, button.list-group-item-warning:focus` sets color: #8a6d3b on background-color: #faf2cc — 4.3:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
  • Low contrast colour pair in CSS (4.3:1) LanguageResources/Library/lib/python3.9/site-packages/docutils/writers/s5_html/themes/default/pretty.css:44 — `#controls #navLinks a` sets color: #779 on background-color: #005 — 4.3:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
D3 · God Classes · ClassTooLong · ×2
  • ClassTooLong: Repository SwiftGit2/SwiftGit2/Repository.swift:179 — ClassTooLong — 801 significant lines (blank, comment-only and punctuation-only lines excluded), 74 methods. The bar is 400 significant lines; this is 401 over it, 2.00× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: MainApp CodeApp/Managers/MainApp.swift:141 — ClassTooLong — 722 significant lines (blank, comment-only and punctuation-only lines excluded), 46 methods. The bar is 400 significant lines; this is 322 over it, 1.81× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D3 · God Classes · FileTooLong · ×2
  • FileTooLong: SwiftGit2/Repository.swift SwiftGit2/SwiftGit2/Repository.swift — FileTooLong — 911 significant lines (blank, comment-only and punctuation-only lines excluded), about 88% of them inside a single declaration: Repository (179-1641). The bar is 500 significant lines; this is 411 over it, 1.82× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: Managers/MainApp.swift CodeApp/Managers/MainApp.swift — FileTooLong — 881 significant lines (blank, comment-only and punctuation-only lines excluded), about 82% of them inside a single declaration: MainApp (141-1230). The bar is 500 significant lines; this is 381 over it, 1.76× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
D4 · Code Duplication · Edited copy of a member (18 corresponding lines) · ×2
  • Edited copy of a member (18 corresponding lines) SwiftGit2/SwiftGit2/Repository.swift:896 — SwiftGit2/SwiftGit2/Repository.swift:896-913 | SwiftGit2/SwiftGit2/Repository.swift:969-990 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) CodeApp/Utilities/KeychainWrapper/KeychainWrapper.swift:224 — CodeApp/Utilities/KeychainWrapper/KeychainWrapper.swift:224-241 | CodeApp/Utilities/KeychainWrapper/KeychainWrapper.swift:248-265 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (22 corresponding lines) · ×2
  • Edited copy of a member (22 corresponding lines) CodeApp/Views/SourceControlSection.swift:314 — CodeApp/Views/SourceControlSection.swift:314-338 | CodeApp/Views/SourceControlSection.swift:350-371 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (22 corresponding lines) CodeApp/Managers/EditorImplementation/MonacoImplementation.swift:168 — CodeApp/Managers/EditorImplementation/MonacoImplementation.swift:168-189 | CodeApp/Managers/TerminalInstance.swift:98-119 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (12 corresponding lines) · ×2
  • Edited copy of a member (12 corresponding lines) SwiftGit2/SwiftGit2/Repository.swift:915 — SwiftGit2/SwiftGit2/Repository.swift:915-926 | SwiftGit2/SwiftGit2/Repository.swift:928-939 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) CodeApp/Managers/TerminalInstance.swift:604 — CodeApp/Managers/TerminalInstance.swift:604-615 | CodeApp/Managers/TerminalInstance.swift:647-665 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 10+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 10+ corresponding lines) CodeApp/Managers/FileSystem/Local/LocalGitServiceProvider.swift:217 — CodeApp/Managers/FileSystem/Local/LocalGitServiceProvider.swift:217-226 | CodeApp/Managers/FileSystem/Local/LocalGitServiceProvider.swift:228-237 | CodeApp/Managers/FileSystem/Local/LocalGitServiceProvider.swift:240-251 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 10+ corresponding lines) CodeApp/Managers/FileSystem/SFTP/SFTPFileSystemProvider.swift:284 — CodeApp/Managers/FileSystem/SFTP/SFTPFileSystemProvider.swift:284-295 | CodeApp/Managers/FileSystem/SFTP/SFTPFileSystemProvider.swift:334-343 | CodeApp/Managers/FileSystem/SFTP/SFTPFileSystemProvider.swift:356-366 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (6 corresponding lines) · ×2
  • Edited copy of a member (6 corresponding lines) CodeApp/Containers/ExplorerContainer.swift:33 — CodeApp/Containers/ExplorerContainer.swift:33-38 | CodeApp/Managers/TerminalInstance.swift:217-222 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) CodeApp/Views/EditorTab.swift:25 — CodeApp/Views/EditorTab.swift:25-30 | CodeApp/Views/EditorTabs.swift:90-95 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (19 lines × 2) · ×2
  • Duplicated block (19 lines × 2) CodeApp/Utilities/Shared/ExtensionCommunicationHelper.swift:15 — CodeApp/Utilities/Shared/ExtensionCommunicationHelper.swift:15-33 | CodeApp/Utilities/Shared/ExtensionCommunicationHelper.swift:36-54 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (19 lines × 2) CodeApp/Utilities/wasm.swift:412 — CodeApp/Utilities/wasm.swift:412-430 | CodeApp/Utilities/wasm.swift:451-469 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `CodeApp/Utilities/wasm.swift:412` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×2
  • Duplicated block (8 lines × 2) CodeApp/Utilities/wasm.swift:273 — CodeApp/Utilities/wasm.swift:273-280 | CodeApp/Utilities/wasm.swift:282-289 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `CodeApp/Utilities/wasm.swift:273` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (8 lines × 2) CodeApp/Views/SettingsView.swift:367 — CodeApp/Views/SettingsView.swift:367-375 | CodeApp/Views/SourceControlIdentityConfiguration.swift:30-37 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `CodeApp/Views/SettingsView.swift:367` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×2
  • Duplicated block (6 lines × 2) CodeApp/Managers/FileSystem/WorkSpaceStorage.swift:465 — CodeApp/Managers/FileSystem/WorkSpaceStorage.swift:465-471 | CodeApp/Managers/FileSystem/WorkSpaceStorage.swift:516-521 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `CodeApp/Managers/FileSystem/WorkSpaceStorage.swift:465` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (6 lines × 2) SwiftGit2/SwiftGit2/Repository.swift:1172 — SwiftGit2/SwiftGit2/Repository.swift:1172-1177 | SwiftGit2/SwiftGit2/Repository.swift:1204-1209 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `SwiftGit2/SwiftGit2/Repository.swift:1172` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
D5 · Coupling · Off the main sequence · ×2
  • Off the main sequence: SwiftWS — SwiftWS: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
  • Off the main sequence: SwiftGit2 — SwiftGit2: abstractness 0.09, instability 0.00, distance 0.91 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
SC1 · Supply-chain hygiene · JavaScript dependencies are not locked · ×2
  • JavaScript dependencies are not locked LanguageResources/Library/lib/python3.9/site-packages/matplotlib/backends/web_backend/package.json:2 — LanguageResources/Library/lib/python3.9/site-packages/matplotlib/backends/web_backend/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
  • JavaScript dependencies are not locked LanguageResources/Library/share/jupyter/labextensions/@jupyter-widgets/jupyterlab-manager/package.json:50 — LanguageResources/Library/share/jupyter/labextensions/@jupyter-widgets/jupyterlab-manager/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (4.4 · ×1
  • Low contrast colour pair in CSS (4.4:1) LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css:1033 — `.bp3-dark .bp3-running-text kbd, .bp3-running-text .bp3-dark kbd, .bp3-dark .bp3-key` sets color: #a7b6c2 on background-color: #394b59 — 4.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (2.7 · ×1
  • Low contrast colour pair in CSS (2.7:1) LanguageResources/Library/share/jupyter/nbconvert/templates/lab/static/index.css:11412 — `.cm-s-base16-dark span.cm-error` sets color: #b0b0b0 on background-color: #ac4142 — 2.7:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (4.2 · ×1
  • Low contrast colour pair in CSS (4.2:1) LanguageResources/Library/share/jupyter/nbconvert/templates/classic/static/style.css:5317 — `a.list-group-item-success:hover, button.list-group-item-success:hover, a.list-group-item-success:focus, button.list-group-item-success:focus` sets color: #3c763d on background-color: #d0e9c6 — 4.2:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (4.1 · ×1
  • Low contrast colour pair in CSS (4.1:1) LanguageResources/Library/share/jupyter/nbconvert/templates/classic/static/style.css:5346 — `a.list-group-item-info:hover, button.list-group-item-info:hover, a.list-group-item-info:focus, button.list-group-item-info:focus` sets color: #31708f on background-color: #c4e3f3 — 4.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (3.9 · ×1
  • Low contrast colour pair in CSS (3.9:1) LanguageResources/Library/share/jupyter/nbconvert/templates/classic/static/style.css:5404 — `a.list-group-item-danger:hover, button.list-group-item-danger:hover, a.list-group-item-danger:focus, button.list-group-item-danger:focus` sets color: #a94442 on background-color: #ebcccc — 3.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (3.3 · ×1
  • Low contrast colour pair in CSS (3.3:1) LanguageResources/Library/share/jupyter/nbconvert/templates/classic/static/style.css:10560 — `div.unrecognized_cell .inner_cell` sets color: red on background-color: #eaeaea — 3.3:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (1.0 · ×1
  • Low contrast colour pair in CSS (1.0:1) LanguageResources/Library/share/jupyter/nbconvert/templates/classic/static/style.css:11190 — `.rendered_html hr` sets color: black on background-color: black — 1.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
D1 · Cyclomatic Complexity · wasmWebViewDelegate.webView (cyclomatic 88) · ×1
  • wasmWebViewDelegate.webView (cyclomatic 88) CodeApp/Utilities/wasm.swift:63 — wasmWebViewDelegate.webView has cyclomatic complexity 88 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: CodeApp/Utilities/wasm.swift holds 2 of the 14 methods over the threshold — including the worst — and 79 of the 158 points over it (50%), 2.7× the next-largest file (CodeApp/Managers/TerminalInstance.swift at 29). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D1 · Cyclomatic Complexity · TerminalInstance.userContentController (cyclomatic 44) · ×1
  • TerminalInstance.userContentController (cyclomatic 44) CodeApp/Managers/TerminalInstance.swift:237 — TerminalInstance.userContentController has cyclomatic complexity 44 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · RunestoneImplementation.detectLangauge (cyclomatic 38) · ×1
  • RunestoneImplementation.detectLangauge (cyclomatic 38) CodeApp/Managers/EditorImplementation/RunestoneImplementation.swift:415 — RunestoneImplementation.detectLangauge has cyclomatic complexity 38 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · CodeApp.swift.createCSDK (cyclomatic 22) · ×1
  • CodeApp.swift.createCSDK (cyclomatic 22) CodeApp/CodeApp.swift:85 — CodeApp.swift.createCSDK has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · wasm.swift.executeWebAssembly (cyclomatic 21) · ×1
  • wasm.swift.executeWebAssembly (cyclomatic 21) CodeApp/Utilities/wasm.swift:550 — wasm.swift.executeWebAssembly has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: CodeApp/Utilities/wasm.swift holds 2 of the 14 methods over the threshold — including the worst — and 79 of the 158 points over it (50%), 2.7× the next-largest file (CodeApp/Managers/TerminalInstance.swift at 29). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D1 · Cyclomatic Complexity · ExplorerFileTree.buildContextMenu (cyclomatic 20) · ×1
  • ExplorerFileTree.buildContextMenu (cyclomatic 20) CodeApp/Views/ExplorerFileTreeSection.swift:91 — ExplorerFileTree.buildContextMenu has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · TerminalKeyboardToolBar.body (cyclomatic 20) · ×1
  • TerminalKeyboardToolBar.body (cyclomatic 20) CodeApp/Views/TerminalKeyboardToolbar.swift:129 — TerminalKeyboardToolBar.body has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · EditorView.body (cyclomatic 17) · ×1
  • EditorView.body (cyclomatic 17) CodeApp/Views/EditorView.swift:33 — EditorView.body has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · MonacoImplementation.userContentController (cyclomatic 17) · ×1
  • MonacoImplementation.userContentController (cyclomatic 17) CodeApp/Managers/EditorImplementation/MonacoImplementation.swift:228 — MonacoImplementation.userContentController has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · node.swift.tokenizeCommand (cyclomatic 17) · ×1
  • node.swift.tokenizeCommand (cyclomatic 17) CodeApp/Utilities/node.swift:286 — node.swift.tokenizeCommand has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · MainView.body (cyclomatic 16) · ×1
  • MainView.body (cyclomatic 16) CodeApp/Containers/MainScene.swift:160 — MainView.body has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · RemoteCreateSection.body (cyclomatic 16) · ×1
  • RemoteCreateSection.body (cyclomatic 16) CodeApp/Views/RemoteCreateSection.swift:119 — RemoteCreateSection.body has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · ShortcutPreview.body (cyclomatic 16) · ×1
  • ShortcutPreview.body (cyclomatic 16) CodeApp/Views/SettingsKeyboardShortcuts.swift:141 — ShortcutPreview.body has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · node.swift.splitScriptLine (cyclomatic 16) · ×1
  • node.swift.splitScriptLine (cyclomatic 16) CodeApp/Utilities/node.swift:232 — node.swift.splitScriptLine has cyclomatic complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D12 · Dependency Hygiene · Dependency not covered by the committed resolution · ×1
  • Dependency not covered by the committed resolution: libgit2-on-ios — `libgit2-on-ios` is declared in SwiftGit2/Package.swift but has no entry in the committed `Package.resolved` beside it, so its version is resolved rather than pinned. Resolve the package and commit the updated `Package.resolved`.
D2 · Cognitive Complexity · wasmWebViewDelegate.webView (cognitive 299) · ×1
  • wasmWebViewDelegate.webView (cognitive 299) CodeApp/Utilities/wasm.swift:63 — wasmWebViewDelegate.webView has cognitive complexity 299 (threshold 15). Drivers by points: if/else 97 (238 pts), error handling 11 (45 pts), loops 2 (11 pts), boolean chains 5 (nesting depth added 184). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function. This file is where this pass's cognitive complexity CONCENTRATES: CodeApp/Utilities/wasm.swift holds 2 of the 23 methods over the threshold — including the worst — and 306 of the 502 points over it (61%), 5.6× the next-largest file (CodeApp/Managers/TerminalInstance.swift at 55). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · TerminalInstance.userContentController (cognitive 63) · ×1
  • TerminalInstance.userContentController (cognitive 63) CodeApp/Managers/TerminalInstance.swift:237 — TerminalInstance.userContentController has cognitive complexity 63 (threshold 15). Drivers by points: if/else 24 (47 pts), match/switch 4 (7 pts), loops 2 (6 pts), boolean chains 3 (nesting depth added 30). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CodeApp.swift.createCSDK (cognitive 41) · ×1
  • CodeApp.swift.createCSDK (cognitive 41) CodeApp/CodeApp.swift:85 — CodeApp.swift.createCSDK has cognitive complexity 41 (threshold 15). Drivers by points: if/else 12 (26 pts), error handling 5 (10 pts), loops 3, boolean chains 2 (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · RunestoneImplementation.detectLangauge (cognitive 37) · ×1
  • RunestoneImplementation.detectLangauge (cognitive 37) CodeApp/Managers/EditorImplementation/RunestoneImplementation.swift:415 — RunestoneImplementation.detectLangauge has cognitive complexity 37 (threshold 15). Drivers by points: if/else 35, boolean chains 2. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · wasm.swift.executeWebAssembly (cognitive 37) · ×1
  • wasm.swift.executeWebAssembly (cognitive 37) CodeApp/Utilities/wasm.swift:550 — wasm.swift.executeWebAssembly has cognitive complexity 37 (threshold 15). Drivers by points: if/else 16 (32 pts), loops 3 (4 pts), ternaries 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: CodeApp/Utilities/wasm.swift holds 2 of the 23 methods over the threshold — including the worst — and 306 of the 502 points over it (61%), 5.6× the next-largest file (CodeApp/Managers/TerminalInstance.swift at 55). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · EditorView.body (cognitive 25) · ×1
  • EditorView.body (cognitive 25) CodeApp/Views/EditorView.swift:33 — EditorView.body has cognitive complexity 25 (threshold 15). Drivers by points: if/else 14 (21 pts), boolean chains 4 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CloudCodeExecutionManager.runCode (cognitive 25) · ×1
  • CloudCodeExecutionManager.runCode (cognitive 25) Extensions/RemoteExecution/CloudCodeExecutionManager.swift:58 — CloudCodeExecutionManager.runCode has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (20 pts), error handling 2 (3 pts), boolean chains 1, ternaries 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · node.swift.tokenizeCommand (cognitive 24) · ×1
  • node.swift.tokenizeCommand (cognitive 24) CodeApp/Utilities/node.swift:286 — node.swift.tokenizeCommand has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 8, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TerminalInstance.webView (cognitive 22) · ×1
  • TerminalInstance.webView (cognitive 22) CodeApp/Managers/TerminalInstance.swift:511 — TerminalInstance.webView has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 2 (5 pts), error handling 1 (2 pts), match/switch 1 (nesting depth added 12). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · ExplorerFileTree.buildContextMenu (cognitive 22) · ×1
  • ExplorerFileTree.buildContextMenu (cognitive 22) CodeApp/Views/ExplorerFileTreeSection.swift:91 — ExplorerFileTree.buildContextMenu has cognitive complexity 22 (threshold 15). Drivers by points: if/else 15, ternaries 3 (5 pts), boolean chains 1, error handling 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · TableViewDelegate.tableView (cognitive 22) · ×1
  • TableViewDelegate.tableView (cognitive 22) CodeApp/Views/FileTreeView.swift:363 — TableViewDelegate.tableView has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 4, loops 1 (2 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ShortcutPreview.body (cognitive 22) · ×1
  • ShortcutPreview.body (cognitive 22) CodeApp/Views/SettingsKeyboardShortcuts.swift:141 — ShortcutPreview.body has cognitive complexity 22 (threshold 15). Drivers by points: if/else 15 (19 pts), boolean chains 3 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · ExplorerFileTree.foldersWithFilter (cognitive 21) · ×1
  • ExplorerFileTree.foldersWithFilter (cognitive 21) CodeApp/Views/ExplorerFileTreeSection.swift:30 — ExplorerFileTree.foldersWithFilter has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (16 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TerminalKeyboardToolBar.body (cognitive 21) · ×1
  • TerminalKeyboardToolBar.body (cognitive 21) CodeApp/Views/TerminalKeyboardToolbar.swift:129 — TerminalKeyboardToolBar.body has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 11, if/else 6 (7 pts), boolean chains 3 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · node.swift.splitScriptLine (cognitive 21) · ×1
  • node.swift.splitScriptLine (cognitive 21) CodeApp/Utilities/node.swift:232 — node.swift.splitScriptLine has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 5, ternaries 1 (2 pts), loops 1 (nesting depth added 5). Of this number, 20 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ExplorerContainer.body (cognitive 20) · ×1
  • ExplorerContainer.body (cognitive 20) CodeApp/Containers/ExplorerContainer.swift:119 — ExplorerContainer.body has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (14 pts), loops 2 (6 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · WorkSpaceStorage._connectToServer (cognitive 20) · ×1
  • WorkSpaceStorage._connectToServer (cognitive 20) CodeApp/Managers/FileSystem/WorkSpaceStorage.swift:146 — WorkSpaceStorage._connectToServer has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 2, error handling 1 (2 pts), match/switch 1 (nesting depth added 8). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · MainView.body (cognitive 19) · ×1
  • MainView.body (cognitive 19) CodeApp/Containers/MainScene.swift:160 — MainView.body has cognitive complexity 19 (threshold 15). Drivers by points: if/else 13 (14 pts), boolean chains 3, ternaries 2 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · RemoteCreateSection.body (cognitive 19) · ×1
  • RemoteCreateSection.body (cognitive 19) CodeApp/Views/RemoteCreateSection.swift:119 — RemoteCreateSection.body has cognitive complexity 19 (threshold 15). Drivers by points: if/else 14 (15 pts), boolean chains 3, ternaries 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · node.swift.runScriptCommand (cognitive 18) · ×1
  • node.swift.runScriptCommand (cognitive 18) CodeApp/Utilities/node.swift:356 — node.swift.runScriptCommand has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (14 pts), loops 3, ternaries 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MonacoImplementation.injectTypes (cognitive 17) · ×1
  • MonacoImplementation.injectTypes (cognitive 17) CodeApp/Managers/EditorImplementation/MonacoImplementation.swift:191 — MonacoImplementation.injectTypes has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (9 pts), error handling 1 (3 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ThemeManager.loadBuiltInThemes (cognitive 16) · ×1
  • ThemeManager.loadBuiltInThemes (cognitive 16) CodeApp/Managers/ThemeManager.swift:46 — ThemeManager.loadBuiltInThemes has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (9 pts), boolean chains 6, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TopBar.body (cognitive 16) · ×1
  • TopBar.body (cognitive 16) CodeApp/Views/TopBar.swift:24 — TopBar.body has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11 (12 pts), boolean chains 2, ternaries 2 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D3 · God Classes · FunctionTooLong · ×1
  • FunctionTooLong: CodeApp.swift.createCSDK CodeApp/CodeApp.swift:85 — FunctionTooLong — createCSDK runs 104 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 4 over it, 1.04× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D35 · Change Coupling · Change coupling · ×1
  • Change coupling: ExplorerFileTreeSection.swift ↔ FileTreeView.swift CodeApp/Views/ExplorerFileTreeSection.swift:1 — `CodeApp/Views/ExplorerFileTreeSection.swift` and `CodeApp/Views/FileTreeView.swift` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `4a476e62` filetree: context menu at root; `4d0a8c4b` Remove unused code and comments; `d5b463e2` filetree: drop to root — run `git show` on any of them.
D4 · Code Duplication · Edited copy of a member (36 corresponding lines) · ×1
  • Edited copy of a member (36 corresponding lines) CodeApp/Managers/FileSystem/SFTP/SFTPFileSystemProvider.swift:115 — CodeApp/Managers/FileSystem/SFTP/SFTPFileSystemProvider.swift:115-171 | CodeApp/Managers/FileSystem/SFTP/SFTPTerminalServiceProvider.swift:40-93 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (32 corresponding lines) · ×1
  • Edited copy of a member (32 corresponding lines) Extensions/MonacoEditor/Views/VimKeyBufferLabel.swift:14 — Extensions/MonacoEditor/Views/VimKeyBufferLabel.swift:14-45 | Extensions/MonacoEditor/Views/VimModeLabel.swift:16-47 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (20 corresponding lines) · ×1
  • Edited copy of a member (20 corresponding lines) CodeApp/Views/ActivityBar.swift:17 — CodeApp/Views/ActivityBar.swift:17-40 | CodeApp/Views/ActivityBar.swift:46-65 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (21 corresponding lines) · ×1
  • Edited copy of a member (21 corresponding lines) SwiftGit2/SwiftGit2/Repository.swift:739 — SwiftGit2/SwiftGit2/Repository.swift:739-760 | SwiftGit2/SwiftGit2/Repository.swift:777-797 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (25 corresponding lines) · ×1
  • Edited copy of a member (25 corresponding lines) CodeApp/Containers/SourceControlContainer.swift:332 — CodeApp/Containers/SourceControlContainer.swift:332-356 | CodeApp/Containers/SourceControlContainer.swift:390-414 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 19+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 19+ corresponding lines) CodeApp/Managers/FileSystem/WorkSpaceStorage.swift:463 — CodeApp/Managers/FileSystem/WorkSpaceStorage.swift:463-482 | CodeApp/Managers/FileSystem/WorkSpaceStorage.swift:514-532 | CodeApp/Managers/FileSystem/WorkSpaceStorage.swift:577-599 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 19 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (19 corresponding lines) · ×1
  • Edited copy of a member (19 corresponding lines) CodeApp/Views/SourceControlAuthenticationConfiguration.swift:354 — CodeApp/Views/SourceControlAuthenticationConfiguration.swift:354-376 | CodeApp/Views/SourceControlAuthenticationConfiguration.swift:388-406 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (14 corresponding lines) · ×1
  • Edited copy of a member (14 corresponding lines) SwiftGit2/SwiftGit2/Repository.swift:720 — SwiftGit2/SwiftGit2/Repository.swift:720-733 | SwiftGit2/SwiftGit2/Repository.swift:762-775 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 17+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 17+ corresponding lines) CodeApp/Containers/SourceControlContainer.swift:100 — CodeApp/Containers/SourceControlContainer.swift:100-118 | CodeApp/Containers/SourceControlContainer.swift:285-302 | CodeApp/Containers/SourceControlContainer.swift:416-432 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (10 corresponding lines) · ×1
  • Edited copy of a member (10 corresponding lines) SwiftGit2/SwiftGit2/Repository.swift:997 — SwiftGit2/SwiftGit2/Repository.swift:997-1008 | SwiftGit2/SwiftGit2/Repository.swift:1054-1063 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 13+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 13+ corresponding lines) CodeApp/Managers/FileSystem/WorkSpaceStorage.swift:484 — CodeApp/Managers/FileSystem/WorkSpaceStorage.swift:484-500 | CodeApp/Managers/FileSystem/WorkSpaceStorage.swift:616-630 | CodeApp/Managers/FileSystem/WorkSpaceStorage.swift:632-644 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 8+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 8+ corresponding lines) CodeApp/Managers/NotificationManager.swift:14 — CodeApp/Managers/NotificationManager.swift:14-22 | CodeApp/Managers/NotificationManager.swift:93-100 | CodeApp/Managers/NotificationManager.swift:102-110 | CodeApp/Managers/NotificationManager.swift:112-119 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (11 corresponding lines) · ×1
  • Edited copy of a member (11 corresponding lines) SwiftGit2/SwiftGit2/Repository.swift:31 — SwiftGit2/SwiftGit2/Repository.swift:31-41 | SwiftGit2/SwiftGit2/Repository.swift:134-148 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (16 corresponding lines) · ×1
  • Edited copy of a member (16 corresponding lines) Extensions/ImageEditor/ImageEditorExtension.swift:39 — Extensions/ImageEditor/ImageEditorExtension.swift:39-54 | Extensions/ImageViewer/ImageViewerExtension.swift:38-53 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 7+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 7+ corresponding lines) SwiftGit2/SwiftGit2/Repository.swift:1069 — SwiftGit2/SwiftGit2/Repository.swift:1069-1076 | SwiftGit2/SwiftGit2/Repository.swift:1082-1088 | SwiftGit2/SwiftGit2/Repository.swift:1095-1104 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (15 corresponding lines) · ×1
  • Edited copy of a member (15 corresponding lines) CodeApp/Containers/SourceControlContainer.swift:120 — CodeApp/Containers/SourceControlContainer.swift:120-136 | CodeApp/Containers/SourceControlContainer.swift:201-215 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 11+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 11+ corresponding lines) CodeApp/Views/SourceControlAuthenticationConfiguration.swift:444 — CodeApp/Views/SourceControlAuthenticationConfiguration.swift:444-454 | CodeApp/Views/SourceControlAuthenticationConfiguration.swift:456-468 | CodeApp/Views/SourceControlAuthenticationConfiguration.swift:470-482 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (6 members, 11+ corresponding lines) · ×1
  • Edited copies of one member (6 members, 11+ corresponding lines) CodeApp/Managers/FileSystem/WorkSpaceStorage.swift:662 — CodeApp/Managers/FileSystem/WorkSpaceStorage.swift:662-672 | CodeApp/Managers/FileSystem/WorkSpaceStorage.swift:682-694 | CodeApp/Managers/FileSystem/WorkSpaceStorage.swift:696-706 | CodeApp/Managers/FileSystem/WorkSpaceStorage.swift:708-718 | CodeApp/Managers/FileSystem/WorkSpaceStorage.swift:732-742 | CodeApp/Managers/FileSystem/WorkSpaceStorage.swift:744-754 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (8 corresponding lines) · ×1
  • Edited copy of a member (8 corresponding lines) Extensions/MonacoLanguageService/MonacoIntellisenseExtension.swift:11 — Extensions/MonacoLanguageService/MonacoIntellisenseExtension.swift:11-18 | Extensions/TerminalService/TerminalExtension.swift:11-18 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (36 lines × 2) · ×1
  • Duplicated block (36 lines × 2) CodeApp/Managers/FileSystem/SFTP/SFTPFileSystemProvider.swift:126 — CodeApp/Managers/FileSystem/SFTP/SFTPFileSystemProvider.swift:126-161 | CodeApp/Managers/FileSystem/SFTP/SFTPTerminalServiceProvider.swift:43-78 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `CodeApp/Managers/FileSystem/SFTP/SFTPFileSystemProvider.swift:126` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (16–17 lines × 2) · ×1
  • Duplicated block (16–17 lines × 2) CodeApp/Utilities/wasm.swift:432 — CodeApp/Utilities/wasm.swift:432-448 | CodeApp/Utilities/wasm.swift:471-486 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `CodeApp/Utilities/wasm.swift:432` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (17 lines × 2) · ×1
  • Duplicated block (17 lines × 2) CodeApp/Views/ExplorerFileTreeSection.swift:145 — CodeApp/Views/ExplorerFileTreeSection.swift:145-161 | CodeApp/Views/ExplorerFileTreeSection.swift:163-179 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `CodeApp/Views/ExplorerFileTreeSection.swift:145` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (12–17 lines × 2) · ×1
  • Duplicated block (12–17 lines × 2) SwiftGit2/SwiftGit2/Repository.swift:88 — SwiftGit2/SwiftGit2/Repository.swift:88-104 | SwiftGit2/SwiftGit2/Repository.swift:165-176 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `SwiftGit2/SwiftGit2/Repository.swift:88` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. Note first that the copies are not typed on the same thing: the declarations holding them bind `credentials` to `Credentials` in one and `Credentials = .default` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (15 lines × 3) · ×1
  • Duplicated block (15 lines × 3) CodeApp/Managers/TerminalInstance.swift:257 — CodeApp/Managers/TerminalInstance.swift:257-271 | CodeApp/Managers/TerminalInstance.swift:281-295 | CodeApp/Managers/TerminalInstance.swift:428-442 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `CodeApp/Managers/TerminalInstance.swift:257` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (12–14 lines × 2) · ×1
  • Duplicated block (12–14 lines × 2) CodeApp/Managers/TerminalInstance.swift:325 — CodeApp/Managers/TerminalInstance.swift:325-338 | CodeApp/Managers/TerminalInstance.swift:545-556 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `CodeApp/Managers/TerminalInstance.swift:325` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (12–13 lines × 2) · ×1
  • Duplicated block (12–13 lines × 2) CodeApp/CodeApp.swift:101 — CodeApp/CodeApp.swift:101-112 | CodeApp/CodeApp.swift:114-126 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (15 lines × 2) · ×1
  • Duplicated block (15 lines × 2) CodeApp/CodeApp.swift:239 — CodeApp/CodeApp.swift:239-253 | NodeExtension/System.swift:45-59 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Duplicated block (10–12 lines × 2) · ×1
  • Duplicated block (10–12 lines × 2) CodeApp/Containers/SourceControlContainer.swift:84 — CodeApp/Containers/SourceControlContainer.swift:84-93 | CodeApp/Containers/SourceControlContainer.swift:183-194 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `CodeApp/Containers/SourceControlContainer.swift:84` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (11–12 lines × 2) · ×1
  • Duplicated block (11–12 lines × 2) CodeApp/Views/SettingsThemeConfiguration.swift:26 — CodeApp/Views/SettingsThemeConfiguration.swift:26-37 | CodeApp/Views/SettingsThemeConfiguration.swift:47-57 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `CodeApp/Views/SettingsThemeConfiguration.swift:26` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×1
  • Duplicated block (12 lines × 2) Extensions/MonacoEditor/Views/VimKeyBufferLabel.swift:16 — Extensions/MonacoEditor/Views/VimKeyBufferLabel.swift:16-27 | Extensions/MonacoEditor/Views/VimModeLabel.swift:18-29 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Extensions/MonacoEditor/Views/VimKeyBufferLabel.swift:16` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×1
  • Duplicated block (11 lines × 2) Extensions/MonacoEditor/Views/VimKeyBufferLabel.swift:31 — Extensions/MonacoEditor/Views/VimKeyBufferLabel.swift:31-41 | Extensions/MonacoEditor/Views/VimModeLabel.swift:33-43 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Extensions/MonacoEditor/Views/VimKeyBufferLabel.swift:31` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (7–8 lines × 2) · ×1
  • Duplicated block (7–8 lines × 2) CodeApp/Managers/NotificationManager.swift:28 — CodeApp/Managers/NotificationManager.swift:28-34 | CodeApp/Managers/NotificationManager.swift:46-53 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `CodeApp/Managers/NotificationManager.swift:28` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×1
  • Duplicated block (7 lines × 2) CodeApp/Views/CompactSidebar.swift:33 — CodeApp/Views/CompactSidebar.swift:33-42 | CodeApp/Views/TopBar.swift:31-37 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `CodeApp/Views/CompactSidebar.swift:33` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (6 lines × 3) · ×1
  • Duplicated block (6 lines × 3) CodeApp/Views/CompactSidebar.swift:37 — CodeApp/Views/CompactSidebar.swift:37-47 | CodeApp/Views/TopBar.swift:35-40 | CodeApp/Views/TopBar.swift:226-231 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `CodeApp/Views/CompactSidebar.swift:37` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (5 lines × 3) · ×1
  • Duplicated block (5 lines × 3) CodeApp/Containers/ExplorerContainer.swift:33 — CodeApp/Containers/ExplorerContainer.swift:33-38 | CodeApp/Managers/TerminalInstance.swift:218-222 | CodeApp/Utilities/file/openFilesApp.swift:11-16 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
X3 · Exception handling · Swallowed exception (empty catch) · ×1
  • Swallowed exception (empty catch) CodeApp/Utilities/wasm.swift:196 — 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.
Minor — 29 finding(s)
X7 · Silent fallback defaults · Silent fallback default on parse failure · ×8
  • Silent fallback default on parse failure LanguageResources/Library/lib/python3.9/_pydecimal.py:2912 — `adjusted` returns `0` when `TypeError` is raised, with no log or raise — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
  • Silent fallback default on parse failure LanguageResources/Library/lib/python3.9/fileinput.py:384 — `fileno` returns `-1` when `ValueError` is raised, with no log or raise — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
  • Silent fallback default on parse failure LanguageResources/Library/lib/python3.9/genericpath.py:31 — `isfile` returns `False` when `(OSError, ValueError)` is raised, with no log or raise — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
  • Silent fallback default on parse failure LanguageResources/Library/lib/python3.9/genericpath.py:43 — `isdir` returns `False` when `(OSError, ValueError)` is raised, with no log or raise — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
  • Silent fallback default on parse failure LanguageResources/Library/lib/python3.9/http/server.py:946 — `nobody_uid` returns `-1` when `ImportError` is raised, with no log or raise — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
  • Silent fallback default on parse failure LanguageResources/Library/lib/python3.9/ntpath.py:234 — `islink` returns `False` when `(OSError, ValueError, AttributeError)` is raised, with no log or raise — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
  • Silent fallback default on parse failure LanguageResources/Library/lib/python3.9/posixpath.py:168 — `islink` returns `False` when `(OSError, ValueError, AttributeError)` is raised, with no log or raise — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
  • Silent fallback default on parse failure LanguageResources/Library/lib/python3.9/test/test_importlib/fixtures.py:218 — `unicode_filename` returns `'☃'` when `ImportError` is raised, with no log or raise — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
X7 · Silent fallback defaults · Silent fallback default in catch · ×8
  • Silent fallback default in catch LanguageResources/Library/lib/python3.9/idlelib/calltip.py:166 — `get_argspec` swallows every exception into `return ''` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
  • Silent fallback default in catch LanguageResources/Library/lib/python3.9/rlcompleter.py:149 — `attr_matches` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
  • Silent fallback default in catch LanguageResources/Library/lib/python3.9/xml/sax/expatreader.py:421 — `external_entity_ref` swallows every exception into `return 0` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
  • Silent fallback default in catch LanguageResources/Library/lib/python3.9/zoneinfo/_tzpath.py:133 — `valid_key` (in `available_timezones`) swallows every exception into `return False` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
  • Silent fallback default in catch REDACTED:192 — `onRequestInteractiveKeyboard` turns every thrown error into `""` — a data error becomes a silent behavior change with no trail. Log the error or let it propagate (`throws`). If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch`, `guard` or `??`, or in the doc comment, and the row stops firing.
  • Silent fallback default in catch CodeApp/Managers/EditorImplementation/MonacoImplementation.swift:568 — `_getMonacoActions` turns every thrown error into `[]` — a data error becomes a silent behavior change with no trail. Log the error or let it propagate (`throws`). If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch`, `guard` or `??`, or in the doc comment, and the row stops firing.
  • Silent fallback default in catch CodeApp/Types/Shared/AppExtensionError.swift:15 — `stringRepresentation` turns every thrown error into `"{}"` — a data error becomes a silent behavior change with no trail. Log the error or let it propagate (`throws`). If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch`, `guard` or `??`, or in the doc comment, and the row stops firing.
  • Silent fallback default in catch Extensions/RemoteExecution/CloudCodeExecutionManager.swift:164 — `generateJavaParameters` turns every thrown error into `[:]` — a data error becomes a silent behavior change with no trail. Log the error or let it propagate (`throws`). If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch`, `guard` or `??`, or in the doc comment, and the row stops firing.
D30 · Dependency Vulnerabilities · Low CVE · ×3
  • REDACTED
  • REDACTED
  • REDACTED
X10 · Duplicated predicate · Duplicated predicate · ×2
  • Duplicated predicate CodeApp/Views/EditorKeyboardToolBar.swift:45 — `UIPasteboard.general.hasStrings || pasteBoardHasContent` appears character-identically in 2 files — CodeApp/Views/EditorKeyboardToolBar.swift, CodeApp/Views/TerminalKeyboardToolbar.swift. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate CodeApp/Managers/FileSystem/SFTP/SFTPFileSystemProvider.swift:158 — `self.session.isConnected && self.session.isAuthorized` appears character-identically in 2 files — CodeApp/Managers/FileSystem/SFTP/SFTPFileSystemProvider.swift, CodeApp/Managers/FileSystem/SFTP/SFTPTerminalServiceProvider.swift. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
D20 · ADR Quality · No ADRs found · ×1
  • No ADRs found Code.xcodeproj/project.pbxproj:1 — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `Code.xcodeproj/project.pbxproj` makes this repository a deployable product (line 1).
D21 · Naming Consistency · `__sFILE` spells `FILE` where 59 names in the project spell it `File` · ×1
  • `__sFILE` spells `FILE` where 59 names in the project spell it `File` LanguageResources/Library/lib/python3.9/lib2to3/tests/data/infinite_recursion.py:2032 — 59 of 60 names in project python spell the token `File` (59 of 60; unit: names in project python containing `File`). Peers: LanguageResources.ClangLib.usr.share.mk.meta2deps.MetaFile (LanguageResources/ClangLib/usr/share/mk/meta2deps.py:171); LanguageResources.Library.lib.python3.9.bz2.BZ2File (LanguageResources/Library/lib/python3.9/bz2.py:27); codecs.EncodedFile (LanguageResources/Library/lib/python3.9/codecs.py:919); LanguageResources.Library.lib.python3.9.distutils.errors.DistutilsFileError (LanguageResources/Library/lib/python3.9/distutils/errors.py:36); LanguageResources.Library.lib.python3.9.distutils.errors.UnknownFileError (LanguageResources/Library/lib/python3.9/distutils/errors.py:96). Rename to `__sFile`. [rule N6]
D26 · Project Cohesion · Projects may be oversized for their cohesion · ×1
  • Projects may be oversized for their cohesion — 1 of 3 project(s) overshoot their size bounds, lowering Project Cohesion to 3.3/10. The most over is `(repository root)` (20590 LoC, 3346 module-visible types across 83 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
M2 · Architecture documentation · No ADRs · ×1
  • No ADRs — 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.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST REDACTED:3 — No static application security testing detected. For this repository's stack, add CodeQL's Swift pack (Swift/Xcode) (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 3 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.
P3 · Security & performance tooling · No dependency-update automation · ×1
  • No dependency-update automation Dependencies/npm.bundle/package.json:2 — `Dependencies/npm.bundle/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`.
P6 · Release Hygiene · Changelog looks stale/thin · ×1
  • Changelog looks stale/thin — The changelog this check read carries 0 versioned entries, against a bar of 3. Counted as either the distinct `x.y.z` versions it names (a link's target is not counted) or its version-shaped section headings (`## [1.2.0]`, `## V14.x.x`, `## Updates in 8.0.x`), whichever is the larger — so a log sectioned by minor series counts its sections, not its individual patch numbers. Entries recorded somewhere this check does not read — release notes generated at tag time from a generator config it did not recognise, or a log kept outside the repository — are not counted here, and this row is about what is re-findable in the tree rather than about how often you release.
Minor — 11 finding(s)
D12 · Dependency Hygiene · Outdated · ×11
  • Outdated: cwlcatchexception — `cwlcatchexception` is resolved at 2.1.1, but 2.2.1 is the newest release tagged on https://github.com/mattgallagher/CwlCatchException.git within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update cwlcatchexception` reaches this one with no change to Package.swift.
  • Outdated: cwlpreconditiontesting — `cwlpreconditiontesting` is resolved at 2.1.0, but 2.2.2 is the newest release tagged on https://github.com/mattgallagher/CwlPreconditionTesting.git within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update cwlpreconditiontesting` reaches this one with no change to Package.swift.
  • Outdated: swift-atomics — `swift-atomics` is resolved at 1.2.0, but 1.3.1 is the newest release tagged on https://github.com/apple/swift-atomics.git within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update swift-atomics` reaches this one with no change to Package.swift.
  • Outdated: swift-collections — `swift-collections` is resolved at 1.1.2, but 1.7.6 is the newest release tagged on https://github.com/apple/swift-collections.git within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update swift-collections` reaches this one with no change to Package.swift.
  • Outdated: swift-nio — `swift-nio` is resolved at 2.68.0, but 2.105.0 is the newest release tagged on https://github.com/apple/swift-nio.git within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update swift-nio` reaches this one with no change to Package.swift.
  • Outdated: swift-nio — `swift-nio` is resolved at 2.69.0, but 2.105.0 is the newest release tagged on https://github.com/apple/swift-nio.git within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update swift-nio` reaches this one with no change to Package.swift.
  • Outdated: swift-nio-transport-services — `swift-nio-transport-services` is resolved at 1.21.0, but 1.28.0 is the newest release tagged on https://github.com/apple/swift-nio-transport-services within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update swift-nio-transport-services` reaches this one with no change to Package.swift.
  • Outdated: swift-system — `swift-system` is resolved at 1.3.2, but 1.9.0 is the newest release tagged on https://github.com/apple/swift-system.git within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update swift-system` reaches this one with no change to Package.swift.
  • Outdated: tree-sitter — `tree-sitter` is resolved at 0.20.9, but 0.27.2 is the newest release tagged on https://github.com/tree-sitter/tree-sitter within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update tree-sitter` reaches this one with no change to Package.swift.
  • Outdated: ziparchive — `ziparchive` is resolved at 2.4.3, but 2.6.0 is the newest release tagged on https://github.com/ZipArchive/ZipArchive.git within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update ziparchive` reaches this one with no change to Package.swift.
  • Outdated: zipfoundation — `zipfoundation` is resolved at 0.9.15, but 0.9.20 is the newest release tagged on https://github.com/weichsel/ZIPFoundation.git within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update zipfoundation` reaches this one with no change to Package.swift.

Appendix B — Reproduction & audit trail

Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-cc1cd8c80e6349248d7afe66ea2734e4/history.json --exit-code 0 --source .1artifacts/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-cc1cd8c80e6349248d7afe66ea2734e4/tree.json --exit-code 0 --source .1artifacts/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 --exclude Dependencies/npm.bundle/node_modules/.bin --exclude Dependencies/npm.bundle/node_modules/npm/bin --exclude Dependencies/npm.bundle/node_modules/npm/docs --exclude Dependencies/npm.bundle/node_modules/npm/lib --exclude Dependencies/npm.bundle/node_modules/npm/man --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/.bin --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/@gar --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/@isaacs --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/@npmcli --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/@tootallnate --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/abbrev --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/agent-base --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/agentkeepalive --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/aggregate-error --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/ajv --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/ansi-regex --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/ansi-styles --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/ansicolors --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/ansistyles --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/aproba --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/archy --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/are-we-there-yet --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/asap --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/asn1 --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/assert-plus --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/asynckit --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/aws-sign2 --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/balanced-match --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/bcrypt-pbkdf --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/bin-links --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/binary-extensions --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/brace-expansion --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/builtins --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/cacache --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/caseless --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/chalk --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/chownr --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/cidr-regex --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/clean-stack --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/cli-columns --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/cli-table3 --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/clone --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/cmd-shim --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/code-point-at --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/color-convert --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/color-name --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/color-support --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/colors --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/columnify --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/combined-stream --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/common-ancestor-path --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/concat-map --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/console-control-strings --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/core-util-is --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/dashdash --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/debug --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/debuglog --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/defaults --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/delayed-stream --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/delegates --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/depd --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/dezalgo --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/diff --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/ecc-jsbn --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/emoji-regex --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/encoding --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/env-paths --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/err-code --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/extend --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/extsprintf --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/fast-deep-equal --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/fast-json-stable-stringify/benchmark --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/fast-json-stable-stringify/example --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/fast-json-stable-stringify/test --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/fastest-levenshtein --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/forever-agent --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/form-data --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/fs-minipass --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/fs.realpath --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/function-bind --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/gauge --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/getpass --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/glob --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/graceful-fs --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/har-schema --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/har-validator --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/has --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/has-flag --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/has-unicode --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/hosted-git-info --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/http-cache-semantics --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/http-proxy-agent --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/http-signature --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/https-proxy-agent --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/humanize-ms --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/iconv-lite --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/ignore-walk --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/imurmurhash --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/indent-string --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/infer-owner --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/inflight --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/inherits --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/ini --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/init-package-json --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/ip --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/ip-regex --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/is-cidr --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/is-core-module --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/is-fullwidth-code-point --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/is-lambda --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/is-typedarray --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/isarray --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/isexe --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/isstream --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/jsbn --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/json-parse-even-better-errors --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/json-schema --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/json-schema-traverse --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/json-stringify-nice --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/json-stringify-safe --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/jsonparse --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/jsprim --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/just-diff --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/just-diff-apply --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/libnpmaccess --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/libnpmdiff --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/libnpmexec --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/libnpmfund --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/libnpmhook --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/libnpmorg --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/libnpmpack --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/libnpmpublish --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/libnpmsearch --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/libnpmteam --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/libnpmversion --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/lru-cache --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/make-fetch-happen --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/mime-db --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/mime-types --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/minimatch --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/minipass --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/minipass-collect --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/minipass-fetch --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/minipass-flush --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/minipass-json-stream --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/minipass-pipeline --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/minipass-sized --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/minizlib --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/mkdirp --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/mkdirp-infer-owner --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/ms --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/mute-stream --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/negotiator --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/node-gyp/bin --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/node-gyp/docs --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/node-gyp/gyp/data --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/node-gyp/gyp/pylib --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/node-gyp/gyp/tools --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/node-gyp/lib --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/node-gyp/node_modules --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/node-gyp/src --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/node-gyp/test --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/nopt --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/normalize-package-data --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/npm-audit-report --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/npm-bundled --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/npm-install-checks --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/npm-normalize-package-bin --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/npm-package-arg --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/npm-packlist --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/npm-pick-manifest --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/npm-profile --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/npm-registry-fetch --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/npm-user-validate --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/npmlog --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/number-is-nan --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/oauth-sign --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/object-assign --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/once --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/opener --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/p-map --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/pacote --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/parse-conflict-json --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/path-is-absolute --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/path-parse --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/performance-now --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/proc-log --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/process-nextick-args --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/promise-all-reject-late --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/promise-call-limit --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/promise-inflight --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/promise-retry --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/promzard --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/psl --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/punycode --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/qrcode-terminal --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/qs --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/read --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/read-cmd-shim --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/read-package-json --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/read-package-json-fast --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/readable-stream --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/readdir-scoped-modules --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/request --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/resolve --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/retry --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/rimraf --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/safe-buffer --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/safer-buffer --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/semver --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/set-blocking --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/signal-exit --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/smart-buffer --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/socks --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/socks-proxy-agent --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/spdx-correct --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/spdx-exceptions --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/spdx-expression-parse --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/spdx-license-ids --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/sshpk --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/ssri --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/string-width --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/string_decoder --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/stringify-package --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/strip-ansi --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/supports-color --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/tar --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/text-table --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/tiny-relative-date --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/treeverse --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/tunnel-agent --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/tweetnacl --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/typedarray-to-buffer --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/unique-filename --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/unique-slug --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/uri-js --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/util-deprecate --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/uuid --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/validate-npm-package-license --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/validate-npm-package-name --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/verror --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/walk-up-path --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/wcwidth --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/which --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/wide-align --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/wrappy --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/write-file-atomic --exclude Dependencies/npm.bundle/node_modules/npm/node_modules/yallist --exclude Dependencies/terminal.bundle --exclude LanguageResources/ClangLib/node_modules/@wasmer/wasi/lib --exclude LanguageResources/ClangLib/node_modules/@wasmer/wasi/node_modules/path-browserify/test --exclude LanguageResources/ClangLib/node_modules/@wasmer/wasm-transformer --exclude LanguageResources/ClangLib/node_modules/@wasmer/wasmfs --exclude LanguageResources/ClangLib/node_modules/base64-js --exclude LanguageResources/ClangLib/node_modules/buffer --exclude LanguageResources/ClangLib/node_modules/ieee754 --exclude LanguageResources/ClangLib/node_modules/isarray --exclude LanguageResources/ClangLib/node_modules/path-browserify --exclude LanguageResources/ClangLib/node_modules/process --exclude LanguageResources/ClangLib/node_modules/randombytes --exclude LanguageResources/ClangLib/node_modules/randomfill --exclude LanguageResources/ClangLib/node_modules/safe-buffer --exclude LanguageResources/ClangLib/usr --exclude LanguageResources/Library .5artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .29artifacts/raw/trivy-fs.json
D31 · IaC & Container Securitytrivy—trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.0—
D32 · Data Compliance (PII/GDPR)semgrep—semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 6 file(s) — `CodeApp/Managers/AppExtensionService.swift`, `CodeApp/Managers/FileSystem/Local/LocalGitCredentialsHelper.swift`, `CodeApp/Managers/FileSystem/WorkSpaceStorage.swift`, `CodeApp/Managers/SearchManager.swift`, `CodeApp/Managers/TerminalInstance.swift`, … (+1 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.0—
D37 · Vulnerability-disclosure Policydisclosure—disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.0—
D40 · Network Egress Confinementruntime-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 Confinementruntime-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 Enforcementruntime-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 Dependenciestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .0artifacts/raw/trivy-fs.json

Run 01a1dc34-516c-7083-8d73-123228266ba1 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Downloadable artifacts

Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.

⬇ Findings, MITRE CWE-tagged .sarif⬇ Health changelog .md