Public report of Ranchero-Software/NetNewsWire, 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, 08:43 UTC · Survey ID cd_e578e86e9538421b9e7dc4a7767f95bb

Ranchero-Software/NetNewsWire

Measured 14 November 2026, 08:42 UTC, at code version 7908c80

CAI score 31out of 100 Weak
CriticalWeakAdequateStrongExemplary
Down 9 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: 82,944 lines of product code in 23 projects, tests not counted · Estimated rebuild effort: about 0.6 person-years · Weakest lens: Security and Compliance, 22

Findings by how serious they are

36 critical 222 serious 466 minor

23 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, 08:42 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.

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 ▸

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

Executive summary

Ranchero-Software/NetNewsWire falls short of our standard for production, in part because it has pipeline tools referenced by a changeable name. It scores 31 out of 100 and is rated Weak, and 12 of its 36 critical findings are security problems.

Security and Compliance, at 22, is the weakest lens and counts most in the score. The best first step is replacing the six passwords or keys found in the code's history, worth about 4 points. Fixing the place where the code runs text as code or as a command would lift Security and Compliance itself, worth about 2 points. Raising Security and Compliance to 70 would lift the score to about 38.

Six passwords or keys are open to anyone who can read the repository. Five pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and fifteen images have no description for people who can't see them. Replacing each exposed password or key, pinning each tool to an exact version and describing the images would close these risks. The place where the code runs text as code or as a command needs a direct call instead. The four sets of files in separate parts that keep changing together need that dependency made explicit.

The product code is 82,944 lines, about €81,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.
Security and Compliance 22 · counts for 46%Accessibility 26 · counts for 25%Code Health 38 · counts for 14%Maturity 39 · counts for 8%Production Readiness 55 · counts for 4%Architecture 98 · counts for 2%Performance 100 · counts for 1%

If Security and Compliance rose from 22 to 70, the lowest score rated Strong, the score would rise from 31 to about 38.

Code composition: what the lines of code are
Product code 88%Tests 12%
New since the last survey: 83 findings

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

  • Cyclomatic Complexity · DownloadedImageCache.revalidateIfDue (cyclomatic 18) Modules/Images/Sources/Images/DownloadedImageCache.swift
  • Cognitive Complexity · ImageParserDelegate.preferredSrcsetCandidate (cognitive 19) Modules/RSParser/Sources/RSParser/HTML/HTMLImageParser.swift
  • Cognitive Complexity · DownloadedImageCache.revalidateIfDue (cognitive 18) Modules/Images/Sources/Images/DownloadedImageCache.swift
  • Cognitive Complexity · DownloadedImageCache.downloadImageFromNetwork (cognitive 17) Modules/Images/Sources/Images/DownloadedImageCache.swift
  • God Classes · TooManyMethods: DownloadedImageCache Modules/Images/Sources/Images/DownloadedImageCache.swift
  • Code Duplication · Edited copy of a member (71 corresponding lines) Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift
  • Code Duplication · Edited copy of a member (24 corresponding lines) Modules/RSParser/Sources/RSParser/Utilities/DateParser.swift
  • Code Duplication · Edited copy of a member (33 corresponding lines) Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift
  • Code Duplication · Edited copy of a member (20 corresponding lines) Modules/ActivityLog/Sources/ActivityLog/ActivityLog.swift
  • Code Duplication · Edited copy of a member (6 corresponding lines) Modules/Images/Sources/Images/FaviconDownloader.swift
  • Code Duplication · Edited copies of one member (4 members, 17+ corresponding lines) Modules/Images/Sources/Images/DownloadFailureTable.swift
  • Code Duplication · Edited copies of one member (3 members, 6+ corresponding lines) Modules/Images/Sources/Images/ArticleThumbnailFinder.swift
  • Code Duplication · Edited copy of a member (37 corresponding lines) Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift
  • Code Duplication · Edited copy of a member (22 corresponding lines) Modules/RSCore/Sources/RSCore/String+RSCore.swift
  • Code Duplication · Edited copy of a member (22 corresponding lines) Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift
  • Code Duplication · Edited copy of a member (12 corresponding lines) Modules/RSCore/Sources/RSCore/String+RSCore.swift
  • Code Duplication · Edited copy of a member (19 corresponding lines) Modules/RSCore/Sources/RSCore/AppKit/MultilineTextFieldSizer.swift
  • Code Duplication · Edited copy of a member (9 corresponding lines) Modules/RSCore/Sources/RSCore/String+RSCore.swift
  • Code Duplication · Edited copy of a member (12 corresponding lines) Modules/RSCore/Sources/RSCore/Comparing.swift
  • Code Duplication · Edited copy of a member (16 corresponding lines) Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift
  • Code Duplication · Edited copy of a member (11 corresponding lines) Modules/ActivityLog/Sources/ActivityLog/ActivityLog.swift
  • Code Duplication · Edited copies of one member (3 members, 4+ corresponding lines) Modules/HTMLMetadata/Sources/HTMLMetadata/HTMLMetadataDownloader.swift
  • Code Duplication · Edited copy of a member (13 corresponding lines) Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift
  • Code Duplication · Edited copy of a member (3 corresponding lines) Modules/RSParser/Sources/RSParser/Utilities/DateParser.swift
  • Code Duplication · Edited copy of a member (9 corresponding lines) Modules/RSCore/Sources/RSCore/AppKit/MultilineTextFieldSizer.swift
  • Code Duplication · Edited copies of one member (3 members, 6+ corresponding lines) Modules/RSCore/Sources/RSCore/AppKit/MultilineTextFieldSizer.swift
  • Code Duplication · Edited copy of a member (4 corresponding lines) Modules/ActivityLog/Sources/ActivityLog/ActivityLog.swift
  • Code Duplication · Edited copies of one member (3 members, 6+ corresponding lines) Modules/Images/Sources/Images/FaviconDownloader.swift
  • Code Duplication · Edited copies of one member (3 members, 8+ corresponding lines) Modules/Images/Sources/Images/FaviconDownloader.swift
  • Code Duplication · Edited copy of a member (11 corresponding lines) Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift
  • Code Duplication · Edited copies of one member (3 members, 7+ corresponding lines) Modules/Images/Sources/Images/DownloadFailureTable.swift
  • Code Duplication · Edited copy of a member (8 corresponding lines) Modules/RSParser/Sources/RSParser/HTML/HTMLAttributes.swift
  • Code Duplication · Edited copy of a member (4 corresponding lines) Modules/HTMLMetadata/Sources/HTMLMetadata/HTMLMetadataTable.swift
  • Code Duplication · Edited copy of a member (3 corresponding lines) Modules/RSCore/Sources/RSCore/AppKit/MultilineTextFieldSizer.swift
  • Code Duplication · Edited copy of a member (8 corresponding lines) Modules/RSDatabase/Sources/RSDatabase/DatabaseQueue.swift
  • Code Duplication · Edited copy of a member (6 corresponding lines) Modules/RSParser/Sources/RSParser/OPML/OPMLFeedSpecifier.swift
  • Code Duplication · Edited copy of a member (4 corresponding lines) Modules/RSCore/Sources/RSCore/StripHTML.swift
  • Code Duplication · Edited copy of a member (4 corresponding lines) Modules/RSCore/Sources/RSCore/AppKit/MultilineTextFieldSizer.swift
  • Code Duplication · Edited copy of a member (9 corresponding lines) Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift
  • Code Duplication · Duplicated block (29–33 lines × 2) Modules/RSCore/Sources/RSCore/AppKit/MultilineTextFieldSizer.swift
  • Code Duplication · Duplicated block (14 lines × 2) Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift
  • Code Duplication · Duplicated block (9 lines × 2) Modules/Images/Sources/Images/HomePageFaviconTable.swift
  • Test Quality · No assertions: testRowHeightsCold Tests/NetNewsWireTests/TimelineRowHeightPerformanceTests.swift
  • Test Quality · No assertions: testRowHeightsWarm Tests/NetNewsWireTests/TimelineRowHeightPerformanceTests.swift
  • Churn × Complexity Hotspots · Hotspot: Modules/Images/Sources/Images/DownloadedImageCache.swift Modules/Images/Sources/Images/DownloadedImageCache.swift
  • Churn × Complexity Hotspots · Hotspot: iOS/MainTimeline/MainTimelineViewController.swift iOS/MainTimeline/MainTimelineViewController.swift
  • Churn × Complexity Hotspots · Hotspot: Shared/Article Rendering/ArticleRenderer.swift Shared/Article Rendering/ArticleRenderer.swift
  • Churn × Complexity Hotspots · Hotspot: Modules/RSWeb/Sources/RSWeb/Downloader.swift Modules/RSWeb/Sources/RSWeb/Downloader.swift
  • Static Analysis (SAST) · REDACTED
  • Change Coupling · Boundary-crossing change coupling: Package.swift ↔ Package.swift Modules/Account/Package.swift
  • Change Coupling · Boundary-crossing change coupling: Package.swift ↔ Package.swift Modules/Articles/Package.swift
  • Change Coupling · Boundary-crossing change coupling: Package.swift ↔ Package.swift Modules/ArticlesDatabase/Package.swift
  • Change Coupling · Boundary-crossing change coupling: Package.swift ↔ Package.swift Modules/ArticlesDatabase/Package.swift
  • Change Coupling · Change coupling: AppDefaults.swift ↔ AppNotifications.swift Shared/AppDefaults.swift
  • Exception handling · Swallowed exception (caught, then discarded) Modules/Images/Sources/Images/DownloadedImageCache.swift
  • Text alternatives · <img> without a text alternative Themes/Appanoose.nnwtheme/template7.3.html
  • Text alternatives · <img> without a text alternative Themes/Biblioteca.nnwtheme/template7.3.html
  • Text alternatives · <img> without a text alternative Themes/Hyperlegible.nnwtheme/template7.3.html
  • Text alternatives · <img> without a text alternative Themes/Promenade.nnwtheme/template7.3.html
  • Text alternatives · <img> without a text alternative Themes/Sepia.nnwtheme/template7.3.html
  • Text alternatives · <img> without a text alternative Themes/Tiqoe Dark.nnwtheme/template7.3.html
  • Text alternatives · <img> without a text alternative Themes/Verdana Revival.nnwtheme/template7.3.html
  • Page structure · Data table has no header cells Themes/Hyperlegible.nnwtheme/template7.3.html
  • Page structure · Data table has no header cells Themes/Sepia.nnwtheme/template7.3.html
  • Page structure · Data table has no header cells Themes/Tiqoe Dark.nnwtheme/template7.3.html
  • Keyboard semantics · Anchor without href Themes/NewsFax.nnwtheme/template7.3.html
  • Visual & motion safety · Low contrast colour pair in CSS (3.1:1) Themes/Verdana Revival.nnwtheme/stylesheet.css
  • Visual & motion safety · Low contrast colour pair in CSS (3.1:1) Themes/Verdana Revival.nnwtheme/stylesheet.css
  • Visual & motion safety · Low contrast colour pair in CSS (4.2:1) Themes/Tiqoe Dark.nnwtheme/stylesheet.css
  • Visual & motion safety · Low contrast colour pair in CSS (2.3:1) Themes/Sepia.nnwtheme/stylesheet.css
  • Visual & motion safety · Low contrast colour pair in CSS (2.3:1) Themes/Promenade.nnwtheme/stylesheet.css
  • Visual & motion safety · Low contrast colour pair in CSS (2.3:1) Themes/Promenade.nnwtheme/stylesheet.css
  • Visual & motion safety · Low contrast colour pair in CSS (3.6:1) Themes/Plum.nnwtheme/stylesheet.css
  • Visual & motion safety · Low contrast colour pair in CSS (2.3:1) Themes/NewsFax.nnwtheme/stylesheet.css
  • Visual & motion safety · Low contrast colour pair in CSS (2.3:1) Themes/NewsFax.nnwtheme/stylesheet.css
  • Visual & motion safety · Low contrast colour pair in CSS (2.3:1) Themes/Hyperlegible.nnwtheme/stylesheet.css
  • Visual & motion safety · Low contrast colour pair in CSS (2.3:1) Themes/Hyperlegible.nnwtheme/stylesheet.css
  • Visual & motion safety · Low contrast colour pair in CSS (3.5:1) Themes/Gray.nnwtheme/stylesheet.css
  • Visual & motion safety · Low contrast colour pair in CSS (2.3:1) Themes/Appanoose.nnwtheme/stylesheet.css
  • Visual & motion safety · Low contrast colour pair in CSS (2.3:1) Themes/Appanoose.nnwtheme/stylesheet.css
  • Visual & motion safety · Low contrast colour pair in CSS (2.3:1) Shared/Article Rendering/stylesheet.css
  • Visual & motion safety · Low contrast colour pair in CSS (2.3:1) Shared/Article Rendering/stylesheet.css
  • Visual & motion safety · Low contrast colour pair in CSS (3.1:1) Shared/Article Rendering/stylesheet.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: 43 findings

These 43 critical or serious findings were in the previous survey, on 26 October 2026, and are gone from this one.

  • Cyclomatic Complexity · RSImage.scaledImageData (cyclomatic 17) Modules/RSCore/Sources/RSCore/RSImage.swift
  • Cognitive Complexity · RSImage.scaledImageData (cognitive 19) Modules/RSCore/Sources/RSCore/RSImage.swift
  • Code Duplication · Duplicated block (29–33 lines × 2) Modules/RSCore/Sources/RSCore/AppKit/MultilineTextFieldSizer.swift
  • Code Duplication · Duplicated block (14 lines × 2) Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift
  • Churn × Complexity Hotspots · Hotspot: Modules/Account/Sources/Account/Feedly/FeedlyAccountDelegate.swift Modules/Account/Sources/Account/Feedly/FeedlyAccountDelegate.swift
  • Churn × Complexity Hotspots · Hotspot: iOS/SceneDelegate.swift iOS/SceneDelegate.swift
  • Churn × Complexity Hotspots · Hotspot: iOS/MainTimeline/Cell/MainTimelineCell.swift iOS/MainTimeline/Cell/MainTimelineCell.swift
  • Churn × Complexity Hotspots · Hotspot: iOS/MainFeed/MainFeedCollectionViewController+Drop.swift iOS/MainFeed/MainFeedCollectionViewController+Drop.swift
  • Churn × Complexity Hotspots · Hotspot: Modules/Images/Sources/Images/FeedIconDownloader.swift Modules/Images/Sources/Images/FeedIconDownloader.swift
  • Churn × Complexity Hotspots · Hotspot: Modules/CloudKitSync/Sources/CloudKitSync/CloudKitZone.swift Modules/CloudKitSync/Sources/CloudKitSync/CloudKitZone.swift
  • Churn × Complexity Hotspots · Repeated repair: iOS/Article/WebViewController.swift iOS/Article/WebViewController.swift
  • Churn × Complexity Hotspots · Repeated repair: iOS/Article/ArticleViewController.swift iOS/Article/ArticleViewController.swift
  • Churn × Complexity Hotspots · Repeated repair: REDACTED REDACTED
  • Churn × Complexity Hotspots · Repeated repair: iOS/RootSplitViewController.swift iOS/RootSplitViewController.swift
  • Churn × Complexity Hotspots · Repeated repair: REDACTED REDACTED
  • Change Coupling · Boundary-crossing change coupling: Package.swift ↔ Package.swift Modules/Account/Package.swift
  • Change Coupling · Boundary-crossing change coupling: Package.swift ↔ Package.swift Modules/Articles/Package.swift
  • Change Coupling · Boundary-crossing change coupling: Package.swift ↔ Package.swift Modules/ArticlesDatabase/Package.swift
  • Change Coupling · Boundary-crossing change coupling: Package.swift ↔ Package.swift Modules/Articles/Package.swift
  • Change Coupling · Boundary-crossing change coupling: Package.swift ↔ Package.swift Modules/Articles/Package.swift
  • Change Coupling · Boundary-crossing change coupling: Package.swift ↔ Package.swift Modules/Secrets/Package.swift
  • Change Coupling · Boundary-crossing change coupling: Package.swift ↔ Package.swift Modules/ArticlesDatabase/Package.swift
  • Change Coupling · Boundary-crossing change coupling: Package.swift ↔ Package.swift Modules/RSCore/Package.swift
  • Change Coupling · Boundary-crossing change coupling: Package.swift ↔ Package.swift Modules/RSWeb/Package.swift
  • Change Coupling · Boundary-crossing change coupling: Package.swift ↔ Package.swift Modules/RSWeb/Package.swift
  • Change Coupling · Boundary-crossing change coupling: Package.swift ↔ Package.swift Modules/ArticlesDatabase/Package.swift
  • Change Coupling · Boundary-crossing change coupling: Package.swift ↔ Package.swift Modules/Articles/Package.swift
  • Change Coupling · Boundary-crossing change coupling: Package.swift ↔ Package.swift Modules/Account/Package.swift
  • Change Coupling · Boundary-crossing change coupling: Package.swift ↔ Package.swift Modules/RSParser/Package.swift
  • Documentation (README) · README may be stale
  • Exception handling · Swallowed exception (empty catch) Modules/Images/Sources/Images/SingleFaviconDownloader.swift
  • Text alternatives · <img> without a text alternative Resources/Themes/Appanoose.nnwtheme/template.html
  • Text alternatives · <img> without a text alternative Resources/Themes/Biblioteca.nnwtheme/template.html
  • Text alternatives · <img> without a text alternative Resources/Themes/Hyperlegible.nnwtheme/template.html
  • Text alternatives · <img> without a text alternative Resources/Themes/Promenade.nnwtheme/template.html
  • Text alternatives · <img> without a text alternative Resources/Themes/Sepia.nnwtheme/template.html
  • Text alternatives · <img> without a text alternative Resources/Themes/Tiqoe Dark.nnwtheme/template.html
  • Text alternatives · <img> without a text alternative Resources/Themes/Verdana Revival.nnwtheme/template.html
  • Page structure · Data table has no header cells Resources/Themes/Hyperlegible.nnwtheme/template.html
  • Page structure · Data table has no header cells Resources/Themes/Sepia.nnwtheme/template.html
  • Page structure · Data table has no header cells Resources/Themes/Tiqoe Dark.nnwtheme/template.html
  • Keyboard semantics · Anchor without href Resources/Themes/NewsFax.nnwtheme/template.html
  • A11y enforcement · Accessibility enforcement below the top rung
Rebuild cost: about €81,000 · Estimate
Cost to rebuild€27,000 to €130,000, for 446 to 1,414 hours of work, about 0.6 person-years for 1 to 2 engineers
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 31. 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: 82,944 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
Resolve the 6 REDACTED finding(s) in Secrets (history) — start with REDACTED (2), REDACTED, REDACTED.
Raises the score by about 4 points · Low effort · Secrets (history)
2
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with project.pbxproj.
Raises the score by about 2 points · Low effort · ADR Quality
3
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED.
Raises the score by about 2 points · Low effort · Static Analysis (SAST)

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 €81,000 to build again, about 0.6 person-years of work. Its weakest lens is Security and Compliance, at 22 (checked 3 of 10). Security and Compliance is about how well the product is protected, and how it handles personal data. Because the weakest lens counts most in the score, work on Security and Compliance also moves the score most.
Based on: the rebuild estimate · the Security and Compliance grade · how much each lens counts
What to do: Start with the Security and Compliance actions in Top priorities.
If you do one thing first · First action
Resolve the 6 REDACTED finding(s) in Secrets (history). Of all the actions in this report, it raises the score most for the work it takes: about 4 points for low effort, because it clears the 6 Secrets (history) findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort

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 Account Account ActivityLog ActivityLog Account->ActivityLog Articles Articles Account->Articles ArticlesDatabase ArticlesDatabase Account->ArticlesDatabase CloudKitSync CloudKitSync Account->CloudKitSync ErrorLog ErrorLog Account->ErrorLog FeedFinder FeedFinder Account->FeedFinder NewsBlur NewsBlur Account->NewsBlur RSCore RSCore Account->RSCore RSDatabase RSDatabase Account->RSDatabase RSParser RSParser Account->RSParser RSWeb RSWeb Account->RSWeb Secrets Secrets Account->Secrets SyncDatabase SyncDatabase Account->SyncDatabase Articles->RSCore ArticlesDatabase->Articles ArticlesDatabase->RSCore ArticlesDatabase->RSDatabase ArticlesDatabase->RSParser CloudKitSync->RSCore ErrorLog->RSCore ErrorLog->RSDatabase FeedFinder->ActivityLog FeedFinder->RSCore FeedFinder->RSParser FeedFinder->RSWeb HTMLMetadata HTMLMetadata HTMLMetadata->ActivityLog HTMLMetadata->RSCore HTMLMetadata->RSDatabase HTMLMetadata->RSParser HTMLMetadata->RSWeb Images Images Images->Account Images->ActivityLog Images->Articles Images->HTMLMetadata Images->RSCore Images->RSDatabase Images->RSParser Images->RSWeb NetNewsWire NetNewsWire NetNewsWire iOS Widget Extension NetNewsWire iOS Widget Extension NewsBlur->RSCore NewsBlur->RSParser NewsBlur->RSWeb NewsBlur->Secrets RSCoreObjC RSCoreObjC RSCore->RSCoreObjC RSDatabaseObjC RSDatabaseObjC RSDatabase->RSDatabaseObjC RSParser->RSCore RSWeb->RSCore RSWeb->RSParser Secrets->ErrorLog Secrets->RSCore SyncDatabase->Articles SyncDatabase->RSCore SyncDatabase->RSDatabase __more__ +3 more projects

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.

30 modules, with 88 dependencies between them. One loop runs through 18 of the modules, marked above the diagonal.

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 Mac.MainWindow.Detail2 Shared.Article Rendering3 Shared.Article Rendering.newsfoot4 Shared.ShareExtension5 Themes.Appanoose_nnwtheme6 Themes.NewsFax_nnwtheme7 buildscripts8 buildscripts.gyb9 iOS.Resources10 iOS.Resources.main_ios11 scripts12 Modules~RSCore~RSCoreResources13 Modules~RSTree~RSTree14 Modules~RSWeb~RSWeb15 Modules~Secrets~Secrets16 Modules~SyncDatabase~SyncDatabase17 Modules~RSDatabase~RSDatabase18 Modules~ErrorLog~ErrorLog19 Modules~Images~Images20 Modules~Articles~Articles21 repository22 Modules~RSParser~RSParser23 Modules~RSCore~RSCore24 Modules~ActivityLog~ActivityLog25 Modules~ArticlesDatabase~ArticlesDatabase26 Modules~CloudKitSync~CloudKitSync27 Modules~FeedFinder~FeedFinder28 Modules~HTMLMetadata~HTMLMetadata29 Modules~NewsBlur~NewsBlur30 Modules~Account~Account
1 Mac.MainWindow.Detail
2 Shared.Article Rendering
3 Shared.Article Rendering.newsfoot
4 Shared.ShareExtension
5 Themes.Appanoose_nnwtheme
6 Themes.NewsFax_nnwtheme
7 buildscripts
8 buildscripts.gyb
9 iOS.Resources
10 iOS.Resources.main_ios
11 scripts
12 Modules~RSCore~RSCoreResources32
13 Modules~RSTree~RSTree12
14 Modules~RSWeb~RSWeb24388
15 Modules~Secrets~Secrets43
16 Modules~SyncDatabase~SyncDatabase3632
17 Modules~RSDatabase~RSDatabase1671
18 Modules~ErrorLog~ErrorLog355
19 Modules~Images~Images562263049
20 Modules~Articles~Articles216385
21 repository123112294023578166
22 Modules~RSParser~RSParser46366
23 Modules~RSCore~RSCore3823
24 Modules~ActivityLog~ActivityLog45
25 Modules~ArticlesDatabase~ArticlesDatabase1448137
26 Modules~CloudKitSync~CloudKitSync333
27 Modules~FeedFinder~FeedFinder24273
28 Modules~HTMLMetadata~HTMLMetadata3629
29 Modules~NewsBlur~NewsBlur110151
30 Modules~Account~Account19151021331351615296713
Uses a module listed above itPart of a loopThe module itself
1 Mac.MainWindow.Detail2 Shared.Article Rendering3 Shared.Article Rendering.newsfoot4 Shared.ShareExtension5 Themes.Appanoose_nnwtheme6 Themes.NewsFax_nnwtheme7 buildscripts8 buildscripts.gyb9 iOS.Resources10 iOS.Resources.main_ios11 scripts12 Modules~RSCore~RSCoreResources13 Modules~RSTree~RSTree14 Modules~RSWeb~RSWeb15 Modules~Secrets~Secrets16 Modules~SyncDatabase~SyncDatabase17 Modules~RSDatabase~RSDatabase18 Modules~ErrorLog~ErrorLog19 Modules~Images~Images20 Modules~Articles~Articles21 repository22 Modules~RSParser~RSParser23 Modules~RSCore~RSCore24 Modules~ActivityLog~ActivityLog25 Modules~ArticlesDatabase~ArticlesDatabase26 Modules~CloudKitSync~CloudKitSync27 Modules~FeedFinder~FeedFinder28 Modules~HTMLMetadata~HTMLMetadata29 Modules~NewsBlur~NewsBlur30 Modules~Account~AccountMac.MainWindow.Detail1Shared.Article Rendering2Shared.Article Rendering.newsfoot3Shared.ShareExtension4Themes.Appanoose_nnwtheme5Themes.NewsFax_nnwtheme6buildscripts7buildscripts.gyb8iOS.Resources9iOS.Resources.main_ios10scripts11Modules~RSCore~RSCoreResources12Modules~RSTree~RSTree13Modules~RSWeb~RSWeb14Modules~Secrets~Secrets15Modules~SyncDatabase~SyncDatabase16Modules~RSDatabase~RSDatabase17Modules~ErrorLog~ErrorLog18Modules~Images~Images19Modules~Articles~Articles20repository21Modules~RSParser~RSParser22Modules~RSCore~RSCore23Modules~ActivityLog~ActivityLog24Modules~ArticlesDatabase~ArticlesDatabase25Modules~CloudKitSync~CloudKitSync26Modules~FeedFinder~FeedFinder27Modules~HTMLMetadata~HTMLMetadata28Modules~NewsBlur~NewsBlur29Modules~Account~Account30321224388433632167135556226304921638512311229402357816646366382345144813733324273362911015119151021331351615296713

At a glance — Code Health · 38% · Weak · gated by R1, R3, X5 ·

At a glance — Architecture · 98% · Exemplary ·

At a glance — Maturity · 39% · Weak · gated by D16, M2, M4 ·

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

At a glance — Security · 22% · Checked 3 of 10 · gated by D29, D36 ·

At a glance — Accessibility · 26% · Weak · gated by AC1, AC4, 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
A05:2025 — Injection436High / Critical
A07:2025 — Authentication Failures7High / Critical
A03:2025 — Software Supply Chain Failures4Medium

Roadmap

Top priorities: Resolve the 6 REDACTED finding(s) in Secrets (history) — start with REDACTED (2), REDACTED, REDACTED; Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href; Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.

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

Do thisHelpsEffortDimension
Resolve the 6 REDACTED finding(s) in Secrets (history) — start with REDACTED (2), REDACTED, REDACTED.+3.6 ptsLowSecrets (history)
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with project.pbxproj.+1.9 ptsLowADR Quality
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED.+1.8 ptsLowStatic Analysis (SAST)
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing.+1.7 ptsLowSupply-chain Provenance & Signing
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing.+1.7 ptsLowSupply-chain Provenance & Signing
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing.+1.7 ptsLowSupply-chain Provenance & Signing
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.+3.2 ptsMediumKeyboard semantics
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.+3.2 ptsMediumVisual & motion safety

File quality

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

FileScoreBandWorst signal
REDACTED4.6MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.6MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.8MixedSecrets (history): REDACTED: REDACTED
Modules/RSCore/Sources/RSCore/Data+RSCore.swift6.3MixedCyclomatic Complexity: Data.isProbablyHTML (cyclomatic 31)
Modules/CloudKitSync/Tests/CloudKitSyncTests/CloudKitSyncTests.swift6.5MixedTest Quality: No assertions (empty test): testExample
REDACTED6.5MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED6.9MixedStatic Analysis (SAST): Medium: REDACTED
Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift7.0MixedCyclomatic Complexity: HTMLScanner.scanAttributeValue (cyclomatic 17)
Modules/RSParser/Tests/RSParserTests/Utilities/DateParserTests.swift7.0MixedTest Quality: No assertions: pubDateStandardForms
Modules/RSParser/Tests/RSParserTests/XML/XMLEncodingTests.swift7.0MixedTest Quality: No assertions: shiftJIS
Modules/ArticlesDatabase/Package.swift7.0MixedChange Coupling: Boundary-crossing change coupling: Package.swift ↔ Package.swift
Modules/RSCore/Sources/RSCore/AppKit/MultilineTextFieldSizer.swift7.0MixedCognitive Complexity: MultilineTextFieldSizer.heightConsideringNeighbors (cognitive 18)
Modules/RSParser/Sources/RSParser/Utilities/DateParser.swift7.1MixedCyclomatic Complexity: DateParser.nextMonthValue (cyclomatic 23)
Modules/RSParser/Tests/RSParserTests/HTML/HTMLMetadataPerformanceTests.swift7.1MixedTest Quality: No assertions: testDaringFireballPerformance
Modules/RSCore/Sources/RSCore/StripHTML.swift7.2MixedCyclomatic Complexity: StripHTML.process (cyclomatic 69)
Modules/RSParser/Sources/RSParser/XML/XMLScanner.swift7.2MixedCyclomatic Complexity: XMLScanner.scanAttributeValue (cyclomatic 19)
Modules/Images/Sources/Images/DownloadedImageCache.swift7.2MixedCyclomatic Complexity: DownloadedImageCache.revalidateIfDue (cyclomatic 18)
Modules/RSParser/Sources/RSParser/HTML/HTMLMetadata.swift7.2MixedCyclomatic Complexity: HTMLMetadata.resolveFeedLinks (cyclomatic 16)
Modules/RSCore/Sources/RSCore/String+RSCore.swift7.2MixedCode Duplication: Edited copy of a member (22 corresponding lines)
Tests/NetNewsWireTests/ArticleStringFormatterPerformanceTests.swift7.2MixedTest Quality: No assertions: testTruncatedFeedName

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 — 36

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 — 222

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 — 466

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

Could not be resolved — 23

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

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 — 54 dimensions across the health lenses
D1D2D3D4D5D6D10D12D13D14D15D16D17D20D21D24D26D27D28D29D30D34D35D36D43AC1AC2AC3AC4AC6AX10AX3AX4AX8AX9M1M2M3M4P1P10P2P3PF3R1R10R2R3R9X14X26X28X3X5

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, 708 of 724 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 01a1d939-2260-75bc-bccc-d6f7e6c96137.

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.

  • D4 Code Duplication — 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. The 16 duplicated block group(s) on this row were found in the languages this pass could tokenize, and they do NOT cover all of this repository's production source: .m (3,105 lines, 17% of production source) went unread, because no language model this pass could load exposed a clone-unit token stream for those file kinds. Duplication in that source is UNMEASURED — its absence from the count above is a gap in this analyzer's language coverage, not a finding that the code is free of duplication.
  • 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 Modules/Account 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. Test source is present (.swift) and this repository declares a SwiftPM test suite (14 packages), but it was not re-run: the analyzer environment could not run it. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
  • 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. 1 of this repository's SwiftPM dependencies could not be fetched at a pinned revision and are repositories api.deps.dev has not indexed, so their licences were not read and the verdict does not cover them: tidemark.
  • 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 — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each 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.
  • D26 Project Cohesion — 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. Project size and spread are measured over build units whose source a code model reads. This repository's .m source is a material share of its production lines and was read by none, so the score is a verdict about the units that were read. Not a finding that the unread source is cohesive — it is unmeasured.
  • D27 Navigability — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Tracing effort is measured over resolved call sites, and all 492 sampled here came from .swift files. This repository's .m source is a material share of its production lines and contributed none, so the score above is a verdict about the part that was read. Not a finding that the unread half navigates well — it is unmeasured.
  • D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `Mac/MainWindow/MainWindowController.swift`, `Modules/Account/Sources/Account/CloudKit/CloudKitRemoteNotificationOperation.swift`, `Modules/Account/Sources/Account/FeedSettingsDatabase.swift`, `Modules/Account/Sources/Account/Feedly/FeedlyAccountDelegate.swift`, `Modules/Account/Sources/Account/ReaderAPI/ReaderAPIAccountDelegate.swift`, … (+9 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
  • D44 Platform End-of-Life — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
  • 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: 26 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.
  • C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
  • C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
  • GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Python, Swift, c, 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 Python, Swift, c, 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.
  • M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
  • 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.
  • X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X19 Unrestored process-global state — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X29 Per-element action decided by a fixed element — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.

Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.

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 REDACTED Scanning: REDACTED 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.
  • D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
  • 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.
  • D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • 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.
  • 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.
  • AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
  • AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
  • AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
  • AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
  • AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
  • AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
  • M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.

Dimensions

D1 · Cyclomatic Complexity7.7 / 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.7 / 10 · rule-coverage 100% · ceiling Prevented

9 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was StripHTML.process at 69. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being ActivityKind.simpleDisplayName at 30 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: Modules/ActivityLog/Sources/ActivityLog/ActivityKind.swift (ActivityKind.simpleDisplayName at 30). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.

StripHTML.process (cyclomatic 69)Modules/RSCore/Sources/RSCore/StripHTML.swift:177
Data.isProbablyHTML (cyclomatic 31)Modules/RSCore/Sources/RSCore/Data+RSCore.swift:137
DateParser.nextMonthValue (cyclomatic 23)Modules/RSParser/Sources/RSParser/Utilities/DateParser.swift:286
XMLScanner.scanAttributeValue (cyclomatic 19)Modules/RSParser/Sources/RSParser/XML/XMLScanner.swift:196
DownloadedImageCache.revalidateIfDue (cyclomatic 18)Modules/Images/Sources/Images/DownloadedImageCache.swift:386

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

What to do

  1. Bring the 2 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with StripHTML.process (cyclomatic 69), Data.isProbablyHTML (cyclomatic 31). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cyclomatic Complexity from 7.7 to about 8.6/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.

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

D2 · Cognitive Complexity6.4 / 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 6.4 / 10 · rule-coverage 100% · ceiling Prevented

20 method(s) exceeded the cognitive complexity threshold of 15; the worst was StripHTML.process at 99.

StripHTML.process (cognitive 99)Modules/RSCore/Sources/RSCore/StripHTML.swift:177
XMLScanner.scanAttributeValue (cognitive 37)Modules/RSParser/Sources/RSParser/XML/XMLScanner.swift:196
HTMLScanner.scanAttributeValue (cognitive 35)Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift:183
DateParser.nextMonthValue (cognitive 32)Modules/RSParser/Sources/RSParser/Utilities/DateParser.swift:286
Data.isProbablyHTML (cognitive 30)Modules/RSCore/Sources/RSCore/Data+RSCore.swift:137

+ 15 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 Cognitive Complexity — start with StripHTML.process (cognitive 99). — Refactoring it lifts Cognitive Complexity from 6.4 to about 6.9/10.

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

D3 · God Classes9.8 / 10Stronggated by 3 serious findings✓ 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 9.8 / 10 · rule-coverage 100% · ceiling Prevented

3 god class(es) detected.

FileTooLong: REDACTEDREDACTED
TooManyMethods: DownloadedImageCacheModules/Images/Sources/Images/DownloadedImageCache.swift:43
MethodTooLong: StripHTML.processModules/RSCore/Sources/RSCore/StripHTML.swift:177

What to do

  1. Resolve the 1 FileTooLong finding(s) in God Classes — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
  2. Resolve the 1 TooManyMethods finding(s) in God Classes — start with DownloadedImageCache.swift. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 MethodTooLong finding(s) in God Classes — start with StripHTML.swift. — One of this dimension's main actionable groups (1 warning-level).

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

D4 · Code Duplication9.5 / 10Stronggated by 50 serious findings✓ 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 9.5 / 10 · rule-coverage 100% · ceiling Verified

16 duplicated block group(s) detected. 1.3 % of the production lines (1,090 of 82,944) are in a reported copy. A further 36 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. Measured on part of this repository only: .m (17% of production source) was not exposed to the token comparison, so duplication there is unmeasured and is not in this count.

Edited copy of a member (4 corresponding lines) · ×4Modules/ActivityLog/Sources/ActivityLog/ActivityLog.swift:273
Edited copies of one member (3 members, 6+ corresponding lines) · ×3Modules/Images/Sources/Images/ArticleThumbnailFinder.swift:56
Edited copy of a member (9 corresponding lines) · ×3Modules/RSCore/Sources/RSCore/String+RSCore.swift:216
Edited copy of a member (6 corresponding lines) · ×2Modules/Images/Sources/Images/FaviconDownloader.swift:43
Edited copy of a member (22 corresponding lines) · ×2Modules/RSCore/Sources/RSCore/String+RSCore.swift:287

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

What to do

  1. Resolve the 4 Edited copy of a member (4 corresponding lines) finding(s) in Code Duplication — start with ActivityLog.swift, HTMLMetadataTable.swift, StripHTML.swift. — One of this dimension's main actionable groups (4 warning-level).
  2. Resolve the 3 Edited copies of one member (3 members, 6+ corresponding lines) finding(s) in Code Duplication — start with ArticleThumbnailFinder.swift, MultilineTextFieldSizer.swift, FaviconDownloader.swift. — One of this dimension's main actionable groups (3 warning-level).
  3. Resolve the 3 Edited copy of a member (9 corresponding lines) finding(s) in Code Duplication — start with String+RSCore.swift, MultilineTextFieldSizer.swift, HTMLScanner.swift. — One of this dimension's main actionable groups (3 warning-level).

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

D5 · Coupling8.4 / 10Strong✓ 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 8.4 / 10 · rule-coverage 100% · ceiling Prevented

23 production modules (SwiftPM+Xcode), 0 dependency cycle(s), 2 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 7 of the 23 (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: ActivityLog · ×2
Unstable project Account
Unstable project HTMLMetadata

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).
  2. Resolve the 1 Unstable project Account finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 Unstable project HTMLMetadata finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).

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

D6 · Cohesion (LCOM4)9.1 / 10Stronggated by 3 serious findings✓ 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 9.1 / 10 · rule-coverage 100% · ceiling Verified

3 of 40 classes have LCOM4 above 3.

Low cohesion: MainThreadOperation (LCOM4 5) · ×3Modules/RSCore/Sources/RSCore/MainThreadOperation.swift:27

What to do

  1. Resolve the 3 Low cohesion finding(s) in Cohesion (LCOM4) — start with MainThreadOperation.swift, NSTableView+RSCore.swift, Data+RSCore.swift. — One of this dimension's main actionable groups (3 warning-level).

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

D10 · Test Quality8.7 / 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.7 / 10 · rule-coverage 100% · ceiling Prevented

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

No assertions (empty test): testExample · ×2Modules/CloudKitSync/Tests/CloudKitSyncTests/CloudKitSyncTests.swift:5
No assertions: testTruncatedFeedName · ×70Tests/NetNewsWireTests/ArticleStringFormatterPerformanceTests.swift:35
Test project verifies nothing: CloudKitSyncTestsModules/CloudKitSync/Tests/CloudKitSyncTests/CloudKitSyncTests.swift:5

What to do

  1. Resolve the 2 No assertions (empty test) finding(s) in Test Quality — start with CloudKitSyncTests.swift, NewsBlurTests.swift. — One of this dimension's main actionable groups (2 issue-level).
  2. Resolve the 70 No assertions finding(s) in Test Quality — start with DateParserTests.swift (29), XMLEncodingTests.swift (10), HTMLMetadataPerformanceTests.swift (5). — One of this dimension's main actionable groups (70 warning-level).
  3. Resolve the 1 Test project verifies nothing finding(s) in Test Quality — start with CloudKitSyncTests.swift. — One of this dimension's main actionable groups (1 warning-level).

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

D12 · Dependency Hygiene9.9 6.0 / 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.0 / 10 · rule-coverage 60% · ceiling Verified

1 outdated direct SwiftPM dependencies, 0 pinning defect(s). 3 of 5 direct dependencies had their releases listed (0 naming no readable repository, 2 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.

Outdated: sparkle

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

D13 · REDACTED Scanning10.0 / 10Exemplary○ Nothing flagged

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 10.0 / 10 · rule-coverage 100% · ceiling Prevented

REDACTED scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.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 3 SwiftPM package(s) use a banned license. SwiftPM has no package registry, so each package's licence is the one its repository declares: 1 of them read from the licence file the repository carries at the revision Package.resolved pins, and 2 — unpinned, or whose licence file could not be read or named — from api.deps.dev, which reports the licence the repository declares today. Graded: every package a committed Package.resolved pins, direct and transitive, and every declared dependency none pins. 1 of them are declared by a manifest that commits no Package.resolved (a library, whose resolution is its consumer's), so their own dependencies are resolved by whoever builds it and are not in this verdict. 2 of them declare no licence that matches a known SPDX licence; that is missing data, not a violation, and none of them is charged. ★ 1 package(s) could not be read at a pinned revision and are not known to the index, and were NOT graded — this verdict does not cover them: `tidemark`.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

D15 · Churn × Complexity Hotspots9.7 / 10Stronggated by 10 serious findings✓ 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 9.7 / 10 · rule-coverage 100% · ceiling Documented

Top hotspots: Modules/Images/Sources/Images/DownloadedImageCache.swift (57×18=1026); iOS/MainTimeline/MainTimelineViewController.swift (40×18=720); Mac/MainWindow/MainWindowController.swift (27×22=594)

Hotspot: Modules/Images/Sources/Images/DownloadedImageCache.swift · ×10Modules/Images/Sources/Images/DownloadedImageCache.swift:386

What to do

  1. Resolve the 10 Hotspot finding(s) in Churn × Complexity Hotspots — start with DownloadedImageCache.swift, MainTimelineViewController.swift, MainWindowController.swift. — One of this dimension's main actionable groups (10 warning-level).

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

D16 · Bus Factor2.5 / 10Weak✓ Tool-verified

What it measures: Whether knowledge is concentrated in too few people (the "bus factor").

Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.

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

77 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is Modules/RSParser/Sources/RSParser/Utilities/DateParser.swift. Counted over 103 of the 212 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Off-boarding risk: anonymized user #1

What to do

  1. Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).

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

D17 · Explicit Debt10.0 / 10Stronggated by 1 serious finding✓ 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 10.0 / 10 · rule-coverage 100% · ceiling Prevented

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

TodoCommentModules/RSParser/Tests/RSParserTests/Feeds/XML/AtomParserTests.swift:284

What to do

  1. Resolve the 1 TodoComment finding(s) in Explicit Debt — start with AtomParserTests.swift. — One of this dimension's main actionable groups (1 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 foundNetNewsWire.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 Consistency7.2 / 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 7.2 / 10 · rule-coverage 100% · ceiling Verified

4 naming inconsistencies among 142 declarations measured against a convention their peers follow.

`streamId` spells `Id` where 149 names in the project spell it `ID` · ×2Modules/Account/Sources/Account/ReaderAPI/ReaderAPIEntry.swift:196
`categoryId` spells `Id` where 149 names in the project spell it `ID`Modules/Account/Sources/Account/ReaderAPI/ReaderAPISubscription.swift:85
`itemId` spells `Id` where 149 names in the project spell it `ID`Modules/Account/Sources/Account/ReaderAPI/ReaderAPIUnreadEntry.swift:22

What to do

  1. Resolve the 2 `streamId` spells `Id` where 149 names in the project spell it `ID` finding(s) in Naming Consistency — start with ReaderAPIEntry.swift, ReaderAPISubscription.swift. — One of this dimension's main actionable groups (2 recommendation-level).
  2. Resolve the 1 `categoryId` spells `Id` where 149 names in the project spell it `ID` finding(s) in Naming Consistency — start with ReaderAPISubscription.swift. — One of this dimension's main actionable groups (1 recommendation-level).
  3. Resolve the 1 `itemId` spells `Id` where 149 names in the project spell it `ID` finding(s) in Naming Consistency — start with ReaderAPIUnreadEntry.swift. — 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.

D24 · Comment Value10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).

Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.

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

0 of 42 judged comments only repeat the code they sit on (0.0 %).

✓ On the Gold path — maintain.

Detailed fixes: d24_recommendation.md.

D26 · Project Cohesion10.0 / 10Exemplary✓ 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 10.0 / 10 · rule-coverage 100% · ceiling Documented

0 of 18 build units (SwiftPM, Xcode) flagged as possibly oversized/incoherent. This repository's .m source was read by no build unit, so this covers part of the tree, not all of it.

✓ On the Gold path — maintain.

Detailed fixes: d26_recommendation.md.

D27 · Navigability9.0 / 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.0 / 10 · rule-coverage 100% · ceiling Documented

31 % of calls cross a namespace and 20 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated. Measured over the .swift source only — this repository's .m was not sampled for call sites, so this score covers part of the tree, not all of it.

✓ On the Gold path — maintain.

Detailed fixes: d27_recommendation.md.

D28 · Secrets (history)4.0 / 10Weak✓ Tool-verified

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

Method: REDACTED 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 4.0 / 10 · rule-coverage 100% · ceiling Documented

6 finding(s): 0 critical, 6 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.

REDACTED
REDACTED

What to do

  1. Resolve the 6 REDACTED finding(s) in Secrets (history) — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (6 issue-level).
  2. Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).

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

D29 · Static Analysis (SAST)0.0 / 10Critical✓ 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 0.0 / 10 · rule-coverage 100% · ceiling Documented

546 finding(s): 0 critical, 6 high, 4 medium, 536 low. 5 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 9 file(s) — `Mac/MainWindow/MainWindowController.swift` (line 1231), `Modules/CloudKitSync/Sources/CloudKitSync/CloudKitZone.swift`, `Modules/RSCore/Tests/RSCoreTests/Resources/apple.html`, `REDACTED` (line 5), `REDACTED`, … (+4 more) — 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
REDACTED
REDACTED
REDACTED

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

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

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

D30 · Dependency Vulnerabilities10.0 / 10Exemplary○ Nothing flagged

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 Gemfile.lock 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 10.0 / 10 · rule-coverage 100% · ceiling Documented

No known-vulnerable dependencies in any ecosystem this repository declares.

✓ On the Gold path — maintain.

Detailed fixes: d30_recommendation.md.

D34 · Knowledge Freshness9.8 / 10Adequategated by 1 critical finding✓ 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 9.8 / 10 · rule-coverage 100% · ceiling Documented

2 of 103 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is REDACTED. Counted over 103 of the 212 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned knowledgeREDACTED:1
Further orphaned files (smaller)
Orphaned filebuildscripts/VerifyNoBS.swift:1

What to do

  1. Resolve the 1 Orphaned knowledge finding(s) in Knowledge Freshness — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  2. Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
  3. Resolve the 1 Orphaned file finding(s) in Knowledge Freshness — start with VerifyNoBS.swift. — One of this dimension's main actionable groups (1 recommendation-level).

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

D35 · Change Coupling9.9 / 10Adequategated by 4 critical findings✓ 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: AtomParser.swift↔RSSParser.swift 65%; Package.swift↔Package.swift 54%; Package.swift↔Package.swift 54%

Boundary-crossing change coupling: Package.swift ↔ Package.swift · ×4Modules/Account/Package.swift:1
Change coupling: AtomParser.swift ↔ RSSParser.swift · ×2Modules/RSParser/Sources/RSParser/Feeds/XML/AtomParser.swift:1

What to do

  1. Resolve the 4 Boundary-crossing change coupling finding(s) in Change Coupling — start with Package.swift (4). — One of this dimension's main actionable groups (4 issue-level).
  2. Resolve the 2 Change coupling finding(s) in Change Coupling — start with AtomParser.swift, AppDefaults.swift. — One of this dimension's main actionable groups (2 warning-level).

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

D36 · Supply-chain Provenance & Signing2.5 / 10Weak✓ Tool-verified

What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.

Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.

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

1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).

REDACTED
REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
  2. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
  3. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).

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

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.

Frontend & cross-cutting dimensions

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

AC1 · Text alternatives2.0 / 10Critical✓ 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. (×15) — Shared/Article Rendering/template.html:39, Themes/Appanoose.nnwtheme/template.html:27, Themes/Appanoose.nnwtheme/template7.3.html:27, …

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.
AC2 · Forms & labels10.0 / 10Exemplary○ Nothing flagged

Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.

Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

AC3 · Page structure4.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"). (×2) — Mac/MainWindow/Detail/page.html:1, iOS/Resources/page.html:1
  • No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×3) — Mac/MainWindow/Detail/page.html:1, Mac/Resources/KeyboardShortcuts/KeyboardShortcuts.html:2, iOS/Resources/page.html:1
  • A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope). (×11) — Mac/Resources/KeyboardShortcuts/KeyboardShortcuts.html:59, Mac/Resources/KeyboardShortcuts/KeyboardShortcuts.html:75, Mac/Resources/KeyboardShortcuts/KeyboardShortcuts.html:85, …

What to do

  • Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC4 · Keyboard semantics1.0 / 10Critical✓ Tool-verified

Other · Accessibility — Whether interactive behaviour is keyboard-reachable — no click handler on a non-interactive element lacking a role, tabindex and key handler, no element the repo's own CSS styles `cursor: pointer` without giving it any of the three, no unfocusable element whose only binding is a mouse enter/leave pair or a double-click, no positive tabindex, no href-less anchor, no placeholder-href (#/javascript) link acting as a button. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: click handlers on non-interactive elements lacking role+tabindex+key handler, positive tabindex values, and href-less anchors. Components skipped, spreads suppressed. Deterministic, hard fact per element.

Coverage: Population: elements that pose a keyboard-semantics question, in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) — a non-natively-interactive element carrying a click handler, a double-click or hover enter/leave binding, a pointer-only gesture on a tabindex="0" element, or `cursor: pointer` from the repo's own CSS; an href-less or placeholder-href (#, javascript:) anchor; and any element with a positive tabindex. Natively interactive elements used correctly (<button>, <a href>, form controls) are NOT in the population — there is nothing to judge — so a page of nothing but correct controls gives AC4 nothing to measure. Keyboard reachability is judged from the markup, never from a rendered page. ★ An interactive element declared in a tagged-template (html`…`) or hyperscript frontend is NOT in this population — no producer reads either — so an empty population is reported as an analyzer gap, never as "this repository has no interactive elements".

  • An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action. (×2) — Themes/NewsFax.nnwtheme/template.html:61, Themes/NewsFax.nnwtheme/template7.3.html:63

What to do

  • Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
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.

  • `body a.footnote, body a.footnote:visited, .newsfoot-footnote-popover + a.footnote:hover` sets color: white on background-color: #8894a0 — 3.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. (×2) — Themes/Verdana Revival.nnwtheme/stylesheet.css:449, Themes/Verdana Revival.nnwtheme/stylesheet.css:478
  • `body a.footnote, body a.footnote:visited, .newsfoot-footnote-popover + a.footnote:hover` sets color: #aaa on background-color: #444 — 4.2:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — Themes/Tiqoe Dark.nnwtheme/stylesheet.css:365
  • `body a.footnote, body a.footnote:visited, .newsfoot-footnote-popover + a.footnote:hover` sets color: white on background-color: #aaa — 2.3:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. (×11) — Themes/Sepia.nnwtheme/stylesheet.css:350, Themes/Promenade.nnwtheme/stylesheet.css:454, Themes/Promenade.nnwtheme/stylesheet.css:480, …
  • `body a.footnote, body a.footnote:visited, .newsfoot-footnote-popover + a.footnote:hover` sets color: white on background-color: #8a8597 — 3.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — Themes/Plum.nnwtheme/stylesheet.css:473
  • `body a.footnote, body a.footnote:visited, .newsfoot-footnote-popover + a.footnote:hover` sets color: white on background-color: #8a8a8a — 3.5:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — Themes/Gray.nnwtheme/stylesheet.css:471
  • `.articleBody a:hover` sets color: white on background-color: rgba(60, 146, 251, 1) — 3.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — Shared/Article Rendering/stylesheet.css:563

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 composition10.0 / 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 purity10.0 / 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.

M1 · Documentation (README)7.6 / 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.

M4 · Documentation accuracy0.0 / 10Critical✓ Tool-verified

Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.

Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.

  • Modules/RSParser/README.md links to `Feeds/ParsedFeed.swift`, but `Modules/RSParser/Feeds/ParsedFeed.swift` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Modules/RSParser/README.md:29
  • Modules/RSParser/README.md links to `Feeds/JSON/RSSInJSONParser.swift`, but `Modules/RSParser/Feeds/JSON/RSSInJSONParser.swift` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Modules/RSParser/README.md:33
  • Modules/RSParser/README.md links to `Feeds/JSON/JSONFeedParser.swift`, but `Modules/RSParser/Feeds/JSON/JSONFeedParser.swift` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Modules/RSParser/README.md:33
  • Modules/RSParser/README.md links to `Feeds/XML/RSSParser.swift`, but `Modules/RSParser/Feeds/XML/RSSParser.swift` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Modules/RSParser/README.md:33
  • Modules/RSParser/README.md links to `Feeds/XML/AtomParser.swift`, but `Modules/RSParser/Feeds/XML/AtomParser.swift` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Modules/RSParser/README.md:33

What to do

  • Reconcile the README with reality: Modules/RSParser/README.md links to `Feeds/ParsedFeed.swift`, but `Modules/RSParser/Feeds/ParsedFeed.swift` does not exist; Modules/RSParser/README.md links to `Feeds/JSON/RSSInJSONParser.swift`, but `Modules/RSParser/Feeds/JSON/RSSInJSONParser.swift` does not exist; Modules/RSParser/README.md links to `Feeds/JSON/JSONFeedParser.swift`, but `Modules/RSParser/Feeds/JSON/JSONFeedParser.swift` does not exist; Modules/RSParser/README.md links to `Feeds/XML/RSSParser.swift`, but `Modules/RSParser/Feeds/XML/RSSParser.swift` does not exist; Modules/RSParser/README.md links to `Feeds/XML/AtomParser.swift`, but `Modules/RSParser/Feeds/XML/AtomParser.swift` does not exist.
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 · Observability6.6 / 10Adequate✓ 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.

  • Only 13/15 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`, `.`.

What to do

  • Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
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 1 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:4

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.
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.

R1 · Type Safety0.0 / 10Critical✓ Tool-verified

React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.

Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.

  • 0 typed · 5 plain JS — the untyped files are Mac/MainWindow/Detail/main_mac.js, REDACTED, Shared/Article Rendering/newsfoot.js, Shared/ShareExtension/SafariExt.js, REDACTED.

What to do

  • Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
R10 · Code Duplication10.0 / 10Exemplary✓ Tool-verified

React / JS · Code Health — The share of the scored frontend lines inside a near-exact copy-pasted block of substantial extent (the D4 clone algorithm over JS/TS tokens, D-386; each line once, 10 at none and 0 at a quarter of the lines, as D4): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.

Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Scored on the share of the scored frontend lines inside a reported copy, on the same curve as D4. Deterministic.

R2 · Cyclomatic Complexity10.0 / 10Exemplary✓ Tool-verified

React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.

Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.

R3 · Large Files2.0 / 10Critical✓ Tool-verified

React / JS · Code Health — How many source files exceed the large-file threshold.

Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.

  • REDACTED has 420 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1

What to do

  • Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R9 · Circular Imports10.0 / 10Exemplary✓ Tool-verified

React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.

Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.

X14 · Bypassable address classification10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.

Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.

X26 · Unsynchronised callback handoff10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.

Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. Deterministic, provable per finding. Advisory.

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 handling7.1 / 10Strong✓ 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. (×5) — Shared/Widget/WidgetDataEncoder.swift:187, Modules/RSCore/Sources/RSCore/AppKit/UserApp.swift:115, Modules/Images/Sources/Images/DownloadedImageCache.swift:403, …
  • 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. (×4) — Modules/RSCore/Sources/RSCore/BinaryDiskCache.swift:37, Modules/RSCore/Sources/RSCore/BinaryDiskCache.swift:45, Modules/RSCore/Sources/RSCore/BinaryDiskCache.swift:49, …

What to do

  • Swallowed exception (caught, then discarded)
X5 · Nullable reference types2.0 / 10Critical✓ Tool-verified

Other · Code Health — Whether Ruby's type checker checks nil and is not undermined by assertions — a file Sorbet reads at `# typed: true` or above, or a Steep target `check`s under its default or strict diagnostics, is one where a method call on a `T.nilable(String)` / `String?` is an error, and each `T.must`, `#: as !nil` or `# steep:ignore NoMethod` is the author telling the checker a value cannot be nil.

Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.

  • This repository commits no Sorbet configuration (`sorbet/config`) and no `Steepfile`, so nothing type-checks its 1 Ruby product file(s): a nilable value reaches a method call silently and raises `NoMethodError: undefined method … for nil` the first time it is nil. A `# typed:` sigil does nothing without a `sorbet/config` beside the code; a Steep run configured only on a command line is not something this check can read.

What to do

  • Adopt a checker and raise it file by file: with Sorbet, `srb init` (or `bundle exec tapioca init`) commits `sorbet/config`, then move each file's sigil from `# typed: false` to `# typed: true` and on to `strict` as its methods get `sig`s — `spoom bump` does the moving; with Steep, write RBS signatures and `check` the product directories in the `Steepfile` under `D::Ruby.default` or `strict`, not `lenient`. Then pay down the assertions rather than adding to them: each `T.must` is a nil the checker could not rule out — narrow it (`return unless x`, `x&.`, `if (y = x)`), make the attribute non-nilable and set it in `initialize`, or change the method so the nil cannot arrive.

WCAG coverage — what static analysis assessed

Statically assessed 15 of 55 WCAG 2.2 Level A/AA success criteria (27%; ≈30% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 40 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
AC2 · Forms & labels1.3.1, 3.3.2, 4.1.2Partial signal
AC3 · Page structure1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2Partial signal
AC4 · Keyboard semantics2.1.1, 2.4.3Partial signal
AC6 · Visual & motion safety1.4.3, 2.4.7Partial — literal CSS only

Not statically assessed — these 40 Level A/AA criteria need runtime or manual evaluation (WCAG-EM): 1.2.1, 1.2.3, 1.2.4, 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.2, 2.1.4, 2.2.2, 2.3.1, 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.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 Health38%Weak — gated by R1, R3, X5Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture98%ExemplarySolid.
Maturity39%Weak — gated by D16, M2, M4Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness55%Adequate — gated by P3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security22%Checked 3 of 10Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Accessibility26%Weak — gated by AC1, AC4, AC6Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance100%ExemplaryStrongest area.
Unscored — 2 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.

  • X10 Duplicated predicate — 14 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X7 Silent fallback defaults — 4 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 6 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.
  • C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
  • P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
Not included — 65 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.

  • AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
  • AX1 Captive dependencies — Not applicable: this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Python imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Ruby imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Swift imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
  • 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.
  • 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.
  • D11 Test Reliability — Test reliability not included — the .swift suite was found but not re-run
  • 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 — No runnable or published unit to look for an example in, and no multi-project root README to look for a map in; the other documentation kinds are withheld (see the gaps), so documentation quality is not applicable here.
  • 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"]`.
  • 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) — 14 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.
  • D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
  • D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
  • D8 Code Coverage — Coverage not measured — Swift suite
  • DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
  • ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and this analysis resolves a call's owner only where the receiver's type is written down in the source. Reported as guidance rather than measured
  • ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
  • IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
  • P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript, Python, Ruby, Swift source, so there is no service whose uptime a failing dependency could take down
  • P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
  • P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
  • PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `Benchmark("…")` in a file importing package-benchmark, or package-benchmark in Package.swift, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
  • PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
  • R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
  • R4 Test Coverage — the JS/TS workspace (5 production file(s)) has no JavaScript/TypeScript test, but it is 1.23% of this repository's production source and the other 98.77% carries 11,643 line(s) of test code this pass cannot read — an incidental frontend's reachability is not the repository's test posture, so it is not scored as one
  • R5 Dependency Freshness — no package-lock.json — dependency freshness not measured (would require an npm lockfile); JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
  • R6 Tooling — no package.json in the repository — test/lint/typecheck wiring is read from package.json scripts (corroborated against CI), so this project's own toolchain isn't measured here
  • R7 Dead Code — Not measured — no application, tooling or test entry point was detected, so no file can be shown to be reachable or unreachable. Declare an entry (package.json main/module/exports, src/index.*, or an index.html script) to enable reachability.
  • R8 Dependency Hygiene — Not measured — no package.json declares any dependency, so there is nothing to check imports against (imports may resolve through a host runtime rather than node).
  • 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 — X12 reached only 7% of this repository's production lines — swift (13,491 lines), objectivec (1,889 lines), c (1,216 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X16 Unfloored truncation loop — X16 reached only 1% of this repository's production lines — swift (13,491 lines), objectivec (1,889 lines), c (1,216 lines), python (1,163 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X19 Unrestored process-global state — X19 reached only 7% of this repository's production lines — swift (13,491 lines), objectivec (1,889 lines), c (1,216 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • 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 — X24 reached only 7% of this repository's production lines — swift (13,491 lines), objectivec (1,889 lines), c (1,216 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • 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
  • X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X29 Per-element action decided by a fixed element — X29 reached only 1% of this repository's production lines — swift (13,491 lines), objectivec (1,889 lines), c (1,216 lines), python (1,163 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Ruby was read, and it logs through none: the standard library's Logger, which Rails.logger is, takes one finished message and no template arguments or fields (as log4net does in C#), so an interpolated message there loses nothing the API could have kept. The console gem (`Console.info`), SemanticLogger, Ougai and dry-logger would be judged.
  • X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

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 — 36 finding(s)
AC1 · Text alternatives · <img> without a text alternative · ×15
  • <img> without a text alternative Shared/Article Rendering/template.html:39 — 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 Themes/Appanoose.nnwtheme/template.html:27 — 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 Themes/Appanoose.nnwtheme/template7.3.html:27 — 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 Themes/Biblioteca.nnwtheme/template.html:2 — 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 Themes/Biblioteca.nnwtheme/template7.3.html:2 — 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 Themes/Hyperlegible.nnwtheme/template.html:37 — 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 Themes/Hyperlegible.nnwtheme/template7.3.html:37 — 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 Themes/Promenade.nnwtheme/template.html:35 — 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 Themes/Promenade.nnwtheme/template7.3.html:35 — 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 Themes/Sepia.nnwtheme/template.html:5 — 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 Themes/Sepia.nnwtheme/template7.3.html:5 — 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 Themes/Tiqoe Dark.nnwtheme/template.html:5 — 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 Themes/Tiqoe Dark.nnwtheme/template7.3.html:5 — 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 Themes/Verdana Revival.nnwtheme/template.html:5 — 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 Themes/Verdana Revival.nnwtheme/template7.3.html:5 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
D28 · Secrets (history) · REDACTED · ×6
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D35 · Change Coupling · Boundary-crossing change coupling · ×4
  • Boundary-crossing change coupling: Package.swift ↔ Package.swift Modules/Account/Package.swift:1 — `Modules/Account/Package.swift` (context Account) and `Modules/Articles/Package.swift` (context Articles) sit in DIFFERENT parts of the tree yet change together 54% of the time (7 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — 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) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `c70a7ab4` Make iOS 18 the minimum target.; `74baa602` Set macOS deployment target to macOS 15 and make the app compatible.; `2fdc011a` Convert to async/await. — run `git show` on any of them.
  • Boundary-crossing change coupling: Package.swift ↔ Package.swift Modules/Articles/Package.swift:1 — `Modules/Articles/Package.swift` (context Articles) and `Modules/ArticlesDatabase/Package.swift` (context ArticlesDatabase) sit in DIFFERENT parts of the tree yet change together 54% of the time (7 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — 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) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `c70a7ab4` Make iOS 18 the minimum target.; `74baa602` Set macOS deployment target to macOS 15 and make the app compatible.; `2fdc011a` Convert to async/await. — run `git show` on any of them.
  • Boundary-crossing change coupling: Package.swift ↔ Package.swift Modules/ArticlesDatabase/Package.swift:1 — `Modules/ArticlesDatabase/Package.swift` (context ArticlesDatabase) and `Modules/SyncDatabase/Package.swift` (context SyncDatabase) sit in DIFFERENT parts of the tree yet change together 53% of the time (8 of the 15 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — 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) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `c70a7ab4` Make iOS 18 the minimum target.; `74baa602` Set macOS deployment target to macOS 15 and make the app compatible.; `2fdc011a` Convert to async/await. — run `git show` on any of them.
  • Boundary-crossing change coupling: Package.swift ↔ Package.swift Modules/ArticlesDatabase/Package.swift:1 — `Modules/ArticlesDatabase/Package.swift` (context ArticlesDatabase) and `Modules/RSWeb/Package.swift` (context RSWeb) sit in DIFFERENT parts of the tree yet 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, and counted over this repository's 10,000 most recent commits rather than its whole history — 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) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `c70a7ab4` Make iOS 18 the minimum target.; `74baa602` Set macOS deployment target to macOS 15 and make the app compatible.; `2fdc011a` Convert to async/await. — run `git show` on any of them.
AC3 · Page structure · <html> without a lang · ×2
  • <html> without a lang Mac/MainWindow/Detail/page.html:1 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang iOS/Resources/page.html:1 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
D10 · Test Quality · No assertions (empty test) · ×2
  • No assertions (empty test): testExample Modules/CloudKitSync/Tests/CloudKitSyncTests/CloudKitSyncTests.swift:5 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): testExample Modules/NewsBlur/Tests/NewsBlurTests/NewsBlurTests.swift:5 — Test method has an empty body — it asserts nothing and exercises no code.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D34 · Knowledge Freshness · Orphaned knowledge · ×1
  • Orphaned knowledge REDACTED:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Serious — 222 finding(s)
D10 · Test Quality · No assertions · ×70
  • No assertions: testTruncatedFeedName Tests/NetNewsWireTests/ArticleStringFormatterPerformanceTests.swift:35 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testTruncatedTitle Tests/NetNewsWireTests/ArticleStringFormatterPerformanceTests.swift:46 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testAttributedTruncatedTitle Tests/NetNewsWireTests/ArticleStringFormatterPerformanceTests.swift:58 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testTruncatedSummary Tests/NetNewsWireTests/ArticleStringFormatterPerformanceTests.swift:69 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testRowHeightsCold Tests/NetNewsWireTests/TimelineRowHeightPerformanceTests.swift:34 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testRowHeightsWarm Tests/NetNewsWireTests/TimelineRowHeightPerformanceTests.swift:45 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testMD5HexPerformance Modules/RSCore/Tests/RSCoreTests/MD5PerformanceTests.swift:17 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testMD5StringPerformance Modules/RSCore/Tests/RSCoreTests/String+RSCoreTests.swift:172 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testStrippingHTMLPerformance Modules/RSCore/Tests/RSCoreTests/StripHTMLPerformanceTests.swift:13 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testFeedTypePerformance Modules/RSParser/Tests/RSParserTests/Feeds/FeedParserTypePerformanceTests.swift:15 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testFeedTypePerformance2 Modules/RSParser/Tests/RSParserTests/Feeds/FeedParserTypePerformanceTests.swift:23 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testFeedTypePerformance3 Modules/RSParser/Tests/RSParserTests/Feeds/FeedParserTypePerformanceTests.swift:31 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testFeedTypePerformance4 Modules/RSParser/Tests/RSParserTests/Feeds/FeedParserTypePerformanceTests.swift:39 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testSixColorsPerformance Modules/RSParser/Tests/RSParserTests/HTML/HTMLLinkPerformanceTests.swift:15 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testDaringFireballPerformance Modules/RSParser/Tests/RSParserTests/HTML/HTMLMetadataPerformanceTests.swift:15 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testFurboPerformance Modules/RSParser/Tests/RSParserTests/HTML/HTMLMetadataPerformanceTests.swift:23 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testInessentialPerformance Modules/RSParser/Tests/RSParserTests/HTML/HTMLMetadataPerformanceTests.swift:31 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testCocoPerformance Modules/RSParser/Tests/RSParserTests/HTML/HTMLMetadataPerformanceTests.swift:39 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testSixColorsPerformance Modules/RSParser/Tests/RSParserTests/HTML/HTMLMetadataPerformanceTests.swift:47 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testHotPathPerformance Modules/RSParser/Tests/RSParserTests/Utilities/DateParserPerformanceTests.swift:17 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: pubDateStandardForms Modules/RSParser/Tests/RSParserTests/Utilities/DateParserTests.swift:69 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: pubDateWithoutWeekday Modules/RSParser/Tests/RSParserTests/Utilities/DateParserTests.swift:78 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: pubDateWithoutSeconds Modules/RSParser/Tests/RSParserTests/Utilities/DateParserTests.swift:83 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: w3cStandardForms Modules/RSParser/Tests/RSParserTests/Utilities/DateParserTests.swift:92 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: w3cMissingTSeparator Modules/RSParser/Tests/RSParserTests/Utilities/DateParserTests.swift:101 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • + 45 more in this group — see findings.md.
AC3 · Page structure · Data table has no header cells · ×11
  • Data table has no header cells Mac/Resources/KeyboardShortcuts/KeyboardShortcuts.html:59 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells Mac/Resources/KeyboardShortcuts/KeyboardShortcuts.html:75 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells Mac/Resources/KeyboardShortcuts/KeyboardShortcuts.html:85 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells Mac/Resources/KeyboardShortcuts/KeyboardShortcuts.html:92 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells Shared/Article Rendering/template.html:36 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells Themes/Hyperlegible.nnwtheme/template.html:34 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells Themes/Hyperlegible.nnwtheme/template7.3.html:34 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells Themes/Sepia.nnwtheme/template.html:2 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells Themes/Sepia.nnwtheme/template7.3.html:2 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells Themes/Tiqoe Dark.nnwtheme/template.html:2 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells Themes/Tiqoe Dark.nnwtheme/template7.3.html:2 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
AC6 · Visual & motion safety · Low contrast colour pair in CSS (2.3 · ×11
  • Low contrast colour pair in CSS (2.3:1) Themes/Sepia.nnwtheme/stylesheet.css:350 — `body a.footnote, body a.footnote:visited, .newsfoot-footnote-popover + a.footnote:hover` sets color: white on background-color: #aaa — 2.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 (2.3:1) Themes/Promenade.nnwtheme/stylesheet.css:454 — `body a.footnote, body a.footnote:visited, .newsfoot-footnote-popover + a.footnote:hover` sets color: white on background-color: #aaa — 2.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 (2.3:1) Themes/Promenade.nnwtheme/stylesheet.css:480 — `body a.footnote, body a.footnote:visited, .newsfoot-footnote-popover + a.footnote:hover` sets color: white on background-color: #aaa — 2.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 (2.3:1) Themes/NewsFax.nnwtheme/stylesheet.css:480 — `body a.footnote, body a.footnote:visited, .newsfoot-footnote-popover + a.footnote:hover` sets color: white on background-color: #aaa — 2.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 (2.3:1) Themes/NewsFax.nnwtheme/stylesheet.css:506 — `body a.footnote, body a.footnote:visited, .newsfoot-footnote-popover + a.footnote:hover` sets color: white on background-color: #aaa — 2.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 (2.3:1) Themes/Hyperlegible.nnwtheme/stylesheet.css:332 — `body a.footnote, body a.footnote:visited, .newsfoot-footnote-popover + a.footnote:hover` sets color: white on background-color: #aaa — 2.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 (2.3:1) Themes/Hyperlegible.nnwtheme/stylesheet.css:362 — `body a.footnote, body a.footnote:visited, .newsfoot-footnote-popover + a.footnote:hover` sets color: white on background-color: #aaa — 2.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 (2.3:1) Themes/Appanoose.nnwtheme/stylesheet.css:383 — `body a.footnote, body a.footnote:visited, .newsfoot-footnote-popover + a.footnote:hover` sets color: white on background-color: #aaa — 2.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 (2.3:1) Themes/Appanoose.nnwtheme/stylesheet.css:413 — `body a.footnote, body a.footnote:visited, .newsfoot-footnote-popover + a.footnote:hover` sets color: white on background-color: #aaa — 2.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 (2.3:1) Shared/Article Rendering/stylesheet.css:345 — `body a.footnote, body a.footnote:visited, .newsfoot-footnote-popover + a.footnote:hover` sets color: white on background-color: #aaa — 2.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 (2.3:1) Shared/Article Rendering/stylesheet.css:375 — `body a.footnote, body a.footnote:visited, .newsfoot-footnote-popover + a.footnote:hover` sets color: white on background-color: #aaa — 2.3:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
D15 · Churn × Complexity Hotspots · Hotspot · ×10
  • Hotspot: Modules/Images/Sources/Images/DownloadedImageCache.swift Modules/Images/Sources/Images/DownloadedImageCache.swift:386 — Modules/Images/Sources/Images/DownloadedImageCache.swift changed 57 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in DownloadedImageCache.revalidateIfDue at line 386. 1 of those changes was a fix/bug commit, and the other 56 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 13:59:08 -08:00' --until='2026-11-12 13:59:08 -08:00' --full-history --no-merges -- Modules/Images/Sources/Images/DownloadedImageCache.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: iOS/MainTimeline/MainTimelineViewController.swift iOS/MainTimeline/MainTimelineViewController.swift:599 — iOS/MainTimeline/MainTimelineViewController.swift changed 40 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in MainTimelineViewController.collectionView at line 599. 2 of those changes were fix/bug commits, and the other 38 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 13:59:08 -08:00' --until='2026-11-12 13:59:08 -08:00' --full-history --no-merges -- iOS/MainTimeline/MainTimelineViewController.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: Mac/MainWindow/MainWindowController.swift Mac/MainWindow/MainWindowController.swift:272 — Mac/MainWindow/MainWindowController.swift changed 27 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in MainWindowController.validateUserInterfaceItem at line 272. 3 of those changes were fix/bug commits, and the other 24 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 13:59:08 -08:00' --until='2026-11-12 13:59:08 -08:00' --full-history --no-merges -- Mac/MainWindow/MainWindowController.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: Mac/AppDelegate.swift Mac/AppDelegate.swift:155 — Mac/AppDelegate.swift changed 24 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in AppDelegate.applicationDidFinishLaunching at line 155. 3 of those changes were fix/bug commits, and the other 21 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 13:59:08 -08:00' --until='2026-11-12 13:59:08 -08:00' --full-history --no-merges -- Mac/AppDelegate.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: Shared/Article Rendering/ArticleRenderer.swift Shared/Article Rendering/ArticleRenderer.swift:258 — Shared/Article Rendering/ArticleRenderer.swift changed 25 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in ArticleRenderer.articleSubstitutions at line 258. 7 of those changes were fix/bug commits, and the other 18 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 13:59:08 -08:00' --until='2026-11-12 13:59:08 -08:00' --full-history --no-merges -- Shared/Article Rendering/ArticleRenderer.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: Modules/RSParser/Sources/RSParser/Feeds/XML/RSSParser.swift Modules/RSParser/Sources/RSParser/Feeds/XML/RSSParser.swift:79 — Modules/RSParser/Sources/RSParser/Feeds/XML/RSSParser.swift changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 44 in RSSDelegate.xmlSAXParser at line 79. 1 of those changes was a fix/bug commit, and the other 8 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 13:59:08 -08:00' --until='2026-11-12 13:59:08 -08:00' --full-history --no-merges -- Modules/RSParser/Sources/RSParser/Feeds/XML/RSSParser.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: Modules/RSParser/Sources/RSParser/Feeds/XML/MediaRSS.swift Modules/RSParser/Sources/RSParser/Feeds/XML/MediaRSS.swift:73 — Modules/RSParser/Sources/RSParser/Feeds/XML/MediaRSS.swift changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in MediaElementTracker.start at line 73. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 13:59:08 -08:00' --until='2026-11-12 13:59:08 -08:00' --full-history --no-merges -- Modules/RSParser/Sources/RSParser/Feeds/XML/MediaRSS.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: Modules/RSParser/Sources/RSParser/Feeds/XML/AtomParser.swift Modules/RSParser/Sources/RSParser/Feeds/XML/AtomParser.swift:111 — Modules/RSParser/Sources/RSParser/Feeds/XML/AtomParser.swift changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in AtomDelegate.xmlSAXParser at line 111. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 13:59:08 -08:00' --until='2026-11-12 13:59:08 -08:00' --full-history --no-merges -- Modules/RSParser/Sources/RSParser/Feeds/XML/AtomParser.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: Modules/ArticlesDatabase/Sources/ArticlesDatabase/Extensions/Article+Database.swift Modules/ArticlesDatabase/Sources/ArticlesDatabase/Extensions/Article+Database.swift:175 — Modules/ArticlesDatabase/Sources/ArticlesDatabase/Extensions/Article+Database.swift changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in Article.databaseDictionary at line 175. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 13:59:08 -08:00' --until='2026-11-12 13:59:08 -08:00' --full-history --no-merges -- Modules/ArticlesDatabase/Sources/ArticlesDatabase/Extensions/Article+Database.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: Modules/RSWeb/Sources/RSWeb/Downloader.swift Modules/RSWeb/Sources/RSWeb/Downloader.swift:67 — Modules/RSWeb/Sources/RSWeb/Downloader.swift changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in Downloader.download at line 67. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 13:59:08 -08:00' --until='2026-11-12 13:59:08 -08:00' --full-history --no-merges -- Modules/RSWeb/Sources/RSWeb/Downloader.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
X3 · Exception handling · Swallowed exception (caught, then discarded) · ×5
  • Swallowed exception (caught, then discarded) Shared/Widget/WidgetDataEncoder.swift:187 — `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) Modules/RSCore/Sources/RSCore/AppKit/UserApp.swift:115 — `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) Modules/Images/Sources/Images/DownloadedImageCache.swift:403 — `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) Modules/Account/Sources/Account/Feedbin/FeedbinEntry.swift:82 — `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) Modules/Account/Sources/Account/Feedbin/FeedbinEntry.swift:87 — `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.
D4 · Code Duplication · Edited copy of a member (4 corresponding lines) · ×4
  • Edited copy of a member (4 corresponding lines) Modules/ActivityLog/Sources/ActivityLog/ActivityLog.swift:273 — Modules/ActivityLog/Sources/ActivityLog/ActivityLog.swift:273-276 | Modules/ActivityLog/Sources/ActivityLog/ActivityLog.swift:282-285 — These two members are one piece of code written twice and then edited apart: 4 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 (4 corresponding lines) Modules/HTMLMetadata/Sources/HTMLMetadata/HTMLMetadataTable.swift:64 — Modules/HTMLMetadata/Sources/HTMLMetadata/HTMLMetadataTable.swift:64-67 | Modules/Images/Sources/Images/DownloadFailureTable.swift:54-57 — These two members are one piece of code written twice and then edited apart: 4 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 (4 corresponding lines) Modules/RSCore/Sources/RSCore/StripHTML.swift:100 — Modules/RSCore/Sources/RSCore/StripHTML.swift:100-109 | Modules/RSParser/Sources/RSParser/Utilities/DateParser.swift:231-234 — These two members are one piece of code written twice and then edited apart: 4 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 (4 corresponding lines) Modules/RSCore/Sources/RSCore/AppKit/MultilineTextFieldSizer.swift:194 — Modules/RSCore/Sources/RSCore/AppKit/MultilineTextFieldSizer.swift:194-201 | iOS/MainTimeline/Cell/MultilineUILabelSizer.swift:104-107 — These two members are one piece of code written twice and then edited apart: 4 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.
X3 · Exception handling · Swallowed exception (empty catch) · ×4
  • Swallowed exception (empty catch) Modules/RSCore/Sources/RSCore/BinaryDiskCache.swift:37 — 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.
  • Swallowed exception (empty catch) Modules/RSCore/Sources/RSCore/BinaryDiskCache.swift:45 — 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.
  • Swallowed exception (empty catch) Modules/RSCore/Sources/RSCore/BinaryDiskCache.swift:49 — 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.
  • Swallowed exception (empty catch) Modules/Account/Sources/Account/AccountManager.swift:231 — 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.
AC3 · Page structure · Page without a main landmark · ×3
  • Page without a main landmark Mac/MainWindow/Detail/page.html:1 — 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 Mac/Resources/KeyboardShortcuts/KeyboardShortcuts.html:2 — 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 iOS/Resources/page.html:1 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (3.1 · ×3
  • Low contrast colour pair in CSS (3.1:1) Themes/Verdana Revival.nnwtheme/stylesheet.css:449 — `body a.footnote, body a.footnote:visited, .newsfoot-footnote-popover + a.footnote:hover` sets color: white on background-color: #8894a0 — 3.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
  • Low contrast colour pair in CSS (3.1:1) Themes/Verdana Revival.nnwtheme/stylesheet.css:478 — `body a.footnote, body a.footnote:visited, .newsfoot-footnote-popover + a.footnote:hover` sets color: white on background-color: #8894a0 — 3.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
  • Low contrast colour pair in CSS (3.1:1) Shared/Article Rendering/stylesheet.css:563 — `.articleBody a:hover` sets color: white on background-color: rgba(60, 146, 251, 1) — 3.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
D4 · Code Duplication · Edited copies of one member (3 members, 6+ corresponding lines) · ×3
  • Edited copies of one member (3 members, 6+ corresponding lines) Modules/Images/Sources/Images/ArticleThumbnailFinder.swift:56 — Modules/Images/Sources/Images/ArticleThumbnailFinder.swift:56-65 | Modules/Images/Sources/Images/FaviconDownloader.swift:43-49 | Modules/Images/Sources/Images/IconImageDownloader.swift:52-57 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 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, 6+ corresponding lines) Modules/RSCore/Sources/RSCore/AppKit/MultilineTextFieldSizer.swift:93 — Modules/RSCore/Sources/RSCore/AppKit/MultilineTextFieldSizer.swift:93-101 | Modules/RSCore/Sources/RSCore/AppKit/MultilineTextFieldSizer.swift:103-111 | iOS/MainTimeline/Cell/MultilineUILabelSizer.swift:66-71 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 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, 6+ corresponding lines) Modules/Images/Sources/Images/FaviconDownloader.swift:125 — Modules/Images/Sources/Images/FaviconDownloader.swift:125-133 | Modules/Images/Sources/Images/FeedIconDownloader.swift:54-59 | Modules/Images/Sources/Images/HomePageIconDownloader.swift:100-105 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 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 (9 corresponding lines) · ×3
  • Edited copy of a member (9 corresponding lines) Modules/RSCore/Sources/RSCore/String+RSCore.swift:216 — Modules/RSCore/Sources/RSCore/String+RSCore.swift:216-224 | Modules/RSCore/Sources/RSCore/String+RSCore.swift:231-239 — 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) Modules/RSCore/Sources/RSCore/AppKit/MultilineTextFieldSizer.swift:81 — Modules/RSCore/Sources/RSCore/AppKit/MultilineTextFieldSizer.swift:81-91 | iOS/MainTimeline/Cell/MultilineUILabelSizer.swift:56-64 — 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) Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift:424 — Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift:424-432 | Modules/RSParser/Sources/RSParser/XML/XMLScanner.swift:369-378 — 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.
D6 · Cohesion (LCOM4) · Low cohesion · ×3
  • Low cohesion: MainThreadOperation (LCOM4 5) Modules/RSCore/Sources/RSCore/MainThreadOperation.swift:27 — MainThreadOperation'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: NSTableView (LCOM4 5) Modules/RSCore/Sources/RSCore/AppKit/NSTableView+RSCore.swift:12 — NSTableView'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: Data (LCOM4 4) Modules/RSCore/Sources/RSCore/Data+RSCore.swift:12 — Data'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.
AC4 · Keyboard semantics · Anchor without href · ×2
  • Anchor without href Themes/NewsFax.nnwtheme/template.html:61 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href Themes/NewsFax.nnwtheme/template7.3.html:63 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
D35 · Change Coupling · Change coupling · ×2
  • Change coupling: AtomParser.swift ↔ RSSParser.swift Modules/RSParser/Sources/RSParser/Feeds/XML/AtomParser.swift:1 — `Modules/RSParser/Sources/RSParser/Feeds/XML/AtomParser.swift` and `Modules/RSParser/Sources/RSParser/Feeds/XML/RSSParser.swift` change together 65% of the time (11 of the 17 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — 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 11 shared commits counted here, the most recent 3 are `d8417db7` Skip enclosure images that are the same as the feed image (as with Le…; `77075a18` Use media:description when no other content or summary is available.; `9ac62210` Parse Media RSS in Atom. Share more Media RSS handling between RSS an… — run `git show` on any of them.
  • Change coupling: AppDefaults.swift ↔ AppNotifications.swift Shared/AppDefaults.swift:1 — `Shared/AppDefaults.swift` and `Shared/AppNotifications.swift` change together 50% of the time (8 of the 16 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — 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 8 shared commits counted here, the most recent 3 are `f02250d3` Add setting for grayscale icons.; `e223d7dc` Add setting to show byline at top of timeline row on Mac.; `128b727f` Add setting to fade read articles in timeline on Mac. — run `git show` on any of them.
D4 · Code Duplication · Edited copy of a member (6 corresponding lines) · ×2
  • Edited copy of a member (6 corresponding lines) Modules/Images/Sources/Images/FaviconDownloader.swift:43 — Modules/Images/Sources/Images/FaviconDownloader.swift:43-49 | Modules/Images/Sources/Images/HomePageIconDownloader.swift:36-41 — 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) Modules/RSParser/Sources/RSParser/OPML/OPMLFeedSpecifier.swift:15 — Modules/RSParser/Sources/RSParser/Feeds/ParsedAuthor.swift:17-22 | Modules/RSParser/Sources/RSParser/OPML/OPMLFeedSpecifier.swift:15-20 — 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 · Edited copy of a member (22 corresponding lines) · ×2
  • Edited copy of a member (22 corresponding lines) Modules/RSCore/Sources/RSCore/String+RSCore.swift:287 — Modules/RSCore/Sources/RSCore/String+RSCore.swift:287-310 | Modules/RSWeb/Sources/RSWeb/String+RSWeb.swift:16-37 — 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) Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift:389 — Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift:389-410 | Modules/RSParser/Sources/RSParser/XML/XMLScanner.swift:293-318 — 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) Modules/RSCore/Sources/RSCore/String+RSCore.swift:29 — Modules/RSCore/Sources/RSCore/String+RSCore.swift:29-40 | Modules/RSCore/Sources/RSCore/String+RSCore.swift:51-63 — 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) Modules/RSCore/Sources/RSCore/Comparing.swift:23 — Modules/RSCore/Sources/RSCore/Comparing.swift:23-34 | Modules/RSCore/Sources/RSCore/Comparing.swift:50-61 — 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 copy of a member (11 corresponding lines) · ×2
  • Edited copy of a member (11 corresponding lines) Modules/ActivityLog/Sources/ActivityLog/ActivityLog.swift:152 — Modules/ActivityLog/Sources/ActivityLog/ActivityLog.swift:152-162 | Modules/ActivityLog/Sources/ActivityLog/ActivityLog.swift:196-207 — 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.
  • Edited copy of a member (11 corresponding lines) Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift:412 — Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift:412-422 | Modules/RSParser/Sources/RSParser/XML/XMLScanner.swift:337-347 — 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 (3 corresponding lines) · ×2
  • Edited copy of a member (3 corresponding lines) Modules/RSParser/Sources/RSParser/Utilities/DateParser.swift:236 — Modules/RSParser/Sources/RSParser/Utilities/DateParser.swift:236-240 | Shared/Extensions/ArticleStringFormatter.swift:304-306 — These two members are one piece of code written twice and then edited apart: 3 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 (3 corresponding lines) Modules/RSCore/Sources/RSCore/AppKit/MultilineTextFieldSizer.swift:55 — Modules/RSCore/Sources/RSCore/AppKit/MultilineTextFieldSizer.swift:55-58 | iOS/MainTimeline/Cell/MultilineUILabelSizer.swift:43-45 — These two members are one piece of code written twice and then edited apart: 3 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 (8 corresponding lines) · ×2
  • Edited copy of a member (8 corresponding lines) Modules/RSParser/Sources/RSParser/HTML/HTMLAttributes.swift:56 — Modules/RSParser/Sources/RSParser/HTML/HTMLAttributes.swift:56-64 | Modules/RSParser/Sources/RSParser/XML/XMLAttributes.swift:69-76 — 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.
  • Edited copy of a member (8 corresponding lines) Modules/RSDatabase/Sources/RSDatabase/DatabaseQueue.swift:79 — Modules/RSDatabase/Sources/RSDatabase/DatabaseQueue.swift:79-90 | Modules/RSDatabase/Sources/RSDatabase/FMDatabase+Extras.swift:76-83 — 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 (15–16 lines × 2) · ×2
  • Duplicated block (15–16 lines × 2) Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift:338 — Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift:338-352 | Modules/RSParser/Sources/RSParser/XML/XMLScanner.swift:383-398 — before extracting anything, compare `Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift` and `Modules/RSParser/Sources/RSParser/XML/XMLScanner.swift` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 114 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift:338` 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 (15–16 lines × 2) Modules/RSParser/Sources/RSParser/XML/XMLScanner.swift:225 — Modules/RSParser/Sources/RSParser/XML/XMLScanner.swift:225-240 | Modules/RSParser/Sources/RSParser/XML/XMLScanner.swift:256-270 — 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 `Modules/RSParser/Sources/RSParser/XML/XMLScanner.swift:225` 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.
D5 · Coupling · Off the main sequence · ×2
  • Off the main sequence: ActivityLog — ActivityLog: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 4 project(s), so it's rigid to change.
  • Off the main sequence: RSParser — RSParser: abstractness 0.06, instability 0.13, distance 0.81 — zone of pain — concrete and depended on by 7 project(s), so it's rigid to change.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (4.2 · ×1
  • Low contrast colour pair in CSS (4.2:1) Themes/Tiqoe Dark.nnwtheme/stylesheet.css:365 — `body a.footnote, body a.footnote:visited, .newsfoot-footnote-popover + a.footnote:hover` sets color: #aaa on background-color: #444 — 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 (3.6 · ×1
  • Low contrast colour pair in CSS (3.6:1) Themes/Plum.nnwtheme/stylesheet.css:473 — `body a.footnote, body a.footnote:visited, .newsfoot-footnote-popover + a.footnote:hover` sets color: white on background-color: #8a8597 — 3.6: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.5 · ×1
  • Low contrast colour pair in CSS (3.5:1) Themes/Gray.nnwtheme/stylesheet.css:471 — `body a.footnote, body a.footnote:visited, .newsfoot-footnote-popover + a.footnote:hover` sets color: white on background-color: #8a8a8a — 3.5:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
D1 · Cyclomatic Complexity · StripHTML.process (cyclomatic 69) · ×1
  • StripHTML.process (cyclomatic 69) Modules/RSCore/Sources/RSCore/StripHTML.swift:177 — StripHTML.process has cyclomatic complexity 69 (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 · Data.isProbablyHTML (cyclomatic 31) · ×1
  • Data.isProbablyHTML (cyclomatic 31) Modules/RSCore/Sources/RSCore/Data+RSCore.swift:137 — Data.isProbablyHTML has cyclomatic complexity 31 (threshold 15). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
D1 · Cyclomatic Complexity · DateParser.nextMonthValue (cyclomatic 23) · ×1
  • DateParser.nextMonthValue (cyclomatic 23) Modules/RSParser/Sources/RSParser/Utilities/DateParser.swift:286 — DateParser.nextMonthValue has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · XMLScanner.scanAttributeValue (cyclomatic 19) · ×1
  • XMLScanner.scanAttributeValue (cyclomatic 19) Modules/RSParser/Sources/RSParser/XML/XMLScanner.swift:196 — XMLScanner.scanAttributeValue has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · DownloadedImageCache.revalidateIfDue (cyclomatic 18) · ×1
  • DownloadedImageCache.revalidateIfDue (cyclomatic 18) Modules/Images/Sources/Images/DownloadedImageCache.swift:386 — DownloadedImageCache.revalidateIfDue has cyclomatic complexity 18 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · HTMLScanner.scanAttributeValue (cyclomatic 17) · ×1
  • HTMLScanner.scanAttributeValue (cyclomatic 17) Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift:183 — HTMLScanner.scanAttributeValue 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 · XMLEncoding.detectEncodingFromDeclaration (cyclomatic 17) · ×1
  • XMLEncoding.detectEncodingFromDeclaration (cyclomatic 17) Modules/RSParser/Sources/RSParser/XML/XMLEncoding.swift:143 — XMLEncoding.detectEncodingFromDeclaration has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
D1 · Cyclomatic Complexity · HTMLMetadata.resolveFeedLinks (cyclomatic 16) · ×1
  • HTMLMetadata.resolveFeedLinks (cyclomatic 16) Modules/RSParser/Sources/RSParser/HTML/HTMLMetadata.swift:127 — HTMLMetadata.resolveFeedLinks has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · HTMLOpenGraphProperties.parse (cyclomatic 16) · ×1
  • HTMLOpenGraphProperties.parse (cyclomatic 16) Modules/RSParser/Sources/RSParser/HTML/HTMLMetadata.swift:229 — HTMLOpenGraphProperties.parse 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.
D10 · Test Quality · Test project verifies nothing · ×1
  • Test project verifies nothing: CloudKitSyncTests Modules/CloudKitSync/Tests/CloudKitSyncTests/CloudKitSyncTests.swift:5 — No conventional assertion call was detected in 1 of 1 tests in `CloudKitSyncTests` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
D17 · Explicit Debt · TodoComment · ×1
  • TodoComment Modules/RSParser/Tests/RSParserTests/Feeds/XML/AtomParserTests.swift:284 — // TODO: parse Atom authors — 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.
D2 · Cognitive Complexity · StripHTML.process (cognitive 99) · ×1
  • StripHTML.process (cognitive 99) Modules/RSCore/Sources/RSCore/StripHTML.swift:177 — StripHTML.process has cognitive complexity 99 (threshold 15). Drivers by points: if/else 23 (50 pts), boolean chains 44, loops 3 (5 pts) (nesting depth added 29). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · XMLScanner.scanAttributeValue (cognitive 37) · ×1
  • XMLScanner.scanAttributeValue (cognitive 37) Modules/RSParser/Sources/RSParser/XML/XMLScanner.swift:196 — XMLScanner.scanAttributeValue has cognitive complexity 37 (threshold 15). Drivers by points: if/else 13 (31 pts), boolean chains 3, loops 2 (3 pts) (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 · HTMLScanner.scanAttributeValue (cognitive 35) · ×1
  • HTMLScanner.scanAttributeValue (cognitive 35) Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift:183 — HTMLScanner.scanAttributeValue has cognitive complexity 35 (threshold 15). Drivers by points: if/else 12 (30 pts), loops 2 (3 pts), 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 · DateParser.nextMonthValue (cognitive 32) · ×1
  • DateParser.nextMonthValue (cognitive 32) Modules/RSParser/Sources/RSParser/Utilities/DateParser.swift:286 — DateParser.nextMonthValue has cognitive complexity 32 (threshold 15). Drivers by points: if/else 14 (25 pts), match/switch 2 (4 pts), boolean chains 2, loops 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Data.isProbablyHTML (cognitive 30) · ×1
  • Data.isProbablyHTML (cognitive 30) Modules/RSCore/Sources/RSCore/Data+RSCore.swift:137 — Data.isProbablyHTML has cognitive complexity 30 (threshold 15). Drivers by points: boolean chains 18, if/else 12. This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
D2 · Cognitive Complexity · HTMLScanner.consumeRawText (cognitive 25) · ×1
  • HTMLScanner.consumeRawText (cognitive 25) Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift:280 — HTMLScanner.consumeRawText has cognitive complexity 25 (threshold 15). Drivers by points: if/else 5 (14 pts), loops 3 (8 pts), boolean chains 3 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · XMLEntities.decodeNumeric (cognitive 24) · ×1
  • XMLEntities.decodeNumeric (cognitive 24) Modules/RSParser/Sources/RSParser/XML/XMLEntities.swift:147 — XMLEntities.decodeNumeric has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (18 pts), loops 2 (4 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 · UserApp.updateStatus (cognitive 23) · ×1
  • UserApp.updateStatus (cognitive 23) Modules/RSCore/Sources/RSCore/AppKit/UserApp.swift:36 — UserApp.updateStatus has cognitive complexity 23 (threshold 15). Drivers by points: if/else 12 (20 pts), boolean chains 2, loops 1 (nesting depth added 8). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
D2 · Cognitive Complexity · ParseContext.token_generator (cognitive 21) · ×1
  • ParseContext.token_generator (cognitive 21) REDACTED:416 — ParseContext.token_generator has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (17 pts), loops 2 (4 pts) (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 · ImageParserDelegate.preferredSrcsetCandidate (cognitive 19) · ×1
  • ImageParserDelegate.preferredSrcsetCandidate (cognitive 19) Modules/RSParser/Sources/RSParser/HTML/HTMLImageParser.swift:134 — ImageParserDelegate.preferredSrcsetCandidate has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 2 (4 pts), boolean chains 3 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DownloadedImageCache.revalidateIfDue (cognitive 18) · ×1
  • DownloadedImageCache.revalidateIfDue (cognitive 18) Modules/Images/Sources/Images/DownloadedImageCache.swift:386 — DownloadedImageCache.revalidateIfDue has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 9, if/else 7 (8 pts), error handling 1 (nesting depth added 1). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · MultilineTextFieldSizer.heightConsideringNeighbors (cognitive 18) · ×1
  • MultilineTextFieldSizer.heightConsideringNeighbors (cognitive 18) Modules/RSCore/Sources/RSCore/AppKit/MultilineTextFieldSizer.swift:221 — MultilineTextFieldSizer.heightConsideringNeighbors has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (9 pts), boolean chains 8, loops 1 (nesting depth added 4). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
D2 · Cognitive Complexity · BuildSettingsVerifier.processXcodeprojAt (cognitive 18) · ×1
  • BuildSettingsVerifier.processXcodeprojAt (cognitive 18) buildscripts/VerifyNoBS.swift:80 — BuildSettingsVerifier.processXcodeprojAt has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (13 pts), ternaries 1 (4 pts), loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DownloadedImageCache.downloadImageFromNetwork (cognitive 17) · ×1
  • DownloadedImageCache.downloadImageFromNetwork (cognitive 17) Modules/Images/Sources/Images/DownloadedImageCache.swift:275 — DownloadedImageCache.downloadImageFromNetwork has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 5, error handling 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 · HTMLOpenGraphProperties.parse (cognitive 17) · ×1
  • HTMLOpenGraphProperties.parse (cognitive 17) Modules/RSParser/Sources/RSParser/HTML/HTMLMetadata.swift:229 — HTMLOpenGraphProperties.parse has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 2, match/switch 1 (2 pts), loops 1 (nesting depth added 6). Of this number, 16 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 · gyb.tokenize_template (cognitive 17) · ×1
  • gyb.tokenize_template (cognitive 17) REDACTED:164 — gyb.tokenize_template has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 1, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · HTMLMetadata.resolveFeedLinks (cognitive 16) · ×1
  • HTMLMetadata.resolveFeedLinks (cognitive 16) Modules/RSParser/Sources/RSParser/HTML/HTMLMetadata.swift:127 — HTMLMetadata.resolveFeedLinks has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 8, if/else 7 (8 pts) (nesting depth added 1). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · HTMLScanner.scanStartTag (cognitive 16) · ×1
  • HTMLScanner.scanStartTag (cognitive 16) Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift:115 — HTMLScanner.scanStartTag has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 1, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · XMLEncoding.detectEncodingFromDeclaration (cognitive 16) · ×1
  • XMLEncoding.detectEncodingFromDeclaration (cognitive 16) Modules/RSParser/Sources/RSParser/XML/XMLEncoding.swift:143 — XMLEncoding.detectEncodingFromDeclaration has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 6, if/else 6, loops 4. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · XMLSAXParser.handleStart (cognitive 16) · ×1
  • XMLSAXParser.handleStart (cognitive 16) Modules/RSParser/Sources/RSParser/XML/XMLSAXParser.swift:144 — XMLSAXParser.handleStart has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (8 pts), ternaries 2 (5 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D3 · God Classes · FileTooLong · ×1
  • FileTooLong: REDACTED REDACTED — FileTooLong — 617 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 117 over it, 1.23× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
D3 · God Classes · TooManyMethods · ×1
  • TooManyMethods: DownloadedImageCache Modules/Images/Sources/Images/DownloadedImageCache.swift:43 — 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.
D3 · God Classes · MethodTooLong · ×1
  • MethodTooLong: StripHTML.process Modules/RSCore/Sources/RSCore/StripHTML.swift:177 — MethodTooLong — process runs 101 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1 over it, 1.01× 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.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Edited copy of a member (71 corresponding lines) · ×1
  • Edited copy of a member (71 corresponding lines) Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift:183 — Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift:183-253 | Modules/RSParser/Sources/RSParser/XML/XMLScanner.swift:196-270 — These two members are one piece of code written twice and then edited apart: 71 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 (24 corresponding lines) · ×1
  • Edited copy of a member (24 corresponding lines) Modules/RSParser/Sources/RSParser/Utilities/DateParser.swift:138 — Modules/RSParser/Sources/RSParser/Utilities/DateParser.swift:138-174 | Modules/RSParser/Sources/RSParser/Utilities/DateParser.swift:178-201 — These two members are one piece of code written twice and then edited apart: 24 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 (33 corresponding lines) · ×1
  • Edited copy of a member (33 corresponding lines) Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift:337 — Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift:337-371 | Modules/RSParser/Sources/RSParser/XML/XMLScanner.swift:382-414 — These two members are one piece of code written twice and then edited apart: 33 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) Modules/ActivityLog/Sources/ActivityLog/ActivityLog.swift:75 — Modules/ActivityLog/Sources/ActivityLog/ActivityLog.swift:75-94 | Modules/ActivityLog/Sources/ActivityLog/ActivityLog.swift:97-116 — 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 copies of one member (4 members, 17+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 17+ corresponding lines) Modules/Images/Sources/Images/DownloadFailureTable.swift:23 — Modules/Images/Sources/Images/DownloadFailureTable.swift:23-39 | Modules/Images/Sources/Images/DownloadedImageTable.swift:79-95 | Modules/Images/Sources/Images/HomePageFaviconTable.swift:29-46 | Modules/Images/Sources/Images/HomePageIconTable.swift:29-46 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (37 corresponding lines) · ×1
  • Edited copy of a member (37 corresponding lines) Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift:75 — Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift:75-111 | Modules/RSParser/Sources/RSParser/XML/XMLScanner.swift:85-126 — These two members are one piece of code written twice and then edited apart: 37 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 (19 corresponding lines) · ×1
  • Edited copy of a member (19 corresponding lines) Modules/RSCore/Sources/RSCore/AppKit/MultilineTextFieldSizer.swift:113 — Modules/RSCore/Sources/RSCore/AppKit/MultilineTextFieldSizer.swift:113-131 | iOS/MainTimeline/Cell/MultilineUILabelSizer.swift:73-97 — 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 (16 corresponding lines) · ×1
  • Edited copy of a member (16 corresponding lines) Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift:257 — Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift:257-273 | Modules/RSParser/Sources/RSParser/XML/XMLScanner.swift:274-289 — 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, 4+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 4+ corresponding lines) Modules/HTMLMetadata/Sources/HTMLMetadata/HTMLMetadataDownloader.swift:34 — Modules/HTMLMetadata/Sources/HTMLMetadata/HTMLMetadataDownloader.swift:34-37 | Modules/RSWeb/Sources/RSWeb/DownloadCache.swift:27-30 | Shared/Extensions/ArticleStringFormatter.swift:37-40 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 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 (13 corresponding lines) · ×1
  • Edited copy of a member (13 corresponding lines) Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift:375 — Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift:375-387 | Modules/RSParser/Sources/RSParser/XML/XMLScanner.swift:322-335 — 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 copies of one member (3 members, 8+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 8+ corresponding lines) Modules/Images/Sources/Images/FaviconDownloader.swift:125 — Mac/MainWindow/Sidebar/SidebarViewController.swift:310-317 | Modules/Images/Sources/Images/FaviconDownloader.swift:125-133 | iOS/MainFeed/MainFeedCollectionViewController.swift:935-942 — These 3 members are one piece of code written 3 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 3 times and the copies 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) Modules/Images/Sources/Images/DownloadFailureTable.swift:41 — Modules/Images/Sources/Images/DownloadFailureTable.swift:41-47 | Modules/Images/Sources/Images/HomePageFaviconTable.swift:48-55 | Modules/Images/Sources/Images/HomePageIconTable.swift:48-55 — 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 · Duplicated block (30–34 lines × 2) · ×1
  • Duplicated block (30–34 lines × 2) Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift:123 — Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift:123-152 | Modules/RSParser/Sources/RSParser/XML/XMLScanner.swift:137-170 — before extracting anything, compare `Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift` and `Modules/RSParser/Sources/RSParser/XML/XMLScanner.swift` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 114 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (29–33 lines × 2) · ×1
  • Duplicated block (29–33 lines × 2) Modules/RSCore/Sources/RSCore/AppKit/MultilineTextFieldSizer.swift:221 — Modules/RSCore/Sources/RSCore/AppKit/MultilineTextFieldSizer.swift:221-253 | iOS/MainTimeline/Cell/MultilineUILabelSizer.swift:124-152 — 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 (17–19 lines × 2) · ×1
  • Duplicated block (17–19 lines × 2) Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift:390 — Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift:390-406 | Modules/RSParser/Sources/RSParser/XML/XMLScanner.swift:295-313 — before extracting anything, compare `Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift` and `Modules/RSParser/Sources/RSParser/XML/XMLScanner.swift` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 114 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (17–18 lines × 2) · ×1
  • Duplicated block (17–18 lines × 2) Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift:205 — Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift:205-222 | Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift:237-253 — 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 `Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift:205` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift:203` calls `reserveCapacity` and `Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift:235` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (14–15 lines × 3) · ×1
  • Duplicated block (14–15 lines × 3) Modules/RSParser/Sources/RSParser/XML/XMLScanner.swift:222 — Modules/RSParser/Sources/RSParser/XML/XMLScanner.swift:222-236 | Modules/RSParser/Sources/RSParser/XML/XMLScanner.swift:253-266 | Modules/RSParser/Sources/RSParser/XML/XMLScanner.swift:396-410 — 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 `Modules/RSParser/Sources/RSParser/XML/XMLScanner.swift:222` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Modules/RSParser/Sources/RSParser/XML/XMLScanner.swift:221` calls `reserveCapacity` and `Modules/RSParser/Sources/RSParser/XML/XMLScanner.swift:252` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (14 lines × 2) · ×1
  • Duplicated block (14 lines × 2) Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift:472 — Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift:472-485 | Modules/RSParser/Sources/RSParser/XML/XMLScanner.swift:452-465 — before extracting anything, compare `Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift` and `Modules/RSParser/Sources/RSParser/XML/XMLScanner.swift` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 114 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (13 lines × 3) · ×1
  • Duplicated block (13 lines × 3) Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift:204 — Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift:204-216 | Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift:236-248 | Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift:350-362 — 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 `Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift:204` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift:203` calls `reserveCapacity` and `Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift:235` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (12–13 lines × 2) · ×1
  • Duplicated block (12–13 lines × 2) Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift:375 — Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift:375-387 | Modules/RSParser/Sources/RSParser/XML/XMLScanner.swift:324-335 — before extracting anything, compare `Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift` and `Modules/RSParser/Sources/RSParser/XML/XMLScanner.swift` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 114 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×1
  • Duplicated block (12 lines × 2) Modules/RSCore/Sources/RSCore/String+RSCore.swift:291 — Modules/RSCore/Sources/RSCore/String+RSCore.swift:291-302 | Modules/RSWeb/Sources/RSWeb/String+RSWeb.swift:20-31 — 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 `Modules/RSCore/Sources/RSCore/String+RSCore.swift:291` 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 lines × 2) · ×1
  • Duplicated block (11 lines × 2) Modules/RSParser/Sources/RSParser/Utilities/DateParser.swift:406 — Modules/RSParser/Sources/RSParser/Utilities/DateParser.swift:406-416 | Modules/RSParser/Sources/RSParser/Utilities/DateParser.swift:424-434 — 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.
D4 · Code Duplication · Duplicated block (10 lines × 2) · ×1
  • Duplicated block (10 lines × 2) Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift:184 — Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift:184-193 | Modules/RSParser/Sources/RSParser/XML/XMLScanner.swift:200-210 — before extracting anything, compare `Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift` and `Modules/RSParser/Sources/RSParser/XML/XMLScanner.swift` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 114 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift:184` 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 (9 lines × 2) · ×1
  • Duplicated block (9 lines × 2) Modules/Images/Sources/Images/HomePageFaviconTable.swift:32 — Modules/Images/Sources/Images/HomePageFaviconTable.swift:32-40 | Modules/Images/Sources/Images/HomePageIconTable.swift:32-40 — 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 `Modules/Images/Sources/Images/HomePageFaviconTable.swift:32` 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. 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 (6 lines × 2) · ×1
  • Duplicated block (6 lines × 2) Modules/RSCore/Sources/RSCore/AppKit/MultilineTextFieldSizer.swift:213 — Modules/RSCore/Sources/RSCore/AppKit/MultilineTextFieldSizer.swift:213-219 | iOS/MainTimeline/Cell/MultilineUILabelSizer.swift:117-122 — 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 (7 lines × 2) · ×1
  • Duplicated block (7 lines × 2) Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift:458 — Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift:458-464 | Modules/RSParser/Sources/RSParser/XML/XMLScanner.swift:438-444 — before extracting anything, compare `Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift` and `Modules/RSParser/Sources/RSParser/XML/XMLScanner.swift` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 114 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D5 · Coupling · Unstable project Account · ×1
  • Unstable project Account — Account has instability 0.93 with 1 dependents.
D5 · Coupling · Unstable project HTMLMetadata · ×1
  • Unstable project HTMLMetadata — HTMLMetadata has instability 0.83 with 1 dependents.
R1 · Type Safety · Type Safety · ×1
  • Type Safety — 0 typed · 5 plain JS — the untyped files are Mac/MainWindow/Detail/main_mac.js, REDACTED, Shared/Article Rendering/newsfoot.js, Shared/ShareExtension/SafariExt.js, REDACTED.
R3 · Large Files · REDACTED · ×1
  • REDACTED: 420 lines of code REDACTED:1 — REDACTED has 420 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
Minor — 465 finding(s)
D29 · Static Analysis (SAST) · REDACTED · ×426
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 401 more in this group — see findings.md.
X10 · Duplicated predicate · Duplicated predicate · ×14
  • Duplicated predicate Modules/RSParser/Sources/RSParser/HTML/HTMLRelativeURLResolver.swift:184 — `b.isASCIIWhitespace || b == .asciiEquals || b == .asciiGreaterThan || b == .asciiSlash` appears character-identically in 2 files — Modules/RSParser/Sources/RSParser/HTML/HTMLRelativeURLResolver.swift, Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.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 Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift:394 — `input[end] == .asciiRightBracket && input[end + 1] == .asciiRightBracket && input[end + 2] == .asciiGreaterThan` appears character-identically in 2 files — Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift, Modules/RSParser/Sources/RSParser/XML/XMLScanner.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 Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift:378 — `input[pos] == .asciiHyphen && input[pos + 1] == .asciiHyphen && input[pos + 2] == .asciiGreaterThan` appears character-identically in 2 files — Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift, Modules/RSParser/Sources/RSParser/XML/XMLScanner.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 Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift:258 — `input[pos] == .asciiLessThan && peek(1) == .asciiSlash` appears character-identically in 2 files — Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift, Modules/RSParser/Sources/RSParser/XML/XMLScanner.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 Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift:415 — `input[pos] == .asciiQuestion && input[pos + 1] == .asciiGreaterThan` appears character-identically in 2 files — Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift, Modules/RSParser/Sources/RSParser/XML/XMLScanner.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 Modules/RSCore/Sources/RSCore/AppKit/MultilineTextFieldSizer.swift:237 — `numberOfLines == 2 && oneWidth > width && heightIsProbablyDoubleLineHeight(oneHeight)` appears character-identically in 2 files — Modules/RSCore/Sources/RSCore/AppKit/MultilineTextFieldSizer.swift, iOS/MainTimeline/Cell/MultilineUILabelSizer.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 Modules/RSCore/Sources/RSCore/AppKit/MultilineTextFieldSizer.swift:241 — `oneWidth < width && (oneWidth > smallNeighbor.width || smallNeighbor.width == 0)` appears character-identically in 2 files — Modules/RSCore/Sources/RSCore/AppKit/MultilineTextFieldSizer.swift, iOS/MainTimeline/Cell/MultilineUILabelSizer.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 Modules/RSCore/Sources/RSCore/AppKit/MultilineTextFieldSizer.swift:234 — `oneWidth < width && heightIsProbablySingleLineHeight(oneHeight)` appears character-identically in 2 files — Modules/RSCore/Sources/RSCore/AppKit/MultilineTextFieldSizer.swift, iOS/MainTimeline/Cell/MultilineUILabelSizer.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 Modules/RSCore/Sources/RSCore/AppKit/MultilineTextFieldSizer.swift:243 — `oneWidth > width && (oneWidth < largeNeighbor.width || largeNeighbor.width == 0)` appears character-identically in 2 files — Modules/RSCore/Sources/RSCore/AppKit/MultilineTextFieldSizer.swift, iOS/MainTimeline/Cell/MultilineUILabelSizer.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 Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift:265 — `pos < input.count && input[pos] != .asciiGreaterThan` appears character-identically in 2 files — Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift, Modules/RSParser/Sources/RSParser/XML/XMLScanner.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 Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift:467 — `pos < input.count && input[pos].isASCIIWhitespace` appears character-identically in 2 files — Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift, Modules/RSParser/Sources/RSParser/XML/XMLScanner.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 Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift:438 — `pos < input.count && input[pos].isXMLNameChar` appears character-identically in 2 files — Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift, Modules/RSParser/Sources/RSParser/XML/XMLScanner.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 Modules/RSParser/Sources/RSParser/HTML/HTMLRelativeURLResolver.swift:203 — `quote == .asciiDoubleQuote || quote == .asciiSingleQuote` appears character-identically in 4 files — Modules/RSParser/Sources/RSParser/HTML/HTMLRelativeURLResolver.swift, Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift, Modules/RSParser/Sources/RSParser/XML/XMLEncoding.swift, Modules/RSParser/Sources/RSParser/XML/XMLScanner.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 Modules/RSCore/Sources/RSCore/AppKit/MultilineTextFieldSizer.swift:247 — `smallNeighbor.width != 0 && smallNeighbor.height == largeNeighbor.height` appears character-identically in 2 files — Modules/RSCore/Sources/RSCore/AppKit/MultilineTextFieldSizer.swift, iOS/MainTimeline/Cell/MultilineUILabelSizer.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.
M4 · Documentation accuracy · README/code drift · ×5
  • README/code drift Modules/RSParser/README.md:29 — Modules/RSParser/README.md links to `Feeds/ParsedFeed.swift`, but `Modules/RSParser/Feeds/ParsedFeed.swift` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift Modules/RSParser/README.md:33 — Modules/RSParser/README.md links to `Feeds/JSON/RSSInJSONParser.swift`, but `Modules/RSParser/Feeds/JSON/RSSInJSONParser.swift` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift Modules/RSParser/README.md:33 — Modules/RSParser/README.md links to `Feeds/JSON/JSONFeedParser.swift`, but `Modules/RSParser/Feeds/JSON/JSONFeedParser.swift` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift Modules/RSParser/README.md:33 — Modules/RSParser/README.md links to `Feeds/XML/RSSParser.swift`, but `Modules/RSParser/Feeds/XML/RSSParser.swift` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift Modules/RSParser/README.md:33 — Modules/RSParser/README.md links to `Feeds/XML/AtomParser.swift`, but `Modules/RSParser/Feeds/XML/AtomParser.swift` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
X7 · Silent fallback defaults · Silent fallback default in catch · ×4
  • Silent fallback default in catch Modules/Account/Sources/Account/Feedbin/FeedbinAccountDelegate.swift:997 — `syncArticleReadState` turns every thrown error into `0` — 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 Modules/Account/Sources/Account/Feedbin/FeedbinAccountDelegate.swift:1022 — `syncArticleStarredState` turns every thrown error into `0` — 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 Modules/Account/Sources/Account/NewsBlur/Internals/NewsBlurAccountDelegate+Internal.swift:305 — `syncStoryReadState` turns every thrown error into `0` — 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 Modules/Account/Sources/Account/NewsBlur/Internals/NewsBlurAccountDelegate+Internal.swift:329 — `syncStoryStarredState` turns every thrown error into `0` — 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.
D21 · Naming Consistency · `streamId` spells `Id` where 149 names in the project spell it `ID` · ×2
  • `streamId` spells `Id` where 149 names in the project spell it `ID` Modules/Account/Sources/Account/ReaderAPI/ReaderAPIEntry.swift:196 — 149 of 153 names in project Modules~Account~Account spell the token `ID` (149 of 153; unit: names in project Modules~Account~Account containing `ID`). Peers: Account.containerID (Modules/Account/Sources/Account/Account.swift:111); Account.accountID (Modules/Account/Sources/Account/Account.swift:118); Account.externalID (Modules/Account/Sources/Account/Account.swift:164); Account._externalIDToFeedDictionary (Modules/Account/Sources/Account/Account.swift:188); Account.externalIDToFeedDictionary (Modules/Account/Sources/Account/Account.swift:189). Rename to `streamID`. [rule N6]
  • `streamId` spells `Id` where 149 names in the project spell it `ID` Modules/Account/Sources/Account/ReaderAPI/ReaderAPISubscription.swift:25 — 149 of 153 names in project Modules~Account~Account spell the token `ID` (149 of 153; unit: names in project Modules~Account~Account containing `ID`). Peers: Account.containerID (Modules/Account/Sources/Account/Account.swift:111); Account.accountID (Modules/Account/Sources/Account/Account.swift:118); Account.externalID (Modules/Account/Sources/Account/Account.swift:164); Account._externalIDToFeedDictionary (Modules/Account/Sources/Account/Account.swift:188); Account.externalIDToFeedDictionary (Modules/Account/Sources/Account/Account.swift:189). Rename to `streamID`. [rule N6]
D16 · Bus Factor · Off-boarding risk · ×1
  • Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 77 significant file(s) lose their only recent owner: Modules/RSParser/Sources/RSParser/Utilities/DateParser.swift, Modules/Account/Sources/Account/NewsBlur/NewsBlurAccountDelegate.swift, Modules/RSParser/Sources/RSParser/XML/XMLSAXParser.swift, Modules/RSParser/Sources/RSParser/Feeds/XML/AtomParser.swift, Modules/Account/Sources/Account/NewsBlur/Internals/NewsBlurAccountDelegate+Internal.swift, Modules/RSParser/Sources/RSParser/HTML/HTMLScanner.swift, Modules/RSCore/Sources/RSCore/StripHTML.swift, Modules/Account/Sources/Account/Feedly/FeedlyModel.swift (+69 more). Pair on, review, or document these before any departure.
D20 · ADR Quality · No ADRs found · ×1
  • No ADRs found NetNewsWire.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 `NetNewsWire.xcodeproj/project.pbxproj` makes this repository a deployable product (line 1).
D21 · Naming Consistency · `categoryId` spells `Id` where 149 names in the project spell it `ID` · ×1
  • `categoryId` spells `Id` where 149 names in the project spell it `ID` Modules/Account/Sources/Account/ReaderAPI/ReaderAPISubscription.swift:85 — 149 of 153 names in project Modules~Account~Account spell the token `ID` (149 of 153; unit: names in project Modules~Account~Account containing `ID`). Peers: Account.containerID (Modules/Account/Sources/Account/Account.swift:111); Account.accountID (Modules/Account/Sources/Account/Account.swift:118); Account.externalID (Modules/Account/Sources/Account/Account.swift:164); Account._externalIDToFeedDictionary (Modules/Account/Sources/Account/Account.swift:188); Account.externalIDToFeedDictionary (Modules/Account/Sources/Account/Account.swift:189). Rename to `categoryID`. [rule N6]
D21 · Naming Consistency · `itemId` spells `Id` where 149 names in the project spell it `ID` · ×1
  • `itemId` spells `Id` where 149 names in the project spell it `ID` Modules/Account/Sources/Account/ReaderAPI/ReaderAPIUnreadEntry.swift:22 — 149 of 153 names in project Modules~Account~Account spell the token `ID` (149 of 153; unit: names in project Modules~Account~Account containing `ID`). Peers: Account.containerID (Modules/Account/Sources/Account/Account.swift:111); Account.accountID (Modules/Account/Sources/Account/Account.swift:118); Account.externalID (Modules/Account/Sources/Account/Account.swift:164); Account._externalIDToFeedDictionary (Modules/Account/Sources/Account/Account.swift:188); Account.externalIDToFeedDictionary (Modules/Account/Sources/Account/Account.swift:189). Rename to `itemID`. [rule N6]
D28 · Secrets (history) · Rotate the exposed credentials · ×1
  • REDACTED
D34 · Knowledge Freshness · Further orphaned files (smaller) · ×1
  • Further orphaned files (smaller) — 1 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than raised one row each — most significant first: buildscripts/VerifyNoBS.swift (2 orphaned of 103 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 103 of the 212 production source files in this repository met that bar). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
D34 · Knowledge Freshness · Orphaned file · ×1
  • Orphaned file buildscripts/VerifyNoBS.swift:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
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.
P2 · Observability · Logging is not universal · ×1
  • Logging is not universal — Only 13/15 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`, `.`.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST REDACTED:4 — 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 1 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.
X5 · Nullable reference types · Ruby's type checker does not check nil everywhere · ×1
  • Ruby's type checker does not check nil everywhere — This repository commits no Sorbet configuration (`sorbet/config`) and no `Steepfile`, so nothing type-checks its 1 Ruby product file(s): a nilable value reaches a method call silently and raises `NoMethodError: undefined method … for nil` the first time it is nil. A `# typed:` sigil does nothing without a `sorbet/config` beside the code; a Steep run configured only on a command line is not something this check can read.
Minor — 1 finding(s)
D12 · Dependency Hygiene · Outdated · ×1
  • Outdated: sparkle — `sparkle` is resolved at 2.9.5, but 2.10.1 is the newest release tagged on https://github.com/sparkle-project/Sparkle.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 sparkle` 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-21cbe5c8db1544efa7130f428cbdbbfc/history.json --exit-code 0 --source .12artifacts/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-21cbe5c8db1544efa7130f428cbdbbfc/tree.json --exit-code 0 --source .2artifacts/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 .546artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesosv-scanner—osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm .0artifacts/raw/osv-scanner.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 14 file(s) — `Mac/MainWindow/MainWindowController.swift`, `Modules/Account/Sources/Account/CloudKit/CloudKitRemoteNotificationOperation.swift`, `Modules/Account/Sources/Account/FeedSettingsDatabase.swift`, `Modules/Account/Sources/Account/Feedly/FeedlyAccountDelegate.swift`, `Modules/Account/Sources/Account/ReaderAPI/ReaderAPIAccountDelegate.swift`, … (+9 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 Dependenciesosv-scanner—osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm .0artifacts/raw/osv-scanner.json

Run 01a1d939-2260-75bc-bccc-d6f7e6c96137 · 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