Public report of swiftlang/swift-testing, published 15 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, 15 November 2026, 01:16 UTC · Survey ID cd_faaa4e16eeec46c6b3134f14a77d3351

swiftlang/swift-testing

Measured 15 November 2026, 01:15 UTC, at code version 442fcfe

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

CAI score 51out of 100 Adequate
CriticalWeakAdequateStrongExemplary
Down 3 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: 39,381 lines of product code in 28 projects, tests not counted · Estimated rebuild effort: about 0.4 person-years · Weakest lens: Production Readiness, 35

Findings by how serious they are

156 critical 266 serious 35 minor

36 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
15 November 2026, 01:15 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 ▸

35of 35 dimensions measured by tools.
448of 457 findings point to an exact file and line, so you can open each one in the code. The other 9 concern the repository as a whole, such as missing documentation.
35dimensions across 6 lenses, read from 39,381 lines of product code in 28 projects.
Chapters

Executive summary

swiftlang/swift-testing falls short of our standard for production, in part because we found no logging, tracing or health checks in the code. It scores 51 out of 100 and is rated Adequate, and nine of its 156 critical findings are security problems in the build pipeline and in its automatic dependency updates.

Production Readiness, at 35, is the weakest lens and counts most in the score. The best first step is making the 98 tests that check nothing check their results, worth about 11 points. Adding a diagnostic log would lift Production Readiness itself, worth about 8 points. Raising Production Readiness to 70 would lift the score to about 64.

Eight pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. One automatic update takes new releases before a bad one can be spotted. Pinning each tool to an exact version and setting a waiting period for automatic updates would close both risks. The 144 tests that check nothing need to check the result they produce.

The product code is 39,381 lines, about €57,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.
Production Readiness 35 · counts for 46%Maturity 56 · counts for 25%Performance 70 · counts for 14%Architecture 73 · counts for 8%Code Health 78 · counts for 4%Security and Compliance 90 · counts for 2%

If Production Readiness rose from 35 to 70, the lowest score rated Strong, the score would rise from 51 to about 64.

Code composition: what the lines of code are
Product code 65%Tests 35%
New since the last survey: 49 findings

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

  • Cognitive Complexity · AttributeInfo.functionArgumentList (cognitive 28) Sources/TestingMacros/Support/AttributeDiscovery.swift
  • Cognitive Complexity · __Expression.expandedDescription (cognitive 16) Sources/Testing/SourceAttribution/Expression.swift
  • Code Duplication · Edited copy of a member (43 corresponding lines) Sources/Testing/Expectations/ExpectationChecking+Macro.swift
  • Code Duplication · Edited copy of a member (18 corresponding lines) Sources/Testing/ABI/Encoded/ABI.EncodedEvent.swift
  • Code Duplication · Edited copy of a member (29 corresponding lines) Sources/Testing/Expectations/ExpectationChecking+Macro.swift
  • Code Duplication · Edited copy of a member (20 corresponding lines) Sources/Testing/Support/Graph.swift
  • Code Duplication · Edited copy of a member (28 corresponding lines) Sources/Testing/Expectations/ExpectationChecking+Macro.swift
  • Code Duplication · Edited copy of a member (22 corresponding lines) Sources/Testing/Expectations/ExpectationChecking+Macro.swift
  • Code Duplication · Edited copy of a member (18 corresponding lines) Sources/Testing/Expectations/ExpectationChecking+Macro.swift
  • Code Duplication · Edited copies of one member (6 members, 19+ corresponding lines) Sources/Testing/Expectations/ExpectationChecking+Macro.swift
  • Code Duplication · Edited copy of a member (20 corresponding lines) Sources/Testing/Expectations/ExpectationChecking+Macro.swift
  • Code Duplication · Edited copies of one member (3 members, 18+ corresponding lines) Sources/TestingMacros/Support/DiagnosticMessage.swift
  • Code Duplication · Edited copy of a member (21 corresponding lines) Sources/Testing/Expectations/ExpectationChecking+Macro.swift
  • Code Duplication · Edited copy of a member (19 corresponding lines) Sources/Testing/Expectations/ExpectationChecking+Macro.swift
  • Code Duplication · Edited copies of one member (7 members, 19+ corresponding lines) Sources/Testing/Expectations/ExpectationChecking+Macro.swift
  • Code Duplication · Edited copy of a member (11 corresponding lines) Sources/Overlays/_Testing_WinSDK/Attachments/HBITMAP+AttachableAsIWICBitmapSource.swift
  • Code Duplication · Edited copy of a member (17 corresponding lines) Sources/Testing/Support/FileHandle.swift
  • Code Duplication · Edited copy of a member (13 corresponding lines) Sources/TestingMacros/Support/DiagnosticMessage.swift
  • Code Duplication · Edited copy of a member (14 corresponding lines) Sources/TestingMacros/ConditionMacro.swift
  • Code Duplication · Edited copy of a member (9 corresponding lines) Sources/Testing/Issues/Issue+Recording.swift
  • Code Duplication · Edited copy of a member (11 corresponding lines) Sources/Testing/Support/Graph.swift
  • Code Duplication · Edited copy of a member (8 corresponding lines) Sources/Testing/Support/Graph.swift
  • Code Duplication · Edited copy of a member (7 corresponding lines) Sources/Testing/Support/JSON.Encodable.swift
  • Code Duplication · Edited copy of a member (8 corresponding lines) Sources/Testing/Parameterization/TypeInfo.swift
  • Code Duplication · Edited copy of a member (9 corresponding lines) Sources/Testing/Attachments/Images/Attachment+AttachableAsImage.swift
  • Code Duplication · Edited copy of a member (7 corresponding lines) Sources/Testing/Traits/ConditionTrait.swift
  • Code Duplication · Edited copy of a member (8 corresponding lines) Sources/Testing/Support/Additions/MutexAdditions.swift
  • Code Duplication · Edited copy of a member (7 corresponding lines) Sources/TestingMacros/Support/DiagnosticMessage.swift
  • Code Duplication · Edited copy of a member (7 corresponding lines) Sources/Overlays/_Testing_Foundation/Attachments/_AttachableEncodableWrapper.swift
  • Code Duplication · Edited copy of a member (8 corresponding lines) Sources/Testing/Events/Recorder/Event.ConsoleOutputRecorder.swift
  • Code Duplication · Edited copies of one member (5 members, 3+ corresponding lines) Sources/Overlays/_Testing_AppKit/Attachments/NSImage+AttachableAsImage.swift
  • Code Duplication · Edited copy of a member (3 corresponding lines) Sources/Overlays/_Testing_Foundation/Attachments/Data+Attachable.swift
  • Code Duplication · Edited copy of a member (3 corresponding lines) Sources/Testing/Traits/IssueHandlingTrait.swift
  • Code Duplication · Edited copy of a member (4 corresponding lines) Sources/EmbeddedPlatform/POSIX/EmbeddedPlatformPOSIX.swift
  • Code Duplication · Edited copy of a member (7 corresponding lines) Sources/Testing/Traits/IssueHandlingTrait.swift
  • Code Duplication · Edited copies of one member (3 members, 3+ corresponding lines) Sources/EmbeddedPlatform/EmbeddedPlatformPOSIX+WASI.swift
  • Code Duplication · Duplicated block (12 lines × 2) Sources/Testing/Events/Recorder/Event.HumanReadableOutputRecorder.swift
  • Code Duplication · Duplicated block (9 lines × 2) Sources/Testing/Support/Environment.swift
  • Code Duplication · Duplicated block (6 lines × 2) Sources/Testing/Attachments/Attachable.swift
  • Code Duplication · Edited copy of a member (13 corresponding lines) Sources/TestingMacros/ExitTestCapturedValueMacro.swift
  • Test Quality · No assertions (empty test): sync Tests/NonisolatedNonsendingByDefaultTests/NonisolatedNonsendingByDefaultTests.swift
  • Test Quality · No assertions (empty test): `async` Tests/NonisolatedNonsendingByDefaultTests/NonisolatedNonsendingByDefaultTests.swift
  • Test Quality · No assertions (empty test): Tests/NonisolatedNonsendingByDefaultTests/NonisolatedNonsendingByDefaultTests.swift
  • Test Quality · No assertions (empty test): tupleDestructuring Sources/EmbeddedShowcase/Tests/Tests.swift
  • Test Quality · Test project verifies nothing: NonisolatedNonsendingByDefaultTests Tests/NonisolatedNonsendingByDefaultTests/NonisolatedNonsendingByDefaultTests.swift
  • Explicit Debt · FixmeComment Sources/Testing/Parameterization/Test.Case.Argument.swift
  • Change Coupling · Change coupling: DiagnosticMessage.swift ↔ TagMacro.swift Sources/TestingMacros/Support/DiagnosticMessage.swift
  • Change Coupling · Change coupling: DiagnosticMessage.swift ↔ TestingMacrosMain.swift Sources/TestingMacros/Support/DiagnosticMessage.swift
  • Exception handling · Swallowed exception (empty catch) Sources/Testing/Traits/TimeLimitTrait.swift

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: 16 findings

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

  • Code Duplication · Near-duplicate member pair (55 shared lines) Sources/Testing/Support/SHA256.swift
  • Code Duplication · Duplicated block (31 lines × 2) Sources/Testing/Events/Recorder/Event.Symbol.swift
  • Code Duplication · Duplicated block (24 lines × 2) Sources/Testing/Support/SHA256.swift
  • Code Duplication · Duplicated block (15 lines × 2) Sources/Testing/Support/SHA256.swift
  • Code Duplication · Duplicated block (12 lines × 2) Sources/Testing/Events/Recorder/Event.HumanReadableOutputRecorder.swift
  • Code Duplication · Duplicated block (9 lines × 2) Sources/TestingMacros/Support/DiagnosticMessage.swift
  • Code Duplication · Duplicated block (7 lines × 2) Sources/Testing/Support/SHA256.swift
  • Code Duplication · Duplicated block (5 lines × 2) Sources/Testing/Support/JSON.Encodable.swift
  • Churn × Complexity Hotspots · Hotspot: Sources/TestingMacros/ConditionMacro.swift Sources/TestingMacros/ConditionMacro.swift
  • Explicit Debt · HackComment Sources/Testing/SourceAttribution/Expression.swift
  • Explicit Debt · FixmeComment Sources/Testing/Parameterization/Test.Case.Argument.swift
  • Explicit Debt · FixmeComment Sources/Testing/Parameterization/Test.Case.Argument.swift
  • Explicit Debt · FixmeComment Sources/Testing/Parameterization/Test.Case.Generator.swift
  • Static Analysis (SAST) · High: watchdog-mutable-reusable-workflow-ref .github/workflows/manual_build_freebsd.yml
  • Change Coupling · Change-coupling hub: DiagnosticMessage.swift → FunctionDeclSyntaxAdditions.swift, TagMacro.swift, TestingMacrosMain.swift Sources/TestingMacros/Support/DiagnosticMessage.swift
  • Supply-chain Provenance & Signing · REDACTED .github/workflows/manual_build_freebsd.yml
Rebuild cost: about €57,000 · Estimate
Cost to rebuild€19,000 to €95,000, for 317 to 1,004 hours of work, about 0.4 person-years for one engineer
Difficulty of the problemStandard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor×0.7 at a score of 51. 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: 39,381 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 98 No assertions finding(s) in Test Quality — start with RunnerTests.swift (25), ConfirmationTests.swift (10), EventRecorderTests.swift (8).
Raises the score by about 11 points · Medium effort · Test Quality
2
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Package.swift.
Raises the score by about 5 points · Low effort · ADR Quality
3
Resolve the 1 Off-boarding risk finding(s) in Bus Factor.
Raises the score by about 4 points · Low effort · Bus Factor

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 €57,000 to build again, about 0.4 person-years of work. Its weakest lens is Production Readiness, at 35 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Resolve the 98 No assertions finding(s) in Test Quality. Of all the actions in this report, it raises the score most for the work it takes: about 11 points for medium effort, because it clears the 98 Test Quality findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 7.5 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 2% to 5% on every change. The history of the code shows how much it changes: about 17,786 lines over the last 90 days, which is about 72,132 lines a year. At that pace, the extra work comes to an estimated 3.6 to 24 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.

Architecture — module dependency graph

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

arch EmbeddedPlatformPOSIX+Testing EmbeddedPlatformPOSIX+Testing _TestingInternals (SwiftPM) _TestingInternals (SwiftPM) EmbeddedPlatformPOSIX+Testing->_TestingInternals (SwiftPM) EmbeddedPlatformPicoSDK+Testing EmbeddedPlatformPicoSDK+Testing EmbeddedPlatformPicoSDK+Testing->_TestingInternals (SwiftPM) EmbeddedPlatformWASI+Testing EmbeddedPlatformWASI+Testing EmbeddedPlatformWASI+Testing->_TestingInternals (SwiftPM) EmbeddedShowcase EmbeddedShowcase EmbeddedShowcase->EmbeddedPlatformPOSIX+Testing EmbeddedShowcase->EmbeddedPlatformWASI+Testing Testing (SwiftPM) Testing (SwiftPM) EmbeddedShowcase->Testing (SwiftPM) SymbolShowcase SymbolShowcase SymbolShowcase->Testing (SwiftPM) Testing (CMake) Testing (CMake) _TestingInternals (CMake) _TestingInternals (CMake) Testing (CMake)->_TestingInternals (CMake) _TestingInterop _TestingInterop Testing (CMake)->_TestingInterop Testing (SwiftPM)->_TestingInternals (SwiftPM) _TestingInterop->_TestingInternals (CMake) _Testing_AppKit (CMake) _Testing_AppKit (CMake) _Testing_AppKit (CMake)->Testing (CMake) _Testing_CoreGraphics (CMake) _Testing_CoreGraphics (CMake) _Testing_AppKit (CMake)->_Testing_CoreGraphics (CMake) _Testing_AppKit (SwiftPM) _Testing_AppKit (SwiftPM) _Testing_AppKit (SwiftPM)->Testing (SwiftPM) _Testing_CoreGraphics (SwiftPM) _Testing_CoreGraphics (SwiftPM) _Testing_AppKit (SwiftPM)->_Testing_CoreGraphics (SwiftPM) _Testing_CoreGraphics (CMake)->Testing (CMake) _Testing_CoreGraphics (SwiftPM)->Testing (SwiftPM) _Testing_CoreImage (CMake) _Testing_CoreImage (CMake) _Testing_CoreImage (CMake)->Testing (CMake) _Testing_CoreImage (CMake)->_Testing_CoreGraphics (CMake) _Testing_CoreImage (SwiftPM) _Testing_CoreImage (SwiftPM) _Testing_CoreImage (SwiftPM)->Testing (SwiftPM) _Testing_CoreImage (SwiftPM)->_Testing_CoreGraphics (SwiftPM) _Testing_Foundation (CMake) _Testing_Foundation (CMake) _Testing_Foundation (CMake)->Testing (CMake) _Testing_Foundation (CMake)->_TestingInternals (CMake) _Testing_Foundation (SwiftPM) _Testing_Foundation (SwiftPM) _Testing_Foundation (SwiftPM)->Testing (SwiftPM) _Testing_Foundation (SwiftPM)->_TestingInternals (SwiftPM) _Testing_UIKit (CMake) _Testing_UIKit (CMake) _Testing_UIKit (CMake)->Testing (CMake) _Testing_UIKit (CMake)->_Testing_CoreGraphics (CMake) _Testing_UIKit (SwiftPM) _Testing_UIKit (SwiftPM) _Testing_UIKit (SwiftPM)->Testing (SwiftPM) _Testing_UIKit (SwiftPM)->_Testing_CoreGraphics (SwiftPM) _Testing_UIKit (SwiftPM)->_Testing_CoreImage (SwiftPM) __more__ +8 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.

7 modules, with 8 dependencies between them. One loop runs through 3 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 Harness2 _TestingInterop3 SymbolShowcase4 TestingMacros5 Testing6 EmbeddedPlatform7 Overlays
1 Harness
2 _TestingInterop
3 SymbolShowcase8
4 TestingMacros1537
5 Testing922
6 EmbeddedPlatform5
7 Overlays526
Uses a module listed above itPart of a loopThe module itself
1 Harness2 _TestingInterop3 SymbolShowcase4 TestingMacros5 Testing6 EmbeddedPlatform7 OverlaysHarness1_TestingInterop2SymbolShowcase3TestingMacros4Testing5EmbeddedPlatform6Overlays7815379225526

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

At a glance — Architecture · 73% · Adequate · gated by AX8 ·

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

At a glance — Readiness · 35% · Weak · gated by D10, P2, P3 ·

At a glance — Security · 90% · Checked 4 of 9 ·

At a glance — Performance · 70% · Strong ·

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 — Injection9High / Critical
A02:2025 — Security Misconfiguration1Medium

Roadmap

Top priorities: Resolve the 144 No assertions (empty test) finding(s) in Test Quality — start with MiscellaneousTests.swift (49), RunnerTests.swift (37), ObjCInteropTests.swift (10); Resolve the 98 No assertions finding(s) in Test Quality — start with RunnerTests.swift (25), ConfirmationTests.swift (10), EventRecorderTests.swift (8); Write a diagnostic trail the user can hand back with a bug report: log through `os.Logger` (one per subsystem), which the unified log keeps and a sysdiagnose carries to you. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.

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

Do thisHelpsEffortDimension
Resolve the 98 No assertions finding(s) in Test Quality — start with RunnerTests.swift (25), ConfirmationTests.swift (10), EventRecorderTests.swift (8).+10.6 ptsMediumTest Quality
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Package.swift.+5.2 ptsLowADR Quality
Resolve the 1 Off-boarding risk finding(s) in Bus Factor.+4.1 ptsLowBus Factor
Write a diagnostic trail the user can hand back with a bug report: log through `os.Logger` (one per subsystem), which the unified log keeps and a sysdiagnose carries to you. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.+7.8 ptsMediumObservability
Resolve the 144 No assertions (empty test) finding(s) in Test Quality — start with MiscellaneousTests.swift (49), RunnerTests.swift (37), ObjCInteropTests.swift (10).+13.4 ptsHighTest Quality
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.+4.7 ptsMediumArchitecture documentation
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.+3.8 ptsMediumSecurity & performance tooling
Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.+2.1 ptsMediumDeployment & Rollback

File quality

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

FileScoreBandWorst signal
Tests/TestingTests/RunnerTests.swift3.0SlopTest Quality: No assertions (empty test): f
Tests/TestingTests/MiscellaneousTests.swift3.0SlopTest Quality: No assertions (empty test): f
Tests/TestingTests/EventRecorderTests.swift3.0SlopTest Quality: No assertions (empty test): successBadger
REDACTED3.7SlopStatic Analysis (SAST): High: REDACTED
Tests/TestingTests/Traits/TestScopingTraitTests.swift3.9SlopTest Quality: No assertions (empty test): f
Tests/TestingTests/ObjCInteropTests.swift4.5MixedTest Quality: No assertions (empty test): wrongAnswer
Sources/TestingMacros/Support/DiagnosticMessage.swift4.8MixedCognitive Complexity: DiagnosticMessage.containingNodeUnsupported (cognitive 20)
Tests/TestingTests/Traits/CommentTests.swift5.0MixedTest Quality: No assertions (empty test): example1
Tests/NonisolatedNonsendingByDefaultTests/NonisolatedNonsendingByDefaultTests.swift5.0MixedTest Quality: No assertions (empty test): sync
REDACTED5.1MixedStatic Analysis (SAST): High: REDACTED
Tests/_MemorySafeTestingTests/MemorySafeTestDecls.swift5.5MixedTest Quality: No assertions (empty test): example
Sources/EmbeddedShowcase/Tests/Tests.swift5.5MixedTest Quality: No assertions (empty test): stringsAndNumbers
Tests/TestingTests/EntryPointTests.swift5.8MixedTest Quality: No assertions (empty test): _someHiddenTest
Tests/TestingTests/Traits/ParallelizationTraitTests.swift5.8MixedTest Quality: No assertions (empty test): example
Sources/TestingMacros/ConditionMacro.swift5.9MixedCognitive Complexity: ConditionMacro.expansion (cognitive 31)
Sources/Testing/Events/Recorder/Event.HumanReadableOutputRecorder.swift6.0MixedExplicit Debt: FixmeComment
Sources/Testing/ABI/EntryPoints/EntryPoint.swift6.0MixedExplicit Debt: TodoComment
Sources/Testing/Events/Recorder/Event.Symbol.swift6.0MixedExplicit Debt: TodoComment
Sources/Testing/Running/Runner.Plan.swift6.0MixedExplicit Debt: FixmeComment
Tests/TestingTests/PlanTests.swift6.1MixedTest Quality: No assertions (empty test): example

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

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

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

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

Could not be resolved — 36

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

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

What we checked — 35 dimensions across the health lenses
D1D2D3D4D5D6D10D13D14D15D16D17D20D27D28D29D31D34D35AX10AX3AX4AX8AX9M1M2M3M4P1P2P3P4P6PF3X3

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, 448 of 457 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 · trivy · checkovSecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3 · 3.2.533✓ deterministic

Every finding is locatable in findings.md. Run 01a1dcc6-3669-70b4-a09f-f7880a5a91ab.

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

Run transparency — what happened this run

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

  • D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the Swift half could not be measured — the Swift suite in . 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 (swift-testing), 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.
  • D12 Dependency Hygiene — 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. Not scored — 4 SwiftPM declaration(s) across 1 `Package.swift` and 0 committed pin(s) were read for PINNING discipline (0 defect(s) reported), but the outdated signal comes from listing each declared repository's release tags rather than from a registry, and none of them resolved to a version to compare, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
  • D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
  • D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
  • D26 Project Cohesion — 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. `(repository root)` (39381 LoC, 326 module-visible types across 38 directories) is over its size bounds, and whether one unit is a coherent whole or a grab-bag is read from its type references: the parts of it that reach the rest only through its shared core. Those are read over the C#/VB code model, which this unit's source did not supply. Its size alone is no verdict on its cohesion, so none is published.
  • 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. `Sources/EmbeddedPlatform/POSIX/EmbeddedPlatformPOSIX.swift` 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 REDACTED) is simply not read here yet.
  • AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository defines its own container in Sources/Testing/Traits/IssueHandlingTrait.swift, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via REDACTED (REDACTED). docker build failed (exit 1) — ------ REDACTED:11 -------------------- 9 | ## 10 | 11 | >>> FROM swiftlang/swift:nightly-main-jammy 12 | 13 | # Set up the current build user in the same way done in the Swift.org CI system: -------------------- ERROR: failed to solve: failed to register layer: write /usr/lib/swift/embedded/Swift.swiftmodule/armv7-apple-none-macho.swiftmodule: no space left on device; runtime evidence skipped.
  • C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
  • C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
  • C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
  • GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Swift, c, cpp 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 no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Swift, c, cpp is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
  • P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
  • P8 Schema migrations — 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 EF Core usage in C# and the schema tooling its file scan recognises only, and no .NET project was loaded, and this repository's language is not one the scan models, 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.
  • S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
  • X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust or Kotlin was found in this repository, 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.
  • 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 reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, 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.
  • X13 Undrained process stream — 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, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, 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.
  • X15 Unvalidated length from an untrusted reader — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Ruby, Python, Go, Rust and Dart source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Ruby, Python, Go, Rust or Dart was found in this repository, 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.
  • 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 reads C# syntax, and JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala or Kotlin was found in this repository, 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.
  • X17 Uncapped recursion over a caller-supplied document — 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, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, 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.
  • X18 Disposal-pattern correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP was found in this repository, 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.
  • 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 reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala or PHP was found in this repository, 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.
  • 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 JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python or Rust was found in this repository, 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.
  • X22 Contradicted release guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java, TypeScript/JavaScript, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded, and this repository's C, C++, Swift is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X23 Unguarded diagnostic materialisation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin or PHP was found in this repository, 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 reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, 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.
  • X25 Inert configuration knob — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart and Ruby source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart or Ruby was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X27 Collection changed while being enumerated — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded, no Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala or Kotlin was found, and this repository's C, C++ 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.
  • 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 reads C# syntax, and JavaScript/TypeScript (Vue and Svelte components included), Java, Rust, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, Rust, Dart, Ruby, Scala or Kotlin was found in this repository, 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.
  • X30 Support guard that admits what it rejects — 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 Scala, JavaScript/TypeScript, Java, Kotlin, Python, PHP, Go, Rust, Dart and Ruby source only, and no C# was loaded and no Scala, JavaScript, TypeScript, Java, Kotlin, Python, PHP, Go, Rust, Dart or Ruby was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala or Rust was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X5 Nullable reference types — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's C, Cpp, Swift is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.

Repo exclusion declarations (.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.
  • D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • 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.
  • 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").
  • D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
  • 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.
  • 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.
  • P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
  • P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

Dimensions

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

12 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was HumanReadableOutputRecorder.record at 66. A further 2 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 Snapshot.init at 19 — they are counted neither in the figure above nor in this dimension's score. 2 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: Sources/Testing/Events/Event.swift (Snapshot.init at 19), Sources/TestingMacros/Support/DiagnosticMessage.swift (DiagnosticMessage._kindString at 19). 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.

HumanReadableOutputRecorder.record (cyclomatic 66)Sources/Testing/Events/Recorder/Event.HumanReadableOutputRecorder.swift:285
EntryPoint.swift.configurationForEntryPoint (cyclomatic 35)Sources/Testing/ABI/EntryPoints/EntryPoint.swift:553
EntryPoint.swift.parseCommandLineArguments (cyclomatic 29)Sources/Testing/ABI/EntryPoints/EntryPoint.swift:387
Symbol.unicodeCharacter (cyclomatic 27)Sources/Testing/Events/Recorder/Event.Symbol.swift:136
AdvancedConsoleOutputRecorder._generateHierarchicalSummary (cyclomatic 22)Sources/Testing/Events/Recorder/Event.AdvancedConsoleOutputRecorder.swift:518

+ 7 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 HumanReadableOutputRecorder.record (cyclomatic 66), EntryPoint.swift.configurationForEntryPoint (cyclomatic 35). — 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.5 to about 8.3/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 Complexity5.8 / 10Adequate✓ Tool-verified

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

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

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

30 method(s) exceeded the cognitive complexity threshold of 15; the worst was HumanReadableOutputRecorder.record at 90.

HumanReadableOutputRecorder.record (cognitive 90)Sources/Testing/Events/Recorder/Event.HumanReadableOutputRecorder.swift:285
AdvancedConsoleOutputRecorder._renderHierarchyNode (cognitive 63)Sources/Testing/Events/Recorder/Event.AdvancedConsoleOutputRecorder.swift:650
AdvancedConsoleOutputRecorder._generateHierarchicalSummary (cognitive 54)Sources/Testing/Events/Recorder/Event.AdvancedConsoleOutputRecorder.swift:518
EntryPoint.swift.configurationForEntryPoint (cognitive 46)Sources/Testing/ABI/EntryPoints/EntryPoint.swift:553
EntryPoint.swift.entryPoint (cognitive 45)Sources/Testing/ABI/EntryPoints/EntryPoint.swift:37

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

What to do

  1. Bring the 2 bodies over 60 down to 60 or less in Cognitive Complexity — start with HumanReadableOutputRecorder.record (cognitive 90), AdvancedConsoleOutputRecorder._renderHierarchyNode (cognitive 63). — 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 Cognitive Complexity from 5.8 to about 6.3/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.

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

D3 · God Classes9.5 / 10Stronggated by 4 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.5 / 10 · rule-coverage 100% · ceiling Prevented

4 god class(es) detected.

MethodTooLong: HumanReadableOutputRecorder.recordSources/Testing/Events/Recorder/Event.HumanReadableOutputRecorder.swift:285
FileTooLong: Expectations/ExpectationChecking+Macro.swiftSources/Testing/Expectations/ExpectationChecking+Macro.swift
FunctionTooLong: EntryPoint.swift.configurationForEntryPointSources/Testing/ABI/EntryPoints/EntryPoint.swift:553
TooManyMethods: DiagnosticMessageSources/TestingMacros/Support/DiagnosticMessage.swift:21

What to do

  1. Resolve the 1 MethodTooLong finding(s) in God Classes — start with Event.HumanReadableOutputRecorder.swift. — One of this dimension's main actionable groups (1 warning-level).
  2. Resolve the 1 FileTooLong finding(s) in God Classes — start with ExpectationChecking+Macro.swift. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 FunctionTooLong finding(s) in God Classes — start with EntryPoint.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 Duplication8.4 / 10Strong✓ 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 8.4 / 10 · rule-coverage 100% · ceiling Verified

24 duplicated block group(s) detected. 4.0 % of the production lines (1,576 of 39,381) 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. 1 of the 60 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.

Duplicated block (11 lines × 2) · ×6Sources/Testing/Expectations/ExpectationChecking+Macro.swift:249
Edited copy of a member (7 corresponding lines) · ×5Sources/Testing/Support/JSON.Encodable.swift:424
Edited copy of a member (8 corresponding lines) · ×4Sources/Testing/Support/Graph.swift:397
Duplicated block (12 lines × 2) · ×3Sources/Testing/Events/Recorder/Event.HumanReadableOutputRecorder.swift:425
Edited copy of a member (18 corresponding lines) · ×2Sources/Testing/ABI/Encoded/ABI.EncodedEvent.swift:291

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

What to do

  1. Resolve the 6 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with ExpectationChecking+Macro.swift (6). — One of this dimension's main actionable groups (6 warning-level).
  2. Resolve the 5 Edited copy of a member (7 corresponding lines) finding(s) in Code Duplication — start with JSON.Encodable.swift, ConditionTrait.swift, DiagnosticMessage.swift. — One of this dimension's main actionable groups (5 warning-level).
  3. Resolve the 4 Edited copy of a member (8 corresponding lines) finding(s) in Code Duplication — start with Graph.swift, TypeInfo.swift, MutexAdditions.swift. — One of this dimension's main actionable groups (4 warning-level).

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

D5 · Coupling9.7 / 10Stronggated by 1 serious finding✓ 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 9.7 / 10 · rule-coverage 100% · ceiling Prevented

28 production modules (SwiftPM+CMake), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 1 module(s) off the main sequence, with abstractness counted on 10 of the 28 (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: _Testing_WinSDK (SwiftPM)

What to do

  1. Resolve the 1 Off the main sequence 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)8.3 / 10Strong✓ Tool-verified

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

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

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

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

2 of 14 classes have LCOM4 above 3.

Low cohesion: EncodedAttachment (LCOM4 5) · ×2Sources/Testing/ABI/Encoded/ABI.EncodedAttachment.swift:57

What to do

  1. Resolve the 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with ABI.EncodedAttachment.swift, Attachable.swift. — One of this dimension's main actionable groups (2 warning-level).

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

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

26 skipped (23 with a documented reason), 242 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 929 tests.

No assertions (empty test): sync · ×144Tests/NonisolatedNonsendingByDefaultTests/NonisolatedNonsendingByDefaultTests.swift:18
No assertions: v0_listingTestsOnly · ×98Tests/TestingTests/ABIEntryPointTests.swift:47
Skipped test: disabled · ×3Tests/TestingTests/MiscellaneousTests.swift:81
Test project verifies nothing: NonisolatedNonsendingByDefaultTests · ×2Tests/NonisolatedNonsendingByDefaultTests/NonisolatedNonsendingByDefaultTests.swift:18
Skipped (documented): foundationGeneratedNSError · ×23Tests/TestingTests/BacktraceTests.swift:110

What to do

  1. Resolve the 144 No assertions (empty test) finding(s) in Test Quality — start with MiscellaneousTests.swift (49), RunnerTests.swift (37), ObjCInteropTests.swift (10). — One of this dimension's main actionable groups (144 issue-level).
  2. Resolve the 98 No assertions finding(s) in Test Quality — start with RunnerTests.swift (25), ConfirmationTests.swift (10), EventRecorderTests.swift (8). — One of this dimension's main actionable groups (98 warning-level).
  3. Resolve the 3 Skipped test finding(s) in Test Quality — start with MiscellaneousTests.swift (2), CommentTests.swift. — One of this dimension's main actionable groups (3 warning-level).

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

D13 · Secret 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

Secret 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 2 SwiftPM package(s) use a banned license. SwiftPM has no package registry, so each package's licence is the one its repository declares: 0 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. 2 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.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

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

Top hotspots: Sources/Testing/ABI/EntryPoints/EntryPoint.swift (22×35=770); Sources/Testing/Events/Recorder/Event.HumanReadableOutputRecorder.swift (7×66=462); Sources/Testing/Events/Recorder/Event.Symbol.swift (3×27=81)

Hotspot: Sources/Testing/ABI/EntryPoints/EntryPoint.swift · ×4Sources/Testing/ABI/EntryPoints/EntryPoint.swift:553

What to do

  1. Resolve the 4 Hotspot finding(s) in Churn × Complexity Hotspots — start with EntryPoint.swift, Event.HumanReadableOutputRecorder.swift, Event.Symbol.swift. — One of this dimension's main actionable groups (4 warning-level).

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

D16 · Bus Factor4.6 / 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 4.6 / 10 · rule-coverage 100% · ceiling Documented

83 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is Sources/Testing/Expectations/Expectation+Macro.swift. Counted over 155 of the 216 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 Debt9.8 / 10Stronggated by 36 serious findings✓ Tool-verified

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

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

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

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

TodoComment · ×23Sources/TestingMacros/Support/ConditionArgumentParsing.swift:237
FixmeComment · ×12Tests/TestingTests/Test.SnapshotTests.swift:26
HackCommentSources/Testing/ExitTests/ExitTest.swift:867

What to do

  1. Resolve the 23 TodoComment finding(s) in Explicit Debt — start with ConditionTrait+Macro.swift (2), ParallelizationTrait.swift (2), ExitTest.swift (2). — One of this dimension's main actionable groups (23 warning-level).
  2. Resolve the 12 FixmeComment finding(s) in Explicit Debt — start with CustomTestStringConvertible.swift (2), Runner.Plan.swift (2), Test.Case.Argument.swift (2). — One of this dimension's main actionable groups (12 warning-level).
  3. Resolve the 1 HackComment finding(s) in Explicit Debt — start with ExitTest.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 foundPackage.swift:93

What to do

  1. Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Package.swift. — 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.

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

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

✓ On the Gold path — maintain.

Detailed fixes: d27_recommendation.md.

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d28_recommendation.md.

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

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

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

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

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

9 finding(s): 0 critical, 9 high, 0 medium, 0 low. 7 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 6 file(s) — `Sources/_TestingInternals/include/Demangle.h` (line 32, line 35, line 36, …), `Sources/_TestingInternals/include/EmbeddedPlatform+Testing.h`, `Sources/_TestingInternals/include/Stubs.h` (line 24, line 70, line 74, …), `Sources/_TestingInternals/include/TestSupport.h` (line 24, line 46, line 47, …), `Sources/_TestingInternals/include/Versions.h` (line 25, line 69, line 78, …), … (+1 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

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

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

D31 · IaC & Container Security9.9 / 10Stronggated by 1 serious finding✓ Tool-verified

What it measures: Whether Dockerfiles / Terraform / Kubernetes config follow security best practices.

Method: IaC/container misconfiguration scan via trivy config (REDACTED/Terraform/K8s/Helm/CloudFormation); severity rules to 0-10 moderate normalizer. NotApplicable without manifests. Exhaustive, deterministic.

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

1 finding(s): 0 critical, 0 high, 1 medium, 0 low.

REDACTED

What to do

  1. Resolve the 1 Medium IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).

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

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d34_recommendation.md.

D35 · Change Coupling8.8 / 10Strong✓ 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 8.8 / 10 · rule-coverage 100% · ceiling Documented

Strongest change-coupling: SuiteDeclarationMacro.swift↔TestDeclarationMacro.swift 87%; ABI.EncodedMessage.swift↔EntryPoint.swift 82%; DiagnosticMessage.swift↔TagMacro.swift 70%

Change coupling: DiagnosticMessage.swift ↔ TagMacro.swift · ×7Sources/TestingMacros/Support/DiagnosticMessage.swift:1
Change-coupling hub: TestDeclarationMacro.swift → SuiteDeclarationMacro.swift, FunctionDeclSyntaxAdditions.swift, TestContentGeneration.swift, TagMacro.swift · ×2Sources/TestingMacros/TestDeclarationMacro.swift

What to do

  1. Resolve the 7 Change coupling finding(s) in Change Coupling — start with DiagnosticMessage.swift (2), Expectation+Macro.swift, SuiteDeclarationMacro.swift. — One of this dimension's main actionable groups (7 warning-level).
  2. Resolve the 2 Change-coupling hub finding(s) in Change Coupling — start with TestDeclarationMacro.swift, EntryPoint.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.

Frontend & cross-cutting dimensions

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

AX10 · Code composition9.8 / 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 isolation2.5 / 10Weak✓ 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.

  • `EmbeddedShowcase` (production) references the test project `EmbeddedShowcaseTests`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
  • `Testing (CMake)` (production) references the test project `_TestDiscovery (CMake)`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
  • `Testing (SwiftPM)` (production) references the test project `_TestDiscovery (SwiftPM)`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.

What to do

  • Remove every production → test project reference: extract any shared test helper into a production support library (which the tests reference), or invert the dependency so the test project depends on production — not the reverse.
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)6.7 / 10Adequate✓ 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

  • Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
M2 · Architecture documentation0.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.
  • No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.

What to do

  • Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
  • Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project 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 accuracy10.0 / 10Exemplary○ Nothing flagged

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.

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.

P2 · Observability0.0 / 10Critical✓ 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.

  • No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.

What to do

  • Write a diagnostic trail the user can hand back with a bug report: log through `os.Logger` (one per subsystem), which the unified log keeps and a sysdiagnose carries to you. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
P3 · Security & performance tooling3.0 / 10Weak✓ 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 5 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:7

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.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback5.0 / 10Adequate✓ Tool-verified

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

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

What to do

  • Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P6 · Release Hygiene5.0 / 10Adequate✓ Tool-verified

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

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

  • No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)

What to do

  • Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF3 · Async & latency hygiene7.0 / 10Strong✓ 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.

  • `sleep` is async and calls sleep — a blocking call inside async code stalls the cooperative pool's thread — one per core — and every task scheduled on it for as long as it runs. (×2) — Sources/Testing/Events/Clock.swift:182, Sources/Testing/Events/Clock.swift:202

What to do

  • Swift: await instead of blocking — `try await Task.sleep(for:)` for Thread.sleep/sleep, a checked continuation instead of a DispatchSemaphore or DispatchGroup wait, the async Process and URLSession APIs; never park a thread waiting on a Task — the cooperative pool cannot guarantee it progress.
X3 · Exception handling6.7 / 10Adequate✓ Tool-verified

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

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

  • 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. — Sources/Testing/Traits/TimeLimitTrait.swift:291

What to do

  • Swallowed exception (empty catch)

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 Health78%StrongSolid.
Architecture73%Adequate — gated by AX8Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity56%Adequate — gated by M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness35%Weak — gated by D10, P2, P3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security90%Checked 4 of 9Strongest area.
Performance70%StrongSolid.
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.

  • D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
  • X10 Duplicated predicate — 6 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 control(s) we could not find positive evidence for

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

  • C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 77 check(s) not relevant to this codebase

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

  • AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
  • AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
  • AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
  • AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
  • AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
  • AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
  • AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No 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.
  • 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
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXR1 Runtime accessibility — docker build failed (exit 1) — ------ REDACTED:11 -------------------- 9 | ## 10 | 11 | >>> FROM swiftlang/swift:nightly-main-jammy 12 | 13 | # Set up the current build user in the same way done in the Swift.org CI system: -------------------- ERROR: failed to solve: failed to register layer: write /usr/lib/swift/embedded/Swift.swiftmodule/armv7-apple-none-macho.swiftmodule: no space left on device; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
  • C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • C4 Data Retention — No personal data detected in a persisted data model — no PII-named property (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a SwiftData @Model, a Core Data, Realm, GRDB or Fluent type, a GRDB or SQLite.swift column, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (CoreData, SwiftData, GRDB, RealmSwift, SQLite, Firebase, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
  • C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named property (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a SwiftData @Model, a Core Data, Realm, GRDB or Fluent type, a GRDB or SQLite.swift column, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (CoreData, SwiftData, GRDB, RealmSwift, SQLite, Firebase, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
  • D11 Test Reliability — Test reliability not included — the .swift suite was found but not re-run
  • D12 Dependency Hygiene — Not scored — 4 SwiftPM declaration(s) across 1 `Package.swift` and 0 committed pin(s) were read for PINNING discipline (0 defect(s) reported), but the outdated signal comes from listing each declared repository's release tags rather than from a registry, and none of them resolved to a version to compare, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
  • 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.
  • D21 Naming Consistency — D21 withholds its case and prefix conventions rows: 1 candidate(s) found and not reported.
  • D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
  • D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
  • D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .swift, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • D25 ADR Conformance — no ADRs to check
  • D26 Project Cohesion — D26 could not read how the parts of this repository's one build unit reference each other, so its cohesion was not measured. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Swift Package.swift/Package.resolved — not scanned yet).
  • D32 Data Compliance (PII/GDPR) — 1 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.
  • D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Swift Package.swift/Package.resolved — not scanned yet).
  • 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 Swift source, so there is no service whose uptime a failing dependency could take down
  • P8 Schema migrations — 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
  • 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.
  • 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 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
  • X12 Unreachable branch — 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
  • X13 Undrained process stream — 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
  • X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X15 Unvalidated length from an untrusted reader — not 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
  • X16 Unfloored truncation loop — 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
  • X17 Uncapped recursion over a caller-supplied document — 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
  • X18 Disposal-pattern correctness — 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
  • X19 Unrestored process-global state — 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
  • 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: this check looks for a pattern guard or `case` label that increments, decrements or assigns while the switch is deciding whether it matches, and in this repository's languages none can. In C a `case` label must be a constant expression, and a switch has no guards, so no label can change state. In C++ a `case` label must be a constant expression, and a switch has no guards, so no label can change state. Swift has no `++` or `--`, and an assignment yields `()`, which cannot be an operand of `&&`, `||` or `?:` nor the Bool a `case … where` clause needs. Not a gap in the analyzer and not a finding about your code.
  • X22 Contradicted release guard — 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
  • X23 Unguarded diagnostic materialisation — 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
  • X24 Document value interpolated into markup unescaped — 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
  • X25 Inert configuration knob — 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
  • X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X27 Collection changed while being enumerated — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X29 Per-element action decided by a fixed element — not 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
  • X30 Support guard that admits what it rejects — 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
  • X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

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 — 156 finding(s)
D10 · Test Quality · No assertions (empty test) · ×144
  • No assertions (empty test): sync Tests/NonisolatedNonsendingByDefaultTests/NonisolatedNonsendingByDefaultTests.swift:18 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): `async` Tests/NonisolatedNonsendingByDefaultTests/NonisolatedNonsendingByDefaultTests.swift:19 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): Tests/NonisolatedNonsendingByDefaultTests/NonisolatedNonsendingByDefaultTests.swift:20 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): noop Tests/TestingTests/DumpTests.swift:34 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): noop Tests/TestingTests/DumpTests.swift:37 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): noop Tests/TestingTests/DumpTests.swift:40 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): noop Tests/TestingTests/DumpTests.swift:43 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): successBadger Tests/TestingTests/EventRecorderTests.swift:680 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): severalLarks Tests/TestingTests/EventRecorderTests.swift:681 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): actuallyCrab Tests/TestingTests/EventRecorderTests.swift:687 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): unavailablePigeon Tests/TestingTests/EventRecorderTests.swift:699 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): futureGrouse Tests/TestingTests/EventRecorderTests.swift:703 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): futureGoose Tests/TestingTests/EventRecorderTests.swift:707 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): futureMouse Tests/TestingTests/EventRecorderTests.swift:711 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): futureMoose Tests/TestingTests/EventRecorderTests.swift:715 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): f Tests/TestingTests/MiscellaneousTests.swift:40 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): succeeds Tests/TestingTests/MiscellaneousTests.swift:63 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): parameterized Tests/TestingTests/MiscellaneousTests.swift:66 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): parameterized2 Tests/TestingTests/MiscellaneousTests.swift:69 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): succeeds Tests/TestingTests/MiscellaneousTests.swift:75 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): succeedsAsync Tests/TestingTests/MiscellaneousTests.swift:78 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): parameterized Tests/TestingTests/MiscellaneousTests.swift:84 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): `static` Tests/TestingTests/MiscellaneousTests.swift:87 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): `reserved1` Tests/TestingTests/MiscellaneousTests.swift:89 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): parameterizedOwned Tests/TestingTests/MiscellaneousTests.swift:101 — Test method has an empty body — it asserts nothing and exercises no code.
  • + 119 more in this group — see findings.md.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AX8 · Test isolation · Production project references a test project · ×3
  • Production project references a test project: EmbeddedShowcase → EmbeddedShowcaseTests — `EmbeddedShowcase` (production) references the test project `EmbeddedShowcaseTests`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
  • Production project references a test project: Testing (CMake) → _TestDiscovery (CMake) — `Testing (CMake)` (production) references the test project `_TestDiscovery (CMake)`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
  • Production project references a test project: Testing (SwiftPM) → _TestDiscovery (SwiftPM) — `Testing (SwiftPM)` (production) references the test project `_TestDiscovery (SwiftPM)`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
Serious — 266 finding(s)
D10 · Test Quality · No assertions · ×98
  • No assertions: v0_listingTestsOnly Tests/TestingTests/ABIEntryPointTests.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: saveValue Tests/TestingTests/AttachmentTests.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: writeAttachment Tests/TestingTests/AttachmentTests.swift:88 — 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: writeAttachmentWithBadName Tests/TestingTests/AttachmentTests.swift:162 — 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: cloneAttachment Tests/TestingTests/AttachmentTests.swift:234 — 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: thrownErrorCapturesBacktrace Tests/TestingTests/BacktraceTests.swift:21 — 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: typedThrownErrorCapturesBacktrace Tests/TestingTests/BacktraceTests.swift:43 — 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: thrownNSErrorCapturesBacktrace Tests/TestingTests/BacktraceTests.swift:76 — 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: successfulConfirmations Tests/TestingTests/ConfirmationTests.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: unsuccessfulConfirmations Tests/TestingTests/ConfirmationTests.swift:30 — 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: mainActorIsolated Tests/TestingTests/ConfirmationTests.swift:99 — 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: basicConfirmation Tests/TestingTests/ConfirmationTests.swift:110 — 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: confirmed0Times Tests/TestingTests/ConfirmationTests.swift:117 — 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: confirmed3Times Tests/TestingTests/ConfirmationTests.swift:122 — 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: basicConfirmation Tests/TestingTests/ConfirmationTests.swift:132 — 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: confirmedTooFewTimes Tests/TestingTests/ConfirmationTests.swift:137 — 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: confirmedTooManyTimes Tests/TestingTests/ConfirmationTests.swift:144 — 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: confirmedOutOfRange Tests/TestingTests/ConfirmationTests.swift:151 — 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: hiddenTests Tests/TestingTests/EntryPointTests.swift:16 — 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: uncommonComments Tests/TestingTests/EventRecorderTests.swift:273 — 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: failWhale Tests/TestingTests/EventRecorderTests.swift:665 — 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: multitudeOcelot Tests/TestingTests/EventRecorderTests.swift:682 — 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: commented Tests/TestingTests/EventRecorderTests.swift:719 — 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: quotationalQuokka Tests/TestingTests/EventRecorderTests.swift:736 — 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: cornyUnicorn🦄 Tests/TestingTests/EventRecorderTests.swift:740 — 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.
  • + 73 more in this group — see findings.md.
D17 · Explicit Debt · TodoComment · ×23
  • TodoComment Sources/TestingMacros/Support/ConditionArgumentParsing.swift:237 — // TODO: capture closures as a different kind of Testing.Expression with a — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment Sources/Testing/EmbeddedPlatform.swift:43 — // TODO: determine whether we can reliably call `print()` here or something else — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment Sources/Testing/Test+Cancellation.swift:44 — // TODO: when our deployment targets allow, we should switch to calling the — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment Sources/Testing/Traits/AttachmentSavingTrait.swift:163 — // TODO: adopt async defer if/when we get it — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment Sources/Testing/Traits/ConditionTrait+Macro.swift:62 — // TODO: Semantic capture of platform name/version (rather than just a comment) — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment Sources/Testing/Traits/ConditionTrait+Macro.swift:94 — // TODO: Semantic capture of platform name/version (rather than just a comment) — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment Sources/Testing/Traits/ParallelizationTrait.swift:17 — // TODO: update this documentation to clarify .serialized vs. .serialized(for:) — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment Sources/Testing/Traits/ParallelizationTrait.swift:176 — // TODO: share an implementation with that function? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment Sources/Testing/SourceAttribution/Backtrace+Symbolication.swift:80 — // TODO: adopt the standard library's Backtrace on these platforms — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment Sources/Testing/SourceAttribution/CustomTestStringConvertible.swift:158 — // TODO: avoid hard-coding — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment Sources/Testing/Running/Runner.Plan.swift:284 — // TODO: split the task group's single task into two serially-run subtasks — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment Sources/Testing/ExitTests/ExitTest.swift:1062 — // TODO: should we record these issues as systemic instead? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment Sources/Testing/ExitTests/ExitTest.swift:1080 — // TODO: should we record these issues as systemic instead? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment Sources/Testing/Events/Event+FallbackEventHandler.swift:138 — // TODO: try to actually extract a source location from arbitrary JSON? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment Sources/Testing/Events/Recorder/Event.Symbol.swift:166 — // TODO: decide on symbol — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment Sources/Testing/Events/Recorder/Event.Symbol.swift:203 — // TODO: decide on symbol — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment Sources/Testing/ABI/EntryPoints/EntryPoint.swift:497 — // TODO: decide if we want to repurpose --num-workers for this use case? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment Sources/Testing/ABI/Encoded/ABI.EncodedError.swift:42 — // TODO: userInfo (partial) encoding — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment Sources/Testing/ABI/Encoded/ABI.EncodedError.swift:63 — // TODO: userInfo (partial) encoding — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment Sources/Testing/ABI/Encoded/ABI.EncodedIssue.swift:318 — // TODO: improve fidelity of issue kind reporting (especially those without associated values) — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment Sources/Testing/ABI/Encoded/ABI.EncodedTest.swift:137 — // TODO: define an encodable form of Test.Case.ID — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment Sources/Overlays/_Testing_Foundation/Attachments/Attachment+URL.swift:68 — // TODO: network URLs? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment Sources/Overlays/_Testing_Foundation/Attachments/_AttachableURLWrapper.swift:159 — // TODO: Windows implementation — 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.
D17 · Explicit Debt · FixmeComment · ×12
  • FixmeComment Tests/TestingTests/Test.SnapshotTests.swift:26 — // FIXME: Compare traits as well, once they are included. — 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.
  • FixmeComment Sources/_TestDiscovery/SectionBounds.swift:228 — // FIXME: Handle longer names ("/%u") from string table — 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.
  • FixmeComment Sources/Testing/Traits/ParallelizationTrait.swift:177 — // FIXME: if this dict rehashes mid-flight, will we deadlock? — 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.
  • FixmeComment Sources/Testing/SourceAttribution/CustomTestStringConvertible.swift:147 — // FIXME: need some sort of description functionality for arbitrary values — 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.
  • FixmeComment Sources/Testing/SourceAttribution/CustomTestStringConvertible.swift:152 — // FIXME: need some sort of description functionality for types — 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.
  • FixmeComment Sources/Testing/Running/Runner.Plan.swift:277 — // FIXME: Parallelize this work. Calling `prepare(...)` on all traits and — 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.
  • FixmeComment Sources/Testing/Running/Runner.Plan.swift:382 — // FIXME: Handle this more gracefully, either by propagating the error — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment Sources/Testing/Running/Runner.swift:383 — // FIXME: this operation is likely O(n log n) or worse when amortized — 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.
  • FixmeComment Sources/Testing/Parameterization/Test.Case.Argument.swift:142 — // FIXME: Capture the error and propagate to the user, not as a test — 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.
  • FixmeComment Sources/Testing/Parameterization/Test.Case.Argument.swift:170 — // FIXME: switch to variadic generics when Embedded Swift support improves — 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.
  • FixmeComment Sources/Testing/Events/Recorder/Event.HumanReadableOutputRecorder.swift:672 — // FIXME: handle test cases here (not supported in the JSON event stream) — 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.
  • FixmeComment Sources/Testing/Attachments/Images/Attachment+AttachableAsImage.swift:105 — // FIXME: no way to express `where AttachableValue == _AttachableImageWrapper<???>` on a property (see rdar://47559973) — 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.
D35 · Change Coupling · Change coupling · ×7
  • Change coupling: DiagnosticMessage.swift ↔ TagMacro.swift Sources/TestingMacros/Support/DiagnosticMessage.swift:1 — `Sources/TestingMacros/Support/DiagnosticMessage.swift` and `Sources/TestingMacros/TagMacro.swift` change together 70% of the time (7 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `461716f6` Reenable suites in Embedded Swift.; `a1bff66a` Update the `@Tag` macro to work in Embedded Swift. (#1905); `ddf67d4b` Add support for module selectors in types during macro expansion. (#1… — run `git show` on any of them.
  • Change coupling: Expectation+Macro.swift ↔ TestingMacrosMain.swift Sources/Testing/Expectations/Expectation+Macro.swift:1 — `Sources/Testing/Expectations/Expectation+Macro.swift` and `Sources/TestingMacros/TestingMacrosMain.swift` change together 67% of the time (8 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these 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 `06a94d49` Enhance closure-based expectation failures. (#1582); `e63d542c` Diagnose when we incorrectly infer the type of a capture list item in…; `eac4833c` Improve the diagnostics for a bad exit test capture. (#1146) — run `git show` on any of them.
  • Change coupling: SuiteDeclarationMacro.swift ↔ TestContentGeneration.swift Sources/TestingMacros/SuiteDeclarationMacro.swift:1 — `Sources/TestingMacros/SuiteDeclarationMacro.swift` and `Sources/TestingMacros/Support/TestContentGeneration.swift` change together 60% of the time (9 of the 15 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `dec4ce60` Simplify the expansion of `@Test` by eliminating the `isolated` thunk…; `acf8538a` Drop remaining Swift 6.2 support. (#1481); `5d7ea2b2` Remove the separate `accessorDecl` declaration from macro expansions.… — run `git show` on any of them.
  • Change coupling: ConditionMacro.swift ↔ TestContentGeneration.swift Sources/TestingMacros/ConditionMacro.swift:1 — `Sources/TestingMacros/ConditionMacro.swift` and `Sources/TestingMacros/Support/TestContentGeneration.swift` change together 60% of the time (9 of the 15 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `dec4ce60` Simplify the expansion of `@Test` by eliminating the `isolated` thunk…; `acf8538a` Drop remaining Swift 6.2 support. (#1481); `5d7ea2b2` Remove the separate `accessorDecl` declaration from macro expansions.… — run `git show` on any of them.
  • Change coupling: ABI.EncodedMessage.swift ↔ Configuration.swift Sources/Testing/ABI/Encoded/ABI.EncodedMessage.swift:1 — `Sources/Testing/ABI/Encoded/ABI.EncodedMessage.swift` and `Sources/Testing/Running/Configuration.swift` change together 55% of the time (6 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `fb93dd4b` Introduce a severity level for issues, and a 'warning' severity (un-r… (at that commit the file was still `Sources/Testing/ABI/v0/Encoded/ABIv0.EncodedMessage.swift`); `afe25055` Revert "Introduce a severity level for issues, and a 'warning' severi… (at that commit the file was still `Sources/Testing/ABI/v0/Encoded/ABIv0.EncodedMessage.swift`); `6a49142b` Introduce a severity level for issues, and a 'warning' severity (#931) (at that commit the file was still `Sources/Testing/ABI/v0/Encoded/ABIv0.EncodedMessage.swift`) — run `git show` on any of them.
  • Change coupling: ABI.EncodedIssue.swift ↔ ABI.EncodedMessage.swift Sources/Testing/ABI/Encoded/ABI.EncodedIssue.swift:1 — `Sources/Testing/ABI/Encoded/ABI.EncodedIssue.swift` and `Sources/Testing/ABI/Encoded/ABI.EncodedMessage.swift` change together 55% of the time (6 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `bb8abff4` Show subexpressions separately in expectation failures. (#1572); `fb93dd4b` Introduce a severity level for issues, and a 'warning' severity (un-r… (at that commit the files were still `Sources/Testing/ABI/v0/Encoded/ABIv0.EncodedIssue.swift` and `Sources/Testing/ABI/v0/Encoded/ABIv0.EncodedMessage.swift`); `afe25055` Revert "Introduce a severity level for issues, and a 'warning' severi… (at that commit the files were still `Sources/Testing/ABI/v0/Encoded/ABIv0.EncodedIssue.swift` and `Sources/Testing/ABI/v0/Encoded/ABIv0.EncodedMessage.swift`) — run `git show` on any of them.
  • Change coupling: DiagnosticMessage.swift ↔ TestingMacrosMain.swift Sources/TestingMacros/Support/DiagnosticMessage.swift:1 — `Sources/TestingMacros/Support/DiagnosticMessage.swift` and `Sources/TestingMacros/TestingMacrosMain.swift` change together 50% of the time (6 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `eac4833c` Improve the diagnostics for a bad exit test capture. (#1146); `9de90844` Remove `#expect(throws: Never.self)` and `#require(throws: Never.self…; `097db6c5` Warn when passing a non-optional value to `try #require(T?)`. (#620) — run `git show` on any of them.
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×6
  • Duplicated block (11 lines × 2) Sources/Testing/Expectations/ExpectationChecking+Macro.swift:249 — Sources/Testing/Expectations/ExpectationChecking+Macro.swift:249-259 | Sources/Testing/Expectations/ExpectationChecking+Macro.swift:431-441 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (11 lines × 2) Sources/Testing/Expectations/ExpectationChecking+Macro.swift:279 — Sources/Testing/Expectations/ExpectationChecking+Macro.swift:279-289 | Sources/Testing/Expectations/ExpectationChecking+Macro.swift:461-471 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (11 lines × 2) Sources/Testing/Expectations/ExpectationChecking+Macro.swift:308 — Sources/Testing/Expectations/ExpectationChecking+Macro.swift:308-318 | Sources/Testing/Expectations/ExpectationChecking+Macro.swift:490-500 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (11 lines × 2) Sources/Testing/Expectations/ExpectationChecking+Macro.swift:337 — Sources/Testing/Expectations/ExpectationChecking+Macro.swift:337-347 | Sources/Testing/Expectations/ExpectationChecking+Macro.swift:519-529 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (11 lines × 2) Sources/Testing/Expectations/ExpectationChecking+Macro.swift:366 — Sources/Testing/Expectations/ExpectationChecking+Macro.swift:366-376 | Sources/Testing/Expectations/ExpectationChecking+Macro.swift:548-558 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (11 lines × 2) Sources/Testing/Expectations/ExpectationChecking+Macro.swift:398 — Sources/Testing/Expectations/ExpectationChecking+Macro.swift:398-408 | Sources/Testing/Expectations/ExpectationChecking+Macro.swift:581-591 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Edited copy of a member (7 corresponding lines) · ×5
  • Edited copy of a member (7 corresponding lines) Sources/Testing/Support/JSON.Encodable.swift:424 — Sources/Testing/Support/JSON.Encodable.swift:424-430 | Sources/Testing/Support/JSON.Encodable.swift:440-446 — These two members are one piece of code written twice and then edited apart: 7 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 (7 corresponding lines) Sources/Testing/Traits/ConditionTrait.swift:123 — Sources/Testing/Traits/ConditionTrait.swift:123-129 | Sources/Testing/Traits/ConditionTrait.swift:182-188 — These two members are one piece of code written twice and then edited apart: 7 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 (7 corresponding lines) Sources/TestingMacros/Support/DiagnosticMessage.swift:181 — Sources/TestingMacros/Support/DiagnosticMessage.swift:181-188 | Sources/TestingMacros/Support/DiagnosticMessage.swift:467-473 — These two members are one piece of code written twice and then edited apart: 7 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 (7 corresponding lines) Sources/Overlays/_Testing_Foundation/Attachments/_AttachableEncodableWrapper.swift:88 — Sources/Overlays/_Testing_Foundation/Attachments/_AttachableEncodableWrapper.swift:88-94 | Sources/Testing/Attachments/Attachment.swift:157-163 — These two members are one piece of code written twice and then edited apart: 7 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 (7 corresponding lines) Sources/Testing/Traits/IssueHandlingTrait.swift:75 — Sources/Testing/Traits/IssueHandlingTrait.swift:75-81 | Sources/Testing/Traits/ParallelizationTrait.swift:144-150 — These two members are one piece of code written twice and then edited apart: 7 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.
D15 · Churn × Complexity Hotspots · Hotspot · ×4
  • Hotspot: Sources/Testing/ABI/EntryPoints/EntryPoint.swift Sources/Testing/ABI/EntryPoints/EntryPoint.swift:553 — Sources/Testing/ABI/EntryPoints/EntryPoint.swift changed 22 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 35 in EntryPoint.swift.configurationForEntryPoint at line 553. 1 of those changes was a fix/bug commit, 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 13:33:34 -05:00' --until='2026-11-14 13:33:34 -05:00' --full-history --no-merges -- Sources/Testing/ABI/EntryPoints/EntryPoint.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: Sources/Testing/Events/Recorder/Event.HumanReadableOutputRecorder.swift Sources/Testing/Events/Recorder/Event.HumanReadableOutputRecorder.swift:285 — Sources/Testing/Events/Recorder/Event.HumanReadableOutputRecorder.swift changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 66 in HumanReadableOutputRecorder.record at line 285. 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 13:33:34 -05:00' --until='2026-11-14 13:33:34 -05:00' --full-history --no-merges -- Sources/Testing/Events/Recorder/Event.HumanReadableOutputRecorder.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: Sources/Testing/Events/Recorder/Event.Symbol.swift Sources/Testing/Events/Recorder/Event.Symbol.swift:136 — Sources/Testing/Events/Recorder/Event.Symbol.swift changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in Symbol.unicodeCharacter at line 136. 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 13:33:34 -05:00' --until='2026-11-14 13:33:34 -05:00' --full-history --no-merges -- Sources/Testing/Events/Recorder/Event.Symbol.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: Sources/TestingMacros/TestDeclarationMacro.swift Sources/TestingMacros/TestDeclarationMacro.swift:53 — Sources/TestingMacros/TestDeclarationMacro.swift changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in TestDeclarationMacro._diagnoseIssues at line 53. 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 13:33:34 -05:00' --until='2026-11-14 13:33:34 -05:00' --full-history --no-merges -- Sources/TestingMacros/TestDeclarationMacro.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.
D4 · Code Duplication · Edited copy of a member (8 corresponding lines) · ×4
  • Edited copy of a member (8 corresponding lines) Sources/Testing/Support/Graph.swift:397 — Sources/Testing/Support/Graph.swift:397-404 | Sources/Testing/Support/Graph.swift:414-421 — 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) Sources/Testing/Parameterization/TypeInfo.swift:589 — Sources/Testing/Parameterization/TypeInfo.swift:589-596 | Sources/Testing/Parameterization/TypeInfo.swift:608-615 — 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) Sources/Testing/Support/Additions/MutexAdditions.swift:72 — Sources/Testing/Support/Additions/MutexAdditions.swift:72-79 | Sources/Testing/Support/Additions/MutexAdditions.swift:84-93 — 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) Sources/Testing/Events/Recorder/Event.ConsoleOutputRecorder.swift:278 — Sources/Testing/Events/Recorder/Event.ConsoleOutputRecorder.swift:278-285 | Sources/Testing/Events/Recorder/Event.ConsoleOutputRecorder.swift:301-308 — 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.
D10 · Test Quality · Skipped test · ×3
  • Skipped test: disabled Tests/TestingTests/MiscellaneousTests.swift:81 — Skipped — Some comment
  • Skipped test: repeatedlyExpect Tests/TestingTests/MiscellaneousTests.swift:654 — Skipped — time-sensitive
  • Skipped test: example3 Tests/TestingTests/Traits/CommentTests.swift:101 — Skipped — I
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×3
  • Duplicated block (12 lines × 2) Sources/Testing/Events/Recorder/Event.HumanReadableOutputRecorder.swift:425 — Sources/Testing/Events/Recorder/Event.HumanReadableOutputRecorder.swift:425-436 | Sources/Testing/Events/Recorder/Event.HumanReadableOutputRecorder.swift:578-589 — 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.
  • Duplicated block (12 lines × 2) Sources/Testing/Expectations/ExpectationChecking+Macro.swift:174 — Sources/Testing/Expectations/ExpectationChecking+Macro.swift:174-185 | Sources/Testing/Expectations/ExpectationChecking+Macro.swift:723-734 — 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 `Sources/Testing/Expectations/ExpectationChecking+Macro.swift:174` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 2) Sources/Testing/Support/Graph.swift:570 — Sources/Testing/Support/Graph.swift:570-581 | Sources/Testing/Support/Graph.swift:630-641 — 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 `Sources/Testing/Support/Graph.swift:570` 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 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.
D10 · Test Quality · Test project verifies nothing · ×2
  • Test project verifies nothing: NonisolatedNonsendingByDefaultTests Tests/NonisolatedNonsendingByDefaultTests/NonisolatedNonsendingByDefaultTests.swift:18 — No conventional assertion call was detected in 3 of 3 tests in `NonisolatedNonsendingByDefaultTests` — 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.
  • Test project verifies nothing: _MemorySafeTestingTests Tests/_MemorySafeTestingTests/MemorySafeTestDecls.swift:22 — No conventional assertion call was detected in 2 of 2 tests in `_MemorySafeTestingTests` — 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.
D35 · Change Coupling · Change-coupling hub · ×2
  • Change-coupling hub: TestDeclarationMacro.swift → SuiteDeclarationMacro.swift, FunctionDeclSyntaxAdditions.swift, TestContentGeneration.swift, TagMacro.swift Sources/TestingMacros/TestDeclarationMacro.swift — `Sources/TestingMacros/TestDeclarationMacro.swift` changes together with 4 other files — `Sources/TestingMacros/SuiteDeclarationMacro.swift`, `Sources/TestingMacros/Support/Additions/FunctionDeclSyntaxAdditions.swift`, `Sources/TestingMacros/Support/TestContentGeneration.swift`, `Sources/TestingMacros/TagMacro.swift` — none of which declares a dependency on it: one file is the hub of 4 separate couplings, not 4 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 4.
  • Change-coupling hub: EntryPoint.swift → ABI.Record+Streaming.swift, ABI.EncodedMessage.swift, Event.Symbol.swift, Color+Loading.swift Sources/Testing/ABI/EntryPoints/EntryPoint.swift — `Sources/Testing/ABI/EntryPoints/EntryPoint.swift` changes together with 4 other files — `Sources/Testing/ABI/ABI.Record+Streaming.swift`, `Sources/Testing/ABI/Encoded/ABI.EncodedMessage.swift`, `Sources/Testing/Events/Recorder/Event.Symbol.swift`, `Sources/Testing/Support/Color/Color+Loading.swift` — none of which declares a dependency on it: one file is the hub of 4 separate couplings, not 4 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 4.
D4 · Code Duplication · Edited copy of a member (18 corresponding lines) · ×2
  • Edited copy of a member (18 corresponding lines) Sources/Testing/ABI/Encoded/ABI.EncodedEvent.swift:291 — Sources/Testing/ABI/Encoded/ABI.EncodedEvent.swift:291-308 | Sources/Testing/ABI/Encoded/ABI.EncodedIssue.swift:213-240 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) Sources/Testing/Expectations/ExpectationChecking+Macro.swift:1118 — Sources/Testing/Expectations/ExpectationChecking+Macro.swift:1118-1135 | Sources/Testing/Expectations/ExpectationChecking+Macro.swift:1144-1163 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (20 corresponding lines) · ×2
  • Edited copy of a member (20 corresponding lines) Sources/Testing/Support/Graph.swift:568 — Sources/Testing/Support/Graph.swift:568-587 | Sources/Testing/Support/Graph.swift:628-647 — 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.
  • Edited copy of a member (20 corresponding lines) Sources/Testing/Expectations/ExpectationChecking+Macro.swift:240 — Sources/Testing/Expectations/ExpectationChecking+Macro.swift:240-259 | Sources/Testing/Expectations/ExpectationChecking+Macro.swift:422-441 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (11 corresponding lines) · ×2
  • Edited copy of a member (11 corresponding lines) Sources/Overlays/_Testing_WinSDK/Attachments/HBITMAP+AttachableAsIWICBitmapSource.swift:15 — Sources/Overlays/_Testing_WinSDK/Attachments/HBITMAP+AttachableAsIWICBitmapSource.swift:15-25 | Sources/Overlays/_Testing_WinSDK/Attachments/HICON+AttachableAsIWICBitmapSource.swift:15-25 — 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) Sources/Testing/Support/Graph.swift:781 — Sources/Testing/Support/Graph.swift:781-791 | Sources/Testing/Support/Graph.swift:809-819 — 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 (13 corresponding lines) · ×2
  • Edited copy of a member (13 corresponding lines) Sources/TestingMacros/Support/DiagnosticMessage.swift:483 — Sources/TestingMacros/Support/DiagnosticMessage.swift:483-495 | Sources/TestingMacros/Support/DiagnosticMessage.swift:883-900 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) Sources/TestingMacros/ExitTestCapturedValueMacro.swift:42 — Sources/TestingMacros/ExitTestCapturedValueMacro.swift:42-54 | Sources/TestingMacros/ExitTestCapturedValueMacro.swift:63-77 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (9 corresponding lines) · ×2
  • Edited copy of a member (9 corresponding lines) Sources/Testing/Issues/Issue+Recording.swift:91 — Sources/Testing/Issues/Issue+Recording.swift:91-99 | Sources/Testing/Issues/Issue+Recording.swift:142-153 — 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) Sources/Testing/Attachments/Images/Attachment+AttachableAsImage.swift:44 — Sources/Testing/Attachments/Images/Attachment+AttachableAsImage.swift:44-52 | Sources/Testing/Attachments/Images/Attachment+AttachableAsImage.swift:78-88 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (3 corresponding lines) · ×2
  • Edited copy of a member (3 corresponding lines) Sources/Overlays/_Testing_Foundation/Attachments/Data+Attachable.swift:24 — Sources/Overlays/_Testing_Foundation/Attachments/Data+Attachable.swift:24-26 | Sources/Testing/Attachments/Attachable.swift:213-215 — 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) Sources/Testing/Traits/IssueHandlingTrait.swift:83 — Sources/Testing/Traits/IssueHandlingTrait.swift:83-85 | Sources/Testing/Traits/TaskLocalTrait.swift:73-81 — 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 · Duplicated block (10 lines × 2) · ×2
  • Duplicated block (10 lines × 2) Sources/Testing/Issues/Issue.swift:242 — Sources/Testing/Issues/Issue.swift:242-251 | Sources/Testing/Issues/Issue.swift:591-600 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (10 lines × 2) Sources/Testing/Issues/Issue.swift:253 — Sources/Testing/Issues/Issue.swift:253-262 | Sources/Testing/Issues/Issue.swift:602-611 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×2
  • Duplicated block (8 lines × 2) Sources/Testing/Expectations/ExpectationChecking+Macro.swift:1189 — Sources/Testing/Expectations/ExpectationChecking+Macro.swift:1189-1196 | Sources/Testing/Expectations/ExpectationChecking+Macro.swift:1240-1247 — 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 `Sources/Testing/Expectations/ExpectationChecking+Macro.swift:1189` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 2) Sources/Testing/Expectations/ExpectationChecking+Macro.swift:1281 — Sources/Testing/Expectations/ExpectationChecking+Macro.swift:1281-1288 | Sources/Testing/Expectations/ExpectationChecking+Macro.swift:1313-1320 — 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 (6 lines × 2) · ×2
  • Duplicated block (6 lines × 2) Sources/Testing/Attachments/Attachable.swift:255 — Sources/Testing/Attachments/Attachable.swift:255-260 | Sources/Testing/Attachments/Attachable.swift:272-277 — 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.
  • Duplicated block (6 lines × 2) Sources/Testing/Expectations/ExpectationChecking+Macro.swift:1000 — Sources/Testing/Expectations/ExpectationChecking+Macro.swift:1000-1005 | Sources/Testing/Expectations/ExpectationChecking+Macro.swift:1146-1151 — 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.
D6 · Cohesion (LCOM4) · Low cohesion · ×2
  • Low cohesion: EncodedAttachment (LCOM4 5) Sources/Testing/ABI/Encoded/ABI.EncodedAttachment.swift:57 — EncodedAttachment'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: Array (LCOM4 4) Sources/Testing/Attachments/Attachable.swift:208 — Array'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.
PF3 · Async & latency hygiene · Sync-over-async blocking · ×2
  • Sync-over-async blocking Sources/Testing/Events/Clock.swift:182 — `sleep` is async and calls sleep — a blocking call inside async code stalls the cooperative pool's thread — one per core — and every task scheduled on it for as long as it runs.
  • Sync-over-async blocking Sources/Testing/Events/Clock.swift:202 — `sleep` is async and calls sleep — a blocking call inside async code stalls the cooperative pool's thread — one per core — and every task scheduled on it for as long as it runs.
D1 · Cyclomatic Complexity · HumanReadableOutputRecorder.record (cyclomatic 66) · ×1
  • HumanReadableOutputRecorder.record (cyclomatic 66) Sources/Testing/Events/Recorder/Event.HumanReadableOutputRecorder.swift:285 — HumanReadableOutputRecorder.record has cyclomatic complexity 66 (threshold 15). Of this number, 64 points are the body's own statements and 2 belong 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.
D1 · Cyclomatic Complexity · EntryPoint.swift.configurationForEntryPoint (cyclomatic 35) · ×1
  • EntryPoint.swift.configurationForEntryPoint (cyclomatic 35) Sources/Testing/ABI/EntryPoints/EntryPoint.swift:553 — EntryPoint.swift.configurationForEntryPoint has cyclomatic complexity 35 (threshold 15). Of this number, 22 points are the body's own statements and 13 belong to 2 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · EntryPoint.swift.parseCommandLineArguments (cyclomatic 29) · ×1
  • EntryPoint.swift.parseCommandLineArguments (cyclomatic 29) Sources/Testing/ABI/EntryPoints/EntryPoint.swift:387 — EntryPoint.swift.parseCommandLineArguments has cyclomatic complexity 29 (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 · Symbol.unicodeCharacter (cyclomatic 27) · ×1
  • Symbol.unicodeCharacter (cyclomatic 27) Sources/Testing/Events/Recorder/Event.Symbol.swift:136 — Symbol.unicodeCharacter has cyclomatic complexity 27 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · AdvancedConsoleOutputRecorder._generateHierarchicalSummary (cyclomatic 22) · ×1
  • AdvancedConsoleOutputRecorder._generateHierarchicalSummary (cyclomatic 22) Sources/Testing/Events/Recorder/Event.AdvancedConsoleOutputRecorder.swift:518 — AdvancedConsoleOutputRecorder._generateHierarchicalSummary has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · AdvancedConsoleOutputRecorder._renderHierarchyNode (cyclomatic 22) · ×1
  • AdvancedConsoleOutputRecorder._renderHierarchyNode (cyclomatic 22) Sources/Testing/Events/Recorder/Event.AdvancedConsoleOutputRecorder.swift:650 — AdvancedConsoleOutputRecorder._renderHierarchyNode has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · EntryPoint.swift.entryPoint (cyclomatic 20) · ×1
  • EntryPoint.swift.entryPoint (cyclomatic 20) Sources/Testing/ABI/EntryPoints/EntryPoint.swift:37 — EntryPoint.swift.entryPoint has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · AttributeInfo.init (cyclomatic 19) · ×1
  • AttributeInfo.init (cyclomatic 19) Sources/TestingMacros/Support/AttributeDiscovery.swift:74 — AttributeInfo.init 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 · _ExprTypeFinder.visitAny (cyclomatic 19) · ×1
  • _ExprTypeFinder.visitAny (cyclomatic 19) Sources/TestingMacros/Support/ClosureCaptureListParsing.swift:120 — _ExprTypeFinder.visitAny 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 · Event.init (cyclomatic 18) · ×1
  • Event.init (cyclomatic 18) Sources/Testing/ABI/Encoded/ABI.EncodedEvent.swift:324 — Event.init has cyclomatic complexity 18 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · WithAttributesSyntax.availability (cyclomatic 18) · ×1
  • WithAttributesSyntax.availability (cyclomatic 18) Sources/TestingMacros/Support/Additions/WithAttributesSyntaxAdditions.swift:44 — WithAttributesSyntax.availability has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · AdvancedConsoleOutputRecorder._processABIEvent (cyclomatic 17) · ×1
  • AdvancedConsoleOutputRecorder._processABIEvent (cyclomatic 17) Sources/Testing/Events/Recorder/Event.AdvancedConsoleOutputRecorder.swift:446 — AdvancedConsoleOutputRecorder._processABIEvent 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.
D17 · Explicit Debt · HackComment · ×1
  • HackComment Sources/Testing/ExitTests/ExitTest.swift:867 — // HACK: specify a blank test identifier ("/") to force the xctest — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
D2 · Cognitive Complexity · HumanReadableOutputRecorder.record (cognitive 90) · ×1
  • HumanReadableOutputRecorder.record (cognitive 90) Sources/Testing/Events/Recorder/Event.HumanReadableOutputRecorder.swift:285 — HumanReadableOutputRecorder.record has cognitive complexity 90 (threshold 15). Drivers by points: if/else 44 (71 pts), boolean chains 9, match/switch 4 (7 pts), loops 1 (3 pts) (nesting depth added 32). Of this number, 84 points are the body's own statements and 6 belong 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 · AdvancedConsoleOutputRecorder._renderHierarchyNode (cognitive 63) · ×1
  • AdvancedConsoleOutputRecorder._renderHierarchyNode (cognitive 63) Sources/Testing/Events/Recorder/Event.AdvancedConsoleOutputRecorder.swift:650 — AdvancedConsoleOutputRecorder._renderHierarchyNode has cognitive complexity 63 (threshold 15). Drivers by points: if/else 14 (35 pts), ternaries 6 (20 pts), loops 2 (5 pts), boolean chains 3 (nesting depth added 38). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · AdvancedConsoleOutputRecorder._generateHierarchicalSummary (cognitive 54) · ×1
  • AdvancedConsoleOutputRecorder._generateHierarchicalSummary (cognitive 54) Sources/Testing/Events/Recorder/Event.AdvancedConsoleOutputRecorder.swift:518 — AdvancedConsoleOutputRecorder._generateHierarchicalSummary has cognitive complexity 54 (threshold 15). Drivers by points: if/else 14 (35 pts), loops 5 (16 pts), ternaries 2, boolean chains 1 (nesting depth added 32). 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 · EntryPoint.swift.configurationForEntryPoint (cognitive 46) · ×1
  • EntryPoint.swift.configurationForEntryPoint (cognitive 46) Sources/Testing/ABI/EntryPoints/EntryPoint.swift:553 — EntryPoint.swift.configurationForEntryPoint has cognitive complexity 46 (threshold 15). Drivers by points: if/else 25 (31 pts), match/switch 6 (11 pts), boolean chains 3, loops 1 (nesting depth added 11). Of this number, 28 points are the body's own statements and 18 belong to 2 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · EntryPoint.swift.entryPoint (cognitive 45) · ×1
  • EntryPoint.swift.entryPoint (cognitive 45) Sources/Testing/ABI/EntryPoints/EntryPoint.swift:37 — EntryPoint.swift.entryPoint has cognitive complexity 45 (threshold 15). Drivers by points: if/else 13 (33 pts), loops 2 (7 pts), boolean chains 4, error handling 1 (nesting depth added 25). 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 · EntryPoint.swift.parseCommandLineArguments (cognitive 39) · ×1
  • EntryPoint.swift.parseCommandLineArguments (cognitive 39) Sources/Testing/ABI/EntryPoints/EntryPoint.swift:387 — EntryPoint.swift.parseCommandLineArguments has cognitive complexity 39 (threshold 15). Drivers by points: if/else 23 (31 pts), boolean chains 4, ternaries 1 (4 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ConditionMacro.expansion (cognitive 31) · ×1
  • ConditionMacro.expansion (cognitive 31) Sources/TestingMacros/ConditionMacro.swift:83 — ConditionMacro.expansion has cognitive complexity 31 (threshold 15). Drivers by points: if/else 14 (23 pts), loops 3 (7 pts), boolean chains 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AttributeInfo.functionArgumentList (cognitive 28) · ×1
  • AttributeInfo.functionArgumentList (cognitive 28) Sources/TestingMacros/Support/AttributeDiscovery.swift:157 — AttributeInfo.functionArgumentList has cognitive complexity 28 (threshold 15). Drivers by points: if/else 9 (18 pts), boolean chains 5, loops 2 (5 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 · DiagnosticMessage+Diagnosing.swift._diagnoseIssuesWithTagsTrait (cognitive 28) · ×1
  • DiagnosticMessage+Diagnosing.swift._diagnoseIssuesWithTagsTrait (cognitive 28) Sources/TestingMacros/Support/DiagnosticMessage+Diagnosing.swift:56 — DiagnosticMessage+Diagnosing.swift._diagnoseIssuesWithTagsTrait has cognitive complexity 28 (threshold 15). Drivers by points: if/else 11 (23 pts), boolean chains 4, loops 1 (nesting depth added 12). Of this number, 16 points are the body's own statements and 12 belong to 2 function items inside it that branch. 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 · AttributeInfo.init (cognitive 26) · ×1
  • AttributeInfo.init (cognitive 26) Sources/TestingMacros/Support/AttributeDiscovery.swift:74 — AttributeInfo.init has cognitive complexity 26 (threshold 15). Drivers by points: if/else 13 (18 pts), boolean chains 8 (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 · ExitTestConditionMacro._diagnoseIssues (cognitive 24) · ×1
  • ExitTestConditionMacro._diagnoseIssues (cognitive 24) Sources/TestingMacros/ConditionMacro.swift:645 — ExitTestConditionMacro._diagnoseIssues has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (18 pts), loops 3 (6 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 · AvailabilityGuards.swift.createSyntaxNode (cognitive 23) · ×1
  • AvailabilityGuards.swift.createSyntaxNode (cognitive 23) Sources/TestingMacros/Support/AvailabilityGuards.swift:201 — AvailabilityGuards.swift.createSyntaxNode has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (10 pts), loops 3 (9 pts), match/switch 1 (2 pts), ternaries 1 (2 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 · Value._encode (cognitive 22) · ×1
  • Value._encode (cognitive 22) Sources/Testing/Support/JSON.Encodable.swift:263 — Value._encode has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (15 pts), loops 1 (3 pts), ternaries 1 (3 pts), match/switch 1 (nesting depth added 11). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · Plan._determineAction (cognitive 22) · ×1
  • Plan._determineAction (cognitive 22) Sources/Testing/Running/Runner.Plan.swift:269 — Plan._determineAction has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (14 pts), error handling 2 (5 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · WithAttributesSyntax.availability (cognitive 22) · ×1
  • WithAttributesSyntax.availability (cognitive 22) Sources/TestingMacros/Support/Additions/WithAttributesSyntaxAdditions.swift:44 — WithAttributesSyntax.availability has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 5, match/switch 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Value._encode (cognitive 21) · ×1
  • Value._encode (cognitive 21) Sources/Testing/Support/JSON.Encodable.swift:197 — Value._encode has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 3, match/switch 1 (3 pts), loops 1 (nesting depth added 8). Of this number, 13 points are the body's own statements and 8 belong to 2 function items inside it that branch. 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 · CommentParsing.swift._trimTriviaToLastDoubleNewline (cognitive 21) · ×1
  • CommentParsing.swift._trimTriviaToLastDoubleNewline (cognitive 21) Sources/TestingMacros/Support/CommentParsing.swift:60 — CommentParsing.swift._trimTriviaToLastDoubleNewline has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (14 pts), match/switch 2 (4 pts), boolean chains 2, 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 · CommandLineArgumentList._parseArgument (cognitive 20) · ×1
  • CommandLineArgumentList._parseArgument (cognitive 20) Sources/Testing/ABI/EntryPoints/CommandLineArgumentList.swift:93 — CommandLineArgumentList._parseArgument has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 3, match/switch 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DiagnosticMessage.containingNodeUnsupported (cognitive 20) · ×1
  • DiagnosticMessage.containingNodeUnsupported (cognitive 20) Sources/TestingMacros/Support/DiagnosticMessage.swift:407 — DiagnosticMessage.containingNodeUnsupported has cognitive complexity 20 (threshold 15). Drivers by points: if/else 16 (18 pts), boolean chains 2 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · DiagnosticMessage+Diagnosing.swift.diagnoseIssuesWithLexicalContext (cognitive 20) · ×1
  • DiagnosticMessage+Diagnosing.swift.diagnoseIssuesWithLexicalContext (cognitive 20) Sources/TestingMacros/Support/DiagnosticMessage+Diagnosing.swift:172 — DiagnosticMessage+Diagnosing.swift.diagnoseIssuesWithLexicalContext has cognitive complexity 20 (threshold 15). Drivers by points: if/else 13 (16 pts), loops 1 (3 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · Attachment._encodingFormat (cognitive 18) · ×1
  • Attachment._encodingFormat (cognitive 18) Sources/Overlays/_Testing_Foundation/Attachments/Attachment+Encodable+NSSecureCoding.swift:42 — Attachment._encodingFormat has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 3 (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 · AdvancedConsoleOutputRecorder._processABIEvent (cognitive 18) · ×1
  • AdvancedConsoleOutputRecorder._processABIEvent (cognitive 18) Sources/Testing/Events/Recorder/Event.AdvancedConsoleOutputRecorder.swift:446 — AdvancedConsoleOutputRecorder._processABIEvent has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (9 pts), match/switch 2 (4 pts), ternaries 1 (3 pts), boolean chains 2 (nesting depth added 8). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · JUnitXMLRecorder._xml (cognitive 17) · ×1
  • JUnitXMLRecorder._xml (cognitive 17) Sources/Testing/Events/Recorder/Event.JUnitXMLRecorder.swift:176 — JUnitXMLRecorder._xml has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (13 pts), loops 2 (4 pts) (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 · TagMacro.expansion (cognitive 17) · ×1
  • TagMacro.expansion (cognitive 17) Sources/TestingMacros/TagMacro.swift:29 — TagMacro.expansion has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 2 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · _ExprTypeFinder.visitAny (cognitive 17) · ×1
  • _ExprTypeFinder.visitAny (cognitive 17) Sources/TestingMacros/Support/ClosureCaptureListParsing.swift:120 — _ExprTypeFinder.visitAny has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 2, match/switch 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 · DiagnosticMessage._addArgumentsFixIts (cognitive 17) · ×1
  • DiagnosticMessage._addArgumentsFixIts (cognitive 17) Sources/TestingMacros/Support/DiagnosticMessage.swift:532 — DiagnosticMessage._addArgumentsFixIts has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (10 pts), ternaries 3 (6 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.
D2 · Cognitive Complexity · __Expression.expandedDescription (cognitive 16) · ×1
  • __Expression.expandedDescription (cognitive 16) Sources/Testing/SourceAttribution/Expression.swift:423 — __Expression.expandedDescription has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 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 · Value.init (cognitive 16) · ×1
  • Value.init (cognitive 16) Sources/Testing/SourceAttribution/Expression.swift:208 — Value.init has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 4, loops 1 (2 pts) (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FileHandle.readToEnd (cognitive 16) · ×1
  • FileHandle.readToEnd (cognitive 16) Sources/Testing/Support/FileHandle.swift:464 — FileHandle.readToEnd has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 8, if/else 5 (7 pts), loops 1 (nesting depth added 2). 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 · AdvancedConsoleOutputRecorder._formatDetailedIssueDescription (cognitive 16) · ×1
  • AdvancedConsoleOutputRecorder._formatDetailedIssueDescription (cognitive 16) Sources/Testing/Events/Recorder/Event.AdvancedConsoleOutputRecorder.swift:753 — AdvancedConsoleOutputRecorder._formatDetailedIssueDescription has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (13 pts), match/switch 1 (2 pts), loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D3 · God Classes · MethodTooLong · ×1
  • MethodTooLong: HumanReadableOutputRecorder.record Sources/Testing/Events/Recorder/Event.HumanReadableOutputRecorder.swift:285 — MethodTooLong — record runs 228 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 128 over it, 2.28× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D3 · God Classes · FileTooLong · ×1
  • FileTooLong: Expectations/ExpectationChecking+Macro.swift Sources/Testing/Expectations/ExpectationChecking+Macro.swift — FileTooLong — 770 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 270 over it, 1.54× 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 · FunctionTooLong · ×1
  • FunctionTooLong: EntryPoint.swift.configurationForEntryPoint Sources/Testing/ABI/EntryPoints/EntryPoint.swift:553 — FunctionTooLong — configurationForEntryPoint runs 131 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 31 over it, 1.31× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D3 · God Classes · TooManyMethods · ×1
  • TooManyMethods: DiagnosticMessage Sources/TestingMacros/Support/DiagnosticMessage.swift:21 — TooManyMethods — 34 methods. The bar is 30 methods; this is 4 over it, 1.13× the bar. Most of these members implement TestingMacros.DiagnosticMessage (32 of 32 members), so moving them onto a smaller type would remove them from that contract rather than reduce it. To reduce it, split the contract instead: give each cohesive group of operations its own smaller interface and its own implementing type. Where the contract has to stay whole, move the work behind these members into collaborator types, so what is left here is a forward per member rather than a responsibility per member.
D31 · IaC & Container Security · Medium IaC · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Edited copy of a member (43 corresponding lines) · ×1
  • Edited copy of a member (43 corresponding lines) Sources/Testing/Expectations/ExpectationChecking+Macro.swift:1173 — Sources/Testing/Expectations/ExpectationChecking+Macro.swift:1173-1215 | Sources/Testing/Expectations/ExpectationChecking+Macro.swift:1223-1266 — These two members are one piece of code written twice and then edited apart: 43 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 (29 corresponding lines) · ×1
  • Edited copy of a member (29 corresponding lines) Sources/Testing/Expectations/ExpectationChecking+Macro.swift:960 — Sources/Testing/Expectations/ExpectationChecking+Macro.swift:960-988 | Sources/Testing/Expectations/ExpectationChecking+Macro.swift:998-1029 — These two members are one piece of code written twice and then edited apart: 29 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 (28 corresponding lines) · ×1
  • Edited copy of a member (28 corresponding lines) Sources/Testing/Expectations/ExpectationChecking+Macro.swift:1041 — Sources/Testing/Expectations/ExpectationChecking+Macro.swift:1041-1068 | Sources/Testing/Expectations/ExpectationChecking+Macro.swift:1079-1107 — These two members are one piece of code written twice and then edited apart: 28 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) · ×1
  • Edited copy of a member (22 corresponding lines) Sources/Testing/Expectations/ExpectationChecking+Macro.swift:1279 — Sources/Testing/Expectations/ExpectationChecking+Macro.swift:1279-1300 | Sources/Testing/Expectations/ExpectationChecking+Macro.swift:1310-1332 — 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 copies of one member (6 members, 19+ corresponding lines) · ×1
  • Edited copies of one member (6 members, 19+ corresponding lines) Sources/Testing/Expectations/ExpectationChecking+Macro.swift:300 — Sources/Testing/Expectations/ExpectationChecking+Macro.swift:300-318 | Sources/Testing/Expectations/ExpectationChecking+Macro.swift:329-347 | Sources/Testing/Expectations/ExpectationChecking+Macro.swift:358-376 | Sources/Testing/Expectations/ExpectationChecking+Macro.swift:482-500 | Sources/Testing/Expectations/ExpectationChecking+Macro.swift:511-529 | Sources/Testing/Expectations/ExpectationChecking+Macro.swift:540-558 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 19 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 18+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 18+ corresponding lines) Sources/TestingMacros/Support/DiagnosticMessage.swift:375 — Sources/TestingMacros/Support/DiagnosticMessage.swift:375-392 | Sources/TestingMacros/Support/DiagnosticMessage.swift:733-754 | Sources/TestingMacros/Support/DiagnosticMessage.swift:768-795 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 18 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 (21 corresponding lines) · ×1
  • Edited copy of a member (21 corresponding lines) Sources/Testing/Expectations/ExpectationChecking+Macro.swift:779 — Sources/Testing/Expectations/ExpectationChecking+Macro.swift:779-799 | Sources/Testing/Expectations/ExpectationChecking+Macro.swift:923-947 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (19 corresponding lines) · ×1
  • Edited copy of a member (19 corresponding lines) Sources/Testing/Expectations/ExpectationChecking+Macro.swift:638 — Sources/Testing/Expectations/ExpectationChecking+Macro.swift:638-656 | Sources/Testing/Expectations/ExpectationChecking+Macro.swift:858-876 — 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 copies of one member (7 members, 19+ corresponding lines) · ×1
  • Edited copies of one member (7 members, 19+ corresponding lines) Sources/Testing/Expectations/ExpectationChecking+Macro.swift:172 — Sources/Testing/Expectations/ExpectationChecking+Macro.swift:172-190 | Sources/Testing/Expectations/ExpectationChecking+Macro.swift:271-289 | Sources/Testing/Expectations/ExpectationChecking+Macro.swift:390-408 | Sources/Testing/Expectations/ExpectationChecking+Macro.swift:453-471 | Sources/Testing/Expectations/ExpectationChecking+Macro.swift:573-591 | Sources/Testing/Expectations/ExpectationChecking+Macro.swift:606-624 | Sources/Testing/Expectations/ExpectationChecking+Macro.swift:721-740 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 19 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (17 corresponding lines) · ×1
  • Edited copy of a member (17 corresponding lines) Sources/Testing/Support/FileHandle.swift:309 — Sources/Testing/Support/FileHandle.swift:309-325 | Sources/Testing/Support/FileHandle.swift:406-425 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (14 corresponding lines) · ×1
  • Edited copy of a member (14 corresponding lines) Sources/TestingMacros/ConditionMacro.swift:371 — Sources/TestingMacros/ConditionMacro.swift:371-384 | Sources/TestingMacros/ConditionMacro.swift:428-444 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 3+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 3+ corresponding lines) Sources/Overlays/_Testing_AppKit/Attachments/NSImage+AttachableAsImage.swift:64 — Sources/Overlays/_Testing_AppKit/Attachments/NSImage+AttachableAsImage.swift:64-66 | Sources/Overlays/_Testing_CoreGraphics/Attachments/CGImage+AttachableAsImage.swift:28-30 | Sources/Overlays/_Testing_CoreImage/Attachments/CIImage+AttachableAsImage.swift:34-36 | Sources/Overlays/_Testing_UIKit/Attachments/UIImage+AttachableAsImage.swift:73-75 | Sources/Overlays/_Testing_WinSDK/Attachments/UnsafeMutablePointer+AttachableAsIWICBitmapSource.swift:23-25 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 3 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 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (4 corresponding lines) · ×1
  • Edited copy of a member (4 corresponding lines) Sources/EmbeddedPlatform/POSIX/EmbeddedPlatformPOSIX.swift:57 — Sources/EmbeddedPlatform/POSIX/EmbeddedPlatformPOSIX.swift:57-60 | Sources/EmbeddedPlatform/WASI/EmbeddedPlatformWASI.swift:46-49 — 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.
D4 · Code Duplication · Edited copies of one member (3 members, 3+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 3+ corresponding lines) Sources/EmbeddedPlatform/EmbeddedPlatformPOSIX+WASI.swift:14 — Sources/EmbeddedPlatform/EmbeddedPlatformPOSIX+WASI.swift:14-16 | Sources/EmbeddedPlatform/POSIX/EmbeddedPlatformPOSIX+WASI.swift:14-16 | Sources/EmbeddedPlatform/WASI/EmbeddedPlatformPOSIX+WASI.swift:14-16 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 3 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 (34 lines × 3) · ×1
  • Duplicated block (34 lines × 3) Sources/EmbeddedPlatform/EmbeddedPlatformPOSIX+WASI.swift:19 — Sources/EmbeddedPlatform/EmbeddedPlatformPOSIX+WASI.swift:19-52 | Sources/EmbeddedPlatform/POSIX/EmbeddedPlatformPOSIX+WASI.swift:19-52 | Sources/EmbeddedPlatform/WASI/EmbeddedPlatformPOSIX+WASI.swift:19-52 — before extracting anything, compare `Sources/EmbeddedPlatform/EmbeddedPlatformPOSIX+WASI.swift` and `Sources/EmbeddedPlatform/POSIX/EmbeddedPlatformPOSIX+WASI.swift` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. 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 (59 lines × 2) · ×1
  • Duplicated block (59 lines × 2) Sources/Testing/Support/SHA256.swift:71 — Sources/Testing/Support/SHA256.swift:71-129 | Sources/TestingMacros/Support/SHA256.swift:71-129 — before extracting anything, compare `Sources/Testing/Support/SHA256.swift` and `Sources/TestingMacros/Support/SHA256.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 110 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 (22 lines × 2) · ×1
  • Duplicated block (22 lines × 2) Sources/Testing/Support/SHA256.swift:132 — Sources/Testing/Support/SHA256.swift:132-153 | Sources/TestingMacros/Support/SHA256.swift:132-153 — before extracting anything, compare `Sources/Testing/Support/SHA256.swift` and `Sources/TestingMacros/Support/SHA256.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 110 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 lines × 2) · ×1
  • Duplicated block (29 lines × 2) Sources/Testing/Support/SHA256.swift:40 — Sources/Testing/Support/SHA256.swift:40-68 | Sources/TestingMacros/Support/SHA256.swift:40-68 — before extracting anything, compare `Sources/Testing/Support/SHA256.swift` and `Sources/TestingMacros/Support/SHA256.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 110 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 (19 lines × 2) · ×1
  • Duplicated block (19 lines × 2) Sources/Testing/ABI/EntryPoints/EntryPoint.swift:930 — Sources/Testing/ABI/EntryPoints/EntryPoint.swift:930-948 | Sources/Testing/ABI/EntryPoints/EntryPoint.swift:952-970 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (16 lines × 2) · ×1
  • Duplicated block (16 lines × 2) Sources/Testing/Expectations/ExpectationChecking+Macro.swift:1200 — Sources/Testing/Expectations/ExpectationChecking+Macro.swift:1200-1215 | Sources/Testing/Expectations/ExpectationChecking+Macro.swift:1251-1266 — 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 `Sources/Testing/Expectations/ExpectationChecking+Macro.swift:1200` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (15 lines × 2) · ×1
  • Duplicated block (15 lines × 2) Sources/Testing/Expectations/ExpectationChecking+Macro.swift:1054 — Sources/Testing/Expectations/ExpectationChecking+Macro.swift:1054-1068 | Sources/Testing/Expectations/ExpectationChecking+Macro.swift:1093-1107 — 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 `Sources/Testing/Expectations/ExpectationChecking+Macro.swift:1054` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (11 lines × 3) · ×1
  • Duplicated block (11 lines × 3) Sources/EmbeddedPlatform/EmbeddedPlatformPOSIX+WASI.swift:55 — Sources/EmbeddedPlatform/EmbeddedPlatformPOSIX+WASI.swift:55-65 | Sources/EmbeddedPlatform/POSIX/EmbeddedPlatformPOSIX+WASI.swift:55-65 | Sources/EmbeddedPlatform/WASI/EmbeddedPlatformPOSIX+WASI.swift:55-65 — before extracting anything, compare `Sources/EmbeddedPlatform/EmbeddedPlatformPOSIX+WASI.swift` and `Sources/EmbeddedPlatform/POSIX/EmbeddedPlatformPOSIX+WASI.swift` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. 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 (9 lines × 2) · ×1
  • Duplicated block (9 lines × 2) Sources/Testing/Support/Environment.swift:165 — Sources/Testing/Support/Environment.swift:165-173 | Sources/Testing/Support/Environment.swift:215-228 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
D5 · Coupling · Off the main sequence · ×1
  • Off the main sequence: _Testing_WinSDK (SwiftPM) — _Testing_WinSDK (SwiftPM): abstractness 1.00, instability 1.00, distance 1.00 — zone of uselessness — abstract and unstable, so it's likely unused.
P2 · Observability · No structured logging · ×1
  • No structured logging — No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
X3 · Exception handling · Swallowed exception (empty catch) · ×1
  • Swallowed exception (empty catch) Sources/Testing/Traits/TimeLimitTrait.swift:291 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Minor — 12 finding(s)
X10 · Duplicated predicate · Duplicated predicate · ×6
  • Duplicated predicate Sources/Testing/SourceAttribution/Backtrace.swift:334 — `os(anyAppleOS) && !SWT_NO_DYNAMIC_LINKING` appears character-identically in 2 files — Sources/Testing/SourceAttribution/Backtrace.swift, Sources/Testing/Support/Environment.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 Sources/Overlays/_Testing_CoreGraphics/Attachments/AttachableAsCGImage.swift:11 — `os(anyAppleOS) && canImport(CoreGraphics)` appears character-identically in 4 files — Sources/Overlays/_Testing_CoreGraphics/Attachments/AttachableAsCGImage.swift, Sources/Overlays/_Testing_CoreGraphics/Attachments/AttachableImageFormat+UTType.swift, Sources/Overlays/_Testing_CoreGraphics/Attachments/CGImage+AttachableAsImage.swift, Sources/Overlays/_Testing_CoreGraphics/Attachments/_AttachableImageWrapper+AttachableWrapper.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 Sources/Overlays/_Testing_Foundation/Attachments/AttachableEncodingFormat+Foundation.swift:15 — `os(anyAppleOS) && canImport(UniformTypeIdentifiers)` appears character-identically in 2 files — Sources/Overlays/_Testing_Foundation/Attachments/AttachableEncodingFormat+Foundation.swift, Sources/Overlays/_Testing_Foundation/Attachments/Attachment+Encodable+NSSecureCoding.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 Sources/Testing/ABI/EntryPoints/EntryPoint.swift:909 — `os(anyAppleOS) || os(Linux) || os(FreeBSD) || os(OpenBSD) || os(Android)` appears character-identically in 4 files — Sources/Testing/ABI/EntryPoints/EntryPoint.swift, Sources/Testing/Support/Environment.swift, Sources/Testing/Support/FileHandle.swift, Sources/Testing/Support/GetSymbol.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 Sources/Testing/ABI/EntryPoints/SwiftPMEntryPoint.swift:27 — `os(anyAppleOS) || os(Linux) || os(FreeBSD) || os(OpenBSD) || os(Android) || os(WASI)` appears character-identically in 3 files — Sources/Testing/ABI/EntryPoints/SwiftPMEntryPoint.swift, Sources/Testing/Support/Environment.swift, Sources/Testing/Support/FileHandle.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 Sources/SymbolShowcase/SymbolShowcaseMain.swift:62 — `os(macOS) || (os(iOS) && targetEnvironment(macCatalyst))` appears character-identically in 4 files — Sources/SymbolShowcase/SymbolShowcaseMain.swift, Sources/Testing/ABI/EntryPoints/EntryPoint.swift, Sources/Testing/Events/Recorder/Event.ConsoleOutputRecorder.swift, Sources/Testing/Events/Recorder/Event.Symbol.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.
D16 · Bus Factor · Off-boarding risk · ×1
  • Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 83 significant file(s) lose their only recent owner: Sources/Testing/Expectations/Expectation+Macro.swift, Sources/TestingMacros/Support/DiagnosticMessage.swift, Sources/Testing/Support/FileHandle.swift, Sources/Testing/Test+Macro.swift, Sources/Testing/Parameterization/TypeInfo.swift, Sources/Testing/SourceAttribution/Expression.swift, Sources/Testing/Support/JSON.Encodable.swift, Sources/TestingMacros/Support/DiagnosticMessage+Diagnosing.swift (+75 more). Pair on, review, or document these before any departure.
D20 · ADR Quality · No ADRs found · ×1
  • No ADRs found Package.swift:93 — No ADRs found. The recognised ADR directories in this tree were read — `Documentation/Proposals` — and none of their files is a decision record (a README, index or template page does not count). 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 `Package.swift` makes this repository a deployable product (line 93).
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.
M2 · Architecture documentation · No architecture diagram/doc · ×1
  • No architecture diagram/doc — No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST REDACTED:7 — 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 5 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.
P6 · Release Hygiene · No changelog · ×1
  • No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
Minor — 23 finding(s)
D10 · Test Quality · Skipped (documented) · ×23
  • Skipped (documented): foundationGeneratedNSError Tests/TestingTests/BacktraceTests.swift:110 — Skipped with a documented reason — a deferral, not lazy debt: conditionally enabled — runs only when its .enabled(if:) condition holds
  • Skipped (documented): confirmationFailureCanBeDescribedAsSingleValue Tests/TestingTests/ConfirmationTests.swift:65 — Skipped with a documented reason — a deferral, not lazy debt: wrapped in withKnownIssue — the body is expected to fail, so its failure is not reported
  • Skipped (documented): dumpPlan Tests/TestingTests/DumpTests.swift:20 — Skipped with a documented reason — a deferral, not lazy debt: conditionally enabled — runs only when its .enabled(if:) condition holds
  • Skipped (documented): angeredKomodo Tests/TestingTests/EventRecorderTests.swift:688 — Skipped with a documented reason — a deferral, not lazy debt: disabled by a .disabled(…) trait
  • Skipped (documented): incensedQuail Tests/TestingTests/EventRecorderTests.swift:691 — Skipped with a documented reason — a deferral, not lazy debt: wrapped in withKnownIssue — the body is expected to fail, so its failure is not reported
  • Skipped (documented): f Tests/TestingTests/EventRecorderTests.swift:750 — Skipped with a documented reason — a deferral, not lazy debt: wrapped in withKnownIssue — the body is expected to fail, so its failure is not reported
  • Skipped (documented): g Tests/TestingTests/EventRecorderTests.swift:760 — Skipped with a documented reason — a deferral, not lazy debt: wrapped in withKnownIssue — the body is expected to fail, so its failure is not reported
  • Skipped (documented): j Tests/TestingTests/EventRecorderTests.swift:776 — Skipped with a documented reason — a deferral, not lazy debt: wrapped in withKnownIssue — the body is expected to fail, so its failure is not reported
  • Skipped (documented): k Tests/TestingTests/EventRecorderTests.swift:783 — Skipped with a documented reason — a deferral, not lazy debt: wrapped in withKnownIssue — the body is expected to fail, so its failure is not reported
  • Skipped (documented): recordWithoutKnownIssueComment Tests/TestingTests/EventRecorderTests.swift:808 — Skipped with a documented reason — a deferral, not lazy debt: wrapped in withKnownIssue — the body is expected to fail, so its failure is not reported
  • Skipped (documented): recordWithKnownIssueComment Tests/TestingTests/EventRecorderTests.swift:815 — Skipped with a documented reason — a deferral, not lazy debt: wrapped in withKnownIssue — the body is expected to fail, so its failure is not reported
  • Skipped (documented): throwWithoutKnownIssueComment Tests/TestingTests/EventRecorderTests.swift:822 — Skipped with a documented reason — a deferral, not lazy debt: wrapped in withKnownIssue — the body is expected to fail, so its failure is not reported
  • Skipped (documented): throwWithKnownIssueComment Tests/TestingTests/EventRecorderTests.swift:830 — Skipped with a documented reason — a deferral, not lazy debt: wrapped in withKnownIssue — the body is expected to fail, so its failure is not reported
  • Skipped (documented): knownIssues Tests/TestingTests/ExitTestTests.swift:535 — Skipped with a documented reason — a deferral, not lazy debt: wrapped in withKnownIssue — the body is expected to fail, so its failure is not reported
  • Skipped (documented): disabledTest Tests/TestingTests/Runner.Plan.SnapshotTests.swift:57 — Skipped with a documented reason — a deferral, not lazy debt: To validate skip action
  • Skipped (documented): erroneousTest Tests/TestingTests/Runner.Plan.SnapshotTests.swift:65 — Skipped with a documented reason — a deferral, not lazy debt: conditionally enabled — runs only when its .enabled(if:) condition holds
  • Skipped (documented): duelingConditions Tests/TestingTests/RunnerTests.swift:70 — Skipped with a documented reason — a deferral, not lazy debt: conditionally enabled — runs only when its .enabled(if:) condition holds
  • Skipped (documented): disabled Tests/TestingTests/Test.Case.ArgumentTests.swift:174 — Skipped with a documented reason — a deferral, not lazy debt: disabled by a .disabled(…) trait
  • Skipped (documented): Tests/TestingTests/Support/GraphTests.swift:553 — Skipped with a documented reason — a deferral, not lazy debt: conditionally enabled — runs only when its .enabled(if:) condition holds
  • Skipped (documented): enabledTraitIf Tests/TestingTests/Traits/ConditionTraitTests.swift:22 — Skipped with a documented reason — a deferral, not lazy debt: conditionally enabled — runs only when its .enabled(if:) condition holds
  • Skipped (documented): disabledTraitClosure Tests/TestingTests/Traits/ConditionTraitTests.swift:28 — Skipped with a documented reason — a deferral, not lazy debt: , .disabled { false }, .bug(
  • Skipped (documented): disabledTraitIf Tests/TestingTests/Traits/ConditionTraitTests.swift:35 — Skipped with a documented reason — a deferral, not lazy debt: disabled by a .disabled(…) trait
  • Skipped (documented): mainActorIsolatedKnownIssue Tests/TestingTests/KnownIssueTests.swift:630 — Skipped with a documented reason — a deferral, not lazy debt: wrapped in withKnownIssue — the body is expected to fail, so its failure is not reported

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-4fba7e54bd764d2baabf3d9af60e966b/history.json --exit-code 0 --source .0artifacts/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-4fba7e54bd764d2baabf3d9af60e966b/tree.json --exit-code 0 --source .0artifacts/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 .9artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesnone (dependency manifest found, not scanned for vulnerabilities here)—none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Swift Package.swift/Package.resolved — not scanned yet).0—
D31 · IaC & Container Securitytrivy—trivy config --format json --quiet .1artifacts/raw/trivy-config.json
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 1 file(s) — `Sources/EmbeddedPlatform/POSIX/EmbeddedPlatformPOSIX.swift` — 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 Dependenciesnone (dependency manifest found, not scanned for vulnerabilities here)—none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Swift Package.swift/Package.resolved — not scanned yet).0—

Run 01a1dcc6-3669-70b4-a09f-f7880a5a91ab · 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