Public report of swiftlang/swift-java, 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, 03:35 UTC · Survey ID cd_042ecbc00bc84e67a15d20c5b1487afe

swiftlang/swift-java

Measured 15 November 2026, 03:23 UTC, at code version 793e154

Dependency hygiene is not measured: Maven/Gradle declarations read, no dependency graph resolved.

CAI score 61out of 100 Adequate
CriticalWeakAdequateStrongExemplary
Up 1 since the last survey

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

A medium codebase: 42,331 lines of product code in 22 projects, tests not counted · Estimated rebuild effort: about 0.5 person-years · Weakest lens: Code Health, 54

Findings by how serious they are

25 critical 313 serious 611 minor

20 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, 03:23 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 ▸

40of 40 dimensions measured by tools.
933of 949 findings point to an exact file and line, so you can open each one in the code. The other 16 concern the repository as a whole, such as missing documentation.
40dimensions across 6 lenses, read from 42,331 lines of product code in 22 projects.
Chapters

Executive summary

swiftlang/swift-java falls short of our standard for a preview release, held back most by its Code Health lens, the quality of the code itself. It scores 61 out of 100 and is rated Adequate, and all 25 of its critical findings are security problems.

Code Health, at 54, is the weakest lens and counts most in the score. The best first step is declaring which values may be missing, worth about 5 points. Recording design decisions comes next, worth about 3 points. Raising Code Health to 67 would lift the score to about 64.

Twenty-one pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Three settings leave the servers or containers unsafe, and one automatic update takes new releases before a bad one can be spotted. Pinning each tool to an exact version, correcting the unsafe settings and setting a waiting period for automatic updates would close these risks.

The product code is 42,331 lines, about €78,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.
Code Health 54 · counts for 46%Production Readiness 58 · counts for 25%Maturity 61 · counts for 14%Security and Compliance 78 · counts for 8%Architecture 93 · counts for 4%Performance 100 · counts for 2%

If Code Health rose from 54 to 67, the lowest score rated Strong, the score would rise from 61 to about 64.

Code composition: what the lines of code are
Product code 59%Tests 41%
New since the last survey: 51 findings

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

  • Code Duplication · Edited copy of a member (77 corresponding lines) Sources/JExtractSwiftLib/FFM/FFMSwift2JavaGenerator+SwiftThunkPrinting.swift
  • Code Duplication · Edited copies of one member (8 members, 22+ corresponding lines) SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple17.java
  • Code Duplication · Edited copy of a member (54 corresponding lines) Sources/JExtractSwiftLib/FFM/FFMSwift2JavaGenerator.swift
  • Code Duplication · Edited copy of a member (31 corresponding lines) Sources/JExtractSwiftLib/FFM/FFMSwift2JavaGenerator+JavaTranslation.swift
  • Code Duplication · Edited copy of a member (27 corresponding lines) Sources/JExtractSwiftLib/JNI/JNIJavaTypeTranslator.swift
  • Code Duplication · Edited copy of a member (30 corresponding lines) Sources/SwiftJava/JavaObject+MethodCalls.swift
  • Code Duplication · Edited copy of a member (16 corresponding lines) Sources/SwiftJavaRuntimeSupport/JextractedTypeBridge.swift
  • Code Duplication · Edited copies of one member (5 members, 15+ corresponding lines) Sources/SwiftJava/SwiftObjects.swift
  • Code Duplication · Edited copy of a member (22 corresponding lines) Sources/SwiftJava/JavaObject+MethodCalls.swift
  • Code Duplication · Edited copy of a member (23 corresponding lines) Sources/JExtractSwiftLib/FFM/FFMSwift2JavaGenerator+SwiftThunkPrinting.swift
  • Code Duplication · Edited copies of one member (3 members, 10+ corresponding lines) Sources/SwiftJava/BridgedValues/JavaBoxing.swift
  • Code Duplication · Edited copy of a member (17 corresponding lines) Sources/JExtractSwiftLib/ExtractedDecls+JavaNaming.swift
  • Code Duplication · Edited copy of a member (14 corresponding lines) Sources/GenerateConfigDocs/ConfigParser.swift
  • Code Duplication · Edited copy of a member (11 corresponding lines) Sources/SwiftJavaToolLib/AndroidAPIVersionSupport/AndroidAPIVersionsParser.swift
  • Code Duplication · Edited copy of a member (12 corresponding lines) Sources/SwiftJavaRuntimeSupport/CollectionBridge.swift
  • Code Duplication · Edited copy of a member (19 corresponding lines) Sources/JExtractSwiftLib/TranslatedDocumentation.swift
  • Code Duplication · Edited copy of a member (17 corresponding lines) Sources/SwiftJavaToolLib/JavaClassTranslator.swift
  • Code Duplication · Edited copy of a member (7 corresponding lines) Sources/SwiftJava/BridgedValues/JavaBoxing.swift
  • Code Duplication · Edited copies of one member (4 members, 7+ corresponding lines) Sources/SwiftJava/BridgedValues/JavaBoxing.swift
  • Code Duplication · Edited copy of a member (7 corresponding lines) Sources/SwiftJava/BridgedValues/JavaBoxing.swift
  • Code Duplication · Edited copy of a member (7 corresponding lines) Sources/SwiftJava/BridgedValues/JavaBoxing.swift
  • Code Duplication · Edited copies of one member (8 members, 3+ corresponding lines) SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple17.java
  • Code Duplication · Edited copy of a member (12 corresponding lines) Sources/JExtractSwiftLib/FFM/CDeclLowering/FFMSwift2JavaGenerator+FunctionLowering.swift
  • Code Duplication · Edited copy of a member (7 corresponding lines) Sources/SwiftJava/BridgedValues/SwiftDictionaryMap+JNI.swift
  • Code Duplication · Edited copy of a member (52 corresponding lines) Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator+JavaBindingsPrinting.swift
  • Code Duplication · Edited copy of a member (12 corresponding lines) Sources/SwiftJavaRuntimeSupport/CollectionBridge.swift
  • Code Duplication · Edited copy of a member (10 corresponding lines) SwiftKitCore/src/main/java/org/swift/swiftkit/core/CallTraces.java
  • Code Duplication · Edited copies of one member (3 members, 9+ corresponding lines) Sources/CodePrinting/CodePrinter+Java.swift
  • Code Duplication · Edited copy of a member (16 corresponding lines) SwiftKitCore/src/main/java/org/swift/swiftkit/core/SwiftLibraries.java
  • Code Duplication · Edited copy of a member (8 corresponding lines) Sources/SwiftJava/Optional+JavaObject.swift
  • Code Duplication · Edited copies of one member (4 members, 4+ corresponding lines) Samples/SwiftAndJavaJarFFMSampleLib/Sources/MySwiftLibrary/MySwiftLibrary.swift
  • Code Duplication · Edited copy of a member (9 corresponding lines) Sources/SwiftJava/BridgedValues/JavaValue+Dictionary.swift
  • Code Duplication · Edited copy of a member (16 corresponding lines) Sources/SwiftJavaTool/SwiftJavaBaseAsyncParsableCommand.swift
  • Code Duplication · Edited copies of one member (4 members, 5+ corresponding lines) Sources/SwiftJava/BridgedValues/SwiftDictionaryMap+JNI.swift
  • Code Duplication · Edited copy of a member (5 corresponding lines) Sources/SwiftJava/BridgedValues/SwiftDictionaryMap+JNI.swift
  • Code Duplication · Edited copy of a member (12 corresponding lines) Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator+JavaBindingsPrinting.swift
  • Code Duplication · Edited copies of one member (8 members, 3+ corresponding lines) SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple17.java
  • Code Duplication · Edited copy of a member (6 corresponding lines) Sources/JExtractSwiftLib/FFM/FFMSwift2JavaGenerator.swift
  • Code Duplication · Edited copies of one member (3 members, 6+ corresponding lines) Sources/SwiftJava/BridgedValues/JobjectBridge.swift
  • Code Duplication · Duplicated block (14 lines × 2) Sources/SwiftJava/JavaObject+MethodCalls.swift
  • Code Duplication · Duplicated block (10 lines × 2) Sources/JExtractSwiftLib/FFM/FFMSwift2JavaGenerator+JavaBindingsPrinting.swift
  • Code Duplication · Duplicated block (10 lines × 2) Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator+SwiftThunkPrinting.swift
  • Code Duplication · Duplicated block (9 lines × 2) Sources/JExtractSwiftLib/FFM/FFMSwift2JavaGenerator.swift
  • Code Duplication · Duplicated block (4–8 lines × 3) Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator+SwiftThunkPrinting.swift
  • Code Duplication · Duplicated block (5 lines × 3) Sources/JExtractSwiftLib/FFM/CDeclLowering/FFMSwift2JavaGenerator+FunctionLowering.swift
  • Code Duplication · Duplicated block (5 lines × 2) Sources/JExtractSwiftLib/FFM/FFMSwift2JavaGenerator+JavaBindingsPrinting.swift
  • Code Duplication · Duplicated block (6 lines × 2) Samples/SwiftJavaExtractFFMSampleApp/Sources/MySwiftLibrary/MySwiftStruct.swift
  • Dependency Hygiene · Floating branch dependency: swift-binding-generator-core
  • Explicit Debt · FixmeComment Package.swift
  • Explicit Debt · TodoComment Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator+SwiftThunkPrinting.swift
  • Change Coupling · Change coupling: SwiftSyntax+Extensions.swift ↔ Configuration.swift Sources/JExtractSwiftLib/Convenience/SwiftSyntax+Extensions.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: 63 findings

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

  • Cyclomatic Complexity · SwiftKnownType.init (cyclomatic 48) Sources/SwiftExtract/SwiftTypes/SwiftKnownTypeDecls.swift
  • Cyclomatic Complexity · SwiftType.init (cyclomatic 32) Sources/SwiftExtract/SwiftTypes/SwiftType.swift
  • Cyclomatic Complexity · SwiftAnalyzer.isUsing (cyclomatic 19) Sources/SwiftExtract/SwiftAnalyzer.swift
  • Cognitive Complexity · SwiftType.init (cognitive 47) Sources/SwiftExtract/SwiftTypes/SwiftType.swift
  • Cognitive Complexity · SwiftTypeLookupContext.unqualifiedLookup (cognitive 28) Sources/SwiftExtract/SwiftTypes/SwiftTypeLookupContext.swift
  • Cognitive Complexity · SwiftFunctionSignature.translateGenericParameters (cognitive 23) Sources/SwiftExtract/SwiftTypes/SwiftFunctionSignature.swift
  • Cognitive Complexity · SwiftParsedModuleSymbolTableBuilder.handle (cognitive 23) Sources/SwiftExtract/SwiftTypes/SwiftParsedModuleSymbolTableBuilder.swift
  • Cognitive Complexity · SwiftType.init (cognitive 23) Sources/SwiftExtract/SwiftTypes/SwiftType.swift
  • Cognitive Complexity · SwiftFunctionSignature.init (cognitive 21) Sources/SwiftExtract/SwiftTypes/SwiftFunctionSignature.swift
  • Cognitive Complexity · SwiftSymbolTable.setup (cognitive 20) Sources/SwiftExtract/SwiftTypes/SwiftSymbolTable.swift
  • Cognitive Complexity · AnalysisResult.typesConforming (cognitive 19) Sources/SwiftExtract/AnalysisResult.swift
  • Cognitive Complexity · SwiftFunctionSignature.variableSelfParameter (cognitive 19) Sources/SwiftExtract/SwiftTypes/SwiftFunctionSignature.swift
  • Cognitive Complexity · SwiftAnalysisVisitor.constraintsMatchSpecialization (cognitive 18) Sources/SwiftExtract/SwiftAnalysisVisitor.swift
  • Cognitive Complexity · SwiftKnownType.init (cognitive 18) Sources/SwiftExtract/SwiftTypes/SwiftKnownTypeDecls.swift
  • Cognitive Complexity · SwiftType+GenericTypes.swift.representativeConcreteType (cognitive 18) Sources/SwiftExtract/SwiftTypes/SwiftType+GenericTypes.swift
  • Cognitive Complexity · JNISwift2JavaGenerator.printProtocolParameterSwiftFunctionHelperClasses (cognitive 17) Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator+SwiftThunkPrinting.swift
  • Cognitive Complexity · SwiftAnalysisVisitor.resolveExtensionRequirements (cognitive 17) Sources/SwiftExtract/SwiftAnalysisVisitor.swift
  • Cognitive Complexity · SwiftDependencyScanner.swift.modules (cognitive 17) Sources/SwiftExtract/SwiftTypes/SwiftDependencyScanner.swift
  • Cognitive Complexity · SwiftAnalysisVisitor.applyPendingSpecializations (cognitive 16) Sources/SwiftExtract/SwiftAnalysisVisitor.swift
  • Cognitive Complexity · SwiftFileFilter.swift.shouldExtractSwiftType (cognitive 16) Sources/SwiftExtract/SwiftFileFilter.swift
  • God Classes · ClassTooLong: SwiftAnalysisVisitor Sources/SwiftExtract/SwiftAnalysisVisitor.swift
  • God Classes · FileTooLong: SwiftExtract/SwiftAnalysisVisitor.swift Sources/SwiftExtract/SwiftAnalysisVisitor.swift
  • God Classes · MethodTooLong: SwiftType.init Sources/SwiftExtract/SwiftTypes/SwiftType.swift
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) Sources/SwiftExtract/Logger.swift
  • Code Duplication · Duplicated block (18 lines × 2) Sources/SwiftExtract/SwiftTypes/SwiftFunctionSignature.swift
  • Code Duplication · Duplicated block (13–14 lines × 2) Sources/SwiftExtract/SwiftTypes/SwiftType.swift
  • Code Duplication · Duplicated block (14 lines × 2) Sources/SwiftJava/JavaObject+MethodCalls.swift
  • Code Duplication · Duplicated block (11–12 lines × 2) Sources/JExtractSwiftLib/FFM/FFMSwift2JavaGenerator+JavaBindingsPrinting.swift
  • Code Duplication · Duplicated block (11–12 lines × 2) Sources/SwiftExtract/SwiftFileFilter.swift
  • Code Duplication · Duplicated block (12 lines × 2) Sources/SwiftExtract/SwiftTypes/SwiftFunctionSignature.swift
  • Code Duplication · Duplicated block (10 lines × 2) Sources/JExtractSwiftLib/FFM/FFMSwift2JavaGenerator+JavaBindingsPrinting.swift
  • Code Duplication · Duplicated block (9 lines × 2) Sources/JExtractSwiftLib/FFM/FFMSwift2JavaGenerator.swift
  • Code Duplication · Duplicated block (9 lines × 2) Sources/JExtractSwiftLib/JavaExtractDecider.swift
  • Code Duplication · Duplicated block (8 lines × 4) Sources/SwiftExtract/Logger.swift
  • Code Duplication · Duplicated block (4–8 lines × 3) Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator+SwiftThunkPrinting.swift
  • Code Duplication · Duplicated block (8 lines × 2) Sources/SwiftExtract/SwiftTypes/SwiftParsedModuleSymbolTableBuilder.swift
  • Code Duplication · Duplicated block (5 lines × 3) Sources/JExtractSwiftLib/FFM/CDeclLowering/FFMSwift2JavaGenerator+FunctionLowering.swift
  • Code Duplication · Duplicated block (5 lines × 2) Sources/SwiftExtract/SwiftTypes/SwiftNominalTypeDeclaration.swift
  • Code Duplication · Duplicated block (5 lines × 2) Sources/JExtractSwiftLib/FFM/FFMSwift2JavaGenerator+JavaBindingsPrinting.swift
  • Code Duplication · Duplicated block (6 lines × 2) Samples/SwiftJavaExtractFFMSampleApp/Sources/MySwiftLibrary/MySwiftStruct.swift
  • Cohesion (LCOM4) · Low cohesion: ExtractedNominalType (LCOM4 4) Sources/SwiftExtract/ExtractedDecls.swift
  • Churn × Complexity Hotspots · Hotspot: Sources/JExtractSwiftLib/FFM/CDeclLowering/FFMSwift2JavaGenerator+FunctionLowering.swift Sources/JExtractSwiftLib/FFM/CDeclLowering/FFMSwift2JavaGenerator+FunctionLowering.swift
  • Explicit Debt · TodoComment Sources/SwiftExtract/SwiftAnalysisVisitor.swift
  • Explicit Debt · FixmeComment Sources/SwiftExtract/SwiftAnalyzer.swift
  • Explicit Debt · FixmeComment Sources/SwiftExtract/SwiftTypes/SwiftKnownModules.swift
  • Explicit Debt · FixmeComment Sources/SwiftExtract/SwiftTypes/SwiftKnownModules.swift
  • Explicit Debt · FixmeComment Sources/SwiftExtract/SwiftTypes/SwiftParameter.swift
  • Explicit Debt · FixmeComment Sources/SwiftExtract/SwiftTypes/SwiftSymbolTable.swift
  • Explicit Debt · TodoComment Sources/SwiftExtract/SwiftTypes/SwiftSymbolTable.swift
  • Explicit Debt · FixmeComment Sources/SwiftExtract/SwiftTypes/SwiftSymbolTable.swift
  • Explicit Debt · TodoComment Sources/SwiftExtract/SwiftTypes/SwiftType+GenericTypes.swift
  • Explicit Debt · FixmeComment Sources/SwiftExtract/SwiftTypes/SwiftType.swift
  • Explicit Debt · FixmeComment Sources/SwiftExtract/SwiftTypes/SwiftTypeLookupContext.swift
  • Explicit Debt · FixmeComment Sources/SwiftExtract/SwiftTypes/SwiftTypeLookupContext.swift
  • Explicit Debt · FixmeComment Sources/SwiftExtract/SwiftTypes/SwiftTypeLookupContext.swift
  • Explicit Debt · TodoComment Sources/SwiftExtract/SwiftTypes/SwiftTypeLookupContext.swift
  • Explicit Debt · TodoComment Sources/SwiftExtract/SwiftTypes/SwiftTypeLookupContext.swift
  • Explicit Debt · FixmeComment Sources/SwiftExtract/SwiftTypes/SwiftTypeLookupContext.swift
  • Explicit Debt · FixmeComment Sources/SwiftExtract/Convenience/SwiftSyntax+Extensions.swift
  • Explicit Debt · FixmeComment Sources/SwiftExtract/Convenience/SwiftSyntax+Extensions.swift
  • Explicit Debt · TodoComment Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator+SwiftThunkPrinting.swift
  • Explicit Debt · TodoComment Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator+SwiftThunkPrinting.swift
  • Change Coupling · Change coupling: SwiftAnalysisVisitor.swift ↔ SwiftSymbolTable.swift Sources/SwiftExtract/SwiftAnalysisVisitor.swift
Rebuild cost: about €78,000 · Estimate
Cost to rebuild€26,000 to €130,000, for 434 to 1,376 hours of work, about 0.5 person-years for 1 to 2 engineers
Difficulty of the problemStandard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor×0.8 at a score of 61. 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: 42,331 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
Declare the default where Java declares it: `@NullMarked` (org.jspecify.annotations) in each package's `package-info.java`, or once in `module-info.java`, and run NullAway (Error Prone) or the Checker Framework so the declaration is enforced.
Then annotate the real exceptions `@Nullable` and resolve the suppressions rather than adding to them: a `@SuppressWarnings("NullAway")` or `castToNonNull(x)` on a value the checker could show to be null is a `NullPointerException` waiting for the path that makes it true — where the value genuinely cannot be null, say something the checker can see instead (a null check, `Objects.requireNonNull`, a non-null field initialised in the constructor).
Raises the score by about 5 points · Medium effort · Nullable reference types
2
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.
Raises the score by about 3 points · Medium effort · Architecture documentation
3
Bring the 41 bodies over 15 down to 15 or less in Cognitive Complexity — start with JavaImplementationMacro.expansion (cognitive 53), JavaTranslator.getSwiftTypeNameAsString (cognitive 51), JavaClassTranslator.init (cognitive 50).
Raises the score by about 3 points · High effort · Cognitive Complexity

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 €78,000 to build again, about 0.5 person-years of work. Its weakest lens is Code Health, at 54 (Adequate). Code Health is about how easy the code is to read and change safely, and code that is hard to read is slow and risky to change, so every future change costs more than it should. Because the weakest lens counts most in the score, work on Code Health also moves the score most.
Based on: the rebuild estimate · the Code Health grade · how much each lens counts
What to do: Start with the Code Health actions in Top priorities.
If you do one thing first · First action
Declare the default where Java declares it: `@NullMarked` (org.jspecify.annotations) in each package's `package-info.java`, or once in `module-info.java`, and run NullAway (Error Prone) or the Checker Framework so the declaration is enforced. Of all the actions in this report, it raises the score most for the work it takes: about 5 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 7.1 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 5,626 lines over the last 90 days, which is about 22,817 lines a year. At that pace, the extra work comes to an estimated 1.2 to 7.6 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.

Architecture — module dependency graph

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

arch CodePrinting CodePrinting SwiftJavaConfigurationShared SwiftJavaConfigurationShared CodePrinting->SwiftJavaConfigurationShared ExampleSwiftLibrary ExampleSwiftLibrary JExtractSwiftLib JExtractSwiftLib JExtractSwiftLib->CodePrinting JExtractSwiftLib->SwiftJavaConfigurationShared SwiftJavaShared SwiftJavaShared JExtractSwiftLib->SwiftJavaShared JavaIO JavaIO JavaUtil JavaUtil JavaIO->JavaUtil SwiftJava SwiftJava JavaIO->SwiftJava JavaLangReflect JavaLangReflect JavaLangReflect->JavaUtil JavaLangReflect->SwiftJava JavaNet JavaNet JavaNet->JavaUtil JavaNet->SwiftJava JavaUtil->SwiftJava JavaUtilFunction JavaUtilFunction JavaUtilFunction->JavaUtil JavaUtilFunction->SwiftJava JavaUtilJar JavaUtilJar JavaUtilJar->JavaUtil JavaUtilJar->SwiftJava SwiftJavaMacros SwiftJavaMacros SwiftJava->SwiftJavaMacros SwiftJavaDocumentation SwiftJavaDocumentation SwiftJavaDocumentation->SwiftJava SwiftJavaRuntimeSupport SwiftJavaRuntimeSupport SwiftJavaDocumentation->SwiftJavaRuntimeSupport SwiftRuntimeFunctions SwiftRuntimeFunctions SwiftJavaDocumentation->SwiftRuntimeFunctions SwiftJavaRuntimeSupport->SwiftJava SwiftJavaToolLib SwiftJavaToolLib SwiftJavaToolLib->CodePrinting SwiftJavaToolLib->JavaLangReflect SwiftJavaToolLib->JavaNet SwiftJavaToolLib->JavaUtilJar SwiftJavaToolLib->SwiftJava SwiftJavaToolLib->SwiftJavaConfigurationShared SwiftJavaToolLib->SwiftJavaShared generate-config-docs generate-config-docs simple-java-project simple-java-project swift-java swift-java swift-java->JExtractSwiftLib swift-java->JavaNet swift-java->JavaUtilJar swift-java->SwiftJava swift-java->SwiftJavaConfigurationShared swift-java->SwiftJavaShared swift-java->SwiftJavaToolLib __more__ +2 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.

25 modules, with 55 dependencies between them. One loop runs through 11 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 (global)2 JavaKitDependencyResolver3 org.swift.swiftkit.core.annotations4 org.swift.swiftkit.core.ref5 org.swift.swiftkit.core.tuple6 org.swift.swiftkit.core.util7 utilities8 SwiftJavaMacros9 SwiftJavaRuntimeSupport10 SwiftJavaShared11 org.swift.swiftkit.core12 JavaStdlib13 org.swift.swiftkit.core.collections14 org.swift.swiftkit.ffm15 SwiftJavaTool16 org.swift.swiftkit.ffm.generated17 SwiftJavaConfigurationShared18 SwiftJavaToolLib19 SwiftJava20 JExtractSwiftLib21 GenerateConfigDocs22 CodePrinting23 ExampleSwiftLibrary24 JavaKit25 SwiftRuntimeFunctions
1 (global)
2 JavaKitDependencyResolver
3 org.swift.swiftkit.core.annotations
4 org.swift.swiftkit.core.ref
5 org.swift.swiftkit.core.tuple
6 org.swift.swiftkit.core.util
7 utilities
8 SwiftJavaMacros334
9 SwiftJavaRuntimeSupport1263
10 SwiftJavaShared1
11 org.swift.swiftkit.core1
12 JavaStdlib2523228
13 org.swift.swiftkit.core.collections6
14 org.swift.swiftkit.ffm9
15 SwiftJavaTool211036715
16 org.swift.swiftkit.ffm.generated4
17 SwiftJavaConfigurationShared17315
18 SwiftJavaToolLib116519220
19 SwiftJava53461339
20 JExtractSwiftLib19627401
21 GenerateConfigDocs1253
22 CodePrinting413
23 ExampleSwiftLibrary82
24 JavaKit2
25 SwiftRuntimeFunctions22
Uses a module listed above itPart of a loopThe module itself
1 (global)2 JavaKitDependencyResolver3 org.swift.swiftkit.core.annotations4 org.swift.swiftkit.core.ref5 org.swift.swiftkit.core.tuple6 org.swift.swiftkit.core.util7 utilities8 SwiftJavaMacros9 SwiftJavaRuntimeSupport10 SwiftJavaShared11 org.swift.swiftkit.core12 JavaStdlib13 org.swift.swiftkit.core.collections14 org.swift.swiftkit.ffm15 SwiftJavaTool16 org.swift.swiftkit.ffm.generated17 SwiftJavaConfigurationShared18 SwiftJavaToolLib19 SwiftJava20 JExtractSwiftLib21 GenerateConfigDocs22 CodePrinting23 ExampleSwiftLibrary24 JavaKit25 SwiftRuntimeFunctions(global)1JavaKitDependencyResolver2org.swift.swiftkit.core.annotations3org.swift.swiftkit.core.ref4org.swift.swiftkit.core.tuple5org.swift.swiftkit.core.util6utilities7SwiftJavaMacros8SwiftJavaRuntimeSupport9SwiftJavaShared10org.swift.swiftkit.core11JavaStdlib12org.swift.swiftkit.core.collections13org.swift.swiftkit.ffm14SwiftJavaTool15org.swift.swiftkit.ffm.generated16SwiftJavaConfigurationShared17SwiftJavaToolLib18SwiftJava19JExtractSwiftLib20GenerateConfigDocs21CodePrinting22ExampleSwiftLibrary23JavaKit24SwiftRuntimeFunctions253341263112523228692110367154173151165192205346133919627401125341382222

At a glance — Code Health · 54% · Adequate · gated by X5 ·

At a glance — Architecture · 93% · Exemplary ·

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

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

At a glance — Security · 78% · Checked 4 of 10 · gated by D29 ·

At a glance — Performance · 100% · Exemplary ·

Security & Compliance — OWASP Top-10 mapping

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

OWASP categoryFindingsSeverity
A05:2025 — Injection22High / Critical
A02:2025 — Security Misconfiguration11High / Critical

Roadmap

Top priorities: Declare the default where Java declares it: `@NullMarked` (org.jspecify.annotations) in each package's `package-info.java`, or once in `module-info.java`, and run NullAway (Error Prone) or the Checker Framework so the declaration is enforced. Then annotate the real exceptions `@Nullable` and resolve the suppressions rather than adding to them: a `@SuppressWarnings("NullAway")` or `castToNonNull(x)` on a value the checker could show to be null is a `NullPointerException` waiting for the path that makes it true — where the value genuinely cannot be null, say something the checker can see instead (a null check, `Objects.requireNonNull`, a non-null field initialised in the constructor); 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; Bring the 41 bodies over 15 down to 15 or less in Cognitive Complexity — start with JavaImplementationMacro.expansion (cognitive 53), JavaTranslator.getSwiftTypeNameAsString (cognitive 51), JavaClassTranslator.init (cognitive 50).

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

Do thisHelpsEffortDimension
Declare the default where Java declares it: `@NullMarked` (org.jspecify.annotations) in each package's `package-info.java`, or once in `module-info.java`, and run NullAway (Error Prone) or the Checker Framework so the declaration is enforced. Then annotate the real exceptions `@Nullable` and resolve the suppressions rather than adding to them: a `@SuppressWarnings("NullAway")` or `castToNonNull(x)` on a value the checker could show to be null is a `NullPointerException` waiting for the path that makes it true — where the value genuinely cannot be null, say something the checker can see instead (a null check, `Objects.requireNonNull`, a non-null field initialised in the constructor).+4.7 ptsMediumNullable reference types
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.+3.4 ptsMediumArchitecture documentation
Bring the 41 bodies over 15 down to 15 or less in Cognitive Complexity — start with JavaImplementationMacro.expansion (cognitive 53), JavaTranslator.getSwiftTypeNameAsString (cognitive 51), JavaClassTranslator.init (cognitive 50).+2.8 ptsHighCognitive Complexity
Swallowed exception (caught, then discarded)+2.6 ptsMediumException handling
Resolve the 58 FixmeComment finding(s) in Explicit Debt — start with JavaClassTranslator.swift (6), FFMSwift2JavaGenerator+JavaTranslation.swift (6), SwiftArenaTest.java (4).+1.2 ptsMediumExplicit Debt
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.+2.0 ptsMediumSecurity & performance tooling
Resolve the 51 TodoComment finding(s) in Explicit Debt — start with JavaClassTranslator.swift (3), ConfigureCommand.swift (3), WrapJavaCommand.swift (3).+1.1 ptsMediumExplicit Debt
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.+1.2 ptsMediumDeployment & Rollback

File quality

Per-file score 0–10 — a quality signature. Of 177 files carrying findings, judged against the Preview bar: 0% slop · 17% mixed · 83% near-clean.

FileScoreBandWorst signal
REDACTED3.0MixedIaC & Container Security: High IaC: REDACTED
REDACTED4.4MixedStatic Analysis (SAST): High: REDACTED
Sources/GenerateConfigDocs/ConfigParser.swift5.5MixedCyclomatic Complexity: ConfigParser.swift.docLines (cyclomatic 19)
REDACTED5.8MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.9MixedIaC & Container Security: Medium IaC: REDACTED
Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator+SwiftThunkPrinting.swift6.0MixedExplicit Debt: FixmeComment
Sources/JExtractSwiftLib/FFM/ConversionStep.swift6.0MixedExplicit Debt: FixmeComment
Sources/JExtractSwiftLib/FFM/CDeclLowering/FFMSwift2JavaGenerator+FunctionLowering.swift6.0MixedExplicit Debt: FixmeComment
Sources/SwiftJavaToolLib/JavaClassTranslator.swift6.0MixedExplicit Debt: TodoComment
Sources/SwiftJavaToolLib/JavaTranslator.swift6.0MixedExplicit Debt: TodoComment
Sources/JExtractSwiftLib/FFM/FFMSwift2JavaGenerator+JavaBindingsPrinting.swift6.0MixedExplicit Debt: FixmeComment
Sources/SwiftJavaMacros/JavaMethodMacro.swift6.0MixedExplicit Debt: FixmeComment
Sources/SwiftJavaMacros/JavaClassMacro.swift6.0MixedExplicit Debt: FixmeComment
Sources/SwiftJavaTool/Commands/WrapJavaCommand.swift6.0MixedExplicit Debt: TodoComment
Sources/JExtractSwiftLib/SwiftDocumentationParsing.swift6.0MixedExplicit Debt: TodoComment
Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator+JavaBindingsPrinting.swift6.0MixedExplicit Debt: TodoComment
Sources/SwiftJavaToolLib/JavaType+Equality.swift6.0MixedExplicit Debt: FixmeComment
Sources/JExtractSwiftLib/FFM/FFMSwift2JavaGenerator+SwiftThunkPrinting.swift6.0MixedExplicit Debt: FixmeComment
SwiftKitCore/src/main/java/org/swift/swiftkit/core/SwiftLibraries.java6.0MixedExplicit Debt: TodoComment
Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator+JavaTranslation.swift6.0MixedExplicit Debt: TodoComment

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

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

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

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

Could not be resolved — 20

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

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

What we checked — 40 dimensions across the health lenses
D1D2D3D4D5D6D10D13D14D15D16D17D19D26D28D29D31D34D35D44AX10AX3AX4AX8AX9M1M2M3M4P1P10P2P3P4P6PF1PF3X20X3X5

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, 933 of 949 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 01a1dd3b-0fee-72c6-8727-22d86d57fa8c.

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

Run transparency — what happened this run

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

  • D4 Code Duplication — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 41 duplicated block group(s) on this row were found in the languages this pass could tokenize, and they do NOT cover all of this repository's production source: .java (10,271 lines, 24% of production source) went unread, because no language model this pass could load exposed a clone-unit token stream for those file kinds. Duplication in that source is UNMEASURED — its absence from the count above is a gap in this analyzer's language coverage, not a finding that the code is free of duplication.
  • D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the Swift half could not be measured — the Swift suite in . 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.
  • D10 Test Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 772 test(s) behind this row are the ones the code-model census could read, and this repository also carries at least 61 test source file(s) (.java) that it cannot: it reads the test types the .swift frontend declared, so a suite in any other language is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
  • 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 reliability NOT SCORED: this repository's production source includes .java, and the jvm executor ran against the .java half and never executed — so reliability was not measured for the repository as a whole. The Swift (3 packages): measured (0 flaky) suite(s) did re-run, and came back with 0 flaky across 1 measured tier(s) — but that is a figure for one half of the product, and we do not publish a partial one as if it were complete. This is OUR limitation, not a defect in the repo — test reliability is excluded from the score rather than counted. The half was driven by a runner we ship, so this is not a missing-runner gap.
  • 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 — 9 Maven/Gradle manifest(s) were read, stating a version for 4 dependency(ies) and leaving 4 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
  • D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Swift Package.swift/Package.resolved, but the licence verdict published here was taken over its JVM dependencies. Nothing was read about its SwiftPM dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
  • D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
  • 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.
  • 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's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
  • D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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.
  • 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. `Plugins/JExtractSwiftPlugin/JExtractSwiftPlugin.swift`, `Plugins/PluginsShared/SwiftExtractConfigurationShared/LogLevel.swift`, `Samples/JavaKitSampleApp/Sources/JavaKitExample/SwiftArgumentParserMain.swift`, `Samples/SwiftJavaExtractJNISampleApp/Sources/MySwiftLibrary/Distributed.swift`, `Samples/SwiftJavaExtractJNISampleApp/Sources/MySwiftLibrary/Isolated.swift`, … (+70 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
  • 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's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • 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 DockerCompose (REDACTED). compose up failed (exit 17 — an image could not be built) — test-swift Error pull access denied for swift-java, repository does not exist or may require 'docker login': denied: requested access to the resource is denied 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.
  • C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
  • C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
  • GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Java, Kotlin, 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.
  • IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Kotlin, Swift is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
  • P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
  • S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
  • X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • 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's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • 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's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.

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

Limitations & what we did not check

We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.

Per-dimension blind spots

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

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
  • 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.
  • D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • 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.
  • D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
  • 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 Complexity6.9 / 10Adequate✓ 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 6.9 / 10 · rule-coverage 100% · ceiling Prevented

29 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was KnownJavaFunctionalInterface.find at 41. A further 7 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 AndroidAPILevel.name at 38 — they are counted neither in the figure above nor in this dimension's score. 5 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/SwiftJavaToolLib/AndroidAPILevel.swift (AndroidAPILevel.name at 38), Sources/JExtractSwiftLib/FFM/FFMSwift2JavaGenerator+JavaTranslation.swift (CType.javaType at 18), Sources/JExtractSwiftLib/FFM/CDeclLowering/CRepresentation.swift (SwiftKnownTypeDeclKind.primitiveCType at 17), Sources/JExtractSwiftLib/JNI/JNIJavaTypeTranslator.swift (JNIJavaTypeTranslator.translate at 16), Sources/SwiftJavaToolLib/ClassParsing/JavaClassFileReader.swift (JavaClassFileReader.parseConstantPool at 16). 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.

KnownJavaFunctionalInterface.find (cyclomatic 41)Sources/JExtractSwiftLib/KnownFunctionalInterfaces.swift:228
JNISwift2JavaGenerator.printFunctionDowncall (cyclomatic 34)Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator+SwiftThunkPrinting.swift:600
JavaImplementationMacro.expansion (cyclomatic 34)Sources/SwiftJavaMacros/ImplementsJavaMacro.swift:51
ConversionStep.asExprSyntax (cyclomatic 30)Sources/JExtractSwiftLib/FFM/ConversionStep.swift:107
LoweredFunctionSignature.cdeclThunk (cyclomatic 30)Sources/JExtractSwiftLib/FFM/CDeclLowering/FFMSwift2JavaGenerator+FunctionLowering.swift:981

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

What to do

  1. Bring the 3 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with KnownJavaFunctionalInterface.find (cyclomatic 41), JNISwift2JavaGenerator.printFunctionDowncall (cyclomatic 34), JavaImplementationMacro.expansion (cyclomatic 34). — 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 3 together lifts Cyclomatic Complexity from 6.9 to about 7.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 Complexity6.1 / 10Adequate✓ Tool-verified

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

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

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

41 method(s) exceeded the cognitive complexity threshold of 15; the worst was JavaImplementationMacro.expansion at 53.

JavaImplementationMacro.expansion (cognitive 53)Sources/SwiftJavaMacros/ImplementsJavaMacro.swift:51
JavaTranslator.getSwiftTypeNameAsString (cognitive 51)Sources/SwiftJavaToolLib/JavaTranslator.swift:155
JavaClassTranslator.init (cognitive 50)Sources/SwiftJavaToolLib/JavaClassTranslator.swift:116
MarkdownRenderer.renderTypeSchemaLines (cognitive 49)Sources/GenerateConfigDocs/MarkdownRenderer.swift:118
JavaClassTranslator.renderMethod (cognitive 48)Sources/SwiftJavaToolLib/JavaClassTranslator.swift:1039

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

What to do

  1. Bring the 41 bodies over 15 down to 15 or less in Cognitive Complexity — start with JavaImplementationMacro.expansion (cognitive 53), JavaTranslator.getSwiftTypeNameAsString (cognitive 51), JavaClassTranslator.init (cognitive 50). — 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 41 together lifts Cognitive Complexity from 6.1 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.

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

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

22 god class(es) detected.

MethodTooLong: CdeclLowering.lowerParameter · ×11Sources/JExtractSwiftLib/FFM/CDeclLowering/FFMSwift2JavaGenerator+FunctionLowering.swift:192
FileTooLong: JNI/JNISwift2JavaGenerator+JavaTranslation.swift · ×7Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator+JavaTranslation.swift
TooManyMethods: JNISwift2JavaGenerator · ×3Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator.swift:27
ClassTooLong: CdeclLoweringSources/JExtractSwiftLib/FFM/CDeclLowering/FFMSwift2JavaGenerator+FunctionLowering.swift:81

What to do

  1. Resolve the 11 MethodTooLong finding(s) in God Classes — start with FFMSwift2JavaGenerator+FunctionLowering.swift (3), JavaClassTranslator.swift (2), JNISwift2JavaGenerator+SwiftThunkPrinting.swift. — One of this dimension's main actionable groups (11 warning-level).
  2. Resolve the 7 FileTooLong finding(s) in God Classes — start with JNISwift2JavaGenerator+JavaTranslation.swift, JavaClassTranslator.swift, JNISwift2JavaGenerator+SwiftThunkPrinting.swift. — One of this dimension's main actionable groups (7 warning-level).
  3. Resolve the 3 TooManyMethods finding(s) in God Classes — start with JNISwift2JavaGenerator.swift, FFMSwift2JavaGenerator.swift, JavaClassTranslator.swift. — One of this dimension's main actionable groups (3 warning-level).

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

D4 · Code Duplication8.0 / 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.0 / 10 · rule-coverage 100% · ceiling Verified

41 duplicated block group(s) detected. 5.0 % of the production lines (2,096 of 42,331) are in a reported copy. A further 46 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 4 of the 87 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. Measured on part of this repository only: .java (24% of production source) was not exposed to the token comparison, so duplication there is unmeasured and is not in this count.

Duplicated block (8 lines × 2) · ×6Sources/CodePrinting/CodePrinter+Java.swift:22
Duplicated block (9 lines × 2) · ×5Sources/JExtractSwiftLib/FFM/CDeclLowering/FFMSwift2JavaGenerator+FunctionLowering.swift:26
Duplicated block (7 lines × 2) · ×5Sources/JExtractSwiftLib/FFM/CDeclLowering/FFMSwift2JavaGenerator+FunctionLowering.swift:1085
Edited copy of a member (12 corresponding lines) · ×4Sources/SwiftJavaRuntimeSupport/CollectionBridge.swift:20
Edited copy of a member (7 corresponding lines) · ×4Sources/SwiftJava/BridgedValues/JavaBoxing.swift:274

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

What to do

  1. Resolve the 6 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with CodePrinter+Java.swift, JavaObject+MethodCalls.swift, ImplementsJavaMacro.swift. — One of this dimension's main actionable groups (6 warning-level).
  2. Resolve the 5 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with FFMSwift2JavaGenerator+FunctionLowering.swift, FFMSwift2JavaGenerator+JavaBindingsPrinting.swift, FFMSwift2JavaGenerator.swift. — One of this dimension's main actionable groups (5 warning-level).
  3. Resolve the 5 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with JavaBoxing.swift (3), FFMSwift2JavaGenerator+FunctionLowering.swift, ConversionStep.swift. — One of this dimension's main actionable groups (5 warning-level).

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

D5 · Coupling9.6 / 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.6 / 10 · rule-coverage 100% · ceiling Prevented

22 production modules (Gradle+SwiftPM), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; 2 module(s) off the main sequence, with abstractness counted on 13 of the 22 (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: SwiftRuntimeFunctions
Off the main sequence: SwiftJavaConfigurationShared

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)7.5 / 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 7.5 / 10 · rule-coverage 100% · ceiling Verified

5 of 24 classes have LCOM4 above 3.

Low cohesion: String (LCOM4 9) · ×5Sources/GenerateConfigDocs/ConfigParser.swift:582

What to do

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

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

D10 · Test Quality10.0 / 10Stronggated by 2 serious findings✓ Tool-verified

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

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

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

2 skipped (1 with a documented reason), 592 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 772 tests (3 harness-style project(s) excluded from the assertion penalty). Measured on the .swift suite only — at least 61 test source file(s) (.java) went unread, so its test quality is unmeasured and is not in these counts.

Skipped test: test_parseRealFileTests/SwiftJavaToolLibTests/AndroidAPIVersionsParserTests.swift:219
No assertions: parseJSONWithCommentsTests/SwiftJavaConfigurationSharedTests/SwiftJavaConfigurationTests.swift:21
No direct assertions: func_accept_array_uint8 · ×591Tests/JExtractSwiftTests/ByteArrayTests.swift:22
Test project verifies nothing: SwiftJavaMacrosTestsTests/SwiftJavaMacrosTests/JavaClassMacroTests.swift:32
Skipped (documented): swiftinterfaceCommonPatternTests/JExtractSwiftTests/IfConfigTests.swift:133

What to do

  1. Resolve the 591 No direct assertions finding(s) in Test Quality — start with JNIClosureTests.swift (48), FunctionLoweringTests.swift (30), FuncCallbackImportTests.swift (25). — One of this dimension's main actionable groups (591 recommendation-level).
  2. Resolve the 1 Skipped test finding(s) in Test Quality — start with AndroidAPIVersionsParserTests.swift. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 No assertions finding(s) in Test Quality — start with SwiftJavaConfigurationTests.swift. — One of this dimension's main actionable groups (1 warning-level).

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

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 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 9 Maven/Gradle manifest(s) declare with a version resolvable from the manifest itself — the same declaration-site closure this analysis reads for dependency currency. The JVM has no lockfile a checkout is guaranteed to carry, so this is deliberately NOT the transitive closure. 4 further coordinate(s) are declared with no version at the declaration site — inherited from a parent POM, a BOM or an unresolved Gradle version reference — and are NOT graded: this verdict covers what the checkout pins, not the full transitive graph. ★ COVERAGE OF THIS VERDICT: it grades this repository's JVM dependencies and nothing else. The repository also declares a Swift Package.swift/Package.resolved, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

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

Top hotspots: Sources/JExtractSwiftLib/KnownFunctionalInterfaces.swift (12×41=492); Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator+SwiftThunkPrinting.swift (6×34=204); Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator+JavaBindingsPrinting.swift (3×17=51)

Hotspot: Sources/JExtractSwiftLib/KnownFunctionalInterfaces.swift · ×3Sources/JExtractSwiftLib/KnownFunctionalInterfaces.swift:228

What to do

  1. Resolve the 3 Hotspot finding(s) in Churn × Complexity Hotspots — start with KnownFunctionalInterfaces.swift, JNISwift2JavaGenerator+SwiftThunkPrinting.swift, JNISwift2JavaGenerator+JavaBindingsPrinting.swift. — One of this dimension's main actionable groups (3 warning-level).

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

D16 · Bus Factor9.0 / 10Strong✓ 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 9.0 / 10 · rule-coverage 100% · ceiling Documented

13 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is Sources/JExtractSwiftLib/KnownFunctionalInterfaces.swift. Counted over 125 of the 319 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
Further sole-owners (lower concentration)

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).
  2. Resolve the 1 Further sole-owners (lower concentration) 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.5 / 10Stronggated by 109 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.5 / 10 · rule-coverage 100% · ceiling Prevented

109 deducted task-comment markers across 42331 LoC (0.2/KLoC) → score 9.5. 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.

FixmeComment · ×58Package.swift:172
TodoComment · ×51Tests/SwiftJavaToolLibTests/CompileJavaWrapTools.swift:128

What to do

  1. Resolve the 58 FixmeComment finding(s) in Explicit Debt — start with JavaClassTranslator.swift (6), FFMSwift2JavaGenerator+JavaTranslation.swift (6), SwiftArenaTest.java (4). — One of this dimension's main actionable groups (58 warning-level).
  2. Resolve the 51 TodoComment finding(s) in Explicit Debt — start with JavaClassTranslator.swift (3), ConfigureCommand.swift (3), WrapJavaCommand.swift (3). — One of this dimension's main actionable groups (51 warning-level).

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

D19 · Documentation Quality10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether the project's documentation is clear, complete, and useful.

Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.

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

1 of 1 documentation facets pass in full. 3 document(s) read across 1 unit(s).

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.md.

D26 · Project Cohesion5.0 / 10Adequate✓ Tool-verified

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

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

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

1 of 4 build units (Gradle, SwiftPM) flagged as possibly oversized/incoherent.

Projects may be oversized for their cohesion

What to do

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

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

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)3.0 / 10Weak✓ 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 3.0 / 10 · rule-coverage 100% · ceiling Documented

22 finding(s): 0 critical, 22 high, 0 medium, 0 low. 15 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 3 file(s) — `SwiftKitFFM/src/main/java/org/swift/swiftkit/ffm/generated/SwiftRuntimeFunctions.java` (line 33, line 34, line 35, …), `REDACTED` (line 24), `gradlew` (line 74, line 178) — 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. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.

REDACTED
REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 3 REDACTED finding(s) charged to Static Analysis (SAST) — the other 14 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once. — One of this dimension's main actionable groups (17 issue-level, 3 of them charged here).
  2. Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
  3. Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).

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

D31 · IaC & Container Security8.2 / 10Adequategated by 3 critical findings✓ 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 8.2 / 10 · rule-coverage 100% · ceiling Documented

11 finding(s): 0 critical, 3 high, 8 medium, 0 low.

REDACTED
REDACTED

What to do

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

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

D34 · Knowledge Freshness9.8 / 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 9.8 / 10 · rule-coverage 100% · ceiling Documented

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

Orphaned file · ×3Sources/JExtractSwiftLib/CTypes/CType.swift:1
Orphaned files with no living knowledge

✓ On the Gold path — maintain.

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

D35 · Change Coupling9.7 / 10Stronggated by 4 serious findings✓ Tool-verified

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

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

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

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

Strongest change-coupling: CRepresentation.swift↔FFMSwift2JavaGenerator+FunctionLowering.swift 91%; MySwiftLibrary.swift↔KnownFunctionalInterfaces.swift 86%; JavaType+JDK.swift↔KnownFunctionalInterfaces.swift 86%

Change coupling: CRepresentation.swift ↔ FFMSwift2JavaGenerator+FunctionLowering.swift · ×3Sources/JExtractSwiftLib/FFM/CDeclLowering/CRepresentation.swift:1
Change coupling clique: MySwiftLibrary.swift, JavaType+JDK.swift, KnownFunctionalInterfaces.swiftSources/ExampleSwiftLibrary/MySwiftLibrary.swift

What to do

  1. Resolve the 3 Change coupling finding(s) in Change Coupling — start with CRepresentation.swift (2), SwiftSyntax+Extensions.swift. — One of this dimension's main actionable groups (3 warning-level).
  2. Resolve the 1 Change coupling clique finding(s) in Change Coupling — start with MySwiftLibrary.swift. — One of this dimension's main actionable groups (1 warning-level).

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

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

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

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

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

0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 7 platform declaration(s) and 8 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Frontend & cross-cutting dimensions

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

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 isolation10.0 / 10Exemplary✓ Tool-verified

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

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

AX9 · CQS / query purity10.0 / 10Exemplary✓ Tool-verified

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

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

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

M1 · Documentation (README)7.7 / 10Strong✓ Tool-verified

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

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

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.

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

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

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

P2 · Observability6.0 / 10Adequate✓ Tool-verified

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

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

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

What to do

  • Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
P3 · Security & performance 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 1 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:1
  • `REDACTED` schedules updates, but no `package-ecosystem` entry covers `gradle`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list. — REDACTED:2

What to do

  • Add a SAST step to CI running what this repository's stack ships: CodeQL's Swift pack (Swift/Xcode) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
  • Dependabot is configured but does not watch `gradle` — add that `package-ecosystem` entry to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
  • 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.
PF1 · Benchmark discipline10.0 / 10Exemplary✓ Tool-verified

Readiness · Performance — Whether the code protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.

Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI; off .NET, the same ladder over Go testing.B, Rust criterion/#[bench]/divan, JMH/kotlinx-benchmark, pytest-benchmark/asv/pyperf, tinybench/mitata/vitest bench/benchmark.js and Swift package-benchmark — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.

PF3 · Async & latency hygiene10.0 / 10Exemplary✓ Tool-verified

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

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

X20 · Mistyped argument guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether an argument guard throws the exception its own condition describes — a guard that rejects a value for being EMPTY and reports it as `NullPointerException` (Java, Kotlin, Scala), `ArgumentError.notNull` (Dart) or `ArgumentNullException` (F#'s `nullArg`) tells the caller a parameter was null when it provably was not.

Method: Roslyn syntax: `throw new ArgumentNullException(nameof(p))` statements (or a repository exception type deriving from it) controlled by an `if` — directly or through the `using`, `lock` or `try` that wraps the throw — whose condition is read for a test that is true of a NON-null `p` — an emptiness test that dereferences it (`p.Count == 0`, `!p.Any()`) or a BCL predicate documented true of the empty value (`string.IsNullOrEmpty(p)`); in the `else` branch, for a conjunct of the admitting condition that is FALSE of a non-null `p`. Range guards are read for bounds that leave nothing and for a `p > C.Count` bound whose index then reaches `C[p]`, `C.RemoveAt(p)` or a method of the same type that indexes with it. Deterministic, provable per finding. Advisory.

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

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

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

  • `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×4) — Sources/SwiftJavaToolLib/JavaHomeSupport.swift:142, Sources/SwiftJava/AndroidSupport.swift:128, Sources/SwiftJava/BridgedValues/JobjectBridge.swift:41, …

What to do

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

Other · Code Health — Whether Java packages are null-marked and not undermined by heavy nullness suppression — a package under `@NullMarked` (or `@NonNullApi`, `@ParametersAreNonnullByDefault`, `@NonNullByDefault`, or a NullAway/Checker Framework configuration naming it) makes an unannotated reference exclude null, and `@SuppressWarnings("NullAway")`, `("nullness")`, `("null")` and `castToNonNull(…)` are what silence it.

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

  • 0/9 of this repository's Java package directories are under a non-null default: a `package-info.java` declaring `@NullMarked` (JSpecify) or `@NonNullApi`, `@ParametersAreNonnullByDefault`, `@NonNullByDefault`, `@DefaultQualifier(NonNull.class)`; a `module-info.java` declaring `@NullMarked`; every type in it `@NullMarked`; or a build that runs NullAway with the package in `AnnotatedPackages`, or the Checker Framework's `NullnessChecker`. Elsewhere every reference admits null and no checker warns on the dereference that throws a `NullPointerException`.

What to do

  • Declare the default where Java declares it: `@NullMarked` (org.jspecify.annotations) in each package's `package-info.java`, or once in `module-info.java`, and run NullAway (Error Prone) or the Checker Framework so the declaration is enforced. Then annotate the real exceptions `@Nullable` and resolve the suppressions rather than adding to them: a `@SuppressWarnings("NullAway")` or `castToNonNull(x)` on a value the checker could show to be null is a `NullPointerException` waiting for the path that makes it true — where the value genuinely cannot be null, say something the checker can see instead (a null check, `Objects.requireNonNull`, a non-null field initialised in the constructor).

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 Health54%Adequate — gated by X5Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture93%ExemplarySolid.
Maturity61%Adequate — gated by M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness58%Adequate — gated by P3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security78%Checked 4 of 10Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance100%ExemplaryStrongest area.
Unscored — 1 check(s) recorded observations but carry no score

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

  • X10 Duplicated predicate — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for

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

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

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 applicable: this repository's Java imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Kotlin imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Swift imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
  • AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Java code is a Spring, JSR-330 or CDI singleton bean. No class in this Kotlin code is a Spring, JSR-330 or CDI singleton bean. 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 — AX6 reached only 24% of this repository's production lines — swift (31,726 lines), kotlin (334 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • 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 — compose up failed (exit 17 — an image could not be built) — test-swift Error pull access denied for swift-java, repository does not exist or may require 'docker login': denied: requested access to the resource is denied 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.
  • D11 Test Reliability — Test reliability not scored — polyglot repository, one half's runner produced no measurement
  • D12 Dependency Hygiene — Not scored — 9 Maven/Gradle manifest(s) were read, stating a version for 4 dependency(ies) and leaving 4 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. 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.
  • D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
  • D21 Naming Consistency — D21 withholds its case and prefix conventions rows: 4 candidate(s) found and not reported.
  • D22 Internal API Consistency — API consistency is measured on C# only; the exposed Swift surface was not measured.
  • D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
  • D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .java, .kt, .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
  • D27 Navigability — symbol resolution incomplete — navigability not assessed
  • 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, a Gradle version catalogue and a Gradle build (build.gradle/build.gradle.kts) — not scanned yet).
  • D32 Data Compliance (PII/GDPR) — 75 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
  • D36 Supply-chain Provenance & Signing — 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).
  • 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, a Gradle version catalogue and a Gradle build (build.gradle/build.gradle.kts) — not scanned yet).
  • D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
  • D8 Code Coverage — Coverage not measured — Swift suite
  • DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (14 value object(s))
  • ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and this analysis resolves a call's owner only where the receiver's type is written down in the source. Reported as guidance rather than measured
  • ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
  • IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • 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 JVM, Swift source, so there is no service whose uptime a failing dependency could take down
  • P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
  • P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
  • PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
  • S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X12 Unreachable branch — X12 reached only 1% of this repository's production lines — swift (31,726 lines), java (10,271 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X16 Unfloored truncation loop — X16 reached only 25% of this repository's production lines — swift (31,726 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X18 Disposal-pattern correctness — X18 reached only 25% of this repository's production lines — swift (31,726 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X21 Side-effecting pattern guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X27 Collection changed while being enumerated — X27 reached only 25% of this repository's production lines — swift (31,726 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Java was read, and it logs through none that an assembled message defeats: java.util.logging's level methods, log4j 1, commons-logging, JBoss Logging and Flogger take one finished message (as log4net does in C#), or it makes no call through a named logger at all. Calls made through SLF4J or log4j 2 (`org.slf4j.Logger`, `org.apache.logging.log4j.Logger`, Lombok's `@Slf4j`) would be judged.
  • X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • 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 — 25 finding(s)
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D31 · IaC & Container Security · High IaC · ×3
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
Serious — 313 finding(s)
D17 · Explicit Debt · FixmeComment · ×58
  • FixmeComment Package.swift:172 — // FIXME: swift-collections 1.7.0 raised its minimum toolchain to Swift 6.2; stay below it while we still support Swift 6.1 — 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 Tests/SwiftJavaToolLibTests/CompileJavaWrapTools.swift:115 — // FIXME: deduplicate this — 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 Tests/SwiftJavaToolLibTests/CompileJavaWrapTools.swift:127 — // FIXME: deduplicate this with SwiftJava.WrapJavaCommand.runCommand !!! — 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 Tests/SwiftJavaToolLibTests/WrapJavaTests/BasicWrapJavaTests.swift:115 — // FIXME: the mapping configuration could be used to nest this properly but today we don't automatically? — 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 Tests/SwiftJavaToolLibTests/WrapJavaTests/GenericsWrapJavaTests.swift:318 — // FIXME: we need this — 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 Tests/JExtractSwiftTests/FunctionLoweringTests.swift:390 — // FIXME: C pretty printing isn't handling parameters of function pointer — 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 SwiftKitFFM/src/main/java/org/swift/swiftkit/ffm/SwiftRuntime.java:320 — // FIXME: this free is not always correct: — 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 SwiftKitFFM/src/main/java/org/swift/swiftkit/ffm/SwiftValueLayout.java:53 — // FIXME: this sequence layout is a workaround, we must properly size pointers when we get them. — 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/SwiftJavaToolLib/JavaClassTranslator.swift:571 — // FIXME: move the 'where ...' part into the render bit — 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/SwiftJavaToolLib/JavaClassTranslator.swift:949 — // FIXME: handle generics in constructors — 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/SwiftJavaToolLib/JavaClassTranslator.swift:971 — // FIXME: make this equals based? — 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/SwiftJavaToolLib/JavaClassTranslator.swift:1070 — // FIXME: cleanup the checking here — 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/SwiftJavaToolLib/JavaClassTranslator.swift:1162 — // FIXME: refactor this so we don't have to duplicate the method signatures — 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/SwiftJavaToolLib/JavaClassTranslator.swift:1349 — // FIXME: constructors are not well handled — 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/SwiftJavaToolLib/JavaTranslator.swift:264 — // FIXME: improve the get 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.
  • FixmeComment Sources/SwiftJavaToolLib/JavaType+Equality.swift:78 — // FIXME: This is a hack. — 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/SwiftJavaTool/SwiftJavaBaseAsyncParsableCommand.swift:103 — // FIXME: replace with stored property inside specific commands — 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/SwiftJavaTool/Java/JavaClassLoader.swift:20 — // FIXME: do we need this here or can we rely on the generated one? — 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/SwiftJavaTool/Commands/ResolveCommand.swift:74 — // FIXME: disentangle the output directory from SwiftJava and then make it a required option in this Command — 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/SwiftJavaMacros/GenerationMode.swift:52 — // FIXME: swift-syntax probably needs an AttributedSyntax node for us — 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/SwiftJavaMacros/JavaClassMacro.swift:179 — // FIXME: This is somewhat of a hack; we could look 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.
  • FixmeComment Sources/SwiftJavaMacros/JavaMethodMacro.swift:32 — // FIXME: nil is a workaround for the fact that extension JavaClass doesn't — 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/SwiftJavaMacros/JavaMethodMacro.swift:191 — /// FIXME: It might be preferable to explicitly specify the type from JavaClass, similar to `typeErasedResult`. — 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/SwiftJava/AnyJavaObject.swift:62 — // FIXME: this is a bad idea, can be null — 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/SwiftJava/Optional+JavaObject.swift:45 — // FIXME: Think about checking the runtime type? — 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.
  • + 33 more in this group — see findings.md.
D17 · Explicit Debt · TodoComment · ×51
  • TodoComment Tests/SwiftJavaToolLibTests/CompileJavaWrapTools.swift:128 — // TODO: especially because nested classes — 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 Tests/SwiftJavaToolLibTests/CompileJavaWrapTools.swift:129 — // WrapJavaCommand().<TODO> — 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 Tests/SwiftJavaToolLibTests/WrapJavaTests/GenericsWrapJavaTests.swift:335 — // TODO: what if we visit in other order, does the wrap-java handle 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 Tests/SwiftJavaToolLibTests/WrapJavaTests/GenericsWrapJavaTests.swift:472 — // TODO: this should be improved some more, we need to generated a `: Map` on the Swift side — 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 Tests/JExtractSwiftTests/ByteArrayTests.swift:25 — // TODO: implement JNI mode here — 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 Tests/JExtractSwiftTests/ByteArrayTests.swift:96 — // TODO: implement JNI mode here — 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 SwiftKitFFM/src/main/java/org/swift/swiftkit/ffm/SwiftRuntime.java:231 — // TODO: A bit annoying to generate, we need an arena for the conversion... — 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 SwiftKitFFM/src/main/java/org/swift/swiftkit/ffm/SwiftRuntime.java:345 — // TODO: we could cache the handles per type once we have them, to speed up subsequent calls — 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 SwiftKitCore/src/main/java/org/swift/swiftkit/core/SimpleCompletableFuture.java:133 — // TODO: If we're representing a Swift Task computation with this future, — 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 SwiftKitCore/src/main/java/org/swift/swiftkit/core/SwiftLibraries.java:164 — // TODO: we could do an in memory file system here — 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 SwiftKitCore/src/main/java/org/swift/swiftkit/core/annotations/NonNull.java:24 — // TODO: Consider depending on jspecify 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 SwiftKitCore/src/main/java/org/swift/swiftkit/core/annotations/Nullable.java:24 — // TODO: Consider depending on jspecify 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/SwiftJavaToolLib/JavaClassTranslator.swift:97 — /// TODO: These are currently unimplemented. — 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/SwiftJavaToolLib/JavaClassTranslator.swift:229 — // TODO: Switch over to "declared" versions of these whenever we don't need — 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/SwiftJavaToolLib/JavaClassTranslator.swift:1017 — // TODO: make it more precise with the "origin" of the generic parameter (outer class etc) — 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/SwiftJavaToolLib/JavaGenericsSupport.swift:45 — // TODO: also handle nested classes here... — 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/SwiftJavaToolLib/JavaTranslator.swift:77 — /// TODO: Make JavaClass Hashable so we can index by the object? — 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/SwiftJavaTool/Commands/ConfigureCommand.swift:42 — // TODO: This should be a "make wrappers" option that just detects when we give it a jar — 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/SwiftJavaTool/Commands/ConfigureCommand.swift:116 — // TODO: make this perhaps "emit type mappings" — 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/SwiftJavaTool/Commands/ConfigureCommand.swift:145 — // TODO: is this correct? — 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/SwiftJavaTool/Commands/JExtractCommand.swift:36 — // TODO: wrap-swift? — 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/SwiftJavaTool/Commands/WrapJavaCommand.swift:123 — // TODO: may need to resolve the dependency configs rather than just get their configs — 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/SwiftJavaTool/Commands/WrapJavaCommand.swift:124 — // TODO: We should cache the resolved classpaths as well so we don't do it many times — 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/SwiftJavaTool/Commands/WrapJavaCommand.swift:432 — // TODO: lower to trace level — 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/SwiftJavaMacros/JavaMethodMacro.swift:97 — // TODO: Improve this unwrapping a bit; — 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.
  • + 26 more in this group — see findings.md.
D3 · God Classes · MethodTooLong · ×11
  • MethodTooLong: CdeclLowering.lowerParameter Sources/JExtractSwiftLib/FFM/CDeclLowering/FFMSwift2JavaGenerator+FunctionLowering.swift:192 — MethodTooLong — lowerParameter runs 182 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 82 over it, 1.82× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: JNISwift2JavaGenerator.printFunctionDowncall Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator+SwiftThunkPrinting.swift:600 — MethodTooLong — printFunctionDowncall 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.
  • MethodTooLong: LoweredFunctionSignature.cdeclThunk Sources/JExtractSwiftLib/FFM/CDeclLowering/FFMSwift2JavaGenerator+FunctionLowering.swift:981 — MethodTooLong — cdeclThunk runs 124 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 24 over it, 1.24× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: CdeclLowering.lowerResult Sources/JExtractSwiftLib/FFM/CDeclLowering/FFMSwift2JavaGenerator+FunctionLowering.swift:687 — MethodTooLong — lowerResult runs 120 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 20 over it, 1.20× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: JavaImplementationMacro.expansion Sources/SwiftJavaMacros/ImplementsJavaMacro.swift:51 — MethodTooLong — expansion runs 120 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 20 over it, 1.20× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: WrapJavaCommand.generateWrappers Sources/SwiftJavaTool/Commands/WrapJavaCommand.swift:144 — MethodTooLong — generateWrappers runs 120 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 20 over it, 1.20× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: JavaClassTranslator.renderMethod Sources/SwiftJavaToolLib/JavaClassTranslator.swift:1039 — MethodTooLong — renderMethod runs 112 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 12 over it, 1.12× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: JavaTranslator.getSwiftTypeNameAsString Sources/SwiftJavaToolLib/JavaTranslator.swift:155 — MethodTooLong — getSwiftTypeNameAsString runs 107 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 7 over it, 1.07× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: JavaMethodMacro.expansion Sources/SwiftJavaMacros/JavaMethodMacro.swift:23 — MethodTooLong — expansion runs 106 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 6 over it, 1.06× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: ConversionStep.asExprSyntax Sources/JExtractSwiftLib/FFM/ConversionStep.swift:107 — MethodTooLong — asExprSyntax runs 103 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 3 over it, 1.03× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: JavaClassTranslator.init Sources/SwiftJavaToolLib/JavaClassTranslator.swift:116 — MethodTooLong — init runs 103 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 3 over it, 1.03× 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.
D31 · IaC & Container Security · Medium IaC · ×8
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D3 · God Classes · FileTooLong · ×7
  • FileTooLong: JNI/JNISwift2JavaGenerator+JavaTranslation.swift Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator+JavaTranslation.swift — FileTooLong — 1522 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1022 over it, 3.04× 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.
  • FileTooLong: SwiftJavaToolLib/JavaClassTranslator.swift Sources/SwiftJavaToolLib/JavaClassTranslator.swift — FileTooLong — 857 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 357 over it, 1.71× 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.
  • FileTooLong: JNI/JNISwift2JavaGenerator+SwiftThunkPrinting.swift Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator+SwiftThunkPrinting.swift — FileTooLong — 784 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 284 over it, 1.57× 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.
  • FileTooLong: CDeclLowering/FFMSwift2JavaGenerator+FunctionLowering.swift Sources/JExtractSwiftLib/FFM/CDeclLowering/FFMSwift2JavaGenerator+FunctionLowering.swift — FileTooLong — 725 significant lines (blank, comment-only and punctuation-only lines excluded), about 70% of them inside a single declaration: CdeclLowering (81-889). The bar is 500 significant lines; this is 225 over it, 1.45× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: FFM/FFMSwift2JavaGenerator+JavaTranslation.swift Sources/JExtractSwiftLib/FFM/FFMSwift2JavaGenerator+JavaTranslation.swift — FileTooLong — 663 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 163 over it, 1.33× 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.
  • FileTooLong: JNI/JNISwift2JavaGenerator+JavaBindingsPrinting.swift Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator+JavaBindingsPrinting.swift — FileTooLong — 663 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 163 over it, 1.33× 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.
  • FileTooLong: FFM/FFMSwift2JavaGenerator+JavaBindingsPrinting.swift Sources/JExtractSwiftLib/FFM/FFMSwift2JavaGenerator+JavaBindingsPrinting.swift — FileTooLong — 535 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 35 over it, 1.07× 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.
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×6
  • Duplicated block (8 lines × 2) Sources/CodePrinting/CodePrinter+Java.swift:22 — Sources/CodePrinting/CodePrinter+Java.swift:22-29 | Sources/CodePrinting/CodePrinter+Swift.swift:35-42 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/CodePrinting/CodePrinter+Java.swift:22` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (8 lines × 2) Sources/SwiftJava/JavaObject+MethodCalls.swift:159 — Sources/SwiftJava/JavaObject+MethodCalls.swift:159-166 | Sources/SwiftJava/JavaObject+MethodCalls.swift:355-362 — 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/SwiftJava/JavaObject+MethodCalls.swift:159` 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.
  • Duplicated block (8 lines × 2) Sources/SwiftJavaMacros/ImplementsJavaMacro.swift:61 — Sources/SwiftJavaMacros/ImplementsJavaMacro.swift:61-68 | Sources/SwiftJavaMacros/JavaClassMacro.swift:35-42 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (8 lines × 2) Sources/SwiftJavaToolLib/AndroidAPIVersionSupport/AndroidAPIVersionsParser.swift:106 — Sources/SwiftJavaToolLib/AndroidAPIVersionSupport/AndroidAPIVersionsParser.swift:106-113 | Sources/SwiftJavaToolLib/AndroidAPIVersionSupport/AndroidAPIVersionsParser.swift:118-125 — 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 (8 lines × 2) Sources/SwiftJava/JavaExtensions/JavaIterator+Iterator.swift:18 — Sources/SwiftJava/JavaExtensions/JavaIterator+Iterator.swift:18-25 | Sources/SwiftJava/JavaExtensions/ListIterator+Iterator.swift:18-25 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (8 lines × 2) Samples/SwiftAndJavaJarFFMSampleLib/src/main/java/com/example/swift/HelloJava2Swift.java:26 — Samples/SwiftAndJavaJarFFMSampleLib/src/main/java/com/example/swift/HelloJava2Swift.java:26-33 | Samples/SwiftJavaExtractFFMSampleApp/src/main/java/com/example/swift/HelloJava2Swift.java:31-38 — before extracting anything, compare `Samples/SwiftAndJavaJarFFMSampleLib/src/main/java/com/example/swift/HelloJava2Swift.java` and `Samples/SwiftJavaExtractFFMSampleApp/src/main/java/com/example/swift/HelloJava2Swift.java` as WHOLE FILES: 86% 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 1 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) · ×5
  • Duplicated block (9 lines × 2) Sources/JExtractSwiftLib/FFM/CDeclLowering/FFMSwift2JavaGenerator+FunctionLowering.swift:26 — Sources/JExtractSwiftLib/FFM/CDeclLowering/FFMSwift2JavaGenerator+FunctionLowering.swift:26-34 | Sources/JExtractSwiftLib/FFM/CDeclLowering/FFMSwift2JavaGenerator+FunctionLowering.swift:42-51 — 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/JExtractSwiftLib/FFM/CDeclLowering/FFMSwift2JavaGenerator+FunctionLowering.swift:26` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (9 lines × 2) Sources/JExtractSwiftLib/FFM/FFMSwift2JavaGenerator+JavaBindingsPrinting.swift:618 — Sources/JExtractSwiftLib/FFM/FFMSwift2JavaGenerator+JavaBindingsPrinting.swift:618-626 | Sources/JExtractSwiftLib/FFM/FFMSwift2JavaGenerator+JavaBindingsPrinting.swift:628-636 — 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 (9 lines × 2) Sources/JExtractSwiftLib/FFM/FFMSwift2JavaGenerator.swift:179 — Sources/JExtractSwiftLib/FFM/FFMSwift2JavaGenerator.swift:179-187 | Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator+JavaBindingsPrinting.swift:46-54 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (9 lines × 2) Sources/SwiftJava/SwiftObjects.swift:46 — Sources/SwiftJava/SwiftObjects.swift:46-54 | Sources/SwiftJava/SwiftObjects.swift:62-70 — 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/SwiftJava/SwiftObjects.swift:46` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) Sources/SwiftJavaToolLib/JavaClassTranslator.swift:627 — Sources/SwiftJavaToolLib/JavaClassTranslator.swift:627-635 | Sources/SwiftJavaToolLib/JavaClassTranslator.swift:708-716 — 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/SwiftJavaToolLib/JavaClassTranslator.swift:627` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×5
  • Duplicated block (7 lines × 2) Sources/JExtractSwiftLib/FFM/CDeclLowering/FFMSwift2JavaGenerator+FunctionLowering.swift:1085 — Sources/JExtractSwiftLib/FFM/CDeclLowering/FFMSwift2JavaGenerator+FunctionLowering.swift:1085-1091 | Sources/JExtractSwiftLib/FFM/CDeclLowering/FFMSwift2JavaGenerator+FunctionLowering.swift:1099-1105 — 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 (7 lines × 2) Sources/JExtractSwiftLib/FFM/ConversionStep.swift:131 — Sources/JExtractSwiftLib/FFM/ConversionStep.swift:131-138 | Sources/JExtractSwiftLib/FFM/ConversionStep.swift:182-188 — 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 (7 lines × 2) Sources/SwiftJava/BridgedValues/JavaBoxing.swift:62 — Sources/SwiftJava/BridgedValues/JavaBoxing.swift:62-68 | Sources/SwiftJava/BridgedValues/JavaBoxing.swift:251-257 — 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 (7 lines × 2) Sources/SwiftJava/BridgedValues/JavaBoxing.swift:82 — Sources/SwiftJava/BridgedValues/JavaBoxing.swift:82-88 | Sources/SwiftJava/BridgedValues/JavaBoxing.swift:231-237 — 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 (7 lines × 2) Sources/SwiftJava/BridgedValues/JavaBoxing.swift:165 — Sources/SwiftJava/BridgedValues/JavaBoxing.swift:165-171 | Sources/SwiftJava/BridgedValues/JavaBoxing.swift:185-191 — 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 · ×5
  • Low cohesion: String (LCOM4 9) Sources/GenerateConfigDocs/ConfigParser.swift:582 — String's methods fall into 9 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 9 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: MySwiftClass (LCOM4 9) Samples/SwiftJavaExtractFFMSampleApp/Sources/MySwiftLibrary/MySwiftClass.swift:15 — MySwiftClass's methods fall into 9 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 9 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: MySwiftClass (LCOM4 5) Sources/ExampleSwiftLibrary/MySwiftLibrary.swift:138 — MySwiftClass'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: MySwiftClass (LCOM4 5) Samples/SwiftAndJavaJarFFMSampleLib/Sources/MySwiftLibrary/MySwiftClass.swift:26 — MySwiftClass'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: JavaTranslator (LCOM4 4) Sources/SwiftJavaToolLib/JavaTranslator.swift:27 — JavaTranslator'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.
D4 · Code Duplication · Edited copy of a member (12 corresponding lines) · ×4
  • Edited copy of a member (12 corresponding lines) Sources/SwiftJavaRuntimeSupport/CollectionBridge.swift:20 — Sources/SwiftJavaRuntimeSupport/CollectionBridge.swift:20-31 | Sources/SwiftJavaRuntimeSupport/CollectionBridge.swift:57-68 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) Sources/JExtractSwiftLib/FFM/CDeclLowering/FFMSwift2JavaGenerator+FunctionLowering.swift:23 — Sources/JExtractSwiftLib/FFM/CDeclLowering/FFMSwift2JavaGenerator+FunctionLowering.swift:23-34 | Sources/JExtractSwiftLib/FFM/CDeclLowering/FFMSwift2JavaGenerator+FunctionLowering.swift:39-51 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) Sources/SwiftJavaRuntimeSupport/CollectionBridge.swift:33 — Sources/SwiftJavaRuntimeSupport/CollectionBridge.swift:33-44 | Sources/SwiftJavaRuntimeSupport/CollectionBridge.swift:70-81 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator+JavaBindingsPrinting.swift:549 — Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator+JavaBindingsPrinting.swift:549-562 | Sources/JExtractSwiftLib/FFM/FFMSwift2JavaGenerator.swift:607-618 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (7 corresponding lines) · ×4
  • Edited copy of a member (7 corresponding lines) Sources/SwiftJava/BridgedValues/JavaBoxing.swift:274 — Sources/SwiftJava/BridgedValues/JavaBoxing.swift:274-280 | Sources/SwiftJava/BridgedValues/JavaBoxing.swift:294-300 — 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/SwiftJava/BridgedValues/JavaBoxing.swift:92 — Sources/SwiftJava/BridgedValues/JavaBoxing.swift:92-98 | Sources/SwiftJava/BridgedValues/JavaBoxing.swift:241-247 — 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/SwiftJava/BridgedValues/JavaBoxing.swift:175 — Sources/SwiftJava/BridgedValues/JavaBoxing.swift:175-181 | Sources/SwiftJava/BridgedValues/JavaBoxing.swift:195-201 — 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/SwiftJava/BridgedValues/SwiftDictionaryMap+JNI.swift:68 — Sources/SwiftJava/BridgedValues/SwiftDictionaryMap+JNI.swift:68-74 | Sources/SwiftJava/BridgedValues/SwiftSet+JNI.swift:52-58 — 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.
X3 · Exception handling · Swallowed exception (caught, then discarded) · ×4
  • Swallowed exception (caught, then discarded) Sources/SwiftJavaToolLib/JavaHomeSupport.swift:142 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) Sources/SwiftJava/AndroidSupport.swift:128 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) Sources/SwiftJava/BridgedValues/JobjectBridge.swift:41 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) Plugins/PluginsShared/PluginUtils.swift:126 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
D15 · Churn × Complexity Hotspots · Hotspot · ×3
  • Hotspot: Sources/JExtractSwiftLib/KnownFunctionalInterfaces.swift Sources/JExtractSwiftLib/KnownFunctionalInterfaces.swift:228 — Sources/JExtractSwiftLib/KnownFunctionalInterfaces.swift changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 41 in KnownJavaFunctionalInterface.find at line 228. 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-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 17:11:37 +09:00' --until='2026-11-10 17:11:37 +09:00' --full-history --no-merges -- Sources/JExtractSwiftLib/KnownFunctionalInterfaces.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/JExtractSwiftLib/JNI/JNISwift2JavaGenerator+SwiftThunkPrinting.swift Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator+SwiftThunkPrinting.swift:600 — Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator+SwiftThunkPrinting.swift changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 34 in JNISwift2JavaGenerator.printFunctionDowncall at line 600. 1 of those changes was a fix/bug commit, and the other 5 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-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 17:11:37 +09:00' --until='2026-11-10 17:11:37 +09:00' --full-history --no-merges -- Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator+SwiftThunkPrinting.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/JExtractSwiftLib/JNI/JNISwift2JavaGenerator+JavaBindingsPrinting.swift Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator+JavaBindingsPrinting.swift:313 — Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator+JavaBindingsPrinting.swift changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in JNISwift2JavaGenerator.printConcreteType at line 313. 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-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 17:11:37 +09:00' --until='2026-11-10 17:11:37 +09:00' --full-history --no-merges -- Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator+JavaBindingsPrinting.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.
D3 · God Classes · TooManyMethods · ×3
  • TooManyMethods: JNISwift2JavaGenerator Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator.swift:27 — TooManyMethods — 89 methods, declared across 7 files: JNI/JNISwift2JavaGenerator+SwiftThunkPrinting.swift (37), JNI/JNISwift2JavaGenerator+JavaBindingsPrinting.swift (36), JNI/JNISwift2JavaGenerator.swift (8), JNI/JNISwift2JavaGenerator+EscapingClosureWrapJava.swift (3), +3 more file(s). The bar is 30 methods; this is 59 over it, 2.97× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: FFMSwift2JavaGenerator Sources/JExtractSwiftLib/FFM/FFMSwift2JavaGenerator.swift:24 — TooManyMethods — 45 methods, declared across 6 files: FFM/FFMSwift2JavaGenerator.swift (20), FFM/FFMSwift2JavaGenerator+JavaBindingsPrinting.swift (14), FFM/FFMSwift2JavaGenerator+SwiftThunkPrinting.swift (6), CDeclLowering/FFMSwift2JavaGenerator+FunctionLowering.swift (3), +2 more file(s). The bar is 30 methods; this is 15 over it, 1.50× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: JavaClassTranslator Sources/SwiftJavaToolLib/JavaClassTranslator.swift:24 — TooManyMethods — 32 methods. The bar is 30 methods; this is 2 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D35 · Change Coupling · Change coupling · ×3
  • Change coupling: CRepresentation.swift ↔ FFMSwift2JavaGenerator+FunctionLowering.swift Sources/JExtractSwiftLib/FFM/CDeclLowering/CRepresentation.swift:1 — `Sources/JExtractSwiftLib/FFM/CDeclLowering/CRepresentation.swift` and `Sources/JExtractSwiftLib/FFM/CDeclLowering/FFMSwift2JavaGenerator+FunctionLowering.swift` change together 91% of the time (10 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 10 shared commits counted here, the most recent 3 are `bead7ace` SwiftExtract: support InlineArray<N, T> / [N of T]; `3228cce9` Native Swift Set support for jextract/jni (#622); `5ff12b1f` jextract/ffm: Support [UInt8] parameters (#477) — run `git show` on any of them.
  • Change coupling: CRepresentation.swift ↔ FFMSwift2JavaGenerator+JavaTranslation.swift Sources/JExtractSwiftLib/FFM/CDeclLowering/CRepresentation.swift:1 — `Sources/JExtractSwiftLib/FFM/CDeclLowering/CRepresentation.swift` and `Sources/JExtractSwiftLib/FFM/FFMSwift2JavaGenerator+JavaTranslation.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 `bead7ace` SwiftExtract: support InlineArray<N, T> / [N of T]; `3228cce9` Native Swift Set support for jextract/jni (#622); `5ff12b1f` jextract/ffm: Support [UInt8] parameters (#477) — run `git show` on any of them.
  • Change coupling: SwiftSyntax+Extensions.swift ↔ Configuration.swift Sources/JExtractSwiftLib/Convenience/SwiftSyntax+Extensions.swift:1 — `Sources/JExtractSwiftLib/Convenience/SwiftSyntax+Extensions.swift` and `Sources/SwiftJavaConfigurationShared/Configuration.swift` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in 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 5 shared commits counted here, the most recent 3 are `2e55cc1a` jextract: Evaluate IfConfigDecl and add --static-build-config option …; `2941b9eb` Revert "jextract: Evaluate IfConfigDecl and add --static-build-config…; `e0f3745a` jextract: Evaluate IfConfigDecl and add --static-build-config option … — run `git show` on any of them.
D4 · Code Duplication · Edited copy of a member (16 corresponding lines) · ×3
  • Edited copy of a member (16 corresponding lines) Sources/SwiftJavaRuntimeSupport/JextractedTypeBridge.swift:70 — Sources/SwiftJavaRuntimeSupport/JextractedTypeBridge.swift:70-86 | Sources/SwiftJavaRuntimeSupport/_JNISwiftErrors.swift:54-69 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) SwiftKitCore/src/main/java/org/swift/swiftkit/core/SwiftLibraries.java:46 — SwiftKitCore/src/main/java/org/swift/swiftkit/core/SwiftLibraries.java:46-62 | SwiftKitFFM/src/main/java/org/swift/swiftkit/ffm/SwiftRuntime.java:38-53 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) Sources/SwiftJavaTool/SwiftJavaBaseAsyncParsableCommand.swift:123 — Sources/SwiftJavaTool/SwiftJavaBaseAsyncParsableCommand.swift:123-138 | Sources/SwiftJavaTool/SwiftJavaBaseAsyncParsableCommand.swift:145-163 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (10 lines × 2) · ×3
  • Duplicated block (10 lines × 2) Sources/JExtractSwiftLib/FFM/FFMSwift2JavaGenerator+JavaBindingsPrinting.swift:459 — Sources/JExtractSwiftLib/FFM/FFMSwift2JavaGenerator+JavaBindingsPrinting.swift:459-468 | Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator+JavaBindingsPrinting.swift:1003-1012 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (10 lines × 2) Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator+SwiftThunkPrinting.swift:891 — Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator+SwiftThunkPrinting.swift:891-900 | Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator+SwiftThunkPrinting.swift:1166-1175 — 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 (10 lines × 2) Sources/SwiftJavaRuntimeSupport/CollectionBridge.swift:33 — Sources/SwiftJavaRuntimeSupport/CollectionBridge.swift:33-42 | Sources/SwiftJavaRuntimeSupport/CollectionBridge.swift:70-79 — 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/SwiftJavaRuntimeSupport/CollectionBridge.swift:33` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×3
  • Duplicated block (6 lines × 2) Sources/JExtractSwiftLib/FFM/FFMSwift2JavaGenerator+SwiftThunkPrinting.swift:90 — Sources/JExtractSwiftLib/FFM/FFMSwift2JavaGenerator+SwiftThunkPrinting.swift:90-95 | Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator+SwiftThunkPrinting.swift:95-100 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (6 lines × 2) SwiftKitCore/src/main/java/org/swift/swiftkit/core/CallTraces.java:25 — SwiftKitCore/src/main/java/org/swift/swiftkit/core/CallTraces.java:25-30 | SwiftKitCore/src/main/java/org/swift/swiftkit/core/CallTraces.java:40-45 — 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 `SwiftKitCore/src/main/java/org/swift/swiftkit/core/CallTraces.java:25` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `SwiftKitCore/src/main/java/org/swift/swiftkit/core/CallTraces.java:31` calls `getStackTrace`, `getClassName` and `SwiftKitCore/src/main/java/org/swift/swiftkit/core/CallTraces.java:46` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (6 lines × 2) Samples/SwiftJavaExtractFFMSampleApp/Sources/MySwiftLibrary/MySwiftStruct.swift:22 — Samples/SwiftJavaExtractFFMSampleApp/Sources/MySwiftLibrary/MySwiftStruct.swift:22-27 | Samples/SwiftJavaExtractJNISampleApp/Sources/MySwiftLibrary/MySwiftStruct.swift:21-26 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Note first that the copies are not typed on the same thing: the declarations holding them bind `cap` to `Int` in one and `Int64` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D12 · Dependency Hygiene · Floating branch dependency · ×2
  • Floating branch dependency: swift-java-jni-core — Dependency `swift-java-jni-core` is declared in Package.swift against branch `main` — the declaration pins no immutable point, so `swift package update` moves this dependency to whatever that branch holds at the time, which is code nobody reviewed. Pin it to a version requirement (`from:`, `.upToNextMajor(from:)`, `exact:`) or to a `revision:` commit SHA.
  • Floating branch dependency: swift-binding-generator-core — Dependency `swift-binding-generator-core` is declared in Package.swift against branch `main` — the declaration pins no immutable point, so `swift package update` moves this dependency to whatever that branch holds at the time, which is code nobody reviewed. Pin it to a version requirement (`from:`, `.upToNextMajor(from:)`, `exact:`) or to a `revision:` commit SHA.
D4 · Code Duplication · Edited copy of a member (17 corresponding lines) · ×2
  • Edited copy of a member (17 corresponding lines) Sources/JExtractSwiftLib/ExtractedDecls+JavaNaming.swift:57 — Sources/JExtractSwiftLib/ExtractedDecls+JavaNaming.swift:57-74 | Sources/JExtractSwiftLib/ExtractedDecls+JavaNaming.swift:83-99 — 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.
  • Edited copy of a member (17 corresponding lines) Sources/SwiftJavaToolLib/JavaClassTranslator.swift:1328 — Sources/SwiftJavaToolLib/JavaClassTranslator.swift:1328-1346 | Sources/SwiftJavaToolLib/JavaClassTranslator.swift:1349-1365 — 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 copies of one member (8 members, 3+ corresponding lines) · ×2
  • Edited copies of one member (8 members, 3+ corresponding lines) SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple17.java:107 — SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple17.java:107-109 | SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple18.java:111-113 | SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple19.java:115-117 | SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple20.java:119-121 | SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple21.java:123-125 | SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple22.java:127-129 | SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple23.java:131-133 | SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple24.java:135-137 — These 8 members are one piece of code written 8 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 8 times and the copies will drift further apart.
  • Edited copies of one member (8 members, 3+ corresponding lines) SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple17.java:102 — SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple17.java:102-104 | SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple18.java:106-108 | SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple19.java:110-112 | SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple20.java:114-116 | SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple21.java:118-120 | SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple22.java:122-124 | SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple23.java:126-128 | SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple24.java:130-132 — These 8 members are one piece of code written 8 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 8 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×2
  • Duplicated block (12 lines × 2) Sources/JExtractSwiftLib/FFM/FFMSwift2JavaGenerator.swift:93 — Sources/JExtractSwiftLib/FFM/FFMSwift2JavaGenerator.swift:93-104 | Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator.swift:103-114 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/JExtractSwiftLib/FFM/FFMSwift2JavaGenerator.swift:93` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (12 lines × 2) Samples/SwiftJavaExtractFFMSampleApp/Sources/MySwiftLibrary/UnsafeRawBufferPointer.swift:20 — Samples/SwiftJavaExtractFFMSampleApp/Sources/MySwiftLibrary/UnsafeRawBufferPointer.swift:20-31 | Samples/SwiftJavaExtractJNISampleApp/Sources/MySwiftLibrary/UnsafeRawBufferPointer.swift:19-30 — before extracting anything, compare `Samples/SwiftJavaExtractFFMSampleApp/Sources/MySwiftLibrary/UnsafeRawBufferPointer.swift` and `Samples/SwiftJavaExtractJNISampleApp/Sources/MySwiftLibrary/UnsafeRawBufferPointer.swift` as WHOLE FILES: 88% 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 1 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 (11 lines × 2) · ×2
  • Duplicated block (11 lines × 2) Sources/JExtractSwiftLib/FFM/CDeclLowering/FFMSwift2JavaGenerator+FunctionLowering.swift:284 — Sources/JExtractSwiftLib/FFM/CDeclLowering/FFMSwift2JavaGenerator+FunctionLowering.swift:284-294 | Sources/JExtractSwiftLib/FFM/CDeclLowering/FFMSwift2JavaGenerator+FunctionLowering.swift:629-639 — 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/JExtractSwiftLib/FFM/CDeclLowering/FFMSwift2JavaGenerator+FunctionLowering.swift:284` 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 (11 lines × 2) Sources/JExtractSwiftLib/FFM/FFMSwift2JavaGenerator+SwiftThunkPrinting.swift:77 — Sources/JExtractSwiftLib/FFM/FFMSwift2JavaGenerator+SwiftThunkPrinting.swift:77-87 | Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator+SwiftThunkPrinting.swift:82-92 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/JExtractSwiftLib/FFM/FFMSwift2JavaGenerator+SwiftThunkPrinting.swift:77` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (13 lines × 2) · ×2
  • Duplicated block (13 lines × 2) Sources/JavaStdlib/JavaLangReflect/HasJavaModifiers.swift:23 — Sources/JavaStdlib/JavaLangReflect/HasJavaModifiers.swift:23-42 | Sources/JavaStdlib/JavaLangReflect/Method+Utilities.swift:18-30 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (13 lines × 2) SwiftKitCore/src/main/java/org/swift/swiftkit/core/SwiftLibraries.java:93 — SwiftKitCore/src/main/java/org/swift/swiftkit/core/SwiftLibraries.java:93-105 | SwiftKitCore/src/main/java/org/swift/swiftkit/core/SwiftLibraries.java:108-120 — 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 `SwiftKitCore/src/main/java/org/swift/swiftkit/core/SwiftLibraries.java:93` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×2
  • Duplicated block (5 lines × 2) Sources/SwiftJava/BridgedValues/SwiftDictionaryMap+JNI.swift:62 — Sources/SwiftJava/BridgedValues/SwiftDictionaryMap+JNI.swift:62-66 | Sources/SwiftJava/BridgedValues/SwiftSet+JNI.swift:46-50 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (5 lines × 2) Sources/JExtractSwiftLib/FFM/FFMSwift2JavaGenerator+JavaBindingsPrinting.swift:523 — Sources/JExtractSwiftLib/FFM/FFMSwift2JavaGenerator+JavaBindingsPrinting.swift:523-527 | Sources/JExtractSwiftLib/FFM/FFMSwift2JavaGenerator+JavaBindingsPrinting.swift:529-533 — 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.
D1 · Cyclomatic Complexity · KnownJavaFunctionalInterface.find (cyclomatic 41) · ×1
  • KnownJavaFunctionalInterface.find (cyclomatic 41) Sources/JExtractSwiftLib/KnownFunctionalInterfaces.swift:228 — KnownJavaFunctionalInterface.find has cyclomatic complexity 41 (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 · JNISwift2JavaGenerator.printFunctionDowncall (cyclomatic 34) · ×1
  • JNISwift2JavaGenerator.printFunctionDowncall (cyclomatic 34) Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator+SwiftThunkPrinting.swift:600 — JNISwift2JavaGenerator.printFunctionDowncall has cyclomatic complexity 34 (threshold 15). Of this number, 33 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
D1 · Cyclomatic Complexity · JavaImplementationMacro.expansion (cyclomatic 34) · ×1
  • JavaImplementationMacro.expansion (cyclomatic 34) Sources/SwiftJavaMacros/ImplementsJavaMacro.swift:51 — JavaImplementationMacro.expansion has cyclomatic complexity 34 (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 · ConversionStep.asExprSyntax (cyclomatic 30) · ×1
  • ConversionStep.asExprSyntax (cyclomatic 30) Sources/JExtractSwiftLib/FFM/ConversionStep.swift:107 — ConversionStep.asExprSyntax has cyclomatic complexity 30 (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 · LoweredFunctionSignature.cdeclThunk (cyclomatic 30) · ×1
  • LoweredFunctionSignature.cdeclThunk (cyclomatic 30) Sources/JExtractSwiftLib/FFM/CDeclLowering/FFMSwift2JavaGenerator+FunctionLowering.swift:981 — LoweredFunctionSignature.cdeclThunk has cyclomatic complexity 30 (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 · JavaClassTranslator.init (cyclomatic 28) · ×1
  • JavaClassTranslator.init (cyclomatic 28) Sources/SwiftJavaToolLib/JavaClassTranslator.swift:116 — JavaClassTranslator.init has cyclomatic complexity 28 (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 · JavaTranslator.getSwiftTypeNameAsString (cyclomatic 28) · ×1
  • JavaTranslator.getSwiftTypeNameAsString (cyclomatic 28) Sources/SwiftJavaToolLib/JavaTranslator.swift:155 — JavaTranslator.getSwiftTypeNameAsString has cyclomatic complexity 28 (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 · CdeclLowering.lowerParameter (cyclomatic 27) · ×1
  • CdeclLowering.lowerParameter (cyclomatic 27) Sources/JExtractSwiftLib/FFM/CDeclLowering/FFMSwift2JavaGenerator+FunctionLowering.swift:192 — CdeclLowering.lowerParameter has cyclomatic complexity 27 (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 · JavaConversionStep.render (cyclomatic 27) · ×1
  • JavaConversionStep.render (cyclomatic 27) Sources/JExtractSwiftLib/FFM/FFMSwift2JavaGenerator+JavaBindingsPrinting.swift:729 — JavaConversionStep.render 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 · JavaMethodMacro.expansion (cyclomatic 27) · ×1
  • JavaMethodMacro.expansion (cyclomatic 27) Sources/SwiftJavaMacros/JavaMethodMacro.swift:23 — JavaMethodMacro.expansion has cyclomatic complexity 27 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · JavaClassMacro.expansion (cyclomatic 26) · ×1
  • JavaClassMacro.expansion (cyclomatic 26) Sources/SwiftJavaMacros/JavaClassMacro.swift:23 — JavaClassMacro.expansion has cyclomatic complexity 26 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · JavaClassTranslator.renderMethod (cyclomatic 26) · ×1
  • JavaClassTranslator.renderMethod (cyclomatic 26) Sources/SwiftJavaToolLib/JavaClassTranslator.swift:1039 — JavaClassTranslator.renderMethod has cyclomatic complexity 26 (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 · CType.printBefore (cyclomatic 25) · ×1
  • CType.printBefore (cyclomatic 25) Sources/JExtractSwiftLib/CTypes/CType.swift:77 — CType.printBefore has cyclomatic complexity 25 (threshold 15). Of this number, 24 points are the body's own statements and 1 belongs to one function item inside it that branches. 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 · FFMSwift2JavaGenerator.printDowncall (cyclomatic 24) · ×1
  • FFMSwift2JavaGenerator.printDowncall (cyclomatic 24) Sources/JExtractSwiftLib/FFM/FFMSwift2JavaGenerator+JavaBindingsPrinting.swift:443 — FFMSwift2JavaGenerator.printDowncall has cyclomatic complexity 24 (threshold 15). Of this number, 23 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · MarkdownRenderer.renderField (cyclomatic 22) · ×1
  • MarkdownRenderer.renderField (cyclomatic 22) Sources/GenerateConfigDocs/MarkdownRenderer.swift:51 — MarkdownRenderer.renderField 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 · WrapJavaCommand.generateWrappers (cyclomatic 22) · ×1
  • WrapJavaCommand.generateWrappers (cyclomatic 22) Sources/SwiftJavaTool/Commands/WrapJavaCommand.swift:144 — WrapJavaCommand.generateWrappers 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 · SwiftToJava.run (cyclomatic 21) · ×1
  • SwiftToJava.run (cyclomatic 21) Sources/JExtractSwiftLib/Swift2Java.swift:33 — SwiftToJava.run has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · CdeclLowering.lowerResult (cyclomatic 21) · ×1
  • CdeclLowering.lowerResult (cyclomatic 21) Sources/JExtractSwiftLib/FFM/CDeclLowering/FFMSwift2JavaGenerator+FunctionLowering.swift:687 — CdeclLowering.lowerResult has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · JavaClassTranslator.swiftAvailableAttributes (cyclomatic 21) · ×1
  • JavaClassTranslator.swiftAvailableAttributes (cyclomatic 21) Sources/SwiftJavaToolLib/JavaClassTranslator.swift:814 — JavaClassTranslator.swiftAvailableAttributes has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · SwiftDocumentationParser.parse (cyclomatic 20) · ×1
  • SwiftDocumentationParser.parse (cyclomatic 20) Sources/JExtractSwiftLib/SwiftDocumentationParsing.swift:70 — SwiftDocumentationParser.parse 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 · ConfigParser.swift.docLines (cyclomatic 19) · ×1
  • ConfigParser.swift.docLines (cyclomatic 19) Sources/GenerateConfigDocs/ConfigParser.swift:96 — ConfigParser.swift.docLines 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 · JavaFieldMacro.expansion (cyclomatic 19) · ×1
  • JavaFieldMacro.expansion (cyclomatic 19) Sources/SwiftJavaMacros/JavaFieldMacro.swift:22 — JavaFieldMacro.expansion has cyclomatic complexity 19 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · ConfigurationBody.parse (cyclomatic 18) · ×1
  • ConfigurationBody.parse (cyclomatic 18) Sources/GenerateConfigDocs/ConfigParser.swift:421 — ConfigurationBody.parse 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 · TopLevelVisitor.defaultCaseName (cyclomatic 17) · ×1
  • TopLevelVisitor.defaultCaseName (cyclomatic 17) Sources/GenerateConfigDocs/ConfigParser.swift:374 — TopLevelVisitor.defaultCaseName has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · MarkdownRenderer.renderTypeSchemaLines (cyclomatic 17) · ×1
  • MarkdownRenderer.renderTypeSchemaLines (cyclomatic 17) Sources/GenerateConfigDocs/MarkdownRenderer.swift:118 — MarkdownRenderer.renderTypeSchemaLines has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · JNISwift2JavaGenerator.printConcreteType (cyclomatic 17) · ×1
  • JNISwift2JavaGenerator.printConcreteType (cyclomatic 17) Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator+JavaBindingsPrinting.swift:313 — JNISwift2JavaGenerator.printConcreteType has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · Type.isEqualToOrSubtypeOf (cyclomatic 17) · ×1
  • Type.isEqualToOrSubtypeOf (cyclomatic 17) Sources/SwiftJavaToolLib/JavaType+Equality.swift:98 — Type.isEqualToOrSubtypeOf has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · CdeclLowering.lowerOptionalParameter (cyclomatic 16) · ×1
  • CdeclLowering.lowerOptionalParameter (cyclomatic 16) Sources/JExtractSwiftLib/FFM/CDeclLowering/FFMSwift2JavaGenerator+FunctionLowering.swift:470 — CdeclLowering.lowerOptionalParameter has cyclomatic complexity 16 (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 · JavaClassTranslator.renderPrimaryType (cyclomatic 16) · ×1
  • JavaClassTranslator.renderPrimaryType (cyclomatic 16) Sources/SwiftJavaToolLib/JavaClassTranslator.swift:412 — JavaClassTranslator.renderPrimaryType has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D10 · Test Quality · Skipped test · ×1
  • Skipped test: test_parseRealFile Tests/SwiftJavaToolLibTests/AndroidAPIVersionsParserTests.swift:219 — Skipped — throws XCTSkip
D10 · Test Quality · No assertions · ×1
  • No assertions: parseJSONWithComments Tests/SwiftJavaConfigurationSharedTests/SwiftJavaConfigurationTests.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.
D12 · Dependency Hygiene · No Package.resolved committed (Benchmarks/Package.swift) · ×1
  • No Package.resolved committed (Benchmarks/Package.swift) — Benchmarks/Package.swift declares 1 dependency and no `.library` product, so it is an APPLICATION — but no `Package.resolved` is committed beside it. Nothing records the versions a working build resolved to, so `swift build` re-resolves against whatever each dependency's git host serves today and two builds of this commit are not guaranteed to be the same build. Build once and commit the resulting `Package.resolved`. (A published LIBRARY correctly omits its resolution — SwiftPM ignores a library's `Package.resolved` when the package is consumed — which is why this is asked only of a package that ships no `.library` product.)
D12 · Dependency Hygiene · No Package.resolved committed (Samples/JavaProbablyPrime/Package.swift) · ×1
  • No Package.resolved committed (Samples/JavaProbablyPrime/Package.swift) — Samples/JavaProbablyPrime/Package.swift declares 1 dependency and no `.library` product, so it is an APPLICATION — but no `Package.resolved` is committed beside it. Nothing records the versions a working build resolved to, so `swift build` re-resolves against whatever each dependency's git host serves today and two builds of this commit are not guaranteed to be the same build. Build once and commit the resulting `Package.resolved`. (A published LIBRARY correctly omits its resolution — SwiftPM ignores a library's `Package.resolved` when the package is consumed — which is why this is asked only of a package that ships no `.library` product.)
D2 · Cognitive Complexity · JavaImplementationMacro.expansion (cognitive 53) · ×1
  • JavaImplementationMacro.expansion (cognitive 53) Sources/SwiftJavaMacros/ImplementsJavaMacro.swift:51 — JavaImplementationMacro.expansion has cognitive complexity 53 (threshold 15). Drivers by points: if/else 18 (31 pts), boolean chains 15, ternaries 3 (6 pts), loops 1 (nesting depth added 16). 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 · JavaTranslator.getSwiftTypeNameAsString (cognitive 51) · ×1
  • JavaTranslator.getSwiftTypeNameAsString (cognitive 51) Sources/SwiftJavaToolLib/JavaTranslator.swift:155 — JavaTranslator.getSwiftTypeNameAsString has cognitive complexity 51 (threshold 15). Drivers by points: if/else 21 (43 pts), boolean chains 8 (nesting depth added 22). 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 · JavaClassTranslator.init (cognitive 50) · ×1
  • JavaClassTranslator.init (cognitive 50) Sources/SwiftJavaToolLib/JavaClassTranslator.swift:116 — JavaClassTranslator.init has cognitive complexity 50 (threshold 15). Drivers by points: if/else 16 (32 pts), loops 5 (7 pts), error handling 3 (6 pts), boolean chains 4, ternaries 1 (nesting depth added 21). 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 · MarkdownRenderer.renderTypeSchemaLines (cognitive 49) · ×1
  • MarkdownRenderer.renderTypeSchemaLines (cognitive 49) Sources/GenerateConfigDocs/MarkdownRenderer.swift:118 — MarkdownRenderer.renderTypeSchemaLines has cognitive complexity 49 (threshold 15). Drivers by points: if/else 16 (36 pts), loops 4 (12 pts), boolean chains 1 (nesting depth added 28). 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 · JavaClassTranslator.renderMethod (cognitive 48) · ×1
  • JavaClassTranslator.renderMethod (cognitive 48) Sources/SwiftJavaToolLib/JavaClassTranslator.swift:1039 — JavaClassTranslator.renderMethod has cognitive complexity 48 (threshold 15). Drivers by points: if/else 20 (35 pts), boolean chains 7, ternaries 5 (6 pts) (nesting depth added 16). 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 · JavaMethodMacro.expansion (cognitive 42) · ×1
  • JavaMethodMacro.expansion (cognitive 42) Sources/SwiftJavaMacros/JavaMethodMacro.swift:23 — JavaMethodMacro.expansion has cognitive complexity 42 (threshold 15). Drivers by points: if/else 25 (31 pts), boolean chains 7, ternaries 2, loops 1, match/switch 1 (nesting depth added 6). 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 · KnownJavaFunctionalInterface.find (cognitive 41) · ×1
  • KnownJavaFunctionalInterface.find (cognitive 41) Sources/JExtractSwiftLib/KnownFunctionalInterfaces.swift:228 — KnownJavaFunctionalInterface.find has cognitive complexity 41 (threshold 15). Drivers by points: if/else 17, match/switch 8 (16 pts), boolean chains 8 (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 · ConversionStep.asExprSyntax (cognitive 41) · ×1
  • ConversionStep.asExprSyntax (cognitive 41) Sources/JExtractSwiftLib/FFM/ConversionStep.swift:107 — ConversionStep.asExprSyntax has cognitive complexity 41 (threshold 15). Drivers by points: if/else 15 (30 pts), loops 4 (10 pts), match/switch 1 (nesting depth added 21). 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 · SwiftDocumentationParser.parse (cognitive 40) · ×1
  • SwiftDocumentationParser.parse (cognitive 40) Sources/JExtractSwiftLib/SwiftDocumentationParsing.swift:70 — SwiftDocumentationParser.parse has cognitive complexity 40 (threshold 15). Drivers by points: if/else 11 (26 pts), ternaries 2 (6 pts), boolean chains 3, match/switch 1 (3 pts), loops 2 (nesting depth added 21). 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 · ConfigParser.swift.docLines (cognitive 39) · ×1
  • ConfigParser.swift.docLines (cognitive 39) Sources/GenerateConfigDocs/ConfigParser.swift:96 — ConfigParser.swift.docLines has cognitive complexity 39 (threshold 15). Drivers by points: if/else 11 (33 pts), loops 2 (4 pts), match/switch 1 (2 pts) (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 · FFMSwift2JavaGenerator.printDowncall (cognitive 39) · ×1
  • FFMSwift2JavaGenerator.printDowncall (cognitive 39) Sources/JExtractSwiftLib/FFM/FFMSwift2JavaGenerator+JavaBindingsPrinting.swift:443 — FFMSwift2JavaGenerator.printDowncall has cognitive complexity 39 (threshold 15). Drivers by points: if/else 20 (26 pts), match/switch 2 (6 pts), loops 3 (4 pts), ternaries 1 (2 pts), boolean chains 1 (nesting depth added 12). Of this number, 38 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · WrapJavaCommand.generateWrappers (cognitive 38) · ×1
  • WrapJavaCommand.generateWrappers (cognitive 38) Sources/SwiftJavaTool/Commands/WrapJavaCommand.swift:144 — WrapJavaCommand.generateWrappers has cognitive complexity 38 (threshold 15). Drivers by points: if/else 17 (32 pts), loops 5 (6 pts) (nesting depth added 16). 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 · CdeclLowering.lowerParameter (cognitive 35) · ×1
  • CdeclLowering.lowerParameter (cognitive 35) Sources/JExtractSwiftLib/FFM/CDeclLowering/FFMSwift2JavaGenerator+FunctionLowering.swift:192 — CdeclLowering.lowerParameter has cognitive complexity 35 (threshold 15). Drivers by points: if/else 8 (15 pts), ternaries 4 (14 pts), match/switch 2 (4 pts), loops 1 (2 pts) (nesting depth added 20). 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 · JavaClassTranslator.genericParameterIsUsedInSignature (cognitive 35) · ×1
  • JavaClassTranslator.genericParameterIsUsedInSignature (cognitive 35) Sources/SwiftJavaToolLib/JavaClassTranslator.swift:968 — JavaClassTranslator.genericParameterIsUsedInSignature has cognitive complexity 35 (threshold 15). Drivers by points: if/else 11 (28 pts), loops 3 (7 pts) (nesting depth added 21). 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 · ConfigurationBody.parse (cognitive 33) · ×1
  • ConfigurationBody.parse (cognitive 33) Sources/GenerateConfigDocs/ConfigParser.swift:421 — ConfigurationBody.parse has cognitive complexity 33 (threshold 15). Drivers by points: if/else 12 (27 pts), boolean chains 3, loops 2 (3 pts) (nesting depth added 16). 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 · MarkdownRenderer.renderField (cognitive 32) · ×1
  • MarkdownRenderer.renderField (cognitive 32) Sources/GenerateConfigDocs/MarkdownRenderer.swift:51 — MarkdownRenderer.renderField has cognitive complexity 32 (threshold 15). Drivers by points: if/else 14 (20 pts), boolean chains 8, loops 1 (3 pts), ternaries 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 · JavaClassTranslator.swiftAvailableAttributes (cognitive 32) · ×1
  • JavaClassTranslator.swiftAvailableAttributes (cognitive 32) Sources/SwiftJavaToolLib/JavaClassTranslator.swift:814 — JavaClassTranslator.swiftAvailableAttributes has cognitive complexity 32 (threshold 15). Drivers by points: if/else 13 (24 pts), boolean chains 6, loops 2 (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 · LoweredFunctionSignature.cdeclThunk (cognitive 31) · ×1
  • LoweredFunctionSignature.cdeclThunk (cognitive 31) Sources/JExtractSwiftLib/FFM/CDeclLowering/FFMSwift2JavaGenerator+FunctionLowering.swift:981 — LoweredFunctionSignature.cdeclThunk has cognitive complexity 31 (threshold 15). Drivers by points: ternaries 8 (16 pts), if/else 9 (11 pts), match/switch 3 (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 · JNISwift2JavaGenerator.printFunctionDowncall (cognitive 30) · ×1
  • JNISwift2JavaGenerator.printFunctionDowncall (cognitive 30) Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator+SwiftThunkPrinting.swift:600 — JNISwift2JavaGenerator.printFunctionDowncall has cognitive complexity 30 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 6, loops 3 (4 pts), match/switch 3 (4 pts), ternaries 2 (3 pts) (nesting depth added 6). Of this number, 28 points are the body's own statements and 2 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 · SwiftSymbolTable.printImportedModules (cognitive 30) · ×1
  • SwiftSymbolTable.printImportedModules (cognitive 30) Sources/JExtractSwiftLib/SymbolTable+Printing.swift:19 — SwiftSymbolTable.printImportedModules has cognitive complexity 30 (threshold 15). Drivers by points: if/else 10 (21 pts), loops 4 (8 pts), boolean chains 1 (nesting depth added 15). 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 · CdeclLowering.lowerResult (cognitive 28) · ×1
  • CdeclLowering.lowerResult (cognitive 28) Sources/JExtractSwiftLib/FFM/CDeclLowering/FFMSwift2JavaGenerator+FunctionLowering.swift:687 — CdeclLowering.lowerResult has cognitive complexity 28 (threshold 15). Drivers by points: ternaries 3 (12 pts), if/else 6 (10 pts), match/switch 2 (4 pts), loops 1 (2 pts) (nesting depth added 16). 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 · SwiftToJava.run (cognitive 27) · ×1
  • SwiftToJava.run (cognitive 27) Sources/JExtractSwiftLib/Swift2Java.swift:33 — SwiftToJava.run has cognitive complexity 27 (threshold 15). Drivers by points: if/else 12 (19 pts), loops 4, boolean chains 3, match/switch 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 · JNISwift2JavaGenerator.writeSwiftThunkSources (cognitive 26) · ×1
  • JNISwift2JavaGenerator.writeSwiftThunkSources (cognitive 26) Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator+SwiftThunkPrinting.swift:57 — JNISwift2JavaGenerator.writeSwiftThunkSources has cognitive complexity 26 (threshold 15). Drivers by points: if/else 5 (12 pts), error handling 3 (8 pts), loops 2 (5 pts), boolean chains 1 (nesting depth added 15). 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 · JavaClassMacro.expansion (cognitive 26) · ×1
  • JavaClassMacro.expansion (cognitive 26) Sources/SwiftJavaMacros/JavaClassMacro.swift:23 — JavaClassMacro.expansion has cognitive complexity 26 (threshold 15). Drivers by points: boolean chains 11, if/else 10 (11 pts), ternaries 3, match/switch 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · JavaClassTranslator.renderPrimaryType (cognitive 24) · ×1
  • JavaClassTranslator.renderPrimaryType (cognitive 24) Sources/SwiftJavaToolLib/JavaClassTranslator.swift:412 — JavaClassTranslator.renderPrimaryType has cognitive complexity 24 (threshold 15). Drivers by points: if/else 15 (17 pts), error handling 3, ternaries 2 (3 pts), boolean chains 1 (nesting depth added 3). 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 · _JNIMethodIDCache.init (cognitive 22) · ×1
  • _JNIMethodIDCache.init (cognitive 22) Sources/SwiftJavaRuntimeSupport/_JNIMethodIDCache.swift:60 — _JNIMethodIDCache.init has cognitive complexity 22 (threshold 15). Drivers by points: if/else 16 (22 pts) (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 · FFMSwift2JavaGenerator.writeSwiftThunkSources (cognitive 20) · ×1
  • FFMSwift2JavaGenerator.writeSwiftThunkSources (cognitive 20) Sources/JExtractSwiftLib/FFM/FFMSwift2JavaGenerator+SwiftThunkPrinting.swift:50 — FFMSwift2JavaGenerator.writeSwiftThunkSources has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (9 pts), error handling 3 (7 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 9). 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 · JNISwift2JavaGenerator.printConcreteType (cognitive 20) · ×1
  • JNISwift2JavaGenerator.printConcreteType (cognitive 20) Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator+JavaBindingsPrinting.swift:313 — JNISwift2JavaGenerator.printConcreteType has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 5, loops 4 (nesting depth added 3). 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 · Type.isEqualToOrSubtypeOf (cognitive 20) · ×1
  • Type.isEqualToOrSubtypeOf (cognitive 20) Sources/SwiftJavaToolLib/JavaType+Equality.swift:98 — Type.isEqualToOrSubtypeOf has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 7 (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 · JavaFieldMacro.expansion (cognitive 20) · ×1
  • JavaFieldMacro.expansion (cognitive 20) Sources/SwiftJavaMacros/JavaFieldMacro.swift:22 — JavaFieldMacro.expansion has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 12, if/else 7, ternaries 1. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · CType.printBefore (cognitive 19) · ×1
  • CType.printBefore (cognitive 19) Sources/JExtractSwiftLib/CTypes/CType.swift:77 — CType.printBefore has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (10 pts), match/switch 4 (7 pts), boolean chains 2 (nesting depth added 8). Of this number, 17 points are the body's own statements and 2 belong to one function item inside it that branches. 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 · JNISwift2JavaGenerator.printEnumCaseInterface (cognitive 19) · ×1
  • JNISwift2JavaGenerator.printEnumCaseInterface (cognitive 19) Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator+JavaBindingsPrinting.swift:656 — JNISwift2JavaGenerator.printEnumCaseInterface has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (12 pts), ternaries 2 (5 pts), loops 2 (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 · SwiftLibraries.loadLibraryWithFallbacks (cognitive 19) · ×1
  • SwiftLibraries.loadLibraryWithFallbacks (cognitive 19) SwiftKitCore/src/main/java/org/swift/swiftkit/core/SwiftLibraries.java:88 — SwiftLibraries.loadLibraryWithFallbacks has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (14 pts), error handling 3 (5 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 · TopLevelVisitor.collectEnumMembers (cognitive 18) · ×1
  • TopLevelVisitor.collectEnumMembers (cognitive 18) Sources/GenerateConfigDocs/ConfigParser.swift:298 — TopLevelVisitor.collectEnumMembers has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 2 (4 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 · JNISwift2JavaGenerator.init (cognitive 18) · ×1
  • JNISwift2JavaGenerator.init (cognitive 18) Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator.swift:77 — JNISwift2JavaGenerator.init has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 2, loops 1 (2 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 · TopLevelVisitor.defaultCaseName (cognitive 17) · ×1
  • TopLevelVisitor.defaultCaseName (cognitive 17) Sources/GenerateConfigDocs/ConfigParser.swift:374 — TopLevelVisitor.defaultCaseName has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11, boolean chains 3, loops 1 (2 pts), match/switch 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · JNISwift2JavaGenerator.printJavaBindingWrapperMethod (cognitive 17) · ×1
  • JNISwift2JavaGenerator.printJavaBindingWrapperMethod (cognitive 17) Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator+JavaBindingsPrinting.swift:877 — JNISwift2JavaGenerator.printJavaBindingWrapperMethod has cognitive complexity 17 (threshold 15). Drivers by points: if/else 13 (16 pts), boolean chains 1 (nesting depth added 3). 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 · JNISwift2JavaGenerator.printConcreteTypeThunks (cognitive 17) · ×1
  • JNISwift2JavaGenerator.printConcreteTypeThunks (cognitive 17) Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator+SwiftThunkPrinting.swift:325 — JNISwift2JavaGenerator.printConcreteTypeThunks has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (7 pts), loops 4 (6 pts), boolean chains 4 (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 · TopLevelVisitor.collectStructMembers (cognitive 16) · ×1
  • TopLevelVisitor.collectStructMembers (cognitive 16) Sources/GenerateConfigDocs/ConfigParser.swift:345 — TopLevelVisitor.collectStructMembers has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 1, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ConfigParser.swift.nilCoalescingFallback (cognitive 16) · ×1
  • ConfigParser.swift.nilCoalescingFallback (cognitive 16) Sources/GenerateConfigDocs/ConfigParser.swift:529 — ConfigParser.swift.nilCoalescingFallback has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (9 pts), boolean chains 4, loops 1 (2 pts), match/switch 1 (nesting depth added 3). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · JavaClassTranslator.shouldExtract (cognitive 16) · ×1
  • JavaClassTranslator.shouldExtract (cognitive 16) Sources/SwiftJavaToolLib/JavaClassTranslator.swift:290 — JavaClassTranslator.shouldExtract has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (8 pts), boolean chains 6, loops 1, match/switch 1 (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.
D3 · God Classes · ClassTooLong · ×1
  • ClassTooLong: CdeclLowering Sources/JExtractSwiftLib/FFM/CDeclLowering/FFMSwift2JavaGenerator+FunctionLowering.swift:81 — ClassTooLong — 509 significant lines (blank, comment-only and punctuation-only lines excluded), 10 methods. The bar is 400 significant lines; this is 109 over it, 1.27× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D35 · Change Coupling · Change coupling clique · ×1
  • Change coupling clique: MySwiftLibrary.swift, JavaType+JDK.swift, KnownFunctionalInterfaces.swift Sources/ExampleSwiftLibrary/MySwiftLibrary.swift — 3 files — `Sources/ExampleSwiftLibrary/MySwiftLibrary.swift`, `Sources/JExtractSwiftLib/JavaTypes/JavaType+JDK.swift`, `Sources/JExtractSwiftLib/KnownFunctionalInterfaces.swift` — all change together with no explicit dependency: a fully-connected co-change clique, not 3 separate couplings. They share one concern (thin parallel siblings over a common abstraction), so extract the shared part into ONE unit and the whole clique's coupling clears at once — you do not need to break each pair individually.
D4 · Code Duplication · Members sharing a duplicated core (15 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (15 members, 50+ identical tokens) SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple10.java:43 — SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple10.java:43-54 | SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple11.java:45-57 | SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple12.java:47-60 | SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple13.java:49-63 | SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple14.java:51-66 | SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple15.java:53-69 | SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple16.java:55-72 | SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple17.java:57-75 | SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple18.java:59-78 | SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple19.java:61-81 | SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple20.java:63-84 | SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple21.java:65-87 | SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple22.java:67-90 | SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple23.java:69-93 | SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple24.java:71-96 — These 15 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 15 times. 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. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 15 times.
D4 · Code Duplication · Edited copy of a member (77 corresponding lines) · ×1
  • Edited copy of a member (77 corresponding lines) Sources/JExtractSwiftLib/FFM/FFMSwift2JavaGenerator+SwiftThunkPrinting.swift:50 — Sources/JExtractSwiftLib/FFM/FFMSwift2JavaGenerator+SwiftThunkPrinting.swift:50-134 | Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator+SwiftThunkPrinting.swift:57-133 — These two members are one piece of code written twice and then edited apart: 77 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 (8 members, 22+ corresponding lines) · ×1
  • Edited copies of one member (8 members, 22+ corresponding lines) SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple17.java:78 — SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple17.java:78-99 | SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple18.java:81-103 | SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple19.java:84-107 | SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple20.java:87-111 | SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple21.java:90-115 | SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple22.java:93-119 | SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple23.java:96-123 | SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple24.java:99-127 — These 8 members are one piece of code written 8 times and then edited apart: every two of them correspond over at least 22 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 8 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (54 corresponding lines) · ×1
  • Edited copy of a member (54 corresponding lines) Sources/JExtractSwiftLib/FFM/FFMSwift2JavaGenerator.swift:71 — Sources/JExtractSwiftLib/FFM/FFMSwift2JavaGenerator.swift:71-124 | Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator.swift:77-147 — These two members are one piece of code written twice and then edited apart: 54 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 (31 corresponding lines) · ×1
  • Edited copy of a member (31 corresponding lines) Sources/JExtractSwiftLib/FFM/FFMSwift2JavaGenerator+JavaTranslation.swift:1036 — Sources/JExtractSwiftLib/FFM/FFMSwift2JavaGenerator+JavaTranslation.swift:1036-1072 | Sources/JExtractSwiftLib/FFM/FFMSwift2JavaGenerator+JavaTranslation.swift:1075-1105 — These two members are one piece of code written twice and then edited apart: 31 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 (27 corresponding lines) · ×1
  • Edited copy of a member (27 corresponding lines) Sources/JExtractSwiftLib/JNI/JNIJavaTypeTranslator.swift:63 — Sources/JExtractSwiftLib/JNI/JNIJavaTypeTranslator.swift:63-89 | Sources/JExtractSwiftLib/JNI/JNIJavaTypeTranslator.swift:91-117 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (30 corresponding lines) · ×1
  • Edited copy of a member (30 corresponding lines) Sources/SwiftJava/JavaObject+MethodCalls.swift:331 — Sources/SwiftJava/JavaObject+MethodCalls.swift:331-362 | Sources/SwiftJava/JavaObject+MethodCalls.swift:366-395 — These two members are one piece of code written twice and then edited apart: 30 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, 15+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 15+ corresponding lines) Sources/SwiftJava/SwiftObjects.swift:25 — Sources/SwiftJava/SwiftObjects.swift:25-42 | Sources/SwiftJava/SwiftObjects.swift:44-58 | Sources/SwiftJava/SwiftObjects.swift:60-74 | Sources/SwiftJava/SwiftObjects.swift:76-91 | Sources/SwiftJava/SwiftObjects.swift:142-160 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 15 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 (22 corresponding lines) · ×1
  • Edited copy of a member (22 corresponding lines) Sources/SwiftJava/JavaObject+MethodCalls.swift:100 — Sources/SwiftJava/JavaObject+MethodCalls.swift:100-122 | Sources/SwiftJava/JavaObject+MethodCalls.swift:125-146 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (23 corresponding lines) · ×1
  • Edited copy of a member (23 corresponding lines) Sources/JExtractSwiftLib/FFM/FFMSwift2JavaGenerator+SwiftThunkPrinting.swift:26 — Sources/JExtractSwiftLib/FFM/FFMSwift2JavaGenerator+SwiftThunkPrinting.swift:26-48 | Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator+SwiftThunkPrinting.swift:33-55 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 10+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 10+ corresponding lines) Sources/SwiftJava/BridgedValues/JavaBoxing.swift:367 — Sources/SwiftJava/BridgedValues/JavaBoxing.swift:367-376 | Sources/SwiftJava/BridgedValues/JavaBoxing.swift:378-387 | Sources/SwiftJava/BridgedValues/JavaBoxing.swift:430-439 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (14 corresponding lines) · ×1
  • Edited copy of a member (14 corresponding lines) Sources/GenerateConfigDocs/ConfigParser.swift:254 — Sources/GenerateConfigDocs/ConfigParser.swift:254-268 | Sources/GenerateConfigDocs/ConfigParser.swift:270-283 — 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 copy of a member (11 corresponding lines) · ×1
  • Edited copy of a member (11 corresponding lines) Sources/SwiftJavaToolLib/AndroidAPIVersionSupport/AndroidAPIVersionsParser.swift:105 — Sources/SwiftJavaToolLib/AndroidAPIVersionSupport/AndroidAPIVersionsParser.swift:105-115 | Sources/SwiftJavaToolLib/AndroidAPIVersionSupport/AndroidAPIVersionsParser.swift:117-127 — 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 (19 corresponding lines) · ×1
  • Edited copy of a member (19 corresponding lines) Sources/JExtractSwiftLib/TranslatedDocumentation.swift:21 — Sources/JExtractSwiftLib/TranslatedDocumentation.swift:21-39 | Sources/JExtractSwiftLib/TranslatedDocumentation.swift:41-59 — 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 (4 members, 7+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 7+ corresponding lines) Sources/SwiftJava/BridgedValues/JavaBoxing.swift:72 — Sources/SwiftJava/BridgedValues/JavaBoxing.swift:72-78 | Sources/SwiftJava/BridgedValues/JavaBoxing.swift:261-267 | Sources/SwiftJava/BridgedValues/JavaBoxing.swift:284-290 | Sources/SwiftJava/BridgedValues/JavaBoxing.swift:304-310 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (52 corresponding lines) · ×1
  • Edited copy of a member (52 corresponding lines) Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator+JavaBindingsPrinting.swift:1067 — Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator+JavaBindingsPrinting.swift:1067-1118 | Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator+JavaBindingsPrinting.swift:1120-1178 — These two members are one piece of code written twice and then edited apart: 52 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 (10 corresponding lines) · ×1
  • Edited copy of a member (10 corresponding lines) SwiftKitCore/src/main/java/org/swift/swiftkit/core/CallTraces.java:24 — SwiftKitCore/src/main/java/org/swift/swiftkit/core/CallTraces.java:24-37 | SwiftKitCore/src/main/java/org/swift/swiftkit/core/CallTraces.java:39-48 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 9+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 9+ corresponding lines) Sources/CodePrinting/CodePrinter+Java.swift:21 — Sources/CodePrinting/CodePrinter+Java.swift:21-29 | Sources/CodePrinting/CodePrinter+Swift.swift:34-42 | Sources/CodePrinting/CodePrinter.swift:99-111 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 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 (8 corresponding lines) · ×1
  • Edited copy of a member (8 corresponding lines) Sources/SwiftJava/Optional+JavaObject.swift:92 — Sources/SwiftJava/Optional+JavaObject.swift:92-102 | Sources/SwiftJava/Optional+JavaObject.swift:104-111 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 4+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 4+ corresponding lines) Samples/SwiftAndJavaJarFFMSampleLib/Sources/MySwiftLibrary/MySwiftLibrary.swift:129 — Samples/SwiftAndJavaJarFFMSampleLib/Sources/MySwiftLibrary/MySwiftLibrary.swift:129-132 | Samples/SwiftJavaExtractFFMSampleApp/Sources/MySwiftLibrary/MySwiftLibrary.swift:251-254 | Samples/SwiftJavaExtractJNISampleApp/Sources/MySwiftLibrary/MySwiftLibrary.swift:87-90 | Sources/ExampleSwiftLibrary/MySwiftLibrary.swift:190-193 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (9 corresponding lines) · ×1
  • Edited copy of a member (9 corresponding lines) Sources/SwiftJava/BridgedValues/JavaValue+Dictionary.swift:23 — Sources/SwiftJava/BridgedValues/JavaValue+Dictionary.swift:23-32 | Sources/SwiftJava/BridgedValues/JavaValue+Set.swift:23-31 — 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 copies of one member (4 members, 5+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 5+ corresponding lines) Sources/SwiftJava/BridgedValues/SwiftDictionaryMap+JNI.swift:34 — Sources/SwiftJava/BridgedValues/SwiftDictionaryMap+JNI.swift:34-42 | Sources/SwiftJava/BridgedValues/SwiftDictionaryMap+JNI.swift:50-54 | Sources/SwiftJava/BridgedValues/SwiftDictionaryMap+JNI.swift:56-60 | Sources/SwiftJava/BridgedValues/SwiftSet+JNI.swift:40-44 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 5 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (5 corresponding lines) · ×1
  • Edited copy of a member (5 corresponding lines) Sources/SwiftJava/BridgedValues/SwiftDictionaryMap+JNI.swift:44 — Sources/SwiftJava/BridgedValues/SwiftDictionaryMap+JNI.swift:44-48 | Sources/SwiftJava/BridgedValues/SwiftSet+JNI.swift:34-38 — These two members are one piece of code written twice and then edited apart: 5 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 (6 corresponding lines) · ×1
  • Edited copy of a member (6 corresponding lines) Sources/JExtractSwiftLib/FFM/FFMSwift2JavaGenerator.swift:386 — Sources/JExtractSwiftLib/FFM/FFMSwift2JavaGenerator.swift:386-391 | Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator+JavaBindingsPrinting.swift:583-588 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 6+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 6+ corresponding lines) Sources/SwiftJava/BridgedValues/JobjectBridge.swift:58 — Sources/SwiftJava/BridgedValues/JobjectBridge.swift:58-63 | Sources/SwiftJavaRuntimeSupport/CollectionBridge.swift:46-51 | Sources/SwiftJavaRuntimeSupport/JextractedTypeBridge.swift:59-64 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (19 lines × 2) · ×1
  • Duplicated block (19 lines × 2) Sources/JExtractSwiftLib/JNI/JNIJavaTypeTranslator.swift:71 — Sources/JExtractSwiftLib/JNI/JNIJavaTypeTranslator.swift:71-89 | Sources/JExtractSwiftLib/JNI/JNIJavaTypeTranslator.swift:99-117 — 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/JExtractSwiftLib/JNI/JNIJavaTypeTranslator.swift:71` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (18 lines × 2) · ×1
  • Duplicated block (18 lines × 2) Sources/JExtractSwiftLib/FFM/FFMSwift2JavaGenerator.swift:106 — Sources/JExtractSwiftLib/FFM/FFMSwift2JavaGenerator.swift:106-123 | Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator.swift:116-133 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/JExtractSwiftLib/FFM/FFMSwift2JavaGenerator.swift:106` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (13–14 lines × 3) · ×1
  • Duplicated block (13–14 lines × 3) Sources/JExtractSwiftLib/JNI/JNIJavaTypeTranslator.swift:46 — Sources/JExtractSwiftLib/JNI/JNIJavaTypeTranslator.swift:46-58 | Sources/JExtractSwiftLib/JNI/JNIJavaTypeTranslator.swift:73-86 | Sources/JExtractSwiftLib/JNI/JNIJavaTypeTranslator.swift:101-114 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/JExtractSwiftLib/JNI/JNIJavaTypeTranslator.swift:46` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (13–14 lines × 2) · ×1
  • Duplicated block (13–14 lines × 2) Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator+JavaBindingsPrinting.swift:127 — Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator+JavaBindingsPrinting.swift:127-139 | Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator+JavaBindingsPrinting.swift:315-328 — 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/JExtractSwiftLib/JNI/JNISwift2JavaGenerator+JavaBindingsPrinting.swift:127` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (14 lines × 2) · ×1
  • Duplicated block (14 lines × 2) Sources/SwiftJava/JavaObject+MethodCalls.swift:104 — Sources/SwiftJava/JavaObject+MethodCalls.swift:104-117 | Sources/SwiftJava/JavaObject+MethodCalls.swift:128-141 — 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/SwiftJava/JavaObject+MethodCalls.swift:104` 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.
D4 · Code Duplication · Duplicated block (9–11 lines × 2) · ×1
  • Duplicated block (9–11 lines × 2) Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator+JavaTranslation.swift:23 — Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator+JavaTranslation.swift:23-33 | Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator+JavaTranslation.swift:101-109 — 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/JExtractSwiftLib/JNI/JNISwift2JavaGenerator+JavaTranslation.swift:23` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (4–8 lines × 3) · ×1
  • Duplicated block (4–8 lines × 3) Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator+SwiftThunkPrinting.swift:699 — Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator+SwiftThunkPrinting.swift:699-706 | Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator+SwiftThunkPrinting.swift:739-746 | Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator+SwiftThunkPrinting.swift:759-762 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator+SwiftThunkPrinting.swift:759` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (5 lines × 3) · ×1
  • Duplicated block (5 lines × 3) Sources/JExtractSwiftLib/FFM/CDeclLowering/FFMSwift2JavaGenerator+FunctionLowering.swift:1053 — Sources/JExtractSwiftLib/FFM/CDeclLowering/FFMSwift2JavaGenerator+FunctionLowering.swift:1053-1057 | Sources/JExtractSwiftLib/FFM/CDeclLowering/FFMSwift2JavaGenerator+FunctionLowering.swift:1087-1091 | Sources/JExtractSwiftLib/FFM/CDeclLowering/FFMSwift2JavaGenerator+FunctionLowering.swift:1101-1105 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/JExtractSwiftLib/FFM/CDeclLowering/FFMSwift2JavaGenerator+FunctionLowering.swift:1053` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (10 lines × 15) · ×1
  • Duplicated block (10 lines × 15) SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple10.java:44 — SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple10.java:44-53 | SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple11.java:46-55 | SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple12.java:48-57 | SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple13.java:50-59 | SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple14.java:52-61 | SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple15.java:54-63 | SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple16.java:56-65 | SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple17.java:58-67 | SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple18.java:60-69 | SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple19.java:62-71 | SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple20.java:64-73 | SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple21.java:66-75 | SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple22.java:68-77 | SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple23.java:70-79 | SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple24.java:72-81 — before extracting anything, compare `SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple11.java` and `SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple12.java` as WHOLE FILES: 82% 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 1 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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note what the matched lines are: every one of them assigns one field to another, so the block is a hand-written mapper between two data shapes rather than behaviour with a helper inside it. Extracting one shared function only works if both sites map the SAME pair of types in the same direction — check that first, because inverse or differently-typed mappers have no single function they can both call. Where they do not, the moves that exist are a generated or reflective mapper, a common embedded/base type the fields live on once, or accepting the run and covering it with a test that fails when a field is added to one side only.
D4 · Code Duplication · Duplicated block (10 lines × 5) · ×1
  • Duplicated block (10 lines × 5) SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple20.java:74 — SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple20.java:74-83 | SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple21.java:76-85 | SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple22.java:78-87 | SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple23.java:80-89 | SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple24.java:82-91 — before extracting anything, compare `SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple20.java` and `SwiftKitCore/src/main/java/org/swift/swiftkit/core/tuple/Tuple21.java` as WHOLE FILES: 88% 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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note what the matched lines are: every one of them assigns one field to another, so the block is a hand-written mapper between two data shapes rather than behaviour with a helper inside it. Extracting one shared function only works if both sites map the SAME pair of types in the same direction — check that first, because inverse or differently-typed mappers have no single function they can both call. Where they do not, the moves that exist are a generated or reflective mapper, a common embedded/base type the fields live on once, or accepting the run and covering it with a test that fails when a field is added to one side only.
D4 · Code Duplication · Duplicated block (21 lines × 2) · ×1
  • Duplicated block (21 lines × 2) Samples/SwiftJavaExtractFFMSampleApp/Sources/MySwiftLibrary/Typealias.swift:20 — Samples/SwiftJavaExtractFFMSampleApp/Sources/MySwiftLibrary/Typealias.swift:20-40 | Samples/SwiftJavaExtractJNISampleApp/Sources/MySwiftLibrary/Typealias.swift:20-40 — before extracting anything, compare `Samples/SwiftJavaExtractFFMSampleApp/Sources/MySwiftLibrary/Typealias.swift` and `Samples/SwiftJavaExtractJNISampleApp/Sources/MySwiftLibrary/Typealias.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 1 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. Read the line range as the matched WINDOW rather than a finished unit: at `Samples/SwiftJavaExtractFFMSampleApp/Sources/MySwiftLibrary/Typealias.swift:20` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D5 · Coupling · Off the main sequence · ×1
  • Off the main sequence: SwiftRuntimeFunctions — SwiftRuntimeFunctions: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Minor — 608 finding(s)
D10 · Test Quality · No direct assertions · ×591
  • No direct assertions: func_accept_array_uint8 Tests/JExtractSwiftTests/ByteArrayTests.swift:22 — No conventional assertion call was detected, and 507 of 605 tests in `JExtractSwiftTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: func_return_array_uint8 Tests/JExtractSwiftTests/ByteArrayTests.swift:93 — No conventional assertion call was detected, and 507 of 605 tests in `JExtractSwiftTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: func_accept_array_uint8_jni Tests/JExtractSwiftTests/ByteArrayTests.swift:191 — No conventional assertion call was detected, and 507 of 605 tests in `JExtractSwiftTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: func_return_array_uint8_jni Tests/JExtractSwiftTests/ByteArrayTests.swift:224 — No conventional assertion call was detected, and 507 of 605 tests in `JExtractSwiftTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: func_accept_unsafeRawBufferPointer_jni Tests/JExtractSwiftTests/ByteArrayTests.swift:258 — No conventional assertion call was detected, and 507 of 605 tests in `JExtractSwiftTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: class_layout Tests/JExtractSwiftTests/ClassPrintingTests.swift:43 — No conventional assertion call was detected, and 507 of 605 tests in `JExtractSwiftTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: jni_topLevelType_resolvedAndQualified Tests/JExtractSwiftTests/CrossModuleDependsOnTests.swift:29 — No conventional assertion call was detected, and 507 of 605 tests in `JExtractSwiftTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: jni_topLevelType_droppedWithoutDependency Tests/JExtractSwiftTests/CrossModuleDependsOnTests.swift:60 — No conventional assertion call was detected, and 507 of 605 tests in `JExtractSwiftTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: jni_twoDependentModules Tests/JExtractSwiftTests/CrossModuleDependsOnTests.swift:85 — No conventional assertion call was detected, and 507 of 605 tests in `JExtractSwiftTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: jni_nestedTypeInDependentModule Tests/JExtractSwiftTests/CrossModuleDependsOnTests.swift:135 — No conventional assertion call was detected, and 507 of 605 tests in `JExtractSwiftTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: data_swiftThunk Tests/JExtractSwiftTests/DataImportTests.swift:71 — No conventional assertion call was detected, and 507 of 605 tests in `JExtractSwiftTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: data_javaBindings Tests/JExtractSwiftTests/DataImportTests.swift:133 — No conventional assertion call was detected, and 507 of 605 tests in `JExtractSwiftTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: dataProtocol_swiftThunk Tests/JExtractSwiftTests/DataImportTests.swift:394 — No conventional assertion call was detected, and 507 of 605 tests in `JExtractSwiftTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: dataProtocol_javaBindings Tests/JExtractSwiftTests/DataImportTests.swift:426 — No conventional assertion call was detected, and 507 of 605 tests in `JExtractSwiftTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: data_jni_accept Tests/JExtractSwiftTests/DataImportTests.swift:489 — No conventional assertion call was detected, and 507 of 605 tests in `JExtractSwiftTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: data_jni_return Tests/JExtractSwiftTests/DataImportTests.swift:524 — No conventional assertion call was detected, and 507 of 605 tests in `JExtractSwiftTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: data_jni_class Tests/JExtractSwiftTests/DataImportTests.swift:555 — No conventional assertion call was detected, and 507 of 605 tests in `JExtractSwiftTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: dataProtocol_jni_genericParameter Tests/JExtractSwiftTests/DataImportTests.swift:585 — No conventional assertion call was detected, and 507 of 605 tests in `JExtractSwiftTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: dataProtocol_jni_multipleGenericParameters Tests/JExtractSwiftTests/DataImportTests.swift:609 — No conventional assertion call was detected, and 507 of 605 tests in `JExtractSwiftTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: dataProtocol_jni_genericParameter_swiftThunk Tests/JExtractSwiftTests/DataImportTests.swift:630 — No conventional assertion call was detected, and 507 of 605 tests in `JExtractSwiftTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: dataProtocol_jni_multipleGenericParameters_swiftThunk Tests/JExtractSwiftTests/DataImportTests.swift:657 — No conventional assertion call was detected, and 507 of 605 tests in `JExtractSwiftTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: func_accept_date Tests/JExtractSwiftTests/DateTests.swift:20 — No conventional assertion call was detected, and 507 of 605 tests in `JExtractSwiftTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: func_return_Date Tests/JExtractSwiftTests/DateTests.swift:72 — No conventional assertion call was detected, and 507 of 605 tests in `JExtractSwiftTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: date_class Tests/JExtractSwiftTests/DateTests.swift:119 — No conventional assertion call was detected, and 507 of 605 tests in `JExtractSwiftTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: data_swiftThunk Tests/JExtractSwiftTests/ExtensionImportTests.swift:29 — No conventional assertion call was detected, and 507 of 605 tests in `JExtractSwiftTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • + 566 more in this group — see findings.md.
D34 · Knowledge Freshness · Orphaned file · ×3
  • Orphaned file Sources/JExtractSwiftLib/CTypes/CType.swift:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Sources/SwiftJavaToolLib/MethodVariance.swift:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Sources/SwiftJavaMacros/GenerationMode.swift:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
X10 · Duplicated predicate · Duplicated predicate · ×2
  • Duplicated predicate Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator+JavaBindingsPrinting.swift:1050 — `type.swiftNominal.isGeneric && !type.isSpecialization` appears character-identically in 2 files — Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator+JavaBindingsPrinting.swift, Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator+SwiftThunkPrinting.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/JExtractSwiftLib/JNI/JNISwift2JavaGenerator+SwiftThunkPrinting.swift:361 — `type.swiftNominal.kind == .enum && type.cases.isEmpty` appears character-identically in 2 files — Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator+SwiftThunkPrinting.swift, Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator.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.
D10 · Test Quality · Test project verifies nothing · ×1
  • Test project verifies nothing: SwiftJavaMacrosTests Tests/SwiftJavaMacrosTests/JavaClassMacroTests.swift:32 — No conventional assertion call was detected in 16 of 16 tests in `SwiftJavaMacrosTests` — 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.
D16 · Bus Factor · Off-boarding risk · ×1
  • Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 10 significant file(s) lose their only recent owner: Sources/SwiftJavaToolLib/AndroidAPILevel.swift, Sources/SwiftJavaTool/CommonOptions.swift, SwiftKitCore/src/main/java/org/swift/swiftkit/core/collections/SwiftDictionaryMap.java, SwiftKitCore/src/main/java/org/swift/swiftkit/core/collections/SwiftSet.java, Sources/JExtractSwiftLib/JavaExtractDecider.swift, Sources/JExtractSwiftLib/JNI/JNISwift2JavaGenerator+LabeledTuples.swift, Sources/JExtractSwiftLib/JavaSourceDependencies.swift, Sources/CodePrinting/CodePrinter+Java.swift (+2 more). Pair on, review, or document these before any departure.
D16 · Bus Factor · Further sole-owners (lower concentration) · ×1
  • Further sole-owners (lower concentration) — 2 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (13 single-owned of 125 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 125 of the 319 production source files in this repository met that bar). They are anonymized user #2 (2 file(s)), anonymized user #3 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: Sources/JExtractSwiftLib/SwiftDocumentationParsing.swift, Sources/SwiftJava/AndroidSupport.swift, Sources/JExtractSwiftLib/KnownFunctionalInterfaces.swift.
D26 · Project Cohesion · Projects may be oversized for their cohesion · ×1
  • Projects may be oversized for their cohesion — 1 of 4 project(s) overshoot their size bounds, lowering Project Cohesion to 5.0/10. The most over is `(repository root)` (32440 LoC, 367 module-visible types across 37 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D34 · Knowledge Freshness · Orphaned files with no living knowledge · ×1
  • Orphaned files with no living knowledge — 3 of 125 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 125 of the 319 production source files in this repository met that bar). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — most significant first: Sources/JExtractSwiftLib/CTypes/CType.swift, Sources/SwiftJavaToolLib/MethodVariance.swift, Sources/SwiftJavaMacros/GenerationMode.swift. Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
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.
P2 · Observability · Logging is not universal · ×1
  • Logging is not universal — Only 2/3 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST REDACTED:1 — No static application security testing detected. For this repository's stack, add CodeQL's Swift pack (Swift/Xcode) (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 1 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
P3 · Security & performance tooling · Dependabot does not watch gradle · ×1
  • Dependabot does not watch gradle REDACTED:2 — `REDACTED` schedules updates, but no `package-ecosystem` entry covers `gradle`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list.
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.)
X5 · Nullable reference types · Java packages are not null-marked everywhere · ×1
  • Java packages are not null-marked everywhere — 0/9 of this repository's Java package directories are under a non-null default: a `package-info.java` declaring `@NullMarked` (JSpecify) or `@NonNullApi`, `@ParametersAreNonnullByDefault`, `@NonNullByDefault`, `@DefaultQualifier(NonNull.class)`; a `module-info.java` declaring `@NullMarked`; every type in it `@NullMarked`; or a build that runs NullAway with the package in `AnnotatedPackages`, or the Checker Framework's `NullnessChecker`. Elsewhere every reference admits null and no checker warns on the dereference that throws a `NullPointerException`.
Minor — 3 finding(s)
D10 · Test Quality · Skipped (documented) · ×1
  • Skipped (documented): swiftinterfaceCommonPattern Tests/JExtractSwiftTests/IfConfigTests.swift:133 — Skipped with a documented reason — a deferral, not lazy debt: conditionally enabled — runs only when its .enabled(if:) condition holds
D12 · Dependency Hygiene · Dependency hygiene PARTLY measured · ×1
  • Dependency hygiene PARTLY measured — Maven/Gradle declarations read, no dependency graph resolved — This repository's Maven/Gradle manifests were read for what they DECLARE: 4 dependency(ies) whose version the file itself states, across 9 manifest(s), plus 4 further coordinate(s) that are managed by a parent or an imported BOM and whose versions therefore appear nowhere in this checkout. That second number is the reason this is only PART of the answer — measured across the corpus, 71.6 % of a Maven repository's dependencies carry no version at the declaration site, so no reader of a checkout can grade them and only a resolution can. This run had no resolution: the build resolved no dependencies (exit 1), so there is nothing to grade for currency. So this dimension is NOT SCORED — grading the declared minority and presenting it as the dependency surface is the confident-clean-over-an-unopened-set defect this dimension has already earned once. Known CVEs in the same graph are a separate question again, reported under D30 wherever the manifest is OSV-readable.
D5 · Coupling · Off the main sequence · ×1
  • Off the main sequence: SwiftJavaConfigurationShared — SwiftJavaConfigurationShared: abstractness 0.00, instability 0.00, distance 1.00 — the shape a shared-kernel / building-block library has BY DESIGN — concrete and widely depended-on is what makes it useful, and this dimension does not penalise it (the distance is reported for completeness, not as a defect). Worth a look only if it has grown past one coherent kernel into an everything-bucket.

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-36ad77c5136c4c0da0b48cf7682ba613/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-36ad77c5136c4c0da0b48cf7682ba613/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 --exclude Sources/JavaStdlib/JavaIO/generated --exclude Sources/JavaStdlib/JavaLangReflect/generated --exclude Sources/JavaStdlib/JavaNet/generated --exclude Sources/JavaStdlib/JavaUtil/generated --exclude Sources/JavaStdlib/JavaUtilFunction/generated --exclude Sources/JavaStdlib/JavaUtilJar/generated --exclude Sources/SwiftJava/generated .22artifacts/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, a Gradle version catalogue and a Gradle build (build.gradle/build.gradle.kts) — not scanned yet).0—
D31 · IaC & Container Securitytrivy—trivy config --format json --quiet .11artifacts/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 75 file(s) — `Plugins/JExtractSwiftPlugin/JExtractSwiftPlugin.swift`, `Plugins/PluginsShared/SwiftExtractConfigurationShared/LogLevel.swift`, `Samples/JavaKitSampleApp/Sources/JavaKitExample/SwiftArgumentParserMain.swift`, `Samples/SwiftJavaExtractJNISampleApp/Sources/MySwiftLibrary/Distributed.swift`, `Samples/SwiftJavaExtractJNISampleApp/Sources/MySwiftLibrary/Isolated.swift`, … (+70 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.0—
D36 · Supply-chain Provenance & Signingprovenance—provenance: not applicable — 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).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, a Gradle version catalogue and a Gradle build (build.gradle/build.gradle.kts) — not scanned yet).0—

Run 01a1dd3b-0fee-72c6-8727-22d86d57fa8c · 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