Public report of Deep-Learning-4-VB-NET/deeplearning4vb, published 21 October 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. This copy doesn't carry the survey's signed record. How a survey is checked →

Deep-Learning-4-VB-NET/deeplearning4vb

Measured 21 October 2026, 16:40 UTC, at code version 0df7a55

Code coverage: not measuredTest reliability: not measuredBoundary Type-Coupling: not measured

Code coverage is not measured: No coverage collector is wired up.

Test reliability is not measured: No test run produced results.

Boundary Type-Coupling is not measured: Bounded contexts not declared.

CAI score 50out of 100 Provisional Up 7 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.

Security and Compliance 100 Exemplary Architecture 86 Adequate Code Health 78 Adequate Domain Modelling 63 Adequate Maturity 61 Adequate Performance 60 Adequate Production Readiness 34 Weak

A large codebase: 180,953 lines of product code in 4 projects, tests not counted · Estimated rebuild effort: about 3.0 person-years · Weakest lens: Production Readiness, 34

Findings by how serious they are

9 critical 238 serious 29 minor

38 dimensions are left out of the score. For each one, Watchdog either couldn't measure it in this code, or found no evidence of the safeguard it looks 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

Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
21 October 2026, 16:40 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 Watchdog. It is open to any tool that implements it, and today Watchdog is the only one that does.

The code didn't build, so the score is provisional
Watchdog couldn't build the code: the build stopped with 68 errors. The dimensions that need a working build, such as complexity, duplication and dead code, were measured on an incomplete picture of the code, so their grades and the score are provisional. Fix the build errors and run the survey again for a final score. The first errors: BC30518: Overload resolution failed because no accessible 'createUninitialized' can be called with these arguments:; BC30518: Overload resolution failed because no accessible 'create' can be called with these arguments:; BC30456: 'Random' is not a member of 'Nd4vb'.; BC30002: Type 'ManagedNDArray' is not defined.; BC30456: 'factory' is not a member of 'Nd4vb'.

The score is deterministic, which means the same code always gets the same score. Watchdog works 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 ▸

36of 40 dimensions measured by tools. The other 4 are advisory notes from an AI model, which explain the code but don't count towards the score.
265of 276 findings point to an exact file and line, so you can open each one in the code. The other 11 concern the repository as a whole, such as missing documentation.
40dimensions across 7 lenses, read from 180,953 lines of product code in 4 projects.
Chapters

Executive summary

Deep-Learning-4-VB-NET/deeplearning4vb scores 50 out of 100, but the score is provisional because the code didn't build, so the ratings below may change once it does.

The weakest lens counts most in the score, and here that is Production Readiness, which scores 34 and is rated Weak. Its CI/CD gates dimension scores 0 out of 10, and until that reaches 4, Production Readiness can't be rated higher than Adequate. The first actions are to add a CI workflow that builds and runs the test suite on every push/PR and to resolve the 2 Deprecated finding(s) in Dependency Hygiene, and if Production Readiness rose to 70, the score would rise from 50 to about 63.

Nine findings are critical, all in Explicit Debt.

Watchdog couldn't measure 35 dimensions in this code, among them Cyclomatic Complexity, Cognitive Complexity and Churn × Complexity Hotspots, so they are left out of the score. The product code is 180,953 lines, which would take an estimated 3.0 person-years, around €430,000, to rebuild.

Code Health 78 Adequate, capped by Solution Shape Architecture 86 Adequate, capped by Project Cohesion Maturity 61 Adequate, capped by Architecture documentation Production Readiness 34 Weak, capped by CI/CD gates and Security & performance tooling Security and Compliance 100 ★ Exemplary Domain Modelling 63 Adequate, capped by Rich vs anemic model and Constructible invalid state Performance 60 Adequate

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

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

If Production Readiness rose from 34 to 70, the lowest score rated Strong, the score would rise from 50 to about 63.

Code composition: what the lines of code are
Product code 47%Tests 53%
New since the last survey: 243 findings

These 243 critical or serious findings weren't in the previous survey, on 6 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.

  • Code Duplication · Near-duplicate member pair (40 shared lines) src/DeepLearning4VB/org/nd4vb/linalg/managed/kernels/ManagedBlas.Level3.vb
  • Code Duplication · Edited copy of a member (45 corresponding lines) src/DeepLearning4VB/org/nd4vb/linalg/managed/kernels/ManagedBlas.Level3.vb
  • Code Duplication · Edited copy of a member (38 corresponding lines) src/DeepLearning4VB/org/nd4vb/linalg/managed/kernels/ManagedBlas.Level3.vb
  • Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) src/DeepLearning4VB/org/datavec/api/writable/ByteWritable.vb
  • Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseTransformBoolOp.vb
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) src/DeepLearning4VB/org/datavec/api/transform/condition/ConditionOp.vb
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseReduceBoolOp.vb
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/Conv2DConfig.vb
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/transforms/custom/DotProductAttention.vb
  • Code Duplication · Duplicated block (43 lines × 2) src/DeepLearning4VB/org/nd4vb/autodiff/functions/DifferentialFunction.vb
  • Code Duplication · Duplicated block (39 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/Conv3DConfig.vb
  • Code Duplication · Duplicated block (25–27 lines × 3) src/DeepLearning4VB/org/datavec/api/transform/analysis/counter/DoubleAnalysisCounter.vb
  • Code Duplication · Duplicated block (24 lines × 2) src/DeepLearning4VB/org/datavec/api/transform/condition/BooleanCondition.vb
  • Code Duplication · Duplicated block (24 lines × 2) src/DeepLearning4VB/org/datavec/api/transform/condition/BooleanCondition.vb
  • Code Duplication · Duplicated block (23 lines × 2) src/DeepLearning4VB/org/datavec/api/transform/transform/doubletransform/DoubleMathFunctionTransform.vb
  • Code Duplication · Duplicated block (21 lines × 3) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/Conv2DConfig.vb
  • Code Duplication · Duplicated block (22 lines × 2) src/DeepLearning4VB/org/datavec/api/transform/transform/doubletransform/DoubleMathOpTransform.vb
  • Code Duplication · Duplicated block (22 lines × 2) src/DeepLearning4VB/org/datavec/api/transform/transform/integer/IntegerMathOpTransform.vb
  • Code Duplication · Duplicated block (20 lines × 4) src/DeepLearning4VB/org/datavec/api/transform/condition/ConditionOp.vb
  • Code Duplication · Duplicated block (20 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/managed/kernels/ManagedBlas.Level3.vb
  • Code Duplication · Duplicated block (16 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/api/shape/LongShapeDescriptor.vb
  • Code Duplication · Duplicated block (17 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/executioner/DefaultOpExecutioner.vb
  • Code Duplication · Duplicated block (17 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/executioner/DefaultOpExecutioner.vb
  • Code Duplication · Duplicated block (15 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/managed/kernels/ManagedBlas.Level3.vb
  • Code Duplication · Duplicated block (15 lines × 5) src/DeepLearning4VB/org/datavec/api/writable/ByteWritable.vb
  • Code Duplication · Duplicated block (15 lines × 3) src/DeepLearning4VB/org/nd4vb/common/util/ArrayUtil.vb
  • Code Duplication · Duplicated block (14 lines × 3) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/Conv2DConfig.vb
  • Code Duplication · Duplicated block (15 lines × 2) src/DeepLearning4VB/org/datavec/api/transform/sequence/window/OverlappingTimeWindowFunction.vb
  • Code Duplication · Duplicated block (15 lines × 2) src/DeepLearning4VB/org/nd4vb/common/util/ArrayUtil.vb
  • Code Duplication · Duplicated block (15 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/managed/kernels/ManagedBlas.Level3.vb
  • Code Duplication · Duplicated block (15 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/managed/kernels/ManagedBlas.Level3.vb
  • Code Duplication · Duplicated block (14 lines × 3) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/DeConv3D.vb
  • Code Duplication · Duplicated block (14 lines × 2) src/DeepLearning4VB/org/datavec/api/transform/analysis/histogram/DoubleHistogramCounter.vb
  • Code Duplication · Duplicated block (12 lines × 2) src/DeepLearning4VB/org/datavec/api/transform/analysis/quality/categorical/CategoricalQualityAddFunction.vb
  • Code Duplication · Duplicated block (12 lines × 2) src/DeepLearning4VB/org/datavec/api/transform/ops/AggregatorImpls.vb
  • Code Duplication · Duplicated block (13 lines × 2) src/DeepLearning4VB/org/datavec/api/transform/sequence/window/OverlappingTimeWindowFunction.vb
  • Code Duplication · Duplicated block (13 lines × 2) src/DeepLearning4VB/org/datavec/api/transform/transform/doubletransform/DoubleMathFunctionTransform.vb
  • Code Duplication · Duplicated block (11 lines × 2) src/DeepLearning4VB/org/datavec/api/transform/ui/components/RenderableComponentHistogram.vb
  • Code Duplication · Duplicated block (14 lines × 2) src/DeepLearning4VB/org/nd4vb/common/util/ArrayUtil.vb
  • Code Duplication · Duplicated block (13 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/Conv3DConfig.vb
  • Code Duplication · Duplicated block (13 lines × 2) src/DeepLearning4VB/org/datavec/api/transform/ops/AggregatorImpls.vb
  • Code Duplication · Duplicated block (13 lines × 2) src/DeepLearning4VB/org/datavec/api/transform/transform/categorical/CategoricalToIntegerTransform.vb
  • Code Duplication · Duplicated block (12 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/Conv3DConfig.vb
  • Code Duplication · Duplicated block (9 lines × 3) src/DeepLearning4VB/org/datavec/api/transform/analysis/quality/integer/IntegerQualityAddFunction.vb
  • Code Duplication · Duplicated block (11 lines × 3) src/DeepLearning4VB/org/nd4vb/linalg/managed/kernels/ElementWiseKernels.vb
  • Code Duplication · Duplicated block (11 lines × 2) src/DeepLearning4VB/org/datavec/api/transform/metadata/IntegerMetaData.vb
  • Code Duplication · Duplicated block (11 lines × 2) src/DeepLearning4VB/org/datavec/api/transform/schema/Schema.vb
  • Code Duplication · Duplicated block (11 lines × 2) src/DeepLearning4VB/org/datavec/api/transform/schema/SequenceSchema.vb
  • Code Duplication · Duplicated block (12 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/Conv2DConfig.vb
  • Code Duplication · Duplicated block (12 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/transforms/custom/DotProductAttention.vb
  • Code Duplication · Duplicated block (11 lines × 2) src/DeepLearning4VB/org/nd4vb/common/util/ArrayUtil.vb
  • Code Duplication · Duplicated block (9 lines × 3) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/DeConv2D.vb
  • Code Duplication · Duplicated block (5 lines × 2) src/DeepLearning4VB/JavaCompat/Arrays.vb
  • Code Duplication · Duplicated block (10 lines × 2) src/DeepLearning4VB/org/nd4vb/common/util/ArrayUtil.vb
  • Code Duplication · Duplicated block (10 lines × 2) src/DeepLearning4VB/org/nd4vb/common/util/ArrayUtil.vb
  • Code Duplication · Duplicated block (10 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/api/shape/Shape.vb
  • Code Duplication · Duplicated block (9 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/indexing/Indices.vb
  • Code Duplication · Duplicated block (9 lines × 2) src/DeepLearning4VB/org/datavec/api/records/reader/impl/FileRecordReader.vb
  • Code Duplication · Duplicated block (8 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseReduceFloatOp.vb
  • Code Duplication · Duplicated block (9 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/indexaccum/FirstIndex.vb
  • Code Duplication · Duplicated block (9 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/Im2col.vb
  • Code Duplication · Duplicated block (7 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/transforms/custom/DotProductAttentionBp.vb
  • Code Duplication · Duplicated block (9 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/api/shape/Shape.vb
  • Code Duplication · Duplicated block (9 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/managed/kernels/ManagedBlas.Level3.vb
  • Code Duplication · Duplicated block (9 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/managed/kernels/ManagedBlas.Level3.vb
  • Code Duplication · Duplicated block (9 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/managed/kernels/ReduceKernels.vb
  • Code Duplication · Duplicated block (7 lines × 4) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/transforms/custom/DotProductAttention.vb
  • Code Duplication · Duplicated block (7 lines × 3) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/Conv2DConfig.vb
  • Code Duplication · Duplicated block (8 lines × 2) src/DeepLearning4VB/org/datavec/api/split/FileSplit.vb
  • Code Duplication · Duplicated block (7 lines × 2) src/DeepLearning4VB/org/datavec/api/transform/metadata/DoubleMetaData.vb
  • Code Duplication · Duplicated block (8 lines × 2) src/DeepLearning4VB/org/nd4vb/autodiff/functions/DifferentialFunction.vb
  • Code Duplication · Duplicated block (7 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/api/blas/params/GemmParams.vb
  • Code Duplication · Duplicated block (8 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseOp.vb
  • Code Duplication · Duplicated block (7 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseReduceBoolOp.vb
  • Code Duplication · Duplicated block (7 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseReduceBoolOp.vb
  • Code Duplication · Duplicated block (4–8 lines × 3) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/executioner/DefaultOpExecutioner.vb
  • Code Duplication · Duplicated block (7 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/indexaccum/FirstIndex.vb
  • Code Duplication · Duplicated block (7 lines × 4) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseReduceBoolOp.vb
  • Code Duplication · Duplicated block (7 lines × 3) src/DeepLearning4VB/org/nd4vb/autodiff/functions/DifferentialFunction.vb
  • Code Duplication · Duplicated block (6 lines × 3) src/DeepLearning4VB/org/nd4vb/linalg/util/NDArrayUtil.vb
  • Code Duplication · Duplicated block (7 lines × 2) src/DeepLearning4VB/JavaCompat/JavaString.vb
  • Code Duplication · Duplicated block (6 lines × 2) src/DeepLearning4VB/org/datavec/api/transform/ui/components/RenderableComponentHistogram.vb
  • Code Duplication · Duplicated block (7 lines × 2) src/DeepLearning4VB/org/datavec/local/transforms/LocalTransformExecutor.vb
  • Code Duplication · Duplicated block (6 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/api/blas/impl/BaseLapack.vb
  • Code Duplication · Duplicated block (5 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/managed/kernels/ReduceKernels.vb
  • Code Duplication · Duplicated block (7 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/managed/ManagedOpExecutioner.vb
  • Code Duplication · Duplicated block (6 lines × 3) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseReduceBoolOp.vb
  • Code Duplication · Duplicated block (6 lines × 2) src/DeepLearning4VB/org/datavec/api/records/reader/impl/inmemory/InMemoryRecordReader.vb
  • Code Duplication · Duplicated block (6 lines × 2) src/DeepLearning4VB/org/datavec/api/transform/analysis/DataAnalysis.vb
  • Code Duplication · Duplicated block (6 lines × 2) src/DeepLearning4VB/org/datavec/api/transform/sequence/expansion/BaseSequenceExpansionTransform.vb
  • Code Duplication · Duplicated block (6 lines × 2) src/DeepLearning4VB/org/datavec/api/transform/transform/categorical/CategoricalToOneHotTransform.vb
  • Code Duplication · Duplicated block (6 lines × 2) src/DeepLearning4VB/org/datavec/local/transforms/AnalyzeLocal.vb
  • Code Duplication · Duplicated block (6 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/managed/kernels/IndexReduceKernels.vb
  • Code Duplication · Duplicated block (5 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/managed/kernels/ManagedBlas.Level3.vb
  • Code Duplication · Duplicated block (5 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/managed/kernels/ReduceKernels.vb
  • Code Duplication · Duplicated block (3–5 lines × 5) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseTransformBoolOp.vb
  • Code Duplication · Duplicated block (5 lines × 2) src/DeepLearning4VB/org/datavec/api/transform/analysis/counter/IntegerAnalysisCounter.vb
  • Code Duplication · Duplicated block (5 lines × 2) src/DeepLearning4VB/org/datavec/api/transform/sequence/window/OverlappingTimeWindowFunction.vb
  • Code Duplication · Duplicated block (5 lines × 2) src/DeepLearning4VB/org/datavec/local/transforms/LocalTransformExecutor.vb
  • Code Duplication · Duplicated block (5 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseBroadcastOp.vb

Watchdog compares 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: 3574 findings

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

  • Cyclomatic Complexity · TransformOpValidation.testTransforms (cyclomatic 98) deeplearning4vb/nd4j/nd4j-backends/nd4j-tests/src/test/java/org/nd4j/autodiff/opvalidation/TransformOpValidation.vb
  • Cyclomatic Complexity · IntegrationTestRunner.runTest (cyclomatic 94) deeplearning4vb/deeplearning4j/dl4j-integration-tests/src/test/java/org/deeplearning4j/integration/IntegrationTestRunner.vb
  • Cyclomatic Complexity · ComputationGraph.outputOfLayersDetached (cyclomatic 84) deeplearning4vb/deeplearning4j/deeplearning4j-nn/src/main/java/org/deeplearning4j/nn/graph/ComputationGraph.vb
  • Cyclomatic Complexity · SbeStatsReport.encode (cyclomatic 83) deeplearning4vb/deeplearning4j/deeplearning4j-ui-parent/deeplearning4j-ui-model/src/main/java/org/deeplearning4j/ui/model/stats/impl/SbeStatsReport.vb
  • Cyclomatic Complexity · KerasLayerUtils.getKerasLayerFromConfig (cyclomatic 82) deeplearning4vb/deeplearning4j/deeplearning4j-modelimport/src/main/java/org/deeplearning4j/nn/modelimport/keras/utils/KerasLayerUtils.vb
  • Cyclomatic Complexity · JavaSourceArgDescriptorSource.processClazz (cyclomatic 81) deeplearning4vb/contrib/codegen-tools/libnd4j-gen/src/main/java/org/nd4j/descriptor/proposal/impl/JavaSourceArgDescriptorSource.vb
  • Cyclomatic Complexity · CudaArgs.getOpCode (cyclomatic 78) deeplearning4vb/nd4j/nd4j-backends/nd4j-backend-impls/nd4j-cuda/src/main/java/org/nd4j/linalg/jcublas/util/CudaArgs.vb
  • Cyclomatic Complexity · TFGraphTestAllHelper.readVars (cyclomatic 70) deeplearning4vb/nd4j/samediff-import/samediff-import-tensorflow/src/test/java/org/nd4j/imports/tfgraphs/TFGraphTestAllHelper.vb
  • Cyclomatic Complexity · LSTMHelpers.activateHelper (cyclomatic 69) deeplearning4vb/deeplearning4j/deeplearning4j-nn/src/main/java/org/deeplearning4j/nn/layers/recurrent/LSTMHelpers.vb
  • Cyclomatic Complexity · AbstractSession.output (cyclomatic 68) deeplearning4vb/nd4j/nd4j-backends/nd4j-api-parent/nd4j-api/src/main/java/org/nd4j/autodiff/samediff/internal/AbstractSession.vb
  • Cyclomatic Complexity · TrainModule.getOverviewDataForSession (cyclomatic 65) deeplearning4vb/deeplearning4j/deeplearning4j-ui-parent/deeplearning4j-vertx/src/main/java/org/deeplearning4j/ui/module/train/TrainModule.vb
  • Cyclomatic Complexity · SameDiff.fitHelper (cyclomatic 65) deeplearning4vb/nd4j/nd4j-backends/nd4j-api-parent/nd4j-api/src/main/java/org/nd4j/autodiff/samediff/SameDiff.vb
  • Cyclomatic Complexity · TFGraphMapper.importGraph (cyclomatic 63) deeplearning4vb/nd4j/nd4j-backends/nd4j-api-parent/nd4j-api/src/main/java/org/nd4j/imports/graphmapper/tf/TFGraphMapper.vb
  • Cyclomatic Complexity · GradCheckUtil.checkGradients (cyclomatic 62) deeplearning4vb/nd4j/nd4j-backends/nd4j-api-parent/nd4j-api/src/main/java/org/nd4j/autodiff/validation/GradCheckUtil.vb
  • Cyclomatic Complexity · LossOpValidation.testLoss2d (cyclomatic 61) deeplearning4vb/nd4j/nd4j-backends/nd4j-tests/src/test/java/org/nd4j/autodiff/opvalidation/LossOpValidation.vb
  • Cyclomatic Complexity · ComputationGraph.calcBackpropGradients (cyclomatic 58) deeplearning4vb/deeplearning4j/deeplearning4j-nn/src/main/java/org/deeplearning4j/nn/graph/ComputationGraph.vb
  • Cyclomatic Complexity · MultiLayerNetwork.outputOfLayerDetached (cyclomatic 58) deeplearning4vb/deeplearning4j/deeplearning4j-nn/src/main/java/org/deeplearning4j/nn/multilayer/MultiLayerNetwork.vb
  • Cyclomatic Complexity · NativeOpExecutioner.exec (cyclomatic 58) deeplearning4vb/nd4j/nd4j-backends/nd4j-backend-impls/nd4j-native/src/main/java/org/nd4j/linalg/cpu/nativecpu/ops/NativeOpExecutioner.vb
  • Cyclomatic Complexity · CudaExecutioner.invoke (cyclomatic 57) deeplearning4vb/nd4j/nd4j-backends/nd4j-backend-impls/nd4j-cuda/src/main/java/org/nd4j/linalg/jcublas/ops/executioner/CudaExecutioner.vb
  • Cyclomatic Complexity · SharedTrainingWrapper.run (cyclomatic 56) deeplearning4vb/deeplearning4j/deeplearning4j-scaleout/spark/dl4j-spark-parameterserver/src/main/java/org/deeplearning4j/spark/parameterserver/pw/SharedTrainingWrapper.vb
  • Cyclomatic Complexity · KerasInitilizationUtils.mapWeightInitialization (cyclomatic 54) deeplearning4vb/deeplearning4j/deeplearning4j-modelimport/src/main/java/org/deeplearning4j/nn/modelimport/keras/utils/KerasInitilizationUtils.vb
  • Cyclomatic Complexity · LSTMHelpers.backpropGradientHelper (cyclomatic 52) deeplearning4vb/deeplearning4j/deeplearning4j-nn/src/main/java/org/deeplearning4j/nn/layers/recurrent/LSTMHelpers.vb
  • Cyclomatic Complexity · TFGraphMapper.initFunctionFromProperties (cyclomatic 52) deeplearning4vb/nd4j/nd4j-backends/nd4j-api-parent/nd4j-api/src/main/java/org/nd4j/imports/graphmapper/tf/TFGraphMapper.vb
  • Cyclomatic Complexity · ComputationGraph.init (cyclomatic 51) deeplearning4vb/deeplearning4j/deeplearning4j-nn/src/main/java/org/deeplearning4j/nn/graph/ComputationGraph.vb
  • Cyclomatic Complexity · BaseEarlyStoppingTrainer.fit (cyclomatic 50) deeplearning4vb/deeplearning4j/deeplearning4j-nn/src/main/java/org/deeplearning4j/earlystopping/trainer/BaseEarlyStoppingTrainer.vb
  • Cyclomatic Complexity · GradientCheckUtil.checkGradients (cyclomatic 50) deeplearning4vb/deeplearning4j/deeplearning4j-nn/src/main/java/org/deeplearning4j/gradientcheck/GradientCheckUtil.vb
  • Cyclomatic Complexity · IntegrationTestBaselineGenerator.runGeneration (cyclomatic 50) deeplearning4vb/deeplearning4j/dl4j-integration-tests/src/test/java/org/deeplearning4j/integration/IntegrationTestBaselineGenerator.vb
  • Cyclomatic Complexity · LossFunctionGradientCheck.getFeaturesAndLabels (cyclomatic 48) deeplearning4vb/deeplearning4j/deeplearning4j-core/src/test/java/org/deeplearning4j/gradientcheck/LossFunctionGradientCheck.vb
  • Cyclomatic Complexity · InferenceSession.getAndParameterizeOp (cyclomatic 48) deeplearning4vb/nd4j/nd4j-backends/nd4j-api-parent/nd4j-api/src/main/java/org/nd4j/autodiff/samediff/internal/InferenceSession.vb
  • Cyclomatic Complexity · TestStatsClasses.testSbeStatsUpdate (cyclomatic 47) deeplearning4vb/deeplearning4j/deeplearning4j-ui-parent/deeplearning4j-ui-model/src/test/java/org/deeplearning4j/ui/stats/TestStatsClasses.vb
  • Cyclomatic Complexity · FlatBuffersMapper.asFlatNode (cyclomatic 47) deeplearning4vb/nd4j/nd4j-backends/nd4j-api-parent/nd4j-api/src/main/java/org/nd4j/autodiff/samediff/serde/FlatBuffersMapper.vb
  • Cyclomatic Complexity · GradientCheckUtil.checkGradients (cyclomatic 46) deeplearning4vb/deeplearning4j/deeplearning4j-nn/src/main/java/org/deeplearning4j/gradientcheck/GradientCheckUtil.vb
  • Cyclomatic Complexity · InferenceSession.getOutputsHelperTensorArrayOps (cyclomatic 46) deeplearning4vb/nd4j/nd4j-backends/nd4j-api-parent/nd4j-api/src/main/java/org/nd4j/autodiff/samediff/internal/InferenceSession.vb
  • Cyclomatic Complexity · FlatBuffersMapper.mapFlatPropertiesToFunctionProperties (cyclomatic 46) deeplearning4vb/nd4j/nd4j-backends/nd4j-api-parent/nd4j-api/src/main/java/org/nd4j/autodiff/samediff/serde/FlatBuffersMapper.vb
  • Cyclomatic Complexity · BaseDataBuffer.asBytes (cyclomatic 46) deeplearning4vb/nd4j/nd4j-backends/nd4j-api-parent/nd4j-api/src/main/java/org/nd4j/linalg/api/buffer/BaseDataBuffer.vb
  • Cyclomatic Complexity · SbeStatsReport.decode (cyclomatic 45) deeplearning4vb/deeplearning4j/deeplearning4j-ui-parent/deeplearning4j-ui-model/src/main/java/org/deeplearning4j/ui/model/stats/impl/SbeStatsReport.vb
  • Cyclomatic Complexity · UpdateFieldsPresentDecoder.appendTo (cyclomatic 45) deeplearning4vb/deeplearning4j/deeplearning4j-ui-parent/deeplearning4j-ui-model/src/main/java/org/deeplearning4j/ui/model/stats/sbe/UpdateFieldsPresentDecoder.vb
  • Cyclomatic Complexity · BaseNDArray.doRowWise (cyclomatic 45) deeplearning4vb/nd4j/nd4j-backends/nd4j-api-parent/nd4j-api/src/main/java/org/nd4j/linalg/api/ndarray/BaseNDArray.vb
  • Cyclomatic Complexity · BaseStatsListener.iterationDone (cyclomatic 44) deeplearning4vb/deeplearning4j/deeplearning4j-ui-parent/deeplearning4j-ui-model/src/main/java/org/deeplearning4j/ui/model/stats/BaseStatsListener.vb
  • Cyclomatic Complexity · CudaExecutioner.naiveExec (cyclomatic 44) deeplearning4vb/nd4j/nd4j-backends/nd4j-backend-impls/nd4j-cuda/src/main/java/org/nd4j/linalg/jcublas/ops/executioner/CudaExecutioner.vb
  • Cyclomatic Complexity · NativeImageLoader.fillNDArray (cyclomatic 43) deeplearning4vb/datavec/datavec-data/datavec-data-image/src/main/java/org/datavec/image/loader/NativeImageLoader.vb
  • Cyclomatic Complexity · SequenceVectors.fit (cyclomatic 43) deeplearning4vb/deeplearning4j/deeplearning4j-nlp-parent/deeplearning4j-nlp/src/main/java/org/deeplearning4j/models/sequencevectors/SequenceVectors.vb
  • Cyclomatic Complexity · ExecDebuggingListener.preOpExecution (cyclomatic 43) deeplearning4vb/nd4j/nd4j-backends/nd4j-api-parent/nd4j-api/src/main/java/org/nd4j/autodiff/listeners/debugging/ExecDebuggingListener.vb
  • Cyclomatic Complexity · ProfileAnalyzer.compareProfiles (cyclomatic 43) deeplearning4vb/nd4j/nd4j-backends/nd4j-api-parent/nd4j-api/src/main/java/org/nd4j/autodiff/listeners/profiler/comparison/ProfileAnalyzer.vb
  • Cyclomatic Complexity · TensorFlowImportValidator.checkAllModelsForImport (cyclomatic 43) deeplearning4vb/nd4j/nd4j-backends/nd4j-api-parent/nd4j-api/src/main/java/org/nd4j/imports/tensorflow/TensorFlowImportValidator.vb
  • Cyclomatic Complexity · BaseNDArray.doColumnWise (cyclomatic 43) deeplearning4vb/nd4j/nd4j-backends/nd4j-api-parent/nd4j-api/src/main/java/org/nd4j/linalg/api/ndarray/BaseNDArray.vb
  • Cyclomatic Complexity · BackTrackLineSearch.optimize (cyclomatic 42) deeplearning4vb/deeplearning4j/deeplearning4j-nn/src/main/java/org/deeplearning4j/optimize/solvers/BackTrackLineSearch.vb
  • Cyclomatic Complexity · ParallelWrapper.fit (cyclomatic 42) deeplearning4vb/deeplearning4j/deeplearning4j-scaleout/deeplearning4j-scaleout-parallelwrapper/src/main/java/org/deeplearning4j/parallelism/ParallelWrapper.vb
  • Cyclomatic Complexity · SameDiff.renameVariable (cyclomatic 42) deeplearning4vb/nd4j/nd4j-backends/nd4j-api-parent/nd4j-api/src/main/java/org/nd4j/autodiff/samediff/SameDiff.vb
  • Cyclomatic Complexity · InferenceSession.doExec (cyclomatic 42) deeplearning4vb/nd4j/nd4j-backends/nd4j-api-parent/nd4j-api/src/main/java/org/nd4j/autodiff/samediff/internal/InferenceSession.vb
  • Cyclomatic Complexity · CudaWorkspace.alloc (cyclomatic 42) deeplearning4vb/nd4j/nd4j-backends/nd4j-backend-impls/nd4j-cuda/src/main/java/org/nd4j/jita/workspace/CudaWorkspace.vb
  • Cyclomatic Complexity · KerasModelUtils.importWeights (cyclomatic 41) deeplearning4vb/deeplearning4j/deeplearning4j-modelimport/src/main/java/org/deeplearning4j/nn/modelimport/keras/utils/KerasModelUtils.vb
  • Cyclomatic Complexity · MultiLayerNetwork.calcBackpropGradients (cyclomatic 41) deeplearning4vb/deeplearning4j/deeplearning4j-nn/src/main/java/org/deeplearning4j/nn/multilayer/MultiLayerNetwork.vb
  • Cyclomatic Complexity · BatchNormalization.preOutput (cyclomatic 40) deeplearning4vb/deeplearning4j/deeplearning4j-nn/src/main/java/org/deeplearning4j/nn/layers/normalization/BatchNormalization.vb
  • Cyclomatic Complexity · FlatBuffersMapper.mapFunctionPropertiesToFlatProperties (cyclomatic 40) deeplearning4vb/nd4j/nd4j-backends/nd4j-api-parent/nd4j-api/src/main/java/org/nd4j/autodiff/samediff/serde/FlatBuffersMapper.vb
  • Cyclomatic Complexity · OpValidation.logCoverageInformation (cyclomatic 40) deeplearning4vb/nd4j/nd4j-backends/nd4j-api-parent/nd4j-api/src/main/java/org/nd4j/autodiff/validation/OpValidation.vb
  • Cyclomatic Complexity · NativeOpExecutioner.calculateOutputShape (cyclomatic 40) deeplearning4vb/nd4j/nd4j-backends/nd4j-backend-impls/nd4j-native/src/main/java/org/nd4j/linalg/cpu/nativecpu/ops/NativeOpExecutioner.vb
  • Cyclomatic Complexity · ComputationGraphConfigurationDeserializer.deserialize (cyclomatic 39) deeplearning4vb/deeplearning4j/deeplearning4j-nn/src/main/java/org/deeplearning4j/nn/conf/serde/ComputationGraphConfigurationDeserializer.vb
  • Cyclomatic Complexity · FineTuneConfiguration.applyToNeuralNetConfiguration (cyclomatic 39) deeplearning4vb/deeplearning4j/deeplearning4j-nn/src/main/java/org/deeplearning4j/nn/transferlearning/FineTuneConfiguration.vb
  • Cyclomatic Complexity · GradCheckUtil.checkActivationGradients (cyclomatic 39) deeplearning4vb/nd4j/nd4j-backends/nd4j-api-parent/nd4j-api/src/main/java/org/nd4j/autodiff/validation/GradCheckUtil.vb
  • Cyclomatic Complexity · MultiLayerConfigurationDeserializer.deserialize (cyclomatic 38) deeplearning4vb/deeplearning4j/deeplearning4j-nn/src/main/java/org/deeplearning4j/nn/conf/serde/MultiLayerConfigurationDeserializer.vb
  • Cyclomatic Complexity · DifferentialFunctionClassHolder.New.ctor (cyclomatic 38) deeplearning4vb/nd4j/nd4j-backends/nd4j-api-parent/nd4j-api/src/main/java/org/nd4j/imports/converters/DifferentialFunctionClassHolder.vb
  • Cyclomatic Complexity · VersionCheck.checkVersions (cyclomatic 38) deeplearning4vb/nd4j/nd4j-backends/nd4j-api-parent/nd4j-api/src/main/java/org/nd4j/versioncheck/VersionCheck.vb
  • Cyclomatic Complexity · RecordReaderMultiDataSetIterator.convertWritablesSequence (cyclomatic 37) deeplearning4vb/deeplearning4j/deeplearning4j-data/deeplearning4j-datavec-iterators/src/main/java/org/deeplearning4j/datasets/datavec/RecordReaderMultiDataSetIterator.vb
  • Cyclomatic Complexity · MultiLayerConfiguration.fromJson (cyclomatic 37) deeplearning4vb/deeplearning4j/deeplearning4j-nn/src/main/java/org/deeplearning4j/nn/conf/MultiLayerConfiguration.vb
  • Cyclomatic Complexity · ProfileAnalyzer.getTraceEvents (cyclomatic 37) deeplearning4vb/nd4j/nd4j-backends/nd4j-api-parent/nd4j-api/src/main/java/org/nd4j/autodiff/listeners/profiler/comparison/ProfileAnalyzer.vb
  • Cyclomatic Complexity · ComputationGraph.ffToLayerActivationsDetached (cyclomatic 36) deeplearning4vb/deeplearning4j/deeplearning4j-nn/src/main/java/org/deeplearning4j/nn/graph/ComputationGraph.vb
  • Cyclomatic Complexity · ParallelWrapper.fit (cyclomatic 36) deeplearning4vb/deeplearning4j/deeplearning4j-scaleout/deeplearning4j-scaleout-parallelwrapper/src/main/java/org/deeplearning4j/parallelism/ParallelWrapper.vb
  • Cyclomatic Complexity · InferenceSession.getOutputs (cyclomatic 36) deeplearning4vb/nd4j/nd4j-backends/nd4j-api-parent/nd4j-api/src/main/java/org/nd4j/autodiff/samediff/internal/InferenceSession.vb
  • Cyclomatic Complexity · CudnnConvolutionHelper.backpropGradient (cyclomatic 35) deeplearning4vb/deeplearning4j/deeplearning4j-cuda/src/main/java/org/deeplearning4j/cuda/convolution/CudnnConvolutionHelper.vb
  • Cyclomatic Complexity · OpValidation.checkDeserializedEquality (cyclomatic 35) deeplearning4vb/nd4j/nd4j-backends/nd4j-api-parent/nd4j-api/src/main/java/org/nd4j/autodiff/validation/OpValidation.vb
  • Cyclomatic Complexity · Nd4jWorkspace.close (cyclomatic 35) deeplearning4vb/nd4j/nd4j-backends/nd4j-api-parent/nd4j-api/src/main/java/org/nd4j/linalg/api/memory/abstracts/Nd4jWorkspace.vb
  • Cyclomatic Complexity · TensorflowConversion.tensorFromNDArray (cyclomatic 35) deeplearning4vb/nd4j/nd4j-tensorflow/src/main/java/org/nd4j/tensorflow/conversion/TensorflowConversion.vb
  • Cyclomatic Complexity · VectorCalculationsThread.run (cyclomatic 34) deeplearning4vb/deeplearning4j/deeplearning4j-nlp-parent/deeplearning4j-nlp/src/main/java/org/deeplearning4j/models/sequencevectors/SequenceVectors.vb
  • Cyclomatic Complexity · EarlyStoppingParallelTrainer.fit (cyclomatic 34) deeplearning4vb/deeplearning4j/deeplearning4j-scaleout/deeplearning4j-scaleout-parallelwrapper/src/main/java/org/deeplearning4j/parallelism/EarlyStoppingParallelTrainer.vb
  • Cyclomatic Complexity · DefaultTrainer.run (cyclomatic 34) deeplearning4vb/deeplearning4j/deeplearning4j-scaleout/deeplearning4j-scaleout-parallelwrapper/src/main/java/org/deeplearning4j/parallelism/trainer/DefaultTrainer.vb
  • Cyclomatic Complexity · TestStatsClasses.testSbeStatsUpdateNullValues (cyclomatic 34) deeplearning4vb/deeplearning4j/deeplearning4j-ui-parent/deeplearning4j-ui-model/src/test/java/org/deeplearning4j/ui/stats/TestStatsClasses.vb
  • Cyclomatic Complexity · BaseNativeNDArrayFactory.createFromNpzFile (cyclomatic 34) deeplearning4vb/nd4j/nd4j-backends/nd4j-api-parent/nd4j-native-api/src/main/java/org/nd4j/nativeblas/BaseNativeNDArrayFactory.vb
  • Cyclomatic Complexity · BaseCudaDataBuffer.reallocate (cyclomatic 34) deeplearning4vb/nd4j/nd4j-backends/nd4j-backend-impls/nd4j-cuda/src/main/java/org/nd4j/linalg/jcublas/buffer/BaseCudaDataBuffer.vb
  • Cyclomatic Complexity · Configuration.loadResource (cyclomatic 33) deeplearning4vb/datavec/datavec-api/src/main/java/org/datavec/api/conf/Configuration.vb
  • Cyclomatic Complexity · CudnnLSTMHelper.activate (cyclomatic 33) deeplearning4vb/deeplearning4j/deeplearning4j-cuda/src/main/java/org/deeplearning4j/cuda/recurrent/CudnnLSTMHelper.vb
  • Cyclomatic Complexity · MergeVertex.getOutputType (cyclomatic 33) deeplearning4vb/deeplearning4j/deeplearning4j-nn/src/main/java/org/deeplearning4j/nn/conf/graph/MergeVertex.vb
  • Cyclomatic Complexity · Evaluation.eval (cyclomatic 33) deeplearning4vb/nd4j/nd4j-backends/nd4j-api-parent/nd4j-api/src/main/java/org/nd4j/evaluation/classification/Evaluation.vb
  • Cyclomatic Complexity · CudaExecutioner.calculateOutputShape (cyclomatic 33) deeplearning4vb/nd4j/nd4j-backends/nd4j-backend-impls/nd4j-cuda/src/main/java/org/nd4j/linalg/jcublas/ops/executioner/CudaExecutioner.vb
  • Cyclomatic Complexity · CnnSentenceDataSetIterator.next (cyclomatic 32) deeplearning4vb/deeplearning4j/deeplearning4j-nlp-parent/deeplearning4j-nlp/src/main/java/org/deeplearning4j/iterator/CnnSentenceDataSetIterator.vb
  • Cyclomatic Complexity · BatchNormalization.backpropGradient (cyclomatic 32) deeplearning4vb/deeplearning4j/deeplearning4j-nn/src/main/java/org/deeplearning4j/nn/layers/normalization/BatchNormalization.vb
  • Cyclomatic Complexity · DataVecDataSetFunction.call (cyclomatic 32) deeplearning4vb/deeplearning4j/deeplearning4j-scaleout/spark/dl4j-spark/src/main/java/org/deeplearning4j/spark/datavec/DataVecDataSetFunction.vb
  • Cyclomatic Complexity · BaseSparkEarlyStoppingTrainer.fit (cyclomatic 32) deeplearning4vb/deeplearning4j/deeplearning4j-scaleout/spark/dl4j-spark/src/main/java/org/deeplearning4j/spark/earlystopping/BaseSparkEarlyStoppingTrainer.vb
  • Cyclomatic Complexity · BaseNDArray.get (cyclomatic 32) deeplearning4vb/nd4j/nd4j-backends/nd4j-api-parent/nd4j-api/src/main/java/org/nd4j/linalg/api/ndarray/BaseNDArray.vb
  • Cyclomatic Complexity · SystemInfo.SystemInfo.Get (cyclomatic 32) deeplearning4vb/nd4j/nd4j-backends/nd4j-api-parent/nd4j-api/src/main/java/org/nd4j/systeminfo/SystemInfo.vb
  • Cyclomatic Complexity · BaseCpuDataBuffer.New.ctor (cyclomatic 32) deeplearning4vb/nd4j/nd4j-backends/nd4j-backend-impls/nd4j-native/src/main/java/org/nd4j/linalg/cpu/nativecpu/buffer/BaseCpuDataBuffer.vb
  • Cyclomatic Complexity · NearestVertexWalker.walk (cyclomatic 31) deeplearning4vb/deeplearning4j/deeplearning4j-nlp-parent/deeplearning4j-nlp/src/main/java/org/deeplearning4j/models/sequencevectors/graph/walkers/impl/NearestVertexWalker.vb
  • Cyclomatic Complexity · ComputationGraph.ffToLayerActivationsInWS (cyclomatic 31) deeplearning4vb/deeplearning4j/deeplearning4j-nn/src/main/java/org/deeplearning4j/nn/graph/ComputationGraph.vb
  • Cyclomatic Complexity · ComputationGraph.doEvaluationHelper (cyclomatic 31) deeplearning4vb/deeplearning4j/deeplearning4j-nn/src/main/java/org/deeplearning4j/nn/graph/ComputationGraph.vb
  • Cyclomatic Complexity · ConvolutionLayer.preOutput (cyclomatic 31) deeplearning4vb/deeplearning4j/deeplearning4j-nn/src/main/java/org/deeplearning4j/nn/layers/convolution/ConvolutionLayer.vb
  • Cyclomatic Complexity · CrashReportingUtil.generateMemoryStatus (cyclomatic 31) deeplearning4vb/deeplearning4j/deeplearning4j-nn/src/main/java/org/deeplearning4j/util/CrashReportingUtil.vb
  • Cyclomatic Complexity · LogFileWriter.encodeGraphStructure (cyclomatic 31) deeplearning4vb/nd4j/nd4j-backends/nd4j-api-parent/nd4j-api/src/main/java/org/nd4j/graph/ui/LogFileWriter.vb
  • Cyclomatic Complexity · BaseNDArray.doTad (cyclomatic 31) deeplearning4vb/nd4j/nd4j-backends/nd4j-api-parent/nd4j-api/src/main/java/org/nd4j/linalg/api/ndarray/BaseNDArray.vb
  • Cyclomatic Complexity · DocsGenerator.generateDocs (cyclomatic 30) deeplearning4vb/contrib/codegen-tools/codegen/src/main/java/org/nd4j/codegen/impl/java/DocsGenerator.vb
  • Cyclomatic Complexity · SVMLightRecordWriter.write (cyclomatic 30) deeplearning4vb/datavec/datavec-api/src/main/java/org/datavec/api/records/writer/impl/misc/SVMLightRecordWriter.vb
Rebuild cost: about €430,000 · Estimate
Cost to rebuild€140,000 to €720,000, for 2,406 to 7,631 hours of work, about 3.0 person-years for 1 to 6 engineers
Difficulty of the problemStandard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor×0.7 at a score of 50. 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.
SizeLarge: 180,953 lines of product code

How the estimate is made: Watchdog prices 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
Add a CI workflow that builds and runs the test suite on every push/PR.
Raises the score by about 12 points · Medium effort · CI/CD gates
2
Resolve the 2 Deprecated finding(s) in Dependency Hygiene — start with DeepLearning4VB.Tests.vbproj (2).
Raises the score by about 5 points · Low effort · Dependency Hygiene
3
Raise allocation-aware density on the hot paths — currently 49 use(s) across 657,209 production line(s) (~0.1/1k).
More of the idioms below on the allocation-heavy paths climbs this toward 10.
Raises the score by about 2 points · Medium effort · Allocation hygiene

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.

If you do one thing first · First action
Fix the build. The code didn't build, so the dimensions that need a working build were measured on an incomplete picture of the code, and every grade in this report is provisional. Once the build works, the next survey gives a final score. The compiler's first errors: BC30518: Overload resolution failed because no accessible 'createUninitialized' can be called with these arguments:; BC30518: Overload resolution failed because no accessible 'create' can be called with these arguments:; BC30456: 'Random' is not a member of 'Nd4vb'.; BC30002: Type 'ManagedNDArray' is not defined.; BC30456: 'factory' is not a member of 'Nd4vb'.
Based on: Solution Shape
Where the investment is most exposed · Value at risk
This code would cost about €430,000 to build again, about 3.0 person-years of work. Its weakest lens is Production Readiness, at 34 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.

Architecture — module dependency graph

Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways — a layering smell or cycle. A clean layered graph has none.

arch DeepLearning4VB DeepLearning4VB

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.

261 modules, with 839 dependencies between them. 8 loops run through 37 of the modules, marked above the diagonal.

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

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →1 JavaCompat2 org.datavec.api.records.metadata3 org.datavec.api.transform.quality.columns4 org.slf4j5 org.datavec.api.writable6 org.nd4vb.common.primitives7 org.nd4vb.linalg.api.shape8 org.datavec.api.conf9 org.datavec.api.records10 org.datavec.api.transform.metadata11 org.nd4vb.common.function12 org.nd4vb.linalg.api.ndarray13 org.datavec.api.split14 org.datavec.api.transform.schema15 org.nd4vb.linalg.api.memory16 org.datavec.api.records.reader17 org.datavec.api.records.writer18 org.datavec.api.transform.analysis19 org.datavec.api.transform.analysis.quality20 org.datavec.api.transform.condition21 org.nd4vb.linalg.api.buffer22 org.datavec.api.records.reader.impl23 org.datavec.api.records.reader.impl.filebatch24 org.datavec.api.records.reader.impl.inmemory25 org.datavec.api.records.writer.impl26 org.datavec.api.transform.filter27 org.datavec.api.transform.reduce28 org.nd4vb.linalg.api.ops29 org.datavec.api.records.reader.impl.csv30 org.datavec.api.records.reader.impl.jackson31 org.datavec.api.records.reader.impl.regex32 org.datavec.api.transform.sequence33 org.nd4vb.linalg.api.ops.executioner34 org.nd4vb.linalg.api.ops.impl.transforms35 org.datavec.api.transform36 org.nd4vb.linalg.factory37 org.datavec.api.records.reader.impl.transform38 org.datavec.api.transform.transforms39 org.nd4vb.linalg.managed40 org.datavec.local.transforms
1 JavaCompat
2 org.datavec.api.records.metadata
3 org.datavec.api.transform.quality.columns
4 org.slf4j
5 org.datavec.api.writable24
6 org.nd4vb.common.primitives1
7 org.nd4vb.linalg.api.shape15
8 org.datavec.api.conf312
9 org.datavec.api.records222
10 org.datavec.api.transform.metadata1111
11 org.nd4vb.common.function1
12 org.nd4vb.linalg.api.ndarray216
13 org.datavec.api.split11
14 org.datavec.api.transform.schema1231
15 org.nd4vb.linalg.api.memory22
16 org.datavec.api.records.reader3333312
17 org.datavec.api.records.writer231
18 org.datavec.api.transform.analysis121
19 org.datavec.api.transform.analysis.quality1221
20 org.datavec.api.transform.condition211
21 org.nd4vb.linalg.api.buffer4122
22 org.datavec.api.records.reader.impl44144449
23 org.datavec.api.records.reader.impl.filebatch2222322
24 org.datavec.api.records.reader.impl.inmemory2222324
25 org.datavec.api.records.writer.impl12111
26 org.datavec.api.transform.filter5411
27 org.datavec.api.transform.reduce54227
28 org.nd4vb.linalg.api.ops12202926
29 org.datavec.api.records.reader.impl.csv66739362
30 org.datavec.api.records.reader.impl.jackson22612123
31 org.datavec.api.records.reader.impl.regex221222212
32 org.datavec.api.transform.sequence2711
33 org.nd4vb.linalg.api.ops.executioner21245427
34 org.nd4vb.linalg.api.ops.impl.transforms161115
35 org.datavec.api.transform11414111225
36 org.nd4vb.linalg.factory1183531
37 org.datavec.api.records.reader.impl.transform22223222
38 org.datavec.api.transform.transforms3233
39 org.nd4vb.linalg.managed1233451123
40 org.datavec.local.transforms1511241142
Uses a module listed above itPart of a loopThe module itself
1 JavaCompat2 org.datavec.api.records.metadata3 org.datavec.api.transform.quality.columns4 org.slf4j5 org.datavec.api.writable6 org.nd4vb.common.primitives7 org.nd4vb.linalg.api.shape8 org.datavec.api.conf9 org.datavec.api.records10 org.datavec.api.transform.metadata11 org.nd4vb.common.function12 org.nd4vb.linalg.api.ndarray13 org.datavec.api.split14 org.datavec.api.transform.schema15 org.nd4vb.linalg.api.memory16 org.datavec.api.records.reader17 org.datavec.api.records.writer18 org.datavec.api.transform.analysis19 org.datavec.api.transform.analysis.quality20 org.datavec.api.transform.condition21 org.nd4vb.linalg.api.buffer22 org.datavec.api.records.reader.impl23 org.datavec.api.records.reader.impl.filebatch24 org.datavec.api.records.reader.impl.inmemory25 org.datavec.api.records.writer.impl26 org.datavec.api.transform.filter27 org.datavec.api.transform.reduce28 org.nd4vb.linalg.api.ops29 org.datavec.api.records.reader.impl.csv30 org.datavec.api.records.reader.impl.jackson31 org.datavec.api.records.reader.impl.regex32 org.datavec.api.transform.sequence33 org.nd4vb.linalg.api.ops.executioner34 org.nd4vb.linalg.api.ops.impl.transforms35 org.datavec.api.transform36 org.nd4vb.linalg.factory37 org.datavec.api.records.reader.impl.transform38 org.datavec.api.transform.transforms39 org.nd4vb.linalg.managed40 org.datavec.local.transformsJavaCompat1org.datavec.api.records.metadata2org.datavec.api.transform.quality.columns3org.slf4j4org.datavec.api.writable5org.nd4vb.common.primitives6org.nd4vb.linalg.api.shape7org.datavec.api.conf8org.datavec.api.records9org.datavec.api.transform.metadata10org.nd4vb.common.function11org.nd4vb.linalg.api.ndarray12org.datavec.api.split13org.datavec.api.transform.schema14org.nd4vb.linalg.api.memory15org.datavec.api.records.reader16org.datavec.api.records.writer17org.datavec.api.transform.analysis18org.datavec.api.transform.analysis.quality19org.datavec.api.transform.condition20org.nd4vb.linalg.api.buffer21org.datavec.api.records.reader.impl22org.datavec.api.records.reader.impl.filebatch23org.datavec.api.records.reader.impl.inmemory24org.datavec.api.records.writer.impl25org.datavec.api.transform.filter26org.datavec.api.transform.reduce27org.nd4vb.linalg.api.ops28org.datavec.api.records.reader.impl.csv29org.datavec.api.records.reader.impl.jackson30org.datavec.api.records.reader.impl.regex31org.datavec.api.transform.sequence32org.nd4vb.linalg.api.ops.executioner33org.nd4vb.linalg.api.ops.impl.transforms34org.datavec.api.transform35org.nd4vb.linalg.factory36org.datavec.api.records.reader.impl.transform37org.datavec.api.transform.transforms38org.nd4vb.linalg.managed39org.datavec.local.transforms4024115312222111112161112312233333122311211221211412244144449222232222223241211154115422712202926667393622261212322122221227112124542716111511414111225118353122223222323312334511231511241142+221 more modules (most-connected shown)

At a glance — Code Health · 78% · Adequate · gated by D18 ·

The Good
D4 · .NET / C# Code Duplication 9.7 D17 · .NET / C# Explicit Debt 9.7 GD1 · Repo Unfinished & placeholder code 10.0 X28 · Repo Index access outside its own emptiness guard 10.0
The Ugly
D18 · .NET / C# Solution Shape 3.0

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

The Good
D5 · .NET / C# Coupling 10.0 D6 · .NET / C# Cohesion (LCOM4) 9.5 D27 · .NET / C# Navigability 8.3 D35 · .NET / C# Change Coupling 10.0 AX10 · Repo Code composition 7.3 AX3 · Repo Project dependency cycles 10.0 AX4 · Repo Dependency direction 10.0 AX5 · Repo Architecture & structure 10.0 AX6 · Repo Interface segregation 9.4 AX8 · Repo Test isolation 10.0
The Ugly
D26 · .NET / C# Project Cohesion 0.0

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

The Good
D19 · .NET / C# Documentation Quality 9.0 D21 · .NET / C# Naming Consistency 10.0 M1 · Repo Documentation (README) 8.0 M3 · Repo Folder & project structure 10.0 M4 · Repo Documentation accuracy 8.0
The Ugly
M2 · Repo Architecture documentation 2.0

At a glance — Readiness · 34% · Weak · gated by P1, P3 ·

The Good
D12 · .NET / C# Dependency Hygiene 8.9 D13 · .NET / C# Secret Scanning 10.0 D14 · .NET / C# License Compliance 10.0
The Ugly
P1 · Repo CI/CD gates 0.0 P3 · Repo Security & performance tooling 0.0

At a glance — Security · 100% · Exemplary ·

The Good
D28 · .NET / C# Secrets (history) 10.0 D29 · .NET / C# Static Analysis (SAST) 10.0 D30 · .NET / C# Dependency Vulnerabilities 10.0 D44 · .NET / C# Platform End-of-Life 10.0

At a glance — Domain Modelling · 63% · Adequate · gated by DM4, DM11 ·

The Good
DM1 · Repo Aggregate boundaries 10.0 DM12 · Repo Ambient inputs in the domain 10.0 DM5 · Repo Encapsulated state 10.0 DM6 · Repo Domain ↔ infrastructure boundary 10.0 DM8 · Repo Value-object opportunities 10.0 DM9 · Repo Scattered domain decisions 10.0
The Ugly
DM11 · Repo Constructible invalid state 3.0 DM4 · Repo Rich vs anemic model 3.0

At a glance — Performance · 60% · Adequate ·

The Bad
PF2 · Repo Allocation hygiene 6.0

Roadmap

First, establish a CI workflow to automatically build and test every push or pull request to ensure immediate feedback on code changes. Next, resolve the two deprecated dependencies in the test project and improve allocation hygiene on hot paths by adopting more idioms to reduce resource usage. Finally, document significant design decisions in a dedicated folder to capture context and consequences, and refactor aggregates to prevent invalid states through guarded constructors or validation logic.

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

Do thisHelpsEffortDimension
Add a CI workflow that builds and runs the test suite on every push/PR.+12.1 ptsMediumCI/CD gates
Resolve the 2 Deprecated finding(s) in Dependency Hygiene — start with DeepLearning4VB.Tests.vbproj (2).+5.0 ptsLowDependency Hygiene
Raise allocation-aware density on the hot paths — currently 49 use(s) across 657,209 production line(s) (~0.1/1k). More of the idioms below on the allocation-heavy paths climbs this toward 10.+2.3 ptsMediumAllocation hygiene
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.+1.7 ptsMediumArchitecture documentation
Resolve the 1 Build failed finding(s) in Solution Shape.+0.7 ptsLowSolution Shape
Resolve the 9 EmptyCatchBlock finding(s) in Explicit Debt — start with JsonMappers.vb (2), Configuration.vb, CSVSequenceRecordReader.vb.+0.6 ptsLowExplicit Debt
Give each aggregate one way in that can refuse — a guarded constructor, value-object parameters that validate themselves, or a private constructor behind a factory that returns a failure.+1.2 ptsMediumConstructible invalid state
Move business rules onto the aggregates/entities they govern so invariants are enforced at the source, not in anemic services.+1.2 ptsMediumRich vs anemic model

File quality

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

FileScoreBandWorst signal
src/DeepLearning4VB/org/datavec/api/transform/serde/JsonMappers.vb4.9MixedExplicit Debt: EmptyCatchBlock
src/DeepLearning4VB/org/datavec/api/transform/sequence/window/OverlappingTimeWindowFunction.vb5.9MixedCode Duplication: Duplicated block (15 lines × 2)
src/DeepLearning4VB/org/nd4vb/linalg/api/ops/executioner/DefaultOpExecutioner.vb6.0MixedExplicit Debt: FixmeComment
src/DeepLearning4VB/org/nd4vb/linalg/api/shape/Shape.vb6.0MixedExplicit Debt: ObsoleteWithCallers
src/DeepLearning4VB/org/nd4vb/linalg/util/NDArrayUtil.vb6.0MixedExplicit Debt: ObsoleteWithCallers
src/DeepLearning4VB/org/nd4vb/linalg/api/ndarray/INDArray.vb6.4MixedExplicit Debt: TodoComment
src/DeepLearning4VB/org/nd4vb/linalg/indexing/Indices.vb6.7MixedExplicit Debt: FixmeComment
src/DeepLearning4VB/org/nd4vb/linalg/api/blas/impl/BaseLapack.vb6.7MixedExplicit Debt: TodoComment
src/DeepLearning4VB/org/datavec/api/transform/analysis/quality/QualityAnalysisAddFunction.vb6.7MixedExplicit Debt: TodoComment
src/DeepLearning4VB/org/datavec/api/transform/join/Join.vb6.9MixedExplicit Debt: ObsoleteWithCallers
src/DeepLearning4VB/org/nd4vb/linalg/util/Nd4vbValidator.vb6.9MixedExplicit Debt: TodoComment
src/DeepLearning4VB/org/nd4vb/linalg/managed/kernels/ManagedBlas.Level3.vb7.0MixedCode Duplication: Near-duplicate member pair (40 shared lines)
src/DeepLearning4VB/org/datavec/api/split/FileSplit.vb7.0MixedCode Duplication: Duplicated block (8 lines × 2)
src/DeepLearning4VB/org/nd4vb/linalg/managed/ManagedOpExecutioner.vb7.0MixedCode Duplication: Duplicated block (7 lines × 2)
src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseScalarBoolOp.vb7.0MixedCode Duplication: Duplicated block (5 lines × 4)
src/DeepLearning4VB/org/nd4vb/common/util/ArrayUtil.vb7.0MixedCode Duplication: Duplicated block (15 lines × 3)
src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseReduceBoolOp.vb7.1MixedCode Duplication: Members sharing a duplicated core (4 members, 50+ identical tokens)
src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/Conv2DConfig.vb7.1MixedCode Duplication: Members sharing a duplicated core (4 members, 50+ identical tokens)
src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/Conv3DConfig.vb7.2MixedCode Duplication: Duplicated block (39 lines × 2)
src/DeepLearning4VB/org/datavec/api/util/ClassPathResource.vb7.3MixedExplicit Debt: ObsoleteWithCallers

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

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

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

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

Could not be resolved — 38

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

Watchdog 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. 36 of 40 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 4 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.7 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.

Every figure here is one of three 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; ◐ Advisory — an LLM prose judgement. 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; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.

What we checked — 40 dimensions across the health lenses
D4D5D6D12D13D14D17D18D19D21D26D27D28D29D30D35D44AX10AX3AX4AX5AX6AX8DM1DM11DM12DM4DM5DM6DM8DM9GD1M1M2M3M4P1P3PF2X28

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, 265 of 276 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, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — 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
Watchdog duplication detector (in-process)Code duplication1.0.0✓ deterministic
Coverage (coverlet / dotnet-coverage)Line & branch coverage10.0.400✓ deterministic
NuGet / dotnetOutdated, vulnerable & deprecated dependencies10.0.400✓ deterministic
git / LibGit2SharpChurn hotspots, knowledge concentration, history2.43.0 · 0.31.0✓ deterministic
gitleaks · semgrep · trivySecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3✓ deterministic
LLM (sampled · advisory)Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurementLocal LLM◐ LLM · sampled · advisory

Every finding is locatable in findings.md. Run 01a15f55-b9c7-7923-b58e-073726090994.

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.

  • D1 Cyclomatic Complexity — not measured this run — Watchdog 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. Most of this repository's production source (.vb) had no cyclomatic complexity computed for it: no method bodies were exposed for those file kinds by any language model this pass could load.
  • D2 Cognitive Complexity — not measured this run — Watchdog 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. Most of this repository's production source (.vb) had no cognitive complexity computed for it: no method bodies were exposed for those file kinds by any language model this pass could load.
  • D4 Code Duplication — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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 123 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: .vb (566,031 lines, 100% 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.
  • D11 Test Reliability — not measured this run — Watchdog 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 MEASURED: the test run produced no results for any test tier, so no test ever ran and flakiness could not be exercised. The cause could not be attributed, so it is excluded from the score rather than read as an absence of tests.
  • D15 Churn × Complexity Hotspots — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. A hotspot is churn × complexity. Churn was measured (259799 line(s) across the 90-day window), but no complexity could be computed for .vb, which is most of this repository's production code — so every churned file would score as complexity 0 and the hotspot list would be empty no matter how tangled the code is. Not scored — this is a gap in the analysis run, not a finding about this repository.
  • D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-contributor repository — bus factor is not applicable (1 contributor(s) across 37 commit(s) sampled, automation and bot accounts excluded). Concentration needs a team to concentrate: with one contributor there is nobody to spread the knowledge to, so there is nothing here for the owner to act on.
  • D17 Explicit Debt — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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 89 deducted marker(s) and the 0.1/KLoC density on this row were taken over this repository's .NET projects ALONE: .vb (566,031 lines, 100% of production source) went unread, because every marker collector on this path is reached through a C# workspace. D17's marker collectors need a compiler we do not have for that language, so none of its nine marker kinds were read there. The debt in that source is UNMEASURED — its absence from the score above is a gap in this analyzer's language coverage, not a finding that the code carries none.
  • D22 Internal API Consistency — 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. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
  • D23 Boundary Type-Coupling — not measured this run — Watchdog 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. Large codebase (180,953 production LoC in the .NET projects) with no declared bounded contexts — cross-boundary type coupling is unassessed Bounded contexts cannot be inferred from a codebase that is not physically organised by them (D-321), so with none declared there are no boundaries for the coupling pass to measure across. You can widen what we reach: name this codebase's bounded contexts (≥2 module groups, e.g. per subsystem) so cross-boundary type coupling can 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"]`.
  • D34 Knowledge Freshness — 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. Too few commits to judge knowledge freshness (37 commit(s) sampled).
  • D39 IL Efficiency — not measured this run — Watchdog 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. IL NOT MEASURED: the analyzer's build of this repository exited 1 and the cause could not be attributed, so no assemblies were produced and there was no IL to read. We do not read it as a defect in the repository: an unattributed failure leans OURS. D18 owns the question of whether this repository builds; it was not answered here.
  • C1 Data Protection — not measured this run — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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.
  • IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
  • X1 Async correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X12 Unreachable branch — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X13 Undrained process stream — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X14 Bypassable address classification — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X15 Unvalidated length from an untrusted reader — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X16 Unfloored truncation loop — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X17 Uncapped recursion over a caller-supplied document — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X18 Disposal-pattern correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X19 Unrestored process-global state — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X2 Cancellation propagation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X20 Mistyped argument guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X21 Side-effecting pattern guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X22 Contradicted release guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X23 Unguarded diagnostic materialisation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X24 Document value interpolated into markup unescaped — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X25 Inert configuration knob — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X26 Unsynchronised callback handoff — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X27 Collection changed while being enumerated — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X29 Per-element action decided by a fixed element — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X3 Exception handling — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X30 Support guard that admits what it rejects — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X32 Type resolved by simple name across every loaded assembly — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X4 Structured logging — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X5 Nullable reference types — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • Production source was not modelled — run is Degraded — No code model read .vb, so the complexity, duplication and architecture dimensions were scored over a minority of this repository rather than its product, and dimensions that abstained did so for want of a model rather than for want of findings. The grade is NOT representative of this repository; diagnostics.md records the exact cause.

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

Limitations & what we did not check

Watchdog assesses the repository exactly as committed, and only the repository. By design it does 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.

  • 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.
  • D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
  • D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • 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.
  • D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
  • D19 Documentation Quality: Documentation quality is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
  • D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
  • 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 Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
  • 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.
  • DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
  • DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
  • M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.

The LLM boundary

LLM-set scores this run (4): D19, D21, D26, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score; each names its own sample and method on its card. They are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.

Dimensions

D4 · Code Duplication9.7 / 10Stronggated by 132 serious findings✓ Tool-verified

What it measures: Copy-pasted code that should be shared instead.

Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.

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

123 duplicated block group(s) detected. A further 9 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. Measured on part of this repository only: .vb (100% of production source) was not exposed to the token comparison, so duplication there is unmeasured and is not in this count.

Duplicated block (5 lines × 2) · ×17src/DeepLearning4VB/JavaCompat/Arrays.vb:148
Duplicated block (7 lines × 2) · ×12src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/transforms/custom/DotProductAttentionBp.vb:64
Duplicated block (6 lines × 2) · ×10src/DeepLearning4VB/org/datavec/api/transform/ui/components/RenderableComponentHistogram.vb:70
Duplicated block (9 lines × 2) · ×9src/DeepLearning4VB/org/nd4vb/linalg/indexing/Indices.vb:293
Duplicated block (15 lines × 2) · ×5src/DeepLearning4VB/org/nd4vb/linalg/managed/kernels/ManagedBlas.Level3.vb:77

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

What to do

  1. Resolve the 17 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with ReduceKernels.vb (2), Conv1D.vb (2), ArrayUtil.vb (2). — One of this dimension's main actionable groups (17 warning-level).
  2. Resolve the 12 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with BaseReduceBoolOp.vb (2), DotProductAttentionBp.vb, DoubleMetaData.vb. — One of this dimension's main actionable groups (12 warning-level).
  3. Resolve the 10 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with RenderableComponentHistogram.vb, BaseLapack.vb, InMemoryRecordReader.vb. — One of this dimension's main actionable groups (10 warning-level).
  4. Stand up a CI pipeline, then gate Code Duplication in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

D5 · Coupling10.0 / 10Exemplary✓ 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 10.0 / 10 · rule-coverage 100% · ceiling Prevented

4 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).

✓ On the Gold path — maintain.

Detailed fixes: d5_recommendation.md.

D6 · Cohesion (LCOM4)9.5 / 10Stronggated by 16 serious findings✓ Tool-verified

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

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

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

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

32 of 768 classes have LCOM4 above 3.

Low cohesion: DefaultOpExecutioner (LCOM4 12) · ×16src/DeepLearning4VB/org/nd4vb/linalg/api/ops/executioner/DefaultOpExecutioner.vb:84

What to do

  1. Resolve the 16 Low cohesion finding(s) in Cohesion (LCOM4) — start with DefaultOpExecutioner.vb, StringAnalysis.vb, RenderableComponentTable.vb. — One of this dimension's main actionable groups (16 warning-level).
  2. Stand up a CI pipeline, then gate Cohesion (LCOM4) in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

D12 · Dependency Hygiene8.9 / 10Strong✓ Tool-verified

What it measures: Whether dependencies are current, secure, and not bloated.

Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.

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

4 outdated, 0 vulnerable, 2 deprecated packages.

Deprecated: MSTest.TestAdapter · ×2tests/DeepLearning4VB.Tests/DeepLearning4VB.Tests.vbproj:24
Outdated: System.Text.Json · ×4

What to do

  1. Resolve the 2 Deprecated finding(s) in Dependency Hygiene — start with DeepLearning4VB.Tests.vbproj (2). — One of this dimension's main actionable groups (2 warning-level).
  2. Stand up a CI pipeline, then gate Dependency Hygiene in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

Detailed fixes: d12_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 108 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 4 direct `PackageReference`(s), and 104 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

D17 · Explicit Debt9.7 / 10Adequategated by 9 critical 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.7 / 10 · rule-coverage 100% · ceiling Prevented

89 deducted debt markers + 0 dead symbols across 180953 LoC in the .NET projects (0.1/KLoC) → score 9.7. Measured on the .NET source only: .vb (100% of production source) was not read, and carries at least 0 uncounted task marker(s) in 0 file(s).

EmptyCatchBlock · ×9src/DeepLearning4VB/org/datavec/api/conf/Configuration.vb:100
TodoComment · ×57src/DeepLearning4VB/org/datavec/api/records/reader/impl/csv/CSVNLinesSequenceRecordReader.vb:123
ObsoleteWithCallers · ×12src/DeepLearning4VB/org/datavec/api/transform/join/Join.vb:172
FixmeComment · ×7src/DeepLearning4VB/org/nd4vb/linalg/api/buffer/BaseDataBuffer.vb:746
BarePragmaDisable · ×3src/DeepLearning4VB/org/nd4vb/common/util/ObjectGraphSerializer.vb:160

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

What to do

  1. Resolve the 9 EmptyCatchBlock finding(s) in Explicit Debt — start with JsonMappers.vb (2), Configuration.vb, CSVSequenceRecordReader.vb. — One of this dimension's main actionable groups (9 issue-level).
  2. Resolve the 57 TodoComment finding(s) in Explicit Debt — start with INDArray.vb (19), Nd4vbValidator.vb (3), CSVNLinesSequenceRecordReader.vb. — One of this dimension's main actionable groups (57 warning-level).
  3. Resolve the 12 ObsoleteWithCallers finding(s) in Explicit Debt — start with Join.vb (3), ClassPathResource.vb (2), DefaultOpExecutioner.vb (2). — One of this dimension's main actionable groups (12 warning-level).
  4. Stand up a CI pipeline, then gate Explicit Debt in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D18 · Solution Shape3.0 / 10Weak✓ Tool-verified

What it measures: Whether the solution is laid out in a sensible, conventional structure.

Method: Solution structure: project count, decomposition, shell-project detection, build success (confirmed failures cap the score); traced to actual .sln files and binaries. Deterministic.

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

4 projects, 3542 source files, 219318 hand-written lines of code (180953 production / 38365 test — the split is derived per file: test is what its project, its own path, or a compile-guarded region marks as test, and a file carrying no test signal counts as production), 2 inter-project edges (build failed).

Build failed

What to do

  1. Resolve the 1 Build failed finding(s) in Solution Shape. — One of this dimension's main actionable groups (1 warning-level).

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

D19 · Documentation QualityExemplary◐ Sampled · advisory

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

Method: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.

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

The repository's root README (DeepLearning4VB) is a clear, well-structured overview of the project: it states what the port is (a VB.NET .NET Framework 4.8.1/.NET 10 deep learning library built with VS2026), its current status (early stage; 975 tests pass on both targets), component naming conventions, requirements (VS2026 + .NET SDK 10.0.100 + .NET Framework 4.8.1 Developer Pack), build/test commands, and a repository layout table that clips mid-sentence before the full overview is shown. The tools/porting README documents the porting scripts in its directory (not the main repo) with Op class conversion details, phase-2 milestones, and run_convert command examples; it does not claim to explain what the project itself does or how to use the library beyond the root README. PHASE2_DESIGN.md is a detailed architecture document for the managed ND4VB tensor engine, covering goal, two-phase design (port Java API vs write a managed backend), milestones, and op-inventory tables; it clips mid-sentence before the full outline sections appear. All four documents are well-structured with clear headings and clip markers, so any truncation is not penalized.

Documentation: no architecture or design documentationREADME.md

✓ On the Gold path — maintain.

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

D21 · Naming ConsistencyExemplary◐ Sampled · advisory

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

Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.

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

0 naming inconsistencies across 0 sampled symbols.

✓ On the Gold path — maintain.

Detailed fixes: d21_recommendation.md.

D26 · Project Cohesion0.0 / 10Critical✓ 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, LLM-independent.

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

1 of 2 projects flagged as possibly oversized/incoherent.

Split DeepLearning4VB(net481)

What to do

  1. Resolve the 1 Split DeepLearning4VB(net481) finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).

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

D27 · Navigability8.3 / 10Strong✓ Tool-verified

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

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

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

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

70 % of calls cross a namespace and 7 % go through an interface, but 94 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: large — vertical-slice locality expected.

What to do

  1. Improve Navigability — currently 8.3/10. — 70 % of calls cross a namespace and 7 % go through an interface, but 94 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: large — vertical-slice locality expected.

Detailed fixes: d27_recommendation.md.

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d28_recommendation.md.

D29 · Static Analysis (SAST)10.0 / 10Exemplary○ Nothing flagged

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

semgrep found no security issues. semgrep hit a parse error in 3 file(s) — `src/DeepLearning4VB/org/nd4vb/linalg/string/NDArrayStrings.vb`, `unported/nd4j/nd4j-backends/nd4j-api-parent/nd4j-api/src/main/java/org/nd4j/ir/MapperNamespace.vb`, `unported/nd4j/nd4j-backends/nd4j-api-parent/nd4j-api/src/main/java/org/nd4j/ir/TensorNamespace.vb` — so no absence of findings in them is evidence of anything, and nothing in them was analysed. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.

✓ On the Gold path — maintain.

Detailed fixes: d29_recommendation.md.

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d30_recommendation.md.

D35 · Change Coupling10.0 / 10Exemplary✓ 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 10.0 / 10 · rule-coverage 100% · ceiling Documented

No strong hidden change-coupling between production files.

✓ On the Gold path — maintain.

Detailed fixes: d35_recommendation.md.

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

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

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

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

0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 2 platform declaration(s) and 0 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 composition7.3 / 10Strong✓ 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.

What to do

  • The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
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.

AX5 · Architecture & structure10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.

Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.

AX6 · Interface segregation9.4 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').

Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.

  • `Table(Of R, C, V)` declares 19 members: `contains`, `containsRow`, `containsColumn`, `containsValue`, `get`, `isEmpty`, `size`, `clear`, `put`, `putAll`, `remove`, `row`, `column`, `cellSet`, `rowKeySet`, `columnKeySet`, `values`, `rowMap`, `columnMap`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/DeepLearning4VB/JavaCompat/Table.vb:47
  • `RecordReader` declares 16 members under just 12 distinct name(s): `initialize`, `initialize`, `batchesSupported`, `next`, `next`, `hasNext`, `Labels`, `reset`, `resetSupported`, `record`, `nextRecord`, `loadFromMetaData`, `loadFromMetaData`, `Listeners`, `setListeners`, `setListeners`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. That is an OVERLOAD SET, not 16 separate responsibilities: a caller binds to 12 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 16 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface. — src/DeepLearning4VB/org/datavec/api/records/reader/RecordReader.vb:39
  • `Level1` declares 19 members under just 13 distinct name(s): `dot`, `dot`, `nrm2`, `asum`, `asum`, `iamax`, `iamax`, `iamax`, `iamin`, `swap`, `copy`, `copy`, `axpy`, `axpy`, `rotg`, `rot`, `rotmg`, `scal`, `supportsDataBufferL1Ops`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. That is an OVERLOAD SET, not 19 separate responsibilities: a caller binds to 13 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 19 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface. — src/DeepLearning4VB/org/nd4vb/linalg/api/blas/Level1.vb:26
  • `Level2` declares 16 members: `gemv`, `gbmv`, `ger`, `sbmv`, `spmv`, `spr`, `spr2`, `symv`, `syr`, `syr2`, `tbmv`, `tbsv`, `tpmv`, `tpsv`, `trmv`, `trsv`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/DeepLearning4VB/org/nd4vb/linalg/api/blas/Level2.vb:25
  • `DataBuffer` declares 76 members: `GenerationId`, `sameUnderlyingData`, `read`, `write`, `array`, `dirty`, `underlyingDataBuffer`, `originalDataBuffer`, `copyAtStride`, `getAllocationMode`, `persist`, `isPersist`, `unPersist`, `ElementSize`, `removeReferencing`, `references`, `addReferencing`, `assign`, `assign`, `assign`, `assign`, `getDoublesAt`, `getFloatsAt`, `getIntsAt`, `getLongsAt`, `getDoublesAt`, `getFloatsAt`, `getIntsAt`, `getLongsAt`, `assign`, `assign`, `setData`, `setData`, `setData`, `setData`, `setData`, `setData`, `setData`, `asBytes`, `dataType`, and 36 more. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 76 declarations carry 51 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 51 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/DeepLearning4VB/org/nd4vb/linalg/api/buffer/DataBuffer.vb:53
  • `DataBufferFactory` declares 126 members: `setAllocationMode`, `allocationMode`, `create`, `create`, `createDouble`, `createSame`, `createSame`, `createFloat`, `createInt`, `createDouble`, `createFloat`, `createInt`, `createDouble`, `createDouble`, `createDouble`, `createFloat`, `createFloat`, `createInt`, `createDouble`, `createFloat`, `createFloat`, `createInt`, `createDouble`, `createFloat`, `createInt`, `createDouble`, `createFloat`, `createInt`, `createDouble`, `createFloat`, `createInt`, `createDouble`, `createDouble`, `createDouble`, `createFloat`, `createFloat`, `createFloat`, `create`, `create`, `createInt`, and 86 more. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 126 declarations carry 23 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 23 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/DeepLearning4VB/org/nd4vb/linalg/api/buffer/factory/DataBufferFactory.vb:40
  • `MemoryManager` declares 20 members: `CurrentWorkspace`, `notifyScopeEntered`, `notifyScopeLeft`, `invokeGcOccasionally`, `invokeGc`, `togglePeriodicGc`, `toggleAveraging`, `PeriodicGcActive`, `LastGcTime`, `OccasionalGcFrequency`, `AverageLoopTime`, `AutoGcWindow`, `collect`, `purgeCaches`, `memcpy`, `memset`, `scopeOutOfWorkspaces`, `BandwidthUse`, `allocatedMemory`, `releaseCurrentContext`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/DeepLearning4VB/org/nd4vb/linalg/api/memory/MemoryManager.vb:35
  • `MemoryWorkspace` declares 25 members: `WorkspaceConfiguration`, `WorkspaceType`, `Id`, `DeviceId`, `ThreadId`, `GenerationId`, `PrimaryOffset`, `notifyScopeEntered`, `notifyScopeBorrowed`, `notifyScopeLeft`, `ScopeActive`, `initializeWorkspace`, `destroyWorkspace`, `destroyWorkspace`, `toggleWorkspaceUse`, `ThisCycleAllocations`, `enableDebug`, `LastCycleAllocations`, `MaxCycleAllocations`, `CurrentSize`, `close`, `ParentWorkspace`, `tagOutOfScopeUse`, `PreviousWorkspace`, `CurrentOffset`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 25 declarations carry 24 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 24 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/DeepLearning4VB/org/nd4vb/linalg/api/memory/MemoryWorkspace.vb:17
  • `MemoryWorkspaceManager` declares 24 members: `UUID`, `DebugMode`, `DefaultWorkspaceConfiguration`, `createNewWorkspace`, `createNewWorkspace`, `createNewWorkspace`, `createNewWorkspace`, `WorkspaceForCurrentThread`, `getWorkspaceForCurrentThread`, `getWorkspaceForCurrentThread`, `setWorkspaceForCurrentThread`, `destroyWorkspace`, `destroyAllWorkspacesForCurrentThread`, `destroyWorkspace`, `AndActivateWorkspace`, `getAndActivateWorkspace`, `getAndActivateWorkspace`, `checkIfWorkspaceExists`, `checkIfWorkspaceExistsAndActive`, `scopeOutOfWorkspaces`, `printAllocationStatisticsForCurrentThread`, `AllWorkspacesIdsForCurrentThread`, `AllWorkspacesForCurrentThread`, `anyWorkspaceActiveForCurrentThread`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 24 declarations carry 18 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 18 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/DeepLearning4VB/org/nd4vb/linalg/api/memory/MemoryWorkspaceManager.vb:29
  • `INDArray` declares 343 members: `shapeInfoToString`, `shapeInfoDataBuffer`, `View`, `Sparse`, `Compressed`, `markAsCompressed`, `rank`, `stride`, `elementWiseStride`, `getDoubleUnsafe`, `getString`, `putScalarUnsafe`, `vectorsAlongDimension`, `vectorAlongDimension`, `tensorsAlongDimension`, `tensorAlongDimension`, `cumsumi`, `cumsum`, `assign`, `assignIf`, `replaceWhere`, `putScalar`, `putScalar`, `putScalar`, `putScalar`, `putScalar`, `putScalar`, `putScalar`, `putScalar`, `putScalar`, `putScalar`, `lt`, `putScalar`, `putScalar`, `eps`, `eq`, `gt`, `gte`, `lte`, `lt`, and 303 more. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 343 declarations carry 216 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 216 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/DeepLearning4VB/org/nd4vb/linalg/api/ndarray/INDArray.vb:55
  • `CustomOp` declares 41 members: `opName`, `opHash`, `InplaceCall`, `outputArguments`, `inputArguments`, `iArgs`, `tArgs`, `bArgs`, `dArgs`, `addTArgument`, `sArgs`, `addIArgument`, `addIArgument`, `addBArgument`, `addDArgument`, `removeIArgument`, `addSArgument`, `removeSArgument`, `getSArgument`, `getBArgument`, `getIArgument`, `numIArguments`, `removeTArgument`, `getTArgument`, `numTArguments`, `numBArguments`, `numDArguments`, `numSArguments`, `addInputArgument`, `removeInputArgument`, `getInputArgument`, `numInputArguments`, `addOutputArgument`, `removeOutputArgument`, `getOutputArgument`, `numOutputArguments`, `calculateOutputShape`, `calculateOutputShape`, `Descriptor`, `assertValidForExecution`, and 1 more. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 41 declarations carry 39 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 39 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/DeepLearning4VB/org/nd4vb/linalg/api/ops/CustomOp.vb:29
  • `OpContext` declares 32 members: `setIArguments`, `getIArguments`, `numIArguments`, `setTArguments`, `getTArguments`, `numTArguments`, `setDArguments`, `getDArguments`, `numDArguments`, `setBArguments`, `getBArguments`, `numBArguments`, `setRngStates`, `RngStates`, `setInputArray`, `setInputArrays`, `setInputArrays`, `getInputArrays`, `numInputArguments`, `getInputArray`, `setOutputArray`, `setOutputArrays`, `setOutputArrays`, `getOutputArrays`, `getOutputArray`, `numOutputArguments`, `markInplace`, `allowHelpers`, `shapeFunctionOverride`, `getExecutionMode`, `setExecutionMode`, `purge`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 32 declarations carry 30 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 30 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/DeepLearning4VB/org/nd4vb/linalg/api/ops/OpContext.vb:18
  • `Aggregate` declares 17 members: `name`, `opNum`, `FinalResult`, `Arguments`, `Shapes`, `IndexingArguments`, `RealArguments`, `IntArrayArguments`, `maxArguments`, `maxShapes`, `maxIntArrays`, `maxIntArraySize`, `maxIndexArguments`, `maxRealArguments`, `RequiredBatchMemorySize`, `SharedMemorySize`, `ThreadsPerInstance`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/DeepLearning4VB/org/nd4vb/linalg/api/ops/aggregates/Aggregate.vb:33
  • `OpExecutioner` declares 61 members: `Verbose`, `Debug`, `type`, `LastOp`, `exec`, `exec`, `execAndReturn`, `execAndReturn`, `execAndReturn`, `execAndReturn`, `execAndReturn`, `exec`, `exec`, `exec`, `exec`, `execAndReturn`, `exec`, `exec`, `exec`, `exec`, `exec`, `exec`, `exec`, `EnvironmentInformation`, `setProfilingMode`, `getProfilingMode`, `ProfilingConfig`, `TADManager`, `printEnvironmentInformation`, `push`, `commit`, `thresholdEncode`, `thresholdEncode`, `thresholdDecode`, `bitmapEncode`, `bitmapEncode`, `bitmapDecode`, `CustomOperations`, `execAndReturn`, `exec`, and 21 more. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 61 declarations carry 34 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 34 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/DeepLearning4VB/org/nd4vb/linalg/api/ops/executioner/OpExecutioner.vb:38
  • `Random` declares 35 members under just 14 distinct name(s): `setSeed`, `getSeed`, `setSeed`, `setSeed`, `nextBytes`, `nextInt`, `nextInt`, `nextInt`, `nextLong`, `nextBoolean`, `nextFloat`, `nextDouble`, `nextGaussian`, `nextGaussian`, `nextGaussian`, `nextGaussian`, `nextGaussian`, `nextDouble`, `nextDouble`, `nextDouble`, `nextDouble`, `nextFloat`, `nextFloat`, `nextFloat`, `nextFloat`, `nextInt`, `nextInt`, `nextInt`, `nextInt`, `Position`, `reSeed`, `reSeed`, `rootState`, `nodeState`, `setStates`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. That is an OVERLOAD SET, not 35 separate responsibilities: a caller binds to 14 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 35 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface. — src/DeepLearning4VB/org/nd4vb/linalg/api/rng/Random.vb:35
  • `Distribution` declares 18 members under just 13 distinct name(s): `probability`, `density`, `cumulativeProbability`, `cumulativeProbability`, `inverseCumulativeProbability`, `NumericalMean`, `NumericalVariance`, `SupportLowerBound`, `SupportUpperBound`, `SupportLowerBoundInclusive`, `SupportUpperBoundInclusive`, `SupportConnected`, `reseedRandomGenerator`, `sample`, `sample`, `sample`, `sample`, `sample`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. That is an OVERLOAD SET, not 18 separate responsibilities: a caller binds to 13 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 18 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface. — src/DeepLearning4VB/org/nd4vb/linalg/api/rng/distribution/Distribution.vb:31
  • `BlasWrapper` declares 39 members: `swap`, `level1`, `level2`, `level3`, `lapack`, `scal`, `scal`, `copy`, `axpy`, `axpy`, `axpy`, `dot`, `nrm2`, `asum`, `iamax`, `gemv`, `gemv`, `gemv`, `ger`, `ger`, `ger`, `gesv`, `checkInfo`, `sysv`, `syev`, `syevx`, `syevx`, `syevd`, `syevr`, `syevr`, `syevr`, `posv`, `geev`, `sygvd`, `gelsd`, `geqrf`, `ormqr`, `saxpy`, `saxpy`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 39 declarations carry 28 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 28 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/DeepLearning4VB/org/nd4vb/linalg/factory/BlasWrapper.vb:36
  • `Environment` declares 28 members: `blasMajorVersion`, `blasMinorVersion`, `blasPatchVersion`, `Verbose`, `Debug`, `Profiling`, `DetectingLeaks`, `DebugAndVerbose`, `LeaksDetector`, `helpersAllowed`, `allowHelpers`, `tadThreshold`, `setTadThreshold`, `elementwiseThreshold`, `setElementwiseThreshold`, `maxThreads`, `setMaxThreads`, `maxMasterThreads`, `setMaxMasterThreads`, `MaxPrimaryMemory`, `MaxSpecialMemory`, `MaxDeviceMemory`, `CPU`, `setGroupLimit`, `setDeviceLimit`, `getGroupLimit`, `getDeviceLimit`, `getDeviceCouner`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/DeepLearning4VB/org/nd4vb/linalg/factory/Environment.vb:29
  • `NDArrayFactory` declares 195 members: `blas`, `lapack`, `level1`, `level2`, `level3`, `createBlas`, `createLevel1`, `createLevel2`, `createLevel3`, `createLapack`, `setOrder`, `setDType`, `create`, `order`, `dtype`, `toFlattened`, `toFlattened`, `toFlattened`, `bilinearProducts`, `toFlattened`, `toFlattened`, `eye`, `rot90`, `rot`, `reverse`, `arange`, `copy`, `rand`, `rand`, `rand`, `appendBias`, `create`, `create`, `concat`, `specialConcat`, `pullRows`, `pullRows`, `pullRows`, `pullRows`, `shuffle`, and 155 more. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 195 declarations carry 47 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 47 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/DeepLearning4VB/org/nd4vb/linalg/factory/NDArrayFactory.vb:50
  • `WorkspaceMgr(Of T)` declares 24 members: `setWorkspaceName`, `getWorkspaceName`, `setWorkspace`, `setConfiguration`, `getConfiguration`, `ScopedOutFor`, `isScopedOut`, `hasConfiguration`, `notifyScopeEntered`, `notifyScopeEntered`, `notifyScopeBorrowed`, `isWorkspaceOpen`, `assertOpen`, `assertNotOpen`, `assertCurrentWorkspace`, `leverageTo`, `validateArrayLocation`, `create`, `create`, `createUninitialized`, `createUninitialized`, `dup`, `dup`, `castTo`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 24 declarations carry 20 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 20 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/DeepLearning4VB/org/nd4vb/linalg/workspace/WorkspaceMgr.vb:35

What to do

  • Split fat interfaces into focused role-interfaces so clients depend only on what they use.
  • Where the width is an overload set rather than separate responsibilities, collapse the overloads instead — segregating those relieves no caller.
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.

DM1 · Aggregate boundaries10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether aggregates reference each other by identity (id) rather than by direct object reference — the core DDD consistency-boundary rule.

Method: Roslyn (DDD-gated): aggregate roots identified by convention; each aggregate field checked for direct references to other aggregates versus id-only. Deterministic, DDD-native.

Coverage: Population: aggregate roots identified by AggregateRoot/IAggregateRoot base/interface NAME convention; reference-by-identity then checked exhaustively within that set — a root not using those names is invisible.

DM11 · Constructible invalid state3.0 / 10Weak✓ Tool-verified

Other · Domain Modelling — Whether an aggregate can be constructed in a state its own rules forbid — a public constructor that takes a raw primitive, stores it, and validates nothing, with no factory beside it. A constructor taking only value objects is not counted: each parameter has already validated itself.

Method: Neutral surface (DDD-gated): each non-abstract entity/aggregate checked for a PUBLIC constructor taking at least one RAW PRIMITIVE parameter whose body contains no guard token (throw / Guard. / Ensure. / ArgumentException / CheckRule), on a type that also offers no static Create/Of/From/New factory. A constructor taking only value objects is never charged -- measured: 64 of 87 unguarded public constructors on the C# corpus take value objects only, so ignoring parameter types would be 73% false positives. One finding per entity. Deterministic.

  • `AggregateAxpy`'s public constructor takes `alpha` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `AggregateAxpy` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — src/DeepLearning4VB/org/nd4vb/linalg/api/ops/aggregates/impl/AggregateAxpy.vb:36
  • `AggregateGEMM`'s public constructor takes `Order`, `TransA`, `TransB`, `M`, … as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `AggregateGEMM` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — src/DeepLearning4VB/org/nd4vb/linalg/api/ops/aggregates/impl/AggregateGEMM.vb:38

What to do

  • Give each aggregate one way in that can refuse — a guarded constructor, value-object parameters that validate themselves, or a private constructor behind a factory that returns a failure.
DM12 · Ambient inputs in the domain10.0 / 10Exemplary○ Nothing flagged

Other · Domain Modelling — Whether domain types receive the time and randomness their rules depend on, rather than reading the process clock or a global random source directly — an ambient read makes the rule it feeds untestable at the instant that matters and lets two reads inside one operation disagree.

Method: Roslyn (DDD-gated, C#/VB only): domain-layer types scanned for ambient reads — DateTime/DateTimeOffset.Now/UtcNow/Today, Random.Shared, new Random(), Stopwatch.GetTimestamp — resolved against the semantic model, with a comment/string-stripped token fallback only where resolution fails. Body reads are scored; field/property initialisers are surfaced unscored. Apply/When folds excluded (ES1 owns them). Deterministic, symbol-resolved.

DM4 · Rich vs anemic model3.0 / 10Weak✓ Tool-verified

Other · Domain Modelling — Whether aggregates/entities carry the behaviour that protects their invariants, rather than being data bags driven by external services.

Method: Roslyn (DDD-gated): entity method BODIES classified mutator-vs-query — only methods that mutate the entity's own declared state count as invariant-protecting behaviour, so a getter/passthrough doesn't rescue an anemic class. Deterministic, exhaustive over domain-layer entities.

Coverage: Population: entities by name/base convention; rich-vs-anemic judged by classifying each method body mutator-vs-query — logic-bearing domain types outside the convention are invisible.

  • `AggregateAxpy` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/DeepLearning4VB/org/nd4vb/linalg/api/ops/aggregates/impl/AggregateAxpy.vb:31
  • `AggregateGEMM` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/DeepLearning4VB/org/nd4vb/linalg/api/ops/aggregates/impl/AggregateGEMM.vb:31

What to do

  • Move business rules onto the aggregates/entities they govern so invariants are enforced at the source, not in anemic services.
DM5 · Encapsulated state10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether entities protect their state — private/init-only setters, and collections handed out as read-only views rather than the mutable backing collection — instead of exposing writable state that bypasses invariants. Softened when a rehydration framework (Marten/EF) is present.

Method: Roslyn (DDD-gated): entities scanned for publicly writable state — public setters, and (C#/VB) own mutable collections handed out through an auto-property, a public field or a bare-field expression getter, where a computed/copying getter is never charged. One finding per entity; score softened when Marten/EF rehydration frameworks present. Deterministic, framework-aware.

Coverage: Population: entities by convention; encapsulation (setter shape) checked exhaustively within the set.

DM6 · Domain ↔ infrastructure boundary10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether the domain layer stays free of infrastructure dependencies (EF/Marten/HTTP/ASP.NET) — the clean-architecture dependency rule.

Method: Roslyn (DDD-gated): domain-layer types scanned for infrastructure usage in member SIGNATURES and inside method/accessor BODIES — resolved calls and object-creations into EF/Marten/HTTP/Mongo/Redis/message-bus types (not just a namespace allowlist). Deterministic, symbol-resolved, exhaustive over domain-layer bodies, DDD-native.

Coverage: Domain layer identified by NAMESPACE heuristic; infrastructure then resolved by symbol in member SIGNATURES and method/accessor BODIES — rename the layer and the check evaporates.

DM8 · Value-object opportunities10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether clusters of primitives that travel together (a missing value object) are extracted — a low-weight suggestion, LLM-confirmed when configured.

Method: Roslyn (DDD-gated): primitive parameter clusters recurring three or more times across signatures extracted, then confirmed by language model when configured. Advisory, low-weight.

DM9 · Scattered domain decisions10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether one domain rule is decided — or one measurement produced — in more than one place, rather than living on the type that owns it.

Method: Neutral body surface plus Roslyn (DDD-gated), two arms. DECISION (Roslyn only): a predicate over a domain type's members judged in two or more types, where none of those decisions live on the owning type — operands of comparisons and relational property patterns only, so a member merely passed as an argument is not judged. DERIVATION: a plain all-numeric carrier of ≥2 members, with no base type and exactly one constructor, CONSTRUCTED as the result of a method (returned or assigned, never inline as an argument) in two or more types other than its own — the same measurement produced twice, which centralising the judgement does not fix. DERIVATION runs on every language whose frontend declares the produced-or-passed fact per construction (Roslyn and the Java sidecar today); a target with only the derivation arm carries an engine gap naming the decision arm as not assessed, and a frontend that declares nothing keeps the dimension not measured rather than clean. Single-member rules, test code and generated code are out of population for both. Advisory.

GD1 · Unfinished & placeholder code10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Unreviewed-generation residue: shipped members still throwing NotImplementedException, and placeholder string literals left in non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.

Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.

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

Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.

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

What to do

  • Add a README to the 2 of 2 project(s) that lack one — worth up to 2 pts.
M2 · Architecture documentation2.0 / 10Critical✓ Tool-verified

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

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

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

What to do

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

Maturity · Maturity — Whether the repo is organised deliberately — src/test separation and consistent project naming.

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

M4 · Documentation accuracy8.0 / 10Strong◐ Sampled · advisory

Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).

Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.

  • README advertises a microservices architecture, but the repo is a single project with no service manifests — searched for: `microservice`, `service-mesh`, `istio`. Each was matched case- and separator-insensitively against file and directory NAMES anywhere in the tree, and against the CONTENTS of manifest and configuration files (package.json and other *.json, *.csproj, *.props, *.sln/*.slnx, *.yml, *.toml, *.config, tool configs such as eslint.config.js, Dockerfile); the README's own prose never counts, so a claim is never refuted by merely being made. Nothing outside that search was read — a footprint living only in a submodule, in a file type not listed here, or under a name none of those terms matches is not seen, and this row is then wrong. — README.md:140

What to do

  • Reconcile the README with reality: README advertises a microservices architecture, but the repo is a single project with no service manifests.
P1 · CI/CD gates0.0 / 10Critical✓ Tool-verified

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.

  • No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.

What to do

  • Add a CI workflow that builds and runs the test suite on every push/PR.
P3 · Security & performance tooling0.0 / 10Critical✓ Tool-verified

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

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

  • No static application security testing detected. For this repository's stack, add a Roslyn security analyzer package referenced from the project (the analyzer packages do analyse VB.NET), plus gitleaks for committed secrets — CodeQL has no VB.NET extractor, so its csharp pack would extract nothing from this tree and then report it clean — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 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.

What to do

  • Run what this repository's stack ships: a Roslyn security analyzer package referenced from the project (the analyzer packages do analyse VB.NET), plus gitleaks for committed secrets — CodeQL has no VB.NET extractor, so its csharp pack would extract nothing from this tree and then report it clean — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
  • Enable Dependabot/Renovate or a dependency-review gate.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
PF2 · Allocation hygiene6.0 / 10Adequate✓ Tool-verified

Readiness · Performance — Whether the code is written to minimise allocations so it doesn't pressure its host's memory manager — buffer/slice views over copies, object pooling, stack or value-type allocation, and buffer writers. Reward-only: credited where present, never penalised where a simpler style is fine.

Method: Production-source scan: density (per 1k LoC) of allocation-aware APIs — in .NET Span/Memory, ArrayPool/ObjectPool, stackalloc, ValueTask, value-type structs, IBufferWriter, string.Create, SkipLocalsInit; off .NET, with comments and strings blanked, Go's sync.Pool, preallocated slices/maps, Grow, strconv.Append* and buf[:0] reuse; the JVM's NIO buffer views, MemorySegment, primitive collections, pools and literal presizes (plus Kotlin primitive arrays and value classes, Scala AnyVal and @specialized); Swift's reserveCapacity, ContiguousArray, withUnsafe* access and ~Copyable. Activated off .NET on the same floor (400 lines, and benchmarks or 8 uses); Rust and garbage-collected scripting languages are not applicable. Reward-only. Deterministic, syntax/text detection.

What to do

  • Raise allocation-aware density on the hot paths — currently 49 use(s) across 657,209 production line(s) (~0.1/1k). More of the idioms below on the allocation-heavy paths climbs this toward 10.
  • Visual Basic: on hot paths, work through Span(Of T)/Memory(Of T) (AsSpan/AsMemory) instead of copies, rent buffers from ArrayPool(Of T), return ValueTask from completions that are usually synchronous, write through IBufferWriter(Of T), and presize List/StringBuilder/Dictionary.
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged

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

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

Reference — by lens

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

LensScoreRatingImpact
Code Health78%Adequate — gated by D18Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture86%Adequate — gated by D26Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity61%Adequate — gated by M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness34%Weak — gated by P1, P3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security100%ExemplaryStrongest area.
Domain Modelling63%Adequate — gated by DM4, DM11Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance60%AdequateAcceptable, with room to improve.
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.

  • SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Not evidenced — 6 control(s) we could not find positive evidence for

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

  • C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
  • P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
Not included — 84 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.
  • AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
  • AX1 Captive dependencies — no DI registrations detected
  • AX2 Stateful singletons — no singleton implementations detected
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
  • AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • D1 Cyclomatic Complexity — cyclomatic complexity not measured — .vb exposed no member bodies
  • D10 Test Quality — ~205143 lines of test source are present (.vb) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
  • D11 Test Reliability — Test reliability not measured — no test run produced results
  • D15 Churn × Complexity Hotspots — complexity unreadable for .vb — churn × complexity hotspots could not be measured
  • D16 Bus Factor — single-contributor repository — bus factor is not applicable
  • D2 Cognitive Complexity — cognitive complexity not measured — .vb exposed no member bodies
  • 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.
  • D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
  • D23 Boundary Type-Coupling — Cross-context type coupling could not be assessed — this codebase's bounded contexts are neither declared nor inferable.
  • D24 Comment Value — No inline comments to assess — comment value is not applicable here.
  • D25 ADR Conformance — no ADRs to check
  • D3 God Classes — Most of this repository's production source (.vb) was not read by god-class detection, so class size was not assessed for the languages that are the product — whatever else this pass did read is not this repository's class size. Not scored — this is a gap in the analyzer, not a verdict about this repository.
  • D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
  • D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
  • D34 Knowledge Freshness — too few commits to judge knowledge freshness
  • D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
  • 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.
  • D39 IL Efficiency — IL not measured — the analyzer's build of the target did not succeed
  • 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 Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
  • D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
  • D8 Code Coverage — Coverage NOT MEASURED: `--collect:"XPlat Code Coverage"` names a data collector that ships in the `coverlet.collector` package, and this repository wires up none — no test project references it and no runsettings declares one. The absence of coverage here is therefore not evidence about the suite or about our analyzer environment: without a collector, `--collect` produces nothing even from a suite that builds and passes. Add a `coverlet.collector` PackageReference to the test project(s) (or commit the Cobertura/OpenCover/lcov report your CI produces) and real coverage will be measured. It is excluded from the score rather than counted as a near-zero defect.
  • D9 Test Distribution — Test source is present (.vb) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so its unit/integration/BDD/E2E split couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
  • DM10 One transaction, one aggregate — no repository writes detected — no operation to judge against the one-aggregate rule
  • DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
  • DM3 Integration-event coupling — no integration events detected — coupling check not applicable
  • DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
  • ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
  • ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • 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 — no CI workflow found
  • P2 Observability — This repo is a library, not a deployed service — it has no process to operate, so production observability (structured logging, tracing/metrics, health checks) is N/A. A library may log via an injected ILogger, but the absence of operational telemetry is not a defect here. If it grows a host (web API, worker), the dimension reactivates.
  • P7 Outbound HTTP resilience — not applicable — this isn't a service/API/worker
  • P8 Schema migrations — no EF Core usage detected
  • P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
  • PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for a BenchmarkDotNet reference in an .fsproj or .vbproj, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
  • PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
  • S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X12 Unreachable branch — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X13 Undrained process stream — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X14 Bypassable address classification — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X15 Unvalidated length from an untrusted reader — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X16 Unfloored truncation loop — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X17 Uncapped recursion over a caller-supplied document — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X18 Disposal-pattern correctness — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X19 Unrestored process-global state — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X20 Mistyped argument guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X21 Side-effecting pattern guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X22 Contradicted release guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X23 Unguarded diagnostic materialisation — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X24 Document value interpolated into markup unescaped — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X25 Inert configuration knob — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X26 Unsynchronised callback handoff — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X27 Collection changed while being enumerated — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X29 Per-element action decided by a fixed element — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X3 Exception handling — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X30 Support guard that admits what it rejects — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X32 Type resolved by simple name across every loaded assembly — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

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

Critical — 9 finding(s)
D17 · Explicit Debt · EmptyCatchBlock · ×9
  • EmptyCatchBlock src/DeepLearning4VB/org/datavec/api/conf/Configuration.vb:100 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock src/DeepLearning4VB/org/datavec/api/records/reader/impl/csv/CSVSequenceRecordReader.vb:93 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock src/DeepLearning4VB/org/datavec/api/records/reader/impl/jackson/JacksonLineSequenceRecordReader.vb:94 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock src/DeepLearning4VB/org/datavec/api/transform/serde/JsonMappers.vb:332 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock src/DeepLearning4VB/org/datavec/api/transform/serde/JsonMappers.vb:401 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock src/DeepLearning4VB/org/datavec/api/transform/transform/time/StringToTimeTransform.vb:234 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock src/DeepLearning4VB/org/nd4vb/common/config/ND4VBClassLoading.vb:89 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock src/DeepLearning4VB/org/nd4vb/common/resources/Downloader.vb:194 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock src/DeepLearning4VB/org/nd4vb/common/resources/strumpf/ResourceFile.vb:220 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
Serious — 238 finding(s)
D17 · Explicit Debt · TodoComment · ×57
  • TodoComment src/DeepLearning4VB/org/datavec/api/records/reader/impl/csv/CSVNLinesSequenceRecordReader.vb:123 — 'TODO handle multi file case... — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `' REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/DeepLearning4VB/org/datavec/api/records/reader/impl/regex/RegexSequenceRecordReader.vb:106 — 'TODO this won't work if regex allows for a newline — 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 src/DeepLearning4VB/org/datavec/api/transform/analysis/quality/QualityAnalysisAddFunction.vb:74 — '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 src/DeepLearning4VB/org/datavec/local/transforms/analysis/histogram/HistogramAddFunction.vb:68 — '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 src/DeepLearning4VB/org/datavec/api/transform/transform/column/DuplicateColumnsTransform.vb:119 — 'TODO safter to copy 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 src/DeepLearning4VB/org/datavec/api/transform/transform/time/DeriveColumnsFromTimeTransform.vb:111 — 'TODO: ranges... if it's a day, we know it must be 1 to 31, 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 src/DeepLearning4VB/org/nd4vb/linalg/api/blas/impl/BaseLapack.vb:284 — ' TODO: consider doing this in place to save memory. This implies U is taken out first — 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 src/DeepLearning4VB/org/nd4vb/linalg/api/blas/impl/BaseLevel1.vb:116 — ' TODO: add nrm2 for half, as call to appropriate NativeOp<HALF> — 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 src/DeepLearning4VB/org/nd4vb/linalg/api/blas/impl/BaseLevel2.vb:79 — ' TODO: provide optimized GEMV kernel eventually — 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 src/DeepLearning4VB/org/nd4vb/linalg/api/ndarray/INDArray.vb:107 — ' TODO: Unused untested method. — 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 src/DeepLearning4VB/org/nd4vb/linalg/api/ndarray/INDArray.vb:120 — ' TODO: Unused untested method. — 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 src/DeepLearning4VB/org/nd4vb/linalg/api/ndarray/INDArray.vb:179 — ' TODO: Unused untested method. — 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 src/DeepLearning4VB/org/nd4vb/linalg/api/ndarray/INDArray.vb:1874 — ' TODO: Unused untested method. — 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 src/DeepLearning4VB/org/nd4vb/linalg/api/ndarray/INDArray.vb:2231 — ' TODO: Unused untested method. — 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 src/DeepLearning4VB/org/nd4vb/linalg/api/ndarray/INDArray.vb:2238 — ' TODO: Unused untested method. — 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 src/DeepLearning4VB/org/nd4vb/linalg/api/ndarray/INDArray.vb:2273 — ' TODO: Unused untested method. — 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 src/DeepLearning4VB/org/nd4vb/linalg/api/ndarray/INDArray.vb:2280 — ' TODO: Unused untested method. — 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 src/DeepLearning4VB/org/nd4vb/linalg/api/ndarray/INDArray.vb:585 — 'TODO: revisit after #8166 is resolved.
  • TodoComment src/DeepLearning4VB/org/nd4vb/linalg/api/ndarray/INDArray.vb:593 — 'TODO: revisit after #8166 is resolved.
  • TodoComment src/DeepLearning4VB/org/nd4vb/linalg/api/ndarray/INDArray.vb:619 — 'TODO: unused / untested method. (only used to forward calls from putWhere(Number,INDArray ,Condition). — 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 src/DeepLearning4VB/org/nd4vb/linalg/api/ndarray/INDArray.vb:628 — 'TODO: unused / untested method. — 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 src/DeepLearning4VB/org/nd4vb/linalg/api/ndarray/INDArray.vb:645 — 'TODO: unused / untested method. — 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 src/DeepLearning4VB/org/nd4vb/linalg/api/ndarray/INDArray.vb:653 — 'TODO: unused / untested method. — 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 src/DeepLearning4VB/org/nd4vb/linalg/api/ndarray/INDArray.vb:696 — 'TODO: unused / untested method. — 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 src/DeepLearning4VB/org/nd4vb/linalg/api/ndarray/INDArray.vb:963 — 'TODO: unused / untested method. — 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.
  • + 32 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×17
  • Duplicated block (5 lines × 2) src/DeepLearning4VB/JavaCompat/Arrays.vb:148 — src/DeepLearning4VB/JavaCompat/Arrays.vb:148-152 | src/DeepLearning4VB/org/datavec/api/transform/serde/JavaJsonWriter.vb:183-187 — 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 (5 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/managed/kernels/ReduceKernels.vb:67 — src/DeepLearning4VB/org/nd4vb/linalg/managed/kernels/ReduceKernels.vb:67-71 | src/DeepLearning4VB/org/nd4vb/linalg/managed/kernels/ReduceKernels.vb:129-133 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/DeepLearning4VB/org/nd4vb/linalg/managed/kernels/ReduceKernels.vb:126` calls `CheckNumericOperand`, `CheckSameLength` and `src/DeepLearning4VB/org/nd4vb/linalg/managed/kernels/ReduceKernels.vb:65` 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 (5 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/managed/kernels/ManagedBlas.Level3.vb:94 — src/DeepLearning4VB/org/nd4vb/linalg/managed/kernels/ManagedBlas.Level3.vb:94-98 | src/DeepLearning4VB/org/nd4vb/linalg/managed/kernels/ManagedBlas.Level3.vb:476-480 — 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 (5 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/managed/kernels/ReduceKernels.vb:393 — src/DeepLearning4VB/org/nd4vb/linalg/managed/kernels/ReduceKernels.vb:393-397 | src/DeepLearning4VB/org/nd4vb/linalg/managed/kernels/ReduceKernels.vb:425-429 — 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 `src/DeepLearning4VB/org/nd4vb/linalg/managed/kernels/ReduceKernels.vb:393` 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 before the matched lines, `src/DeepLearning4VB/org/nd4vb/linalg/managed/kernels/ReduceKernels.vb:422` calls `Double`, `CInt`, `InnerStrides` and `src/DeepLearning4VB/org/nd4vb/linalg/managed/kernels/ReduceKernels.vb:391` 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 (5 lines × 2) src/DeepLearning4VB/org/datavec/api/transform/analysis/counter/IntegerAnalysisCounter.vb:258 — src/DeepLearning4VB/org/datavec/api/transform/analysis/counter/IntegerAnalysisCounter.vb:258-262 | src/DeepLearning4VB/org/datavec/api/transform/analysis/counter/LongAnalysisCounter.vb:251-255 — before extracting anything, compare `src/DeepLearning4VB/org/datavec/api/transform/analysis/counter/IntegerAnalysisCounter.vb` and `src/DeepLearning4VB/org/datavec/api/transform/analysis/counter/LongAnalysisCounter.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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.
  • Duplicated block (5 lines × 2) src/DeepLearning4VB/org/datavec/api/transform/sequence/window/OverlappingTimeWindowFunction.vb:271 — src/DeepLearning4VB/org/datavec/api/transform/sequence/window/OverlappingTimeWindowFunction.vb:271-275 | src/DeepLearning4VB/org/datavec/api/transform/sequence/window/TimeWindowFunction.vb:242-246 — before extracting anything, compare `src/DeepLearning4VB/org/datavec/api/transform/sequence/window/OverlappingTimeWindowFunction.vb` and `src/DeepLearning4VB/org/datavec/api/transform/sequence/window/TimeWindowFunction.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 33 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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.
  • Duplicated block (5 lines × 2) src/DeepLearning4VB/org/datavec/local/transforms/LocalTransformExecutor.vb:292 — src/DeepLearning4VB/org/datavec/local/transforms/LocalTransformExecutor.vb:292-296 | src/DeepLearning4VB/org/datavec/local/transforms/LocalTransformExecutor.vb:300-304 — 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 (5 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseBroadcastOp.vb:180 — src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseBroadcastOp.vb:180-184 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseScalarOp.vb:187-191 — 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. 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.
  • Duplicated block (5 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/Conv1D.vb:83 — src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/Conv1D.vb:83-87 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/Conv1DDerivative.vb:79-83 — 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) src/DeepLearning4VB/org/nd4vb/common/util/ArrayUtil.vb:1573 — src/DeepLearning4VB/org/nd4vb/common/util/ArrayUtil.vb:1573-1578 | src/DeepLearning4VB/org/nd4vb/linalg/api/shape/Shape.vb:1270-1274 — 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 (5 lines × 2) src/DeepLearning4VB/org/nd4vb/common/util/ArrayUtil.vb:1682 — src/DeepLearning4VB/org/nd4vb/common/util/ArrayUtil.vb:1682-1686 | src/DeepLearning4VB/org/nd4vb/linalg/util/LongUtils.vb:45-49 — 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 (5 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseReduceFloatOp.vb:124 — src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseReduceFloatOp.vb:124-129 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/summarystats/Variance.vb:450-454 — 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 (5 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/image/ResizeArea.vb:105 — src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/image/ResizeArea.vb:105-109 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/image/ResizeBilinear.vb:111-115 — 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) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/DepthToSpace.vb:68 — src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/DepthToSpace.vb:68-72 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/SpaceToDepth.vb:68-72 — before extracting anything, compare `src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/DepthToSpace.vb` and `src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/SpaceToDepth.vb` 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.
  • Duplicated block (5 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/reduce/bp/CumProdBp.vb:85 — src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/reduce/bp/CumProdBp.vb:85-89 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/reduce/bp/CumSumBp.vb:85-90 — before extracting anything, compare `src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/reduce/bp/CumProdBp.vb` and `src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/reduce/bp/CumSumBp.vb` as WHOLE FILES: 95% 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/reduce/bp/CumSumBp.vb:81` calls `New` and `src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/reduce/bp/CumProdBp.vb:80` 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 (5 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/Conv1D.vb:99 — src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/Conv1D.vb:99-103 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/Conv1DDerivative.vb:95-99 — 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) tools/porting/convert_ops.py:478 — tools/porting/convert_ops.py:478-482 | tools/porting/convert_ops.py:506-510 — 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 · ×16
  • Low cohesion: DefaultOpExecutioner (LCOM4 12) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/executioner/DefaultOpExecutioner.vb:84 — DefaultOpExecutioner's methods fall into 12 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 12 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: Builder (LCOM4 8) src/DeepLearning4VB/org/datavec/api/transform/analysis/columns/StringAnalysis.vb:166 — Builder's methods fall into 8 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 8 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: Builder (LCOM4 8) src/DeepLearning4VB/org/datavec/api/transform/ui/components/RenderableComponentTable.vb:279 — Builder's methods fall into 8 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 8 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: Builder (LCOM4 6) src/DeepLearning4VB/org/datavec/api/records/mapper/RecordMapper.vb:184 — Builder's methods fall into 6 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 6 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: Builder (LCOM4 5) src/DeepLearning4VB/org/datavec/api/transform/analysis/columns/BytesAnalysis.vb:130 — Builder'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: Builder (LCOM4 5) src/DeepLearning4VB/org/datavec/api/transform/sequence/window/OverlappingTimeWindowFunction.vb:377 — Builder'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: Builder (LCOM4 5) src/DeepLearning4VB/org/datavec/api/transform/sequence/window/TimeWindowFunction.vb:351 — Builder'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: Builder (LCOM4 5) src/DeepLearning4VB/org/datavec/api/transform/stringreduce/StringReducer.vb:267 — Builder'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: Builder (LCOM4 5) src/DeepLearning4VB/org/datavec/api/transform/ui/components/RenderableComponentLineChart.vb:339 — Builder'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: BaseOpContext (LCOM4 5) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseOpContext.vb:40 — BaseOpContext'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: FileSplit (LCOM4 4) src/DeepLearning4VB/org/datavec/api/split/FileSplit.vb:35 — FileSplit's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: BaseScalarBoolOp (LCOM4 4) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseScalarBoolOp.vb:42 — BaseScalarBoolOp's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: BaseScalarOp (LCOM4 4) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseScalarOp.vb:48 — BaseScalarOp's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: DynamicCustomOp (LCOM4 4) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/DynamicCustomOp.vb:72 — DynamicCustomOp's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: ManagedOpExecutioner (LCOM4 4) src/DeepLearning4VB/org/nd4vb/linalg/managed/ManagedOpExecutioner.vb:93 — ManagedOpExecutioner's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: ManagedMemoryManager (LCOM4 4) src/DeepLearning4VB/org/nd4vb/linalg/managed/memory/ManagedMemoryManager.vb:28 — ManagedMemoryManager'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.
D17 · Explicit Debt · ObsoleteWithCallers · ×12
  • ObsoleteWithCallers src/DeepLearning4VB/org/datavec/api/transform/join/Join.vb:172 — <Obsolete> setKeyColumns
  • ObsoleteWithCallers src/DeepLearning4VB/org/datavec/api/transform/join/Join.vb:178 — <Obsolete> setKeyColumnsLeft
  • ObsoleteWithCallers src/DeepLearning4VB/org/datavec/api/transform/join/Join.vb:184 — <Obsolete> setKeyColumnsRight
  • ObsoleteWithCallers src/DeepLearning4VB/org/datavec/api/util/ClassPathResource.vb:26 — <Obsolete> ClassPathResource
  • ObsoleteWithCallers src/DeepLearning4VB/org/datavec/api/util/ClassPathResource.vb:30 — <Obsolete> .ctor
  • ObsoleteWithCallers src/DeepLearning4VB/org/datavec/api/util/ReflectionUtils.vb:38 — <Obsolete> ReflectionUtils
  • ObsoleteWithCallers src/DeepLearning4VB/org/nd4vb/linalg/api/ndarray/INDArray.vb:793 — <Obsolete> repmat
  • ObsoleteWithCallers src/DeepLearning4VB/org/nd4vb/linalg/api/ops/executioner/DefaultOpExecutioner.vb:259 — <Obsolete> setProfilingMode
  • ObsoleteWithCallers src/DeepLearning4VB/org/nd4vb/linalg/api/ops/executioner/DefaultOpExecutioner.vb:285 — <Obsolete> getProfilingMode
  • ObsoleteWithCallers src/DeepLearning4VB/org/nd4vb/linalg/api/shape/Shape.vb:967 — <Obsolete> getOffset
  • ObsoleteWithCallers src/DeepLearning4VB/org/nd4vb/linalg/util/NDArrayUtil.vb:34 — <Obsolete> NDArrayUtil
  • ObsoleteWithCallers src/DeepLearning4VB/org/nd4vb/linalg/util/NDArrayUtil.vb:54 — <Obsolete> toNDArray
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×12
  • Duplicated block (7 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/transforms/custom/DotProductAttentionBp.vb:64 — src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/transforms/custom/DotProductAttentionBp.vb:64-70 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/transforms/custom/MultiHeadDotProductAttentionBp.vb:64-70 — before extracting anything, compare `src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/transforms/custom/DotProductAttentionBp.vb` and `src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/transforms/custom/MultiHeadDotProductAttentionBp.vb` as WHOLE FILES: 89% 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.
  • Duplicated block (7 lines × 2) src/DeepLearning4VB/org/datavec/api/transform/metadata/DoubleMetaData.vb:157 — src/DeepLearning4VB/org/datavec/api/transform/metadata/DoubleMetaData.vb:157-163 | src/DeepLearning4VB/org/datavec/api/transform/metadata/FloatMetaData.vb:157-163 — 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 (7 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/api/blas/params/GemmParams.vb:162 — src/DeepLearning4VB/org/nd4vb/linalg/api/blas/params/GemmParams.vb:162-168 | src/DeepLearning4VB/org/nd4vb/linalg/api/blas/params/GemvParameters.vb:84-90 — 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 (7 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseReduceBoolOp.vb:133 — src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseReduceBoolOp.vb:133-139 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseReduceLongOp.vb:128-134 — before extracting anything, compare `src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseReduceBoolOp.vb` and `src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseReduceLongOp.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 136 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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.
  • Duplicated block (7 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseReduceBoolOp.vb:151 — src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseReduceBoolOp.vb:151-157 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseReduceLongOp.vb:146-152 — before extracting anything, compare `src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseReduceBoolOp.vb` and `src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseReduceLongOp.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 136 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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.
  • Duplicated block (7 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/indexaccum/FirstIndex.vb:133 — src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/indexaccum/FirstIndex.vb:133-139 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/indexaccum/LastIndex.vb:148-154 — before extracting anything, compare `src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/indexaccum/FirstIndex.vb` and `src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/indexaccum/LastIndex.vb` 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 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.
  • Duplicated block (7 lines × 2) src/DeepLearning4VB/JavaCompat/JavaString.vb:90 — src/DeepLearning4VB/JavaCompat/JavaString.vb:90-96 | src/DeepLearning4VB/JavaCompat/JavaString.vb:99-105 — 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. 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.
  • Duplicated block (7 lines × 2) src/DeepLearning4VB/org/datavec/local/transforms/LocalTransformExecutor.vb:427 — src/DeepLearning4VB/org/datavec/local/transforms/LocalTransformExecutor.vb:427-436 | src/DeepLearning4VB/org/datavec/local/transforms/LocalTransformExecutor.vb:439-445 — 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. 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.
  • Duplicated block (7 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/managed/ManagedOpExecutioner.vb:350 — src/DeepLearning4VB/org/nd4vb/linalg/managed/ManagedOpExecutioner.vb:350-357 | src/DeepLearning4VB/org/nd4vb/linalg/managed/ManagedOpExecutioner.vb:476-482 — 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. 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.
  • Duplicated block (7 lines × 2) src/DeepLearning4VB/org/datavec/api/transform/analysis/counter/IntegerAnalysisCounter.vb:58 — src/DeepLearning4VB/org/datavec/api/transform/analysis/counter/IntegerAnalysisCounter.vb:58-64 | src/DeepLearning4VB/org/datavec/api/transform/analysis/counter/LongAnalysisCounter.vb:59-65 — before extracting anything, compare `src/DeepLearning4VB/org/datavec/api/transform/analysis/counter/IntegerAnalysisCounter.vb` and `src/DeepLearning4VB/org/datavec/api/transform/analysis/counter/LongAnalysisCounter.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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.
  • Duplicated block (7 lines × 2) src/DeepLearning4VB/org/datavec/api/transform/serde/JsonMappers.vb:434 — src/DeepLearning4VB/org/datavec/api/transform/serde/JsonMappers.vb:434-440 | src/DeepLearning4VB/org/nd4vb/common/config/ND4VBClassLoading.vb:168-174 — 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 (7 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/reduce/bp/CumProdBp.vb:50 — src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/reduce/bp/CumProdBp.vb:50-56 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/reduce/bp/CumSumBp.vb:50-56 — before extracting anything, compare `src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/reduce/bp/CumProdBp.vb` and `src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/reduce/bp/CumSumBp.vb` as WHOLE FILES: 95% 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/reduce/bp/CumProdBp.vb:59` calls `New` and `src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/reduce/bp/CumSumBp.vb:60` 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.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×10
  • Duplicated block (6 lines × 2) src/DeepLearning4VB/org/datavec/api/transform/ui/components/RenderableComponentHistogram.vb:70 — src/DeepLearning4VB/org/datavec/api/transform/ui/components/RenderableComponentHistogram.vb:70-75 | src/DeepLearning4VB/org/datavec/api/transform/ui/components/RenderableComponentLineChart.vb:83-88 — 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 (6 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/api/blas/impl/BaseLapack.vb:293 — src/DeepLearning4VB/org/nd4vb/linalg/api/blas/impl/BaseLapack.vb:293-298 | src/DeepLearning4VB/org/nd4vb/linalg/api/blas/impl/BaseLapack.vb:317-322 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (6 lines × 2) src/DeepLearning4VB/org/datavec/api/records/reader/impl/inmemory/InMemoryRecordReader.vb:247 — src/DeepLearning4VB/org/datavec/api/records/reader/impl/inmemory/InMemoryRecordReader.vb:247-252 | src/DeepLearning4VB/org/datavec/api/records/reader/impl/inmemory/InMemorySequenceRecordReader.vb:293-298 — before extracting anything, compare `src/DeepLearning4VB/org/datavec/api/records/reader/impl/inmemory/InMemoryRecordReader.vb` and `src/DeepLearning4VB/org/datavec/api/records/reader/impl/inmemory/InMemorySequenceRecordReader.vb` 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. 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.
  • Duplicated block (6 lines × 2) src/DeepLearning4VB/org/datavec/api/transform/analysis/DataAnalysis.vb:70 — src/DeepLearning4VB/org/datavec/api/transform/analysis/DataAnalysis.vb:70-75 | src/DeepLearning4VB/org/datavec/api/transform/quality/DataQualityAnalysis.vb:74-79 — 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 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.
  • Duplicated block (6 lines × 2) src/DeepLearning4VB/org/datavec/api/transform/sequence/expansion/BaseSequenceExpansionTransform.vb:226 — src/DeepLearning4VB/org/datavec/api/transform/sequence/expansion/BaseSequenceExpansionTransform.vb:226-231 | src/DeepLearning4VB/org/datavec/api/transform/stringreduce/StringReducer.vb:235-240 — 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) src/DeepLearning4VB/org/datavec/api/transform/transform/categorical/CategoricalToOneHotTransform.vb:188 — src/DeepLearning4VB/org/datavec/api/transform/transform/categorical/CategoricalToOneHotTransform.vb:188-193 | src/DeepLearning4VB/org/datavec/api/transform/transform/integer/IntegerToOneHotTransform.vb:178-183 — 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) src/DeepLearning4VB/org/datavec/local/transforms/AnalyzeLocal.vb:185 — src/DeepLearning4VB/org/datavec/local/transforms/AnalyzeLocal.vb:185-190 | src/DeepLearning4VB/org/datavec/local/transforms/AnalyzeLocal.vb:226-231 — 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. 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.
  • Duplicated block (6 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/managed/kernels/IndexReduceKernels.vb:107 — src/DeepLearning4VB/org/nd4vb/linalg/managed/kernels/IndexReduceKernels.vb:107-112 | src/DeepLearning4VB/org/nd4vb/linalg/managed/kernels/SummaryStatsKernels.vb:113-118 — 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 `src/DeepLearning4VB/org/nd4vb/linalg/managed/kernels/IndexReduceKernels.vb:107` 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.
  • Duplicated block (6 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseBroadcastBoolOp.vb:141 — src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseBroadcastBoolOp.vb:141-146 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseBroadcastOp.vb:137-142 — before extracting anything, compare `src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseBroadcastBoolOp.vb` and `src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseBroadcastOp.vb` as WHOLE FILES: 84% 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.
  • Duplicated block (6 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/transforms/comparison/CompareAndReplace.vb:97 — src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/transforms/comparison/CompareAndReplace.vb:97-102 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/transforms/comparison/CompareAndSet.vb:164-169 — 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.
D4 · Code Duplication · Duplicated block (9 lines × 2) · ×9
  • Duplicated block (9 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/indexing/Indices.vb:293 — src/DeepLearning4VB/org/nd4vb/linalg/indexing/Indices.vb:293-301 | src/DeepLearning4VB/org/nd4vb/linalg/indexing/Indices.vb:318-326 — 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) src/DeepLearning4VB/org/datavec/api/records/reader/impl/FileRecordReader.vb:210 — src/DeepLearning4VB/org/datavec/api/records/reader/impl/FileRecordReader.vb:210-218 | src/DeepLearning4VB/org/datavec/api/records/reader/impl/jackson/JacksonRecordReader.vb:151-160 — 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 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/DeepLearning4VB/org/datavec/api/records/reader/impl/FileRecordReader.vb:208` calls `invokeListeners` and `src/DeepLearning4VB/org/datavec/api/records/reader/impl/jackson/JacksonRecordReader.vb:150` 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 (9 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/indexaccum/FirstIndex.vb:147 — src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/indexaccum/FirstIndex.vb:147-155 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/indexaccum/LastIndex.vb:162-170 — before extracting anything, compare `src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/indexaccum/FirstIndex.vb` and `src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/indexaccum/LastIndex.vb` 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 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.
  • Duplicated block (9 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/Im2col.vb:73 — src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/Im2col.vb:73-81 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/Im2colBp.vb:59-67 — before extracting anything, compare `src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/Im2col.vb` and `src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/Im2colBp.vb` as WHOLE FILES: 87% 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.
  • Duplicated block (9 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/api/shape/Shape.vb:1005 — src/DeepLearning4VB/org/nd4vb/linalg/api/shape/Shape.vb:1005-1013 | src/DeepLearning4VB/org/nd4vb/linalg/api/shape/Shape.vb:1020-1028 — 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) src/DeepLearning4VB/org/nd4vb/linalg/managed/kernels/ManagedBlas.Level3.vb:300 — src/DeepLearning4VB/org/nd4vb/linalg/managed/kernels/ManagedBlas.Level3.vb:300-308 | src/DeepLearning4VB/org/nd4vb/linalg/managed/kernels/ManagedBlas.Level3.vb:310-318 — 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) src/DeepLearning4VB/org/nd4vb/linalg/managed/kernels/ManagedBlas.Level3.vb:682 — src/DeepLearning4VB/org/nd4vb/linalg/managed/kernels/ManagedBlas.Level3.vb:682-690 | src/DeepLearning4VB/org/nd4vb/linalg/managed/kernels/ManagedBlas.Level3.vb:692-700 — 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) src/DeepLearning4VB/org/nd4vb/linalg/managed/kernels/ReduceKernels.vb:175 — src/DeepLearning4VB/org/nd4vb/linalg/managed/kernels/ReduceKernels.vb:175-183 | src/DeepLearning4VB/org/nd4vb/linalg/managed/kernels/ReduceKernels.vb:247-258 — 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) src/DeepLearning4VB/org/nd4vb/linalg/exception/ND4VBException.vb:33 — src/DeepLearning4VB/org/nd4vb/linalg/exception/ND4VBException.vb:33-42 | src/DeepLearning4VB/org/nd4vb/linalg/workspace/ND4VBWorkspaceException.vb:17-25 — 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 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.
D17 · Explicit Debt · FixmeComment · ×7
  • FixmeComment src/DeepLearning4VB/org/nd4vb/linalg/api/buffer/BaseDataBuffer.vb:746 — ' FIXME (Java): this is BAD. it takes too long to work, and it breaks general equals contract — 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 src/DeepLearning4VB/org/nd4vb/linalg/api/iter/LinearIndexLookup.vb:31 — ' FIXME: long! — 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 src/DeepLearning4VB/org/nd4vb/linalg/api/ops/executioner/DefaultOpExecutioner.vb:144 — ' FIXME: Remove this method, after we'll add support for <int> dtype operations — 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 src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/reduce/SufficientStatistics.vb:79 — ' FIXME — 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 src/DeepLearning4VB/org/nd4vb/linalg/api/ops/random/compat/RandomStandardNormal.vb:81 — ' FIXME: why the hell 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 src/DeepLearning4VB/org/nd4vb/linalg/env/impl/NDArrayUnpackAction.vb:40 — ' FIXME (Java): get rid of direct variable access eventually!!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 src/DeepLearning4VB/org/nd4vb/linalg/indexing/Indices.vb:249 — ' FIXME: LONG — 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.
D4 · Code Duplication · Duplicated block (15 lines × 2) · ×5
  • Duplicated block (15 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/managed/kernels/ManagedBlas.Level3.vb:77 — src/DeepLearning4VB/org/nd4vb/linalg/managed/kernels/ManagedBlas.Level3.vb:77-91 | src/DeepLearning4VB/org/nd4vb/linalg/managed/kernels/ManagedBlas.Level3.vb:459-473 — 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 (15 lines × 2) src/DeepLearning4VB/org/datavec/api/transform/sequence/window/OverlappingTimeWindowFunction.vb:252 — src/DeepLearning4VB/org/datavec/api/transform/sequence/window/OverlappingTimeWindowFunction.vb:252-266 | src/DeepLearning4VB/org/datavec/api/transform/sequence/window/TimeWindowFunction.vb:224-238 — before extracting anything, compare `src/DeepLearning4VB/org/datavec/api/transform/sequence/window/OverlappingTimeWindowFunction.vb` and `src/DeepLearning4VB/org/datavec/api/transform/sequence/window/TimeWindowFunction.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 33 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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.
  • Duplicated block (15 lines × 2) src/DeepLearning4VB/org/nd4vb/common/util/ArrayUtil.vb:3223 — src/DeepLearning4VB/org/nd4vb/common/util/ArrayUtil.vb:3223-3237 | src/DeepLearning4VB/org/nd4vb/common/util/ArrayUtil.vb:3263-3277 — 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 (15 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/managed/kernels/ManagedBlas.Level3.vb:200 — src/DeepLearning4VB/org/nd4vb/linalg/managed/kernels/ManagedBlas.Level3.vb:200-214 | src/DeepLearning4VB/org/nd4vb/linalg/managed/kernels/ManagedBlas.Level3.vb:582-596 — 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 (15 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/managed/kernels/ManagedBlas.Level3.vb:245 — src/DeepLearning4VB/org/nd4vb/linalg/managed/kernels/ManagedBlas.Level3.vb:245-259 | src/DeepLearning4VB/org/nd4vb/linalg/managed/kernels/ManagedBlas.Level3.vb:627-641 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×5
  • Duplicated block (12 lines × 2) src/DeepLearning4VB/org/datavec/api/transform/analysis/quality/categorical/CategoricalQualityAddFunction.vb:48 — src/DeepLearning4VB/org/datavec/api/transform/analysis/quality/categorical/CategoricalQualityAddFunction.vb:48-59 | src/DeepLearning4VB/org/datavec/api/transform/analysis/quality/time/TimeQualityAddFunction.vb:48-59 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (12 lines × 2) src/DeepLearning4VB/org/datavec/api/transform/ops/AggregatorImpls.vb:496 — src/DeepLearning4VB/org/datavec/api/transform/ops/AggregatorImpls.vb:496-507 | src/DeepLearning4VB/org/datavec/api/transform/ops/AggregatorImpls.vb:580-591 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (12 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/Conv3DConfig.vb:64 — src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/Conv3DConfig.vb:64-75 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/Pooling3DConfig.vb:47-58 — before extracting anything, compare `src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/Conv3DConfig.vb` and `src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/Pooling3DConfig.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 81 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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.
  • Duplicated block (12 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/Conv2DConfig.vb:83 — src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/Conv2DConfig.vb:83-94 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/DeConv2DConfig.vb:66-77 — before extracting anything, compare `src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/Conv2DConfig.vb` and `src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/DeConv2DConfig.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 61 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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.
  • Duplicated block (12 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/transforms/custom/DotProductAttention.vb:80 — src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/transforms/custom/DotProductAttention.vb:80-91 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/transforms/custom/MultiHeadDotProductAttention.vb:79-90 — before extracting anything, compare `src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/transforms/custom/DotProductAttention.vb` and `src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/transforms/custom/MultiHeadDotProductAttention.vb` 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 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.
D4 · Code Duplication · Duplicated block (13 lines × 2) · ×5
  • Duplicated block (13 lines × 2) src/DeepLearning4VB/org/datavec/api/transform/sequence/window/OverlappingTimeWindowFunction.vb:132 — src/DeepLearning4VB/org/datavec/api/transform/sequence/window/OverlappingTimeWindowFunction.vb:132-144 | src/DeepLearning4VB/org/datavec/api/transform/sequence/window/TimeWindowFunction.vb:115-127 — before extracting anything, compare `src/DeepLearning4VB/org/datavec/api/transform/sequence/window/OverlappingTimeWindowFunction.vb` and `src/DeepLearning4VB/org/datavec/api/transform/sequence/window/TimeWindowFunction.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 33 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/DeepLearning4VB/org/datavec/api/transform/sequence/window/OverlappingTimeWindowFunction.vb:145` calls `convert` and `src/DeepLearning4VB/org/datavec/api/transform/sequence/window/TimeWindowFunction.vb:128` 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 (13 lines × 2) src/DeepLearning4VB/org/datavec/api/transform/transform/doubletransform/DoubleMathFunctionTransform.vb:70 — src/DeepLearning4VB/org/datavec/api/transform/transform/doubletransform/DoubleMathFunctionTransform.vb:70-82 | src/DeepLearning4VB/org/datavec/api/transform/transform/floattransform/FloatMathFunctionTransform.vb:88-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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/DeepLearning4VB/org/datavec/api/transform/transform/doubletransform/DoubleMathFunctionTransform.vb:69` calls `signum` and `src/DeepLearning4VB/org/datavec/api/transform/transform/floattransform/FloatMathFunctionTransform.vb:87` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (13 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/Conv3DConfig.vb:98 — src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/Conv3DConfig.vb:98-110 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/Pooling3DConfig.vb:67-79 — before extracting anything, compare `src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/Conv3DConfig.vb` and `src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/Pooling3DConfig.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 81 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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.
  • Duplicated block (13 lines × 2) src/DeepLearning4VB/org/datavec/api/transform/ops/AggregatorImpls.vb:477 — src/DeepLearning4VB/org/datavec/api/transform/ops/AggregatorImpls.vb:477-489 | src/DeepLearning4VB/org/datavec/api/transform/ops/AggregatorImpls.vb:561-573 — 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 (13 lines × 2) src/DeepLearning4VB/org/datavec/api/transform/transform/categorical/CategoricalToIntegerTransform.vb:40 — src/DeepLearning4VB/org/datavec/api/transform/transform/categorical/CategoricalToIntegerTransform.vb:40-52 | src/DeepLearning4VB/org/datavec/api/transform/transform/categorical/CategoricalToOneHotTransform.vb:41-53 — 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.
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×5
  • Duplicated block (11 lines × 2) src/DeepLearning4VB/org/datavec/api/transform/ui/components/RenderableComponentHistogram.vb:99 — src/DeepLearning4VB/org/datavec/api/transform/ui/components/RenderableComponentHistogram.vb:99-109 | src/DeepLearning4VB/org/datavec/api/transform/ui/components/RenderableComponentLineChart.vb:128-138 — 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 (11 lines × 2) src/DeepLearning4VB/org/datavec/api/transform/metadata/IntegerMetaData.vb:113 — src/DeepLearning4VB/org/datavec/api/transform/metadata/IntegerMetaData.vb:113-123 | src/DeepLearning4VB/org/datavec/api/transform/metadata/LongMetaData.vb:119-129 — 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 (11 lines × 2) src/DeepLearning4VB/org/datavec/api/transform/schema/Schema.vb:327 — src/DeepLearning4VB/org/datavec/api/transform/schema/Schema.vb:327-337 | src/DeepLearning4VB/org/datavec/api/transform/schema/SequenceSchema.vb:108-118 — 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 (11 lines × 2) src/DeepLearning4VB/org/datavec/api/transform/schema/SequenceSchema.vb:162 — src/DeepLearning4VB/org/datavec/api/transform/schema/SequenceSchema.vb:162-172 | src/DeepLearning4VB/org/datavec/api/transform/schema/SequenceSchema.vb:192-202 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/DeepLearning4VB/org/datavec/api/transform/schema/SequenceSchema.vb:160` calls `record` and `src/DeepLearning4VB/org/datavec/api/transform/schema/SequenceSchema.vb:191` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (11 lines × 2) src/DeepLearning4VB/org/nd4vb/common/util/ArrayUtil.vb:1525 — src/DeepLearning4VB/org/nd4vb/common/util/ArrayUtil.vb:1525-1536 | src/DeepLearning4VB/org/nd4vb/common/util/ArrayUtil.vb:1543-1553 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×5
  • Duplicated block (8 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseReduceFloatOp.vb:169 — src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseReduceFloatOp.vb:169-176 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseReduceSameOp.vb:151-158 — 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) src/DeepLearning4VB/org/datavec/api/split/FileSplit.vb:162 — src/DeepLearning4VB/org/datavec/api/split/FileSplit.vb:162-169 | src/DeepLearning4VB/org/datavec/api/split/NumberedFileInputSplit.vb:80-87 — 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) src/DeepLearning4VB/org/nd4vb/autodiff/functions/DifferentialFunction.vb:315 — src/DeepLearning4VB/org/nd4vb/autodiff/functions/DifferentialFunction.vb:315-322 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/BaseConvolutionConfig.vb:99-106 — before extracting anything, compare `src/DeepLearning4VB/org/nd4vb/autodiff/functions/DifferentialFunction.vb` and `src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/BaseConvolutionConfig.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 58 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (8 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseOp.vb:214 — src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseOp.vb:214-221 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/BaseConvolutionConfig.vb:87-94 — 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 (8 lines × 2) src/DeepLearning4VB/org/datavec/api/records/reader/impl/csv/CSVRecordReader.vb:191 — src/DeepLearning4VB/org/datavec/api/records/reader/impl/csv/CSVRecordReader.vb:191-198 | src/DeepLearning4VB/org/datavec/api/records/reader/impl/regex/RegexLineRecordReader.vb:122-129 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) · ×4
  • Members sharing a duplicated core (4 members, 50+ identical tokens) src/DeepLearning4VB/org/datavec/api/transform/condition/ConditionOp.vb:49 — src/DeepLearning4VB/org/datavec/api/transform/condition/ConditionOp.vb:49-68 | src/DeepLearning4VB/org/datavec/api/transform/condition/ConditionOp.vb:73-92 | src/DeepLearning4VB/org/datavec/api/transform/condition/ConditionOp.vb:97-116 | src/DeepLearning4VB/org/datavec/api/transform/condition/ConditionOp.vb:121-140 — These 4 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 4 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 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseReduceBoolOp.vb:151 — src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseReduceBoolOp.vb:151-158 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseReduceFloatOp.vb:169-181 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseReduceLongOp.vb:146-153 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseReduceSameOp.vb:151-160 — These 4 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 4 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 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/Conv2DConfig.vb:216 — src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/Conv2DConfig.vb:216-256 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/DeConv2DConfig.vb:189-226 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/DeConv3DConfig.vb:240-289 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/Pooling2DConfig.vb:226-272 — These 4 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 4 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 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/transforms/custom/DotProductAttention.vb:79 — src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/transforms/custom/DotProductAttention.vb:79-91 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/transforms/custom/DotProductAttentionBp.vb:63-72 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/transforms/custom/MultiHeadDotProductAttention.vb:78-90 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/transforms/custom/MultiHeadDotProductAttentionBp.vb:63-72 — These 4 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 4 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 4 times.
D4 · Code Duplication · Duplicated block (17 lines × 2) · ×4
  • Duplicated block (17 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/executioner/DefaultOpExecutioner.vb:404 — src/DeepLearning4VB/org/nd4vb/linalg/api/ops/executioner/DefaultOpExecutioner.vb:404-420 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/executioner/DefaultOpExecutioner.vb:432-448 — 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 (17 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/executioner/DefaultOpExecutioner.vb:536 — src/DeepLearning4VB/org/nd4vb/linalg/api/ops/executioner/DefaultOpExecutioner.vb:536-552 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/executioner/DefaultOpExecutioner.vb:573-589 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (17 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/Conv3DConfig.vb:334 — src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/Conv3DConfig.vb:334-350 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/Pooling3DConfig.vb:303-319 — before extracting anything, compare `src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/Conv3DConfig.vb` and `src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/Pooling3DConfig.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 81 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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.
  • Duplicated block (17 lines × 2) src/DeepLearning4VB/org/datavec/api/transform/transform/categorical/CategoricalToIntegerTransform.vb:104 — src/DeepLearning4VB/org/datavec/api/transform/transform/categorical/CategoricalToIntegerTransform.vb:104-120 | src/DeepLearning4VB/org/datavec/api/transform/transform/categorical/CategoricalToOneHotTransform.vb:129-152 — 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.
D4 · Code Duplication · Duplicated block (10 lines × 2) · ×4
  • Duplicated block (10 lines × 2) src/DeepLearning4VB/org/nd4vb/common/util/ArrayUtil.vb:1851 — src/DeepLearning4VB/org/nd4vb/common/util/ArrayUtil.vb:1851-1860 | src/DeepLearning4VB/org/nd4vb/common/util/ArrayUtil.vb:1913-1924 — 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. 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.
  • Duplicated block (10 lines × 2) src/DeepLearning4VB/org/nd4vb/common/util/ArrayUtil.vb:1875 — src/DeepLearning4VB/org/nd4vb/common/util/ArrayUtil.vb:1875-1884 | src/DeepLearning4VB/org/nd4vb/common/util/ArrayUtil.vb:1939-1950 — 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. 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.
  • Duplicated block (10 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/api/shape/Shape.vb:174 — src/DeepLearning4VB/org/nd4vb/linalg/api/shape/Shape.vb:174-183 | src/DeepLearning4VB/org/nd4vb/linalg/api/shape/Shape.vb:206-215 — 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) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/DepthwiseConv2D.vb:109 — src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/DepthwiseConv2D.vb:109-118 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/DepthwiseConv2DBp.vb:78-87 — 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.
D4 · Code Duplication · Duplicated block (7 lines × 3) · ×4
  • Duplicated block (7 lines × 3) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/Conv2DConfig.vb:83 — src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/Conv2DConfig.vb:83-89 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/DeConv2DConfig.vb:66-72 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/Pooling2DConfig.vb:70-76 — before extracting anything, compare `src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/Conv2DConfig.vb` and `src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/DeConv2DConfig.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 61 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/Pooling2DConfig.vb:78` calls `ret`, `ToString` and `src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/Conv2DConfig.vb:91` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (7 lines × 3) src/DeepLearning4VB/org/nd4vb/autodiff/functions/DifferentialFunction.vb:300 — src/DeepLearning4VB/org/nd4vb/autodiff/functions/DifferentialFunction.vb:300-306 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseOp.vb:214-220 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/BaseConvolutionConfig.vb:87-93 — before extracting anything, compare `src/DeepLearning4VB/org/nd4vb/autodiff/functions/DifferentialFunction.vb` and `src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/BaseConvolutionConfig.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 58 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/DeepLearning4VB/org/nd4vb/autodiff/functions/DifferentialFunction.vb:308` calls `CLng`, `DirectCast`, `If` and `src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseOp.vb:221` 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 (7 lines × 3) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/shape/Create.vb:130 — src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/shape/Create.vb:130-136 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/shape/OnesLike.vb:118-124 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/shape/ZerosLike.vb:118-124 — 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 all 3 call sites, so a change lands once.
  • Duplicated block (7 lines × 3) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/Conv2DConfig.vb:261 — src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/Conv2DConfig.vb:261-267 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/DeConv2DConfig.vb:231-237 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/Pooling2DConfig.vb:277-283 — before extracting anything, compare `src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/Conv2DConfig.vb` and `src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/DeConv2DConfig.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 61 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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.
D17 · Explicit Debt · BarePragmaDisable · ×3
  • BarePragmaDisable src/DeepLearning4VB/org/nd4vb/common/util/ObjectGraphSerializer.vb:160 — #Disable Warning SYSLIB0050 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
  • BarePragmaDisable src/DeepLearning4VB/org/nd4vb/linalg/util/FeatureUtil.vb:46 — #Disable Warning BC40008 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
  • BarePragmaDisable src/DeepLearning4VB/org/nd4vb/linalg/util/FeatureUtil.vb:63 — #Disable Warning BC40008 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
D4 · Code Duplication · Duplicated block (14 lines × 2) · ×3
  • Duplicated block (14 lines × 2) src/DeepLearning4VB/org/datavec/api/transform/analysis/histogram/DoubleHistogramCounter.vb:63 — src/DeepLearning4VB/org/datavec/api/transform/analysis/histogram/DoubleHistogramCounter.vb:63-76 | src/DeepLearning4VB/org/datavec/api/transform/analysis/histogram/StringHistogramCounter.vb:64-77 — 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 (14 lines × 2) src/DeepLearning4VB/org/nd4vb/common/util/ArrayUtil.vb:2797 — src/DeepLearning4VB/org/nd4vb/common/util/ArrayUtil.vb:2797-2810 | src/DeepLearning4VB/org/nd4vb/common/util/ArrayUtil.vb:2820-2833 — 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 (14 lines × 2) src/DeepLearning4VB/org/datavec/api/transform/transform/BaseColumnTransform.vb:85 — src/DeepLearning4VB/org/datavec/api/transform/transform/BaseColumnTransform.vb:85-98 | src/DeepLearning4VB/org/datavec/api/transform/transform/string/StringListToCategoricalSetTransform.vb:133-161 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Duplicated block (9 lines × 3) · ×3
  • Duplicated block (9 lines × 3) src/DeepLearning4VB/org/datavec/api/transform/analysis/quality/integer/IntegerQualityAddFunction.vb:55 — src/DeepLearning4VB/org/datavec/api/transform/analysis/quality/integer/IntegerQualityAddFunction.vb:55-63 | src/DeepLearning4VB/org/datavec/api/transform/analysis/quality/longq/LongQualityAddFunction.vb:55-63 | src/DeepLearning4VB/org/datavec/api/transform/analysis/quality/real/RealQualityAddFunction.vb:57-65 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (9 lines × 3) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/DeConv2D.vb:104 — src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/DeConv2D.vb:104-112 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/DeConv2DTF.vb:92-100 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/Pooling2D.vb:116-124 — 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 all 3 call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/Pooling2D.vb:114` calls `getType` and `src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/DeConv2D.vb:103` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (9 lines × 3) src/DeepLearning4VB/org/datavec/api/exceptions/DataVecException.vb:31 — src/DeepLearning4VB/org/datavec/api/exceptions/DataVecException.vb:31-43 | src/DeepLearning4VB/org/datavec/api/exceptions/UnknownFormatException.vb:36-44 | src/DeepLearning4VB/org/datavec/api/io/converters/WritableConverterException.vb:34-42 — before extracting anything, compare `src/DeepLearning4VB/org/datavec/api/exceptions/DataVecException.vb` and `src/DeepLearning4VB/org/datavec/api/exceptions/UnknownFormatException.vb` as WHOLE FILES: 84% 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.
D4 · Code Duplication · Duplicated block (7 lines × 4) · ×3
  • Duplicated block (7 lines × 4) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/transforms/custom/DotProductAttention.vb:80 — src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/transforms/custom/DotProductAttention.vb:80-86 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/transforms/custom/DotProductAttentionBp.vb:64-70 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/transforms/custom/MultiHeadDotProductAttention.vb:79-85 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/transforms/custom/MultiHeadDotProductAttentionBp.vb:64-70 — before extracting anything, compare `src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/transforms/custom/DotProductAttention.vb` and `src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/transforms/custom/MultiHeadDotProductAttention.vb` 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 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.
  • Duplicated block (7 lines × 4) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseReduceBoolOp.vb:151 — src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseReduceBoolOp.vb:151-157 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseReduceFloatOp.vb:169-176 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseReduceLongOp.vb:146-152 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseReduceSameOp.vb:151-158 — before extracting anything, compare `src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseReduceBoolOp.vb` and `src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseReduceLongOp.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 136 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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.
  • Duplicated block (7 lines × 4) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/shape/MergeMax.vb:90 — src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/shape/MergeMax.vb:90-96 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/shape/MergeSum.vb:100-106 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/shape/ParallelStack.vb:83-89 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/shape/Stack.vb:135-141 — before extracting anything, compare `src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/shape/MergeMax.vb` and `src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/shape/MergeSum.vb` as WHOLE FILES: 85% 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.
D4 · Code Duplication · Duplicated block (5 lines × 4) · ×3
  • Duplicated block (5 lines × 4) src/DeepLearning4VB/org/datavec/api/transform/transform/BaseTransform.vb:57 — src/DeepLearning4VB/org/datavec/api/transform/transform/BaseTransform.vb:57-61 | src/DeepLearning4VB/org/datavec/api/transform/transform/column/AddConstantColumnTransform.vb:89-93 | src/DeepLearning4VB/org/datavec/api/transform/transform/column/DuplicateColumnsTransform.vb:127-131 | src/DeepLearning4VB/org/datavec/api/transform/transform/time/DeriveColumnsFromTimeTransform.vb:181-185 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 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 4 times. 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.
  • Duplicated block (5 lines × 4) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseScalarBoolOp.vb:99 — src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseScalarBoolOp.vb:99-105 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseTransformBoolOp.vb:130-134 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseTransformFloatOp.vb:115-119 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseTransformSameOp.vb:125-129 — 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 all 4 call sites, so a change lands once. 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.
  • Duplicated block (5 lines × 4) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/transforms/segment/UnsortedSegmentMax.vb:73 — src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/transforms/segment/UnsortedSegmentMax.vb:73-77 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/transforms/segment/UnsortedSegmentMean.vb:69-73 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/transforms/segment/UnsortedSegmentMin.vb:73-77 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/transforms/segment/UnsortedSegmentSum.vb:73-78 — before extracting anything, compare `src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/transforms/segment/UnsortedSegmentMax.vb` and `src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/transforms/segment/UnsortedSegmentMean.vb` 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. 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.
D12 · Dependency Hygiene · Deprecated · ×2
  • Deprecated: MSTest.TestAdapter tests/DeepLearning4VB.Tests/DeepLearning4VB.Tests.vbproj:24 — MSTest.TestAdapter 3.6.4 — Legacy
  • Deprecated: MSTest.TestFramework tests/DeepLearning4VB.Tests/DeepLearning4VB.Tests.vbproj:25 — MSTest.TestFramework 3.6.4 — Legacy
D4 · Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) · ×2
  • Members sharing a duplicated core (5 members, 50+ identical tokens) src/DeepLearning4VB/org/datavec/api/writable/ByteWritable.vb:80 — src/DeepLearning4VB/org/datavec/api/writable/ByteWritable.vb:80-94 | src/DeepLearning4VB/org/datavec/api/writable/DoubleWritable.vb:78-92 | src/DeepLearning4VB/org/datavec/api/writable/FloatWritable.vb:79-93 | src/DeepLearning4VB/org/datavec/api/writable/IntWritable.vb:80-94 | src/DeepLearning4VB/org/datavec/api/writable/LongWritable.vb:80-94 — These 5 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 5 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 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseTransformBoolOp.vb:110 — src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseTransformBoolOp.vb:110-122 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseTransformFloatOp.vb:95-107 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseTransformSameOp.vb:105-117 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseTransformStrictOp.vb:94-112 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/transforms/MaxOut.vb:104-120 — These 5 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 5 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 5 times.
D4 · Code Duplication · Duplicated block (39 lines × 2) · ×2
  • Duplicated block (39 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/Conv3DConfig.vb:281 — src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/Conv3DConfig.vb:281-319 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/Pooling3DConfig.vb:250-288 — before extracting anything, compare `src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/Conv3DConfig.vb` and `src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/Pooling3DConfig.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 81 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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.
  • Duplicated block (39 lines × 2) src/DeepLearning4VB/org/datavec/api/transform/analysis/quality/QualityAnalysisAddFunction.vb:51 — src/DeepLearning4VB/org/datavec/api/transform/analysis/quality/QualityAnalysisAddFunction.vb:51-89 | src/DeepLearning4VB/org/datavec/local/transforms/analysis/aggregate/AnalysisAddFunction.vb:44-84 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Duplicated block (24 lines × 2) · ×2
  • Duplicated block (24 lines × 2) src/DeepLearning4VB/org/datavec/api/transform/condition/BooleanCondition.vb:124 — src/DeepLearning4VB/org/datavec/api/transform/condition/BooleanCondition.vb:124-147 | src/DeepLearning4VB/org/datavec/api/transform/condition/BooleanCondition.vb:158-181 — 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 (24 lines × 2) src/DeepLearning4VB/org/datavec/api/transform/condition/BooleanCondition.vb:185 — src/DeepLearning4VB/org/datavec/api/transform/condition/BooleanCondition.vb:185-208 | src/DeepLearning4VB/org/datavec/api/transform/condition/BooleanCondition.vb:220-243 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (22 lines × 2) · ×2
  • Duplicated block (22 lines × 2) src/DeepLearning4VB/org/datavec/api/transform/transform/doubletransform/DoubleMathOpTransform.vb:67 — src/DeepLearning4VB/org/datavec/api/transform/transform/doubletransform/DoubleMathOpTransform.vb:67-88 | src/DeepLearning4VB/org/datavec/api/transform/transform/floattransform/FloatMathOpTransform.vb:67-88 — 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 (22 lines × 2) src/DeepLearning4VB/org/datavec/api/transform/transform/integer/IntegerMathOpTransform.vb:66 — src/DeepLearning4VB/org/datavec/api/transform/transform/integer/IntegerMathOpTransform.vb:66-87 | src/DeepLearning4VB/org/datavec/api/transform/transform/longtransform/LongMathOpTransform.vb:66-87 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Duplicated block (20 lines × 2) · ×2
  • Duplicated block (20 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/managed/kernels/ManagedBlas.Level3.vb:120 — src/DeepLearning4VB/org/nd4vb/linalg/managed/kernels/ManagedBlas.Level3.vb:120-139 | src/DeepLearning4VB/org/nd4vb/linalg/managed/kernels/ManagedBlas.Level3.vb:502-521 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (20 lines × 2) src/DeepLearning4VB/org/datavec/api/transform/transform/categorical/CategoricalToOneHotTransform.vb:103 — src/DeepLearning4VB/org/datavec/api/transform/transform/categorical/CategoricalToOneHotTransform.vb:103-122 | src/DeepLearning4VB/org/datavec/api/transform/transform/integer/IntegerToOneHotTransform.vb:95-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.
D4 · Code Duplication · Duplicated block (14 lines × 3) · ×2
  • Duplicated block (14 lines × 3) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/Conv2DConfig.vb:239 — src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/Conv2DConfig.vb:239-252 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/DeConv2DConfig.vb:212-225 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/DeConv3DConfig.vb:275-288 — before extracting anything, compare `src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/Conv2DConfig.vb` and `src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/DeConv2DConfig.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 61 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/Conv2DConfig.vb:253` calls `Equals` and `src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/DeConv2DConfig.vb:226` 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 (14 lines × 3) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/DeConv3D.vb:104 — src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/DeConv3D.vb:104-117 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/DeConv3DDerivative.vb:75-88 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/DeConv3DTF.vb:78-91 — 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 all 3 call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (6 lines × 3) · ×2
  • Duplicated block (6 lines × 3) src/DeepLearning4VB/org/nd4vb/linalg/util/NDArrayUtil.vb:42 — src/DeepLearning4VB/org/nd4vb/linalg/util/NDArrayUtil.vb:42-47 | src/DeepLearning4VB/org/nd4vb/linalg/util/NDArrayUtil.vb:56-61 | src/DeepLearning4VB/org/nd4vb/linalg/util/NDArrayUtil.vb:69-74 — 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.
  • Duplicated block (6 lines × 3) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseReduceBoolOp.vb:135 — src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseReduceBoolOp.vb:135-140 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseReduceLongOp.vb:130-135 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseReduceSameOp.vb:135-140 — before extracting anything, compare `src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseReduceBoolOp.vb` and `src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseReduceLongOp.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 136 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 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.
DM11 · Constructible invalid state · Constructible in an invalid state · ×2
  • Constructible in an invalid state: AggregateAxpy src/DeepLearning4VB/org/nd4vb/linalg/api/ops/aggregates/impl/AggregateAxpy.vb:36 — `AggregateAxpy`'s public constructor takes `alpha` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `AggregateAxpy` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: AggregateGEMM src/DeepLearning4VB/org/nd4vb/linalg/api/ops/aggregates/impl/AggregateGEMM.vb:38 — `AggregateGEMM`'s public constructor takes `Order`, `TransA`, `TransB`, `M`, … as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `AggregateGEMM` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
DM4 · Rich vs anemic model · Anemic entity · ×2
  • Anemic entity: AggregateAxpy src/DeepLearning4VB/org/nd4vb/linalg/api/ops/aggregates/impl/AggregateAxpy.vb:31 — `AggregateAxpy` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: AggregateGEMM src/DeepLearning4VB/org/nd4vb/linalg/api/ops/aggregates/impl/AggregateGEMM.vb:31 — `AggregateGEMM` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
D17 · Explicit Debt · HackComment · ×1
  • HackComment src/DeepLearning4VB/org/nd4vb/linalg/string/NDArrayStrings.vb:227 — 'hack fix for slice issue with 'f' order — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
D18 · Solution Shape · Build failed · ×1
  • Build failed — The target solution did not build cleanly (errors: 68), which caps Solution Shape at 3/10 — the most basic shape signal is that it compiles. First errors: BC30518: Overload resolution failed because no accessible 'createUninitialized' can be called with these arguments:; BC30518: Overload resolution failed because no accessible 'create' can be called with these arguments:; BC30456: 'Random' is not a member of 'Nd4vb'.; BC30002: Type 'ManagedNDArray' is not defined.; BC30456: 'factory' is not a member of 'Nd4vb'..
D4 · Code Duplication · Near-duplicate member pair (40 shared lines) · ×1
  • Near-duplicate member pair (40 shared lines) src/DeepLearning4VB/org/nd4vb/linalg/managed/kernels/ManagedBlas.Level3.vb:50 — src/DeepLearning4VB/org/nd4vb/linalg/managed/kernels/ManagedBlas.Level3.vb:50-139 | src/DeepLearning4VB/org/nd4vb/linalg/managed/kernels/ManagedBlas.Level3.vb:432-521 — These two members are variants of one another: 40 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication · Edited copy of a member (45 corresponding lines) · ×1
  • Edited copy of a member (45 corresponding lines) src/DeepLearning4VB/org/nd4vb/linalg/managed/kernels/ManagedBlas.Level3.vb:170 — src/DeepLearning4VB/org/nd4vb/linalg/managed/kernels/ManagedBlas.Level3.vb:170-214 | src/DeepLearning4VB/org/nd4vb/linalg/managed/kernels/ManagedBlas.Level3.vb:552-596 — These two members are one piece of code written twice and then edited apart: 45 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 (38 corresponding lines) · ×1
  • Edited copy of a member (38 corresponding lines) src/DeepLearning4VB/org/nd4vb/linalg/managed/kernels/ManagedBlas.Level3.vb:222 — src/DeepLearning4VB/org/nd4vb/linalg/managed/kernels/ManagedBlas.Level3.vb:222-259 | src/DeepLearning4VB/org/nd4vb/linalg/managed/kernels/ManagedBlas.Level3.vb:604-641 — These two members are one piece of code written twice and then edited apart: 38 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 (43 lines × 2) · ×1
  • Duplicated block (43 lines × 2) src/DeepLearning4VB/org/nd4vb/autodiff/functions/DifferentialFunction.vb:340 — src/DeepLearning4VB/org/nd4vb/autodiff/functions/DifferentialFunction.vb:340-382 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/BaseConvolutionConfig.vb:116-158 — before extracting anything, compare `src/DeepLearning4VB/org/nd4vb/autodiff/functions/DifferentialFunction.vb` and `src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/BaseConvolutionConfig.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 58 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (25–27 lines × 3) · ×1
  • Duplicated block (25–27 lines × 3) src/DeepLearning4VB/org/datavec/api/transform/analysis/counter/DoubleAnalysisCounter.vb:113 — src/DeepLearning4VB/org/datavec/api/transform/analysis/counter/DoubleAnalysisCounter.vb:113-139 | src/DeepLearning4VB/org/datavec/api/transform/analysis/counter/IntegerAnalysisCounter.vb:126-150 | src/DeepLearning4VB/org/datavec/api/transform/analysis/counter/LongAnalysisCounter.vb:119-143 — before extracting anything, compare `src/DeepLearning4VB/org/datavec/api/transform/analysis/counter/IntegerAnalysisCounter.vb` and `src/DeepLearning4VB/org/datavec/api/transform/analysis/counter/LongAnalysisCounter.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 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 (23 lines × 2) · ×1
  • Duplicated block (23 lines × 2) src/DeepLearning4VB/org/datavec/api/transform/transform/doubletransform/DoubleMathFunctionTransform.vb:45 — src/DeepLearning4VB/org/datavec/api/transform/transform/doubletransform/DoubleMathFunctionTransform.vb:45-67 | src/DeepLearning4VB/org/datavec/api/transform/transform/floattransform/FloatMathFunctionTransform.vb:65-87 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/DeepLearning4VB/org/datavec/api/transform/transform/doubletransform/DoubleMathFunctionTransform.vb:69` calls `signum` and `src/DeepLearning4VB/org/datavec/api/transform/transform/floattransform/FloatMathFunctionTransform.vb:89` 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.
D4 · Code Duplication · Duplicated block (21 lines × 3) · ×1
  • Duplicated block (21 lines × 3) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/Conv2DConfig.vb:220 — src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/Conv2DConfig.vb:220-240 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/DeConv2DConfig.vb:193-213 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/Pooling2DConfig.vb:230-250 — before extracting anything, compare `src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/Conv2DConfig.vb` and `src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/convolution/config/DeConv2DConfig.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 61 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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.
D4 · Code Duplication · Duplicated block (20 lines × 4) · ×1
  • Duplicated block (20 lines × 4) src/DeepLearning4VB/org/datavec/api/transform/condition/ConditionOp.vb:49 — src/DeepLearning4VB/org/datavec/api/transform/condition/ConditionOp.vb:49-68 | src/DeepLearning4VB/org/datavec/api/transform/condition/ConditionOp.vb:73-92 | src/DeepLearning4VB/org/datavec/api/transform/condition/ConditionOp.vb:97-116 | src/DeepLearning4VB/org/datavec/api/transform/condition/ConditionOp.vb:121-140 — all 4 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.
D4 · Code Duplication · Duplicated block (16 lines × 2) · ×1
  • Duplicated block (16 lines × 2) src/DeepLearning4VB/org/nd4vb/linalg/api/shape/LongShapeDescriptor.vb:72 — src/DeepLearning4VB/org/nd4vb/linalg/api/shape/LongShapeDescriptor.vb:72-87 | src/DeepLearning4VB/org/nd4vb/linalg/api/shape/ShapeDescriptor.vb:65-80 — 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.
D4 · Code Duplication · Duplicated block (15 lines × 5) · ×1
  • Duplicated block (15 lines × 5) src/DeepLearning4VB/org/datavec/api/writable/ByteWritable.vb:80 — src/DeepLearning4VB/org/datavec/api/writable/ByteWritable.vb:80-94 | src/DeepLearning4VB/org/datavec/api/writable/DoubleWritable.vb:78-92 | src/DeepLearning4VB/org/datavec/api/writable/FloatWritable.vb:79-93 | src/DeepLearning4VB/org/datavec/api/writable/IntWritable.vb:80-94 | src/DeepLearning4VB/org/datavec/api/writable/LongWritable.vb:80-94 — 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 all 5 call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (15 lines × 3) · ×1
  • Duplicated block (15 lines × 3) src/DeepLearning4VB/org/nd4vb/common/util/ArrayUtil.vb:4000 — src/DeepLearning4VB/org/nd4vb/common/util/ArrayUtil.vb:4000-4014 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/DynamicCustomOp.vb:694-708 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/layers/recurrent/weights/RNNWeights.vb:40-54 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
D4 · Code Duplication · Duplicated block (11 lines × 3) · ×1
  • Duplicated block (11 lines × 3) src/DeepLearning4VB/org/nd4vb/linalg/managed/kernels/ElementWiseKernels.vb:40 — src/DeepLearning4VB/org/nd4vb/linalg/managed/kernels/ElementWiseKernels.vb:40-50 | src/DeepLearning4VB/org/nd4vb/linalg/managed/kernels/ElementWiseKernels.vb:116-126 | src/DeepLearning4VB/org/nd4vb/linalg/managed/kernels/ElementWiseKernels.vb:194-204 — 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.
D4 · Code Duplication · Duplicated block (4–8 lines × 3) · ×1
  • Duplicated block (4–8 lines × 3) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/executioner/DefaultOpExecutioner.vb:317 — src/DeepLearning4VB/org/nd4vb/linalg/api/ops/executioner/DefaultOpExecutioner.vb:317-320 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/executioner/OpExecutionerUtil.vb:161-168 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/executioner/OpExecutionerUtil.vb:179-186 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
D4 · Code Duplication · Duplicated block (3–5 lines × 5) · ×1
  • Duplicated block (3–5 lines × 5) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseTransformBoolOp.vb:110 — src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseTransformBoolOp.vb:110-114 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseTransformFloatOp.vb:95-99 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseTransformSameOp.vb:105-109 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseTransformStrictOp.vb:94-96 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/transforms/MaxOut.vb:104-108 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 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 5 times. 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 (3–102 lines × 5) · ×1
  • Duplicated block (3–102 lines × 5) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseReduceBoolOp.vb:163 — src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseReduceBoolOp.vb:163-165 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseReduceLongOp.vb:159-161 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/reduce/custom/BaseDynamicCustomBoolReduction.vb:40-141 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/reduce/custom/BaseDynamicCustomIndexReduction.vb:173-175 | src/DeepLearning4VB/org/nd4vb/linalg/api/ops/impl/reduce/custom/BaseDynamicCustomLongReduction.vb:40-147 — before extracting anything, compare `src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseReduceBoolOp.vb` and `src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseReduceLongOp.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 136 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseReduceBoolOp.vb:168` calls `emptyValue` and `src/DeepLearning4VB/org/nd4vb/linalg/api/ops/BaseReduceLongOp.vb:164` 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.
D4 · Code Duplication · Duplicated block (5 lines × 6) · ×1
  • Duplicated block (5 lines × 6) src/DeepLearning4VB/org/datavec/api/transform/transform/BaseColumnsMathOpTransform.vb:137 — src/DeepLearning4VB/org/datavec/api/transform/transform/BaseColumnsMathOpTransform.vb:137-141 | src/DeepLearning4VB/org/datavec/api/transform/transform/column/ReorderColumnsTransform.vb:129-133 | src/DeepLearning4VB/org/datavec/api/transform/transform/condition/ConditionalCopyValueTransform.vb:103-107 | src/DeepLearning4VB/org/datavec/api/transform/transform/condition/ConditionalReplaceValueTransform.vb:93-97 | src/DeepLearning4VB/org/datavec/api/transform/transform/condition/ConditionalReplaceValueTransformWithDefault.vb:117-121 | src/DeepLearning4VB/org/datavec/api/transform/transform/string/ConcatenateStringColumns.vb:104-108 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 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 6 times.
D4 · Code Duplication · Duplicated block (6 lines × 6) · ×1
  • Duplicated block (6 lines × 6) src/DeepLearning4VB/org/datavec/api/transform/transform/BaseColumnTransform.vb:157 — src/DeepLearning4VB/org/datavec/api/transform/transform/BaseColumnTransform.vb:157-162 | src/DeepLearning4VB/org/datavec/api/transform/transform/categorical/PivotTransform.vb:219-224 | src/DeepLearning4VB/org/datavec/api/transform/transform/condition/ConditionalCopyValueTransform.vb:125-130 | src/DeepLearning4VB/org/datavec/api/transform/transform/condition/ConditionalReplaceValueTransform.vb:118-123 | src/DeepLearning4VB/org/datavec/api/transform/transform/condition/ConditionalReplaceValueTransformWithDefault.vb:134-139 | src/DeepLearning4VB/org/datavec/api/transform/transform/parse/ParseDoubleTransform.vb:68-73 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 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 6 times. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/DeepLearning4VB/org/datavec/api/transform/transform/categorical/PivotTransform.vb:227` calls `toString` and `src/DeepLearning4VB/org/datavec/api/transform/transform/condition/ConditionalCopyValueTransform.vb:133` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D8 · Code Coverage · Coverage not measured · ×1
  • Coverage not measured — no coverage collector is wired up — Coverage NOT MEASURED: `--collect:"XPlat Code Coverage"` names a data collector that ships in the `coverlet.collector` package, and this repository wires up none — no test project references it and no runsettings declares one. The absence of coverage here is therefore not evidence about the suite or about our analyzer environment: without a collector, `--collect` produces nothing even from a suite that builds and passes. Add a `coverlet.collector` PackageReference to the test project(s) (or commit the Cobertura/OpenCover/lcov report your CI produces) and real coverage will be measured. It is excluded from the score rather than counted as a near-zero defect.
P1 · CI/CD gates · No CI pipeline · ×1
  • No CI pipeline — No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
SC1 · Supply-chain hygiene · NuGet dependencies are not locked · ×1
  • NuGet dependencies are not locked — No packages.lock.json and no central package management — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
Minor — 25 finding(s)
AX6 · Interface segregation · Fat interface · ×20
  • Fat interface: Table(Of R, C, V) (19 members) src/DeepLearning4VB/JavaCompat/Table.vb:47 — `Table(Of R, C, V)` declares 19 members: `contains`, `containsRow`, `containsColumn`, `containsValue`, `get`, `isEmpty`, `size`, `clear`, `put`, `putAll`, `remove`, `row`, `column`, `cellSet`, `rowKeySet`, `columnKeySet`, `values`, `rowMap`, `columnMap`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: RecordReader (16 members) src/DeepLearning4VB/org/datavec/api/records/reader/RecordReader.vb:39 — `RecordReader` declares 16 members under just 12 distinct name(s): `initialize`, `initialize`, `batchesSupported`, `next`, `next`, `hasNext`, `Labels`, `reset`, `resetSupported`, `record`, `nextRecord`, `loadFromMetaData`, `loadFromMetaData`, `Listeners`, `setListeners`, `setListeners`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. That is an OVERLOAD SET, not 16 separate responsibilities: a caller binds to 12 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 16 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface.
  • Fat interface: Level1 (19 members) src/DeepLearning4VB/org/nd4vb/linalg/api/blas/Level1.vb:26 — `Level1` declares 19 members under just 13 distinct name(s): `dot`, `dot`, `nrm2`, `asum`, `asum`, `iamax`, `iamax`, `iamax`, `iamin`, `swap`, `copy`, `copy`, `axpy`, `axpy`, `rotg`, `rot`, `rotmg`, `scal`, `supportsDataBufferL1Ops`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. That is an OVERLOAD SET, not 19 separate responsibilities: a caller binds to 13 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 19 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface.
  • Fat interface: Level2 (16 members) src/DeepLearning4VB/org/nd4vb/linalg/api/blas/Level2.vb:25 — `Level2` declares 16 members: `gemv`, `gbmv`, `ger`, `sbmv`, `spmv`, `spr`, `spr2`, `symv`, `syr`, `syr2`, `tbmv`, `tbsv`, `tpmv`, `tpsv`, `trmv`, `trsv`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: DataBuffer (76 members) src/DeepLearning4VB/org/nd4vb/linalg/api/buffer/DataBuffer.vb:53 — `DataBuffer` declares 76 members: `GenerationId`, `sameUnderlyingData`, `read`, `write`, `array`, `dirty`, `underlyingDataBuffer`, `originalDataBuffer`, `copyAtStride`, `getAllocationMode`, `persist`, `isPersist`, `unPersist`, `ElementSize`, `removeReferencing`, `references`, `addReferencing`, `assign`, `assign`, `assign`, `assign`, `getDoublesAt`, `getFloatsAt`, `getIntsAt`, `getLongsAt`, `getDoublesAt`, `getFloatsAt`, `getIntsAt`, `getLongsAt`, `assign`, `assign`, `setData`, `setData`, `setData`, `setData`, `setData`, `setData`, `setData`, `asBytes`, `dataType`, and 36 more. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 76 declarations carry 51 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 51 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: DataBufferFactory (126 members) src/DeepLearning4VB/org/nd4vb/linalg/api/buffer/factory/DataBufferFactory.vb:40 — `DataBufferFactory` declares 126 members: `setAllocationMode`, `allocationMode`, `create`, `create`, `createDouble`, `createSame`, `createSame`, `createFloat`, `createInt`, `createDouble`, `createFloat`, `createInt`, `createDouble`, `createDouble`, `createDouble`, `createFloat`, `createFloat`, `createInt`, `createDouble`, `createFloat`, `createFloat`, `createInt`, `createDouble`, `createFloat`, `createInt`, `createDouble`, `createFloat`, `createInt`, `createDouble`, `createFloat`, `createInt`, `createDouble`, `createDouble`, `createDouble`, `createFloat`, `createFloat`, `createFloat`, `create`, `create`, `createInt`, and 86 more. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 126 declarations carry 23 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 23 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: MemoryManager (20 members) src/DeepLearning4VB/org/nd4vb/linalg/api/memory/MemoryManager.vb:35 — `MemoryManager` declares 20 members: `CurrentWorkspace`, `notifyScopeEntered`, `notifyScopeLeft`, `invokeGcOccasionally`, `invokeGc`, `togglePeriodicGc`, `toggleAveraging`, `PeriodicGcActive`, `LastGcTime`, `OccasionalGcFrequency`, `AverageLoopTime`, `AutoGcWindow`, `collect`, `purgeCaches`, `memcpy`, `memset`, `scopeOutOfWorkspaces`, `BandwidthUse`, `allocatedMemory`, `releaseCurrentContext`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: MemoryWorkspace (25 members) src/DeepLearning4VB/org/nd4vb/linalg/api/memory/MemoryWorkspace.vb:17 — `MemoryWorkspace` declares 25 members: `WorkspaceConfiguration`, `WorkspaceType`, `Id`, `DeviceId`, `ThreadId`, `GenerationId`, `PrimaryOffset`, `notifyScopeEntered`, `notifyScopeBorrowed`, `notifyScopeLeft`, `ScopeActive`, `initializeWorkspace`, `destroyWorkspace`, `destroyWorkspace`, `toggleWorkspaceUse`, `ThisCycleAllocations`, `enableDebug`, `LastCycleAllocations`, `MaxCycleAllocations`, `CurrentSize`, `close`, `ParentWorkspace`, `tagOutOfScopeUse`, `PreviousWorkspace`, `CurrentOffset`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 25 declarations carry 24 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 24 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: MemoryWorkspaceManager (24 members) src/DeepLearning4VB/org/nd4vb/linalg/api/memory/MemoryWorkspaceManager.vb:29 — `MemoryWorkspaceManager` declares 24 members: `UUID`, `DebugMode`, `DefaultWorkspaceConfiguration`, `createNewWorkspace`, `createNewWorkspace`, `createNewWorkspace`, `createNewWorkspace`, `WorkspaceForCurrentThread`, `getWorkspaceForCurrentThread`, `getWorkspaceForCurrentThread`, `setWorkspaceForCurrentThread`, `destroyWorkspace`, `destroyAllWorkspacesForCurrentThread`, `destroyWorkspace`, `AndActivateWorkspace`, `getAndActivateWorkspace`, `getAndActivateWorkspace`, `checkIfWorkspaceExists`, `checkIfWorkspaceExistsAndActive`, `scopeOutOfWorkspaces`, `printAllocationStatisticsForCurrentThread`, `AllWorkspacesIdsForCurrentThread`, `AllWorkspacesForCurrentThread`, `anyWorkspaceActiveForCurrentThread`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 24 declarations carry 18 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 18 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: INDArray (343 members) src/DeepLearning4VB/org/nd4vb/linalg/api/ndarray/INDArray.vb:55 — `INDArray` declares 343 members: `shapeInfoToString`, `shapeInfoDataBuffer`, `View`, `Sparse`, `Compressed`, `markAsCompressed`, `rank`, `stride`, `elementWiseStride`, `getDoubleUnsafe`, `getString`, `putScalarUnsafe`, `vectorsAlongDimension`, `vectorAlongDimension`, `tensorsAlongDimension`, `tensorAlongDimension`, `cumsumi`, `cumsum`, `assign`, `assignIf`, `replaceWhere`, `putScalar`, `putScalar`, `putScalar`, `putScalar`, `putScalar`, `putScalar`, `putScalar`, `putScalar`, `putScalar`, `putScalar`, `lt`, `putScalar`, `putScalar`, `eps`, `eq`, `gt`, `gte`, `lte`, `lt`, and 303 more. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 343 declarations carry 216 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 216 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: CustomOp (41 members) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/CustomOp.vb:29 — `CustomOp` declares 41 members: `opName`, `opHash`, `InplaceCall`, `outputArguments`, `inputArguments`, `iArgs`, `tArgs`, `bArgs`, `dArgs`, `addTArgument`, `sArgs`, `addIArgument`, `addIArgument`, `addBArgument`, `addDArgument`, `removeIArgument`, `addSArgument`, `removeSArgument`, `getSArgument`, `getBArgument`, `getIArgument`, `numIArguments`, `removeTArgument`, `getTArgument`, `numTArguments`, `numBArguments`, `numDArguments`, `numSArguments`, `addInputArgument`, `removeInputArgument`, `getInputArgument`, `numInputArguments`, `addOutputArgument`, `removeOutputArgument`, `getOutputArgument`, `numOutputArguments`, `calculateOutputShape`, `calculateOutputShape`, `Descriptor`, `assertValidForExecution`, and 1 more. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 41 declarations carry 39 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 39 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: OpContext (32 members) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/OpContext.vb:18 — `OpContext` declares 32 members: `setIArguments`, `getIArguments`, `numIArguments`, `setTArguments`, `getTArguments`, `numTArguments`, `setDArguments`, `getDArguments`, `numDArguments`, `setBArguments`, `getBArguments`, `numBArguments`, `setRngStates`, `RngStates`, `setInputArray`, `setInputArrays`, `setInputArrays`, `getInputArrays`, `numInputArguments`, `getInputArray`, `setOutputArray`, `setOutputArrays`, `setOutputArrays`, `getOutputArrays`, `getOutputArray`, `numOutputArguments`, `markInplace`, `allowHelpers`, `shapeFunctionOverride`, `getExecutionMode`, `setExecutionMode`, `purge`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 32 declarations carry 30 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 30 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: Aggregate (17 members) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/aggregates/Aggregate.vb:33 — `Aggregate` declares 17 members: `name`, `opNum`, `FinalResult`, `Arguments`, `Shapes`, `IndexingArguments`, `RealArguments`, `IntArrayArguments`, `maxArguments`, `maxShapes`, `maxIntArrays`, `maxIntArraySize`, `maxIndexArguments`, `maxRealArguments`, `RequiredBatchMemorySize`, `SharedMemorySize`, `ThreadsPerInstance`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: OpExecutioner (61 members) src/DeepLearning4VB/org/nd4vb/linalg/api/ops/executioner/OpExecutioner.vb:38 — `OpExecutioner` declares 61 members: `Verbose`, `Debug`, `type`, `LastOp`, `exec`, `exec`, `execAndReturn`, `execAndReturn`, `execAndReturn`, `execAndReturn`, `execAndReturn`, `exec`, `exec`, `exec`, `exec`, `execAndReturn`, `exec`, `exec`, `exec`, `exec`, `exec`, `exec`, `exec`, `EnvironmentInformation`, `setProfilingMode`, `getProfilingMode`, `ProfilingConfig`, `TADManager`, `printEnvironmentInformation`, `push`, `commit`, `thresholdEncode`, `thresholdEncode`, `thresholdDecode`, `bitmapEncode`, `bitmapEncode`, `bitmapDecode`, `CustomOperations`, `execAndReturn`, `exec`, and 21 more. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 61 declarations carry 34 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 34 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: Random (35 members) src/DeepLearning4VB/org/nd4vb/linalg/api/rng/Random.vb:35 — `Random` declares 35 members under just 14 distinct name(s): `setSeed`, `getSeed`, `setSeed`, `setSeed`, `nextBytes`, `nextInt`, `nextInt`, `nextInt`, `nextLong`, `nextBoolean`, `nextFloat`, `nextDouble`, `nextGaussian`, `nextGaussian`, `nextGaussian`, `nextGaussian`, `nextGaussian`, `nextDouble`, `nextDouble`, `nextDouble`, `nextDouble`, `nextFloat`, `nextFloat`, `nextFloat`, `nextFloat`, `nextInt`, `nextInt`, `nextInt`, `nextInt`, `Position`, `reSeed`, `reSeed`, `rootState`, `nodeState`, `setStates`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. That is an OVERLOAD SET, not 35 separate responsibilities: a caller binds to 14 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 35 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface.
  • Fat interface: Distribution (18 members) src/DeepLearning4VB/org/nd4vb/linalg/api/rng/distribution/Distribution.vb:31 — `Distribution` declares 18 members under just 13 distinct name(s): `probability`, `density`, `cumulativeProbability`, `cumulativeProbability`, `inverseCumulativeProbability`, `NumericalMean`, `NumericalVariance`, `SupportLowerBound`, `SupportUpperBound`, `SupportLowerBoundInclusive`, `SupportUpperBoundInclusive`, `SupportConnected`, `reseedRandomGenerator`, `sample`, `sample`, `sample`, `sample`, `sample`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. That is an OVERLOAD SET, not 18 separate responsibilities: a caller binds to 13 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 18 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface.
  • Fat interface: BlasWrapper (39 members) src/DeepLearning4VB/org/nd4vb/linalg/factory/BlasWrapper.vb:36 — `BlasWrapper` declares 39 members: `swap`, `level1`, `level2`, `level3`, `lapack`, `scal`, `scal`, `copy`, `axpy`, `axpy`, `axpy`, `dot`, `nrm2`, `asum`, `iamax`, `gemv`, `gemv`, `gemv`, `ger`, `ger`, `ger`, `gesv`, `checkInfo`, `sysv`, `syev`, `syevx`, `syevx`, `syevd`, `syevr`, `syevr`, `syevr`, `posv`, `geev`, `sygvd`, `gelsd`, `geqrf`, `ormqr`, `saxpy`, `saxpy`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 39 declarations carry 28 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 28 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: Environment (28 members) src/DeepLearning4VB/org/nd4vb/linalg/factory/Environment.vb:29 — `Environment` declares 28 members: `blasMajorVersion`, `blasMinorVersion`, `blasPatchVersion`, `Verbose`, `Debug`, `Profiling`, `DetectingLeaks`, `DebugAndVerbose`, `LeaksDetector`, `helpersAllowed`, `allowHelpers`, `tadThreshold`, `setTadThreshold`, `elementwiseThreshold`, `setElementwiseThreshold`, `maxThreads`, `setMaxThreads`, `maxMasterThreads`, `setMaxMasterThreads`, `MaxPrimaryMemory`, `MaxSpecialMemory`, `MaxDeviceMemory`, `CPU`, `setGroupLimit`, `setDeviceLimit`, `getGroupLimit`, `getDeviceLimit`, `getDeviceCouner`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: NDArrayFactory (195 members) src/DeepLearning4VB/org/nd4vb/linalg/factory/NDArrayFactory.vb:50 — `NDArrayFactory` declares 195 members: `blas`, `lapack`, `level1`, `level2`, `level3`, `createBlas`, `createLevel1`, `createLevel2`, `createLevel3`, `createLapack`, `setOrder`, `setDType`, `create`, `order`, `dtype`, `toFlattened`, `toFlattened`, `toFlattened`, `bilinearProducts`, `toFlattened`, `toFlattened`, `eye`, `rot90`, `rot`, `reverse`, `arange`, `copy`, `rand`, `rand`, `rand`, `appendBias`, `create`, `create`, `concat`, `specialConcat`, `pullRows`, `pullRows`, `pullRows`, `pullRows`, `shuffle`, and 155 more. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 195 declarations carry 47 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 47 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: WorkspaceMgr(Of T) (24 members) src/DeepLearning4VB/org/nd4vb/linalg/workspace/WorkspaceMgr.vb:35 — `WorkspaceMgr(Of T)` declares 24 members: `setWorkspaceName`, `getWorkspaceName`, `setWorkspace`, `setConfiguration`, `getConfiguration`, `ScopedOutFor`, `isScopedOut`, `hasConfiguration`, `notifyScopeEntered`, `notifyScopeEntered`, `notifyScopeBorrowed`, `isWorkspaceOpen`, `assertOpen`, `assertNotOpen`, `assertCurrentWorkspace`, `leverageTo`, `validateArrayLocation`, `create`, `create`, `createUninitialized`, `createUninitialized`, `dup`, `dup`, `castTo`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 24 declarations carry 20 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 20 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
D19 · Documentation Quality · Documentation · ×1
  • Documentation: no architecture or design documentation README.md — The PHASE2_DESIGN.md architecture doc is excellent but it is not referenced in any document, leaving readers who skim the root README unable to find where the managed ND4VB tensor engine and its op-inventory tables are documented. Link PHASE2_DESIGN.md from the root README so a reader can navigate directly to the design of the managed backend.
D26 · Project Cohesion · Split DeepLearning4VB(net481) · ×1
  • Split DeepLearning4VB(net481) — A deep learning framework whose namespaces are all ops implementations and data APIs for one domain, so it is a huge grab-bag. Suggested:
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.
M4 · Documentation accuracy · README/code drift · ×1
  • README/code drift README.md:140 — README advertises a microservices architecture, but the repo is a single project with no service manifests — searched for: `microservice`, `service-mesh`, `istio`. Each was matched case- and separator-insensitively against file and directory NAMES anywhere in the tree, and against the CONTENTS of manifest and configuration files (package.json and other *.json, *.csproj, *.props, *.sln/*.slnx, *.yml, *.toml, *.config, tool configs such as eslint.config.js, Dockerfile); the README's own prose never counts, so a claim is never refuted by merely being made. Nothing outside that search was read — a footprint living only in a submodule, in a file type not listed here, or under a name none of those terms matches is not seen, and this row is then wrong.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST — No static application security testing detected. For this repository's stack, add a Roslyn security analyzer package referenced from the project (the analyzer packages do analyse VB.NET), plus gitleaks for committed secrets — CodeQL has no VB.NET extractor, so its csharp pack would extract nothing from this tree and then report it clean — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 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.
Minor — 4 finding(s)
D12 · Dependency Hygiene · Outdated · ×4
  • Outdated: System.Text.Json — System.Text.Json 9.0.4 → 10.0.13 available (referenced by DeepLearning4VB).
  • Outdated: Microsoft.NET.Test.Sdk — Microsoft.NET.Test.Sdk 17.12.0 → 18.11.0 available (referenced by DeepLearning4VB.Tests).
  • Outdated: MSTest.TestAdapter — MSTest.TestAdapter 3.6.4 → 4.5.1 available (referenced by DeepLearning4VB.Tests).
  • Outdated: MSTest.TestFramework — MSTest.TestFramework 3.6.4 → 4.5.1 available (referenced by DeepLearning4VB.Tests).

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/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-a2601ef2bf6a4195a45169d9efe5ed28/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/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-a2601ef2bf6a4195a45169d9efe5ed28/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/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off .0artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesdotnet—dotnet list DeepLearning4VB.slnx package --vulnerable --include-transitive --format json0artifacts/raw/dotnet-vulnerable.json
D31 · IaC & Container Securitytrivy—trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.0—
D32 · Data Compliance (PII/GDPR)semgrep—semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.0—
D36 · Supply-chain Provenance & Signingprovenance—provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.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 (no readable dependency manifest)—none (no readable dependency manifest): 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 Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).0—

Run 01a15f55-b9c7-7923-b58e-073726090994 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Issues: 9 · Warnings: 238 · Recommendations: 25 · Info: 4 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 21-10-2026 @ 16:40 UTC.

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