Executive summary
fslaborg/Deedle falls short of our standard for production, held back most by its Architecture lens, the way the code is structured into parts. It scores 58 out of 100 and is rated Adequate, and 15 of its 20 critical findings are security problems in the build pipeline and in its code.
Architecture, at 56, is the weakest lens, level with Production Readiness, and counts most in the score. The best first step is replacing each deprecated dependency, worth about 2 points. Fixing the silenced warnings comes next, worth about 1 point.
Ten pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. One secret can leak from the build pipeline, and one weakness in the code could be used by an attacker. Pinning each tool to an exact version, limiting the secret to its own step and fixing the weaknesses the scanner points to would close these risks. Correcting the flagged pipeline settings would fix the three weaknesses in the build pipeline's configuration. The five warnings switched off for a whole file need narrowing to the lines that need them.
The product code is 26,904 lines, about β¬44,000 to rebuild.
The weakest lenses score close to each other, so improving any of them moves the score.
New since the last survey: 1 finding
- Code Duplication Β· Duplicated block (11 lines × 10) src/Deedle.Parquet/Parquet.fs
Fixed since the last survey: 59 findings
- Code Duplication Β· Duplicated block (6 lines × 10) src/Deedle.Parquet/Parquet.fs
- Code Coverage Β· Coverage not measured β no coverage collector is wired up
- Explicit Debt Β· AnalyzerSeverityNone repeated across 21 files packages/Microsoft.CodeAnalysis.Analyzers/editorconfig/PortedFromFxCopRulesEnabled/.editorconfig
- Explicit Debt Β· AnalyzerSeverityNone repeated across 21 files packages/Microsoft.CodeAnalysis.Analyzers/editorconfig/PortedFromFxCopRulesEnabled/.editorconfig
- Explicit Debt Β· AnalyzerSeverityNone repeated across 21 files packages/Microsoft.CodeAnalysis.Analyzers/editorconfig/PortedFromFxCopRulesEnabled/.editorconfig
- Explicit Debt Β· AnalyzerSeverityNone repeated across 21 files packages/Microsoft.CodeAnalysis.Analyzers/editorconfig/PortedFromFxCopRulesEnabled/.editorconfig
- Explicit Debt Β· AnalyzerSeverityNone repeated across 21 files packages/Microsoft.CodeAnalysis.Analyzers/editorconfig/PortedFromFxCopRulesEnabled/.editorconfig
- Explicit Debt Β· AnalyzerSeverityNone repeated across 21 files packages/Microsoft.CodeAnalysis.Analyzers/editorconfig/PortedFromFxCopRulesEnabled/.editorconfig
- Explicit Debt Β· AnalyzerSeverityNone repeated across 23 files packages/Microsoft.CodeAnalysis.Analyzers/editorconfig/PortedFromFxCopRulesEnabled/.editorconfig
- Explicit Debt Β· AnalyzerSeverityNone repeated across 21 files packages/Microsoft.CodeAnalysis.Analyzers/editorconfig/PortedFromFxCopRulesEnabled/.editorconfig
- Explicit Debt Β· AnalyzerSeverityNone repeated across 21 files packages/Microsoft.CodeAnalysis.Analyzers/editorconfig/PortedFromFxCopRulesEnabled/.editorconfig
- Explicit Debt Β· AnalyzerSeverityNone repeated across 21 files packages/Microsoft.CodeAnalysis.Analyzers/editorconfig/PortedFromFxCopRulesEnabled/.editorconfig
- Explicit Debt Β· AnalyzerSeverityNone repeated across 21 files packages/Microsoft.CodeAnalysis.Analyzers/editorconfig/PortedFromFxCopRulesEnabled/.editorconfig
- Explicit Debt Β· AnalyzerSeverityNone repeated across 21 files packages/Microsoft.CodeAnalysis.Analyzers/editorconfig/PortedFromFxCopRulesEnabled/.editorconfig
- Explicit Debt Β· AnalyzerSeverityNone repeated across 21 files packages/Microsoft.CodeAnalysis.Analyzers/editorconfig/PortedFromFxCopRulesEnabled/.editorconfig
- Explicit Debt Β· AnalyzerSeverityNone repeated across 21 files packages/Microsoft.CodeAnalysis.Analyzers/editorconfig/PortedFromFxCopRulesEnabled/.editorconfig
- Explicit Debt Β· AnalyzerSeverityNone repeated across 23 files packages/Microsoft.CodeAnalysis.Analyzers/editorconfig/PortedFromFxCopRulesEnabled/.editorconfig
- Explicit Debt Β· AnalyzerSeverityNone repeated across 21 files packages/Microsoft.CodeAnalysis.Analyzers/editorconfig/PortedFromFxCopRulesEnabled/.editorconfig
- Explicit Debt Β· AnalyzerSeverityNone repeated across 21 files packages/Microsoft.CodeAnalysis.Analyzers/editorconfig/PortedFromFxCopRulesEnabled/.editorconfig
- Explicit Debt Β· AnalyzerSeverityNone repeated across 21 files packages/Microsoft.CodeAnalysis.Analyzers/editorconfig/PortedFromFxCopRulesEnabled/.editorconfig
- Explicit Debt Β· AnalyzerSeverityNone repeated across 21 files packages/Microsoft.CodeAnalysis.Analyzers/editorconfig/PortedFromFxCopRulesEnabled/.editorconfig
- Explicit Debt Β· AnalyzerSeverityNone repeated across 23 files packages/Microsoft.CodeAnalysis.Analyzers/editorconfig/PortedFromFxCopRulesEnabled/.editorconfig
- Explicit Debt Β· AnalyzerSeverityNone repeated across 21 files packages/Microsoft.CodeAnalysis.Analyzers/editorconfig/PortedFromFxCopRulesEnabled/.editorconfig
- Explicit Debt Β· AnalyzerSeverityNone repeated across 21 files packages/Microsoft.CodeAnalysis.Analyzers/editorconfig/PortedFromFxCopRulesEnabled/.editorconfig
- Explicit Debt Β· AnalyzerSeverityNone repeated across 21 files packages/Microsoft.CodeAnalysis.Analyzers/editorconfig/PortedFromFxCopRulesEnabled/.editorconfig
- Explicit Debt Β· AnalyzerSeverityNone repeated across 21 files packages/Microsoft.CodeAnalysis.Analyzers/editorconfig/PortedFromFxCopRulesEnabled/.editorconfig
- Explicit Debt Β· AnalyzerSeverityNone repeated across 21 files packages/Microsoft.CodeAnalysis.Analyzers/editorconfig/PortedFromFxCopRulesEnabled/.editorconfig
- Explicit Debt Β· AnalyzerSeverityNone repeated across 21 files packages/Microsoft.CodeAnalysis.Analyzers/editorconfig/PortedFromFxCopRulesEnabled/.editorconfig
- Explicit Debt Β· AnalyzerSeverityNone repeated across 21 files packages/Microsoft.CodeAnalysis.Analyzers/editorconfig/PortedFromFxCopRulesEnabled/.editorconfig
- Explicit Debt Β· AnalyzerSeverityNone repeated across 23 files packages/Microsoft.CodeAnalysis.Analyzers/editorconfig/PortedFromFxCopRulesEnabled/.editorconfig
- Explicit Debt Β· AnalyzerSeverityNone repeated across 21 files packages/Microsoft.CodeAnalysis.Analyzers/editorconfig/PortedFromFxCopRulesEnabled/.editorconfig
- Explicit Debt Β· AnalyzerSeverityNone repeated across 21 files packages/Microsoft.CodeAnalysis.Analyzers/editorconfig/PortedFromFxCopRulesEnabled/.editorconfig
- Explicit Debt Β· AnalyzerSeverityNone repeated across 21 files packages/Microsoft.CodeAnalysis.Analyzers/editorconfig/PortedFromFxCopRulesEnabled/.editorconfig
- Explicit Debt Β· AnalyzerSeverityNone repeated across 21 files packages/Microsoft.CodeAnalysis.Analyzers/editorconfig/PortedFromFxCopRulesEnabled/.editorconfig
- Explicit Debt Β· AnalyzerSeverityNone repeated across 21 files packages/Microsoft.CodeAnalysis.Analyzers/editorconfig/PortedFromFxCopRulesEnabled/.editorconfig
- Explicit Debt Β· AnalyzerSeverityNone repeated across 21 files packages/Microsoft.CodeAnalysis.Analyzers/editorconfig/PortedFromFxCopRulesEnabled/.editorconfig
- Explicit Debt Β· AnalyzerSeverityNone repeated across 21 files packages/Microsoft.CodeAnalysis.Analyzers/editorconfig/PortedFromFxCopRulesEnabled/.editorconfig
- Explicit Debt Β· AnalyzerSeverityNone repeated across 21 files packages/Microsoft.CodeAnalysis.Analyzers/editorconfig/PortedFromFxCopRulesEnabled/.editorconfig
- Explicit Debt Β· AnalyzerSeverityNone repeated across 21 files packages/Microsoft.CodeAnalysis.Analyzers/editorconfig/PortedFromFxCopRulesEnabled/.editorconfig
- Explicit Debt Β· AnalyzerSeverityNone repeated across 21 files packages/Microsoft.CodeAnalysis.Analyzers/editorconfig/PortedFromFxCopRulesEnabled/.editorconfig
- Explicit Debt Β· AnalyzerSeverityNone repeated across 21 files packages/Microsoft.CodeAnalysis.Analyzers/editorconfig/PortedFromFxCopRulesEnabled/.editorconfig
- Explicit Debt Β· AnalyzerSeverityNone repeated across 21 files packages/Microsoft.CodeAnalysis.Analyzers/editorconfig/PortedFromFxCopRulesEnabled/.editorconfig
- Explicit Debt Β· AnalyzerSeverityNone repeated across 21 files packages/Microsoft.CodeAnalysis.Analyzers/editorconfig/PortedFromFxCopRulesEnabled/.editorconfig
- Explicit Debt Β· AnalyzerSeverityNone repeated across 21 files packages/Microsoft.CodeAnalysis.Analyzers/editorconfig/PortedFromFxCopRulesEnabled/.editorconfig
- Explicit Debt Β· AnalyzerSeverityNone repeated across 21 files packages/Microsoft.CodeAnalysis.Analyzers/editorconfig/PortedFromFxCopRulesEnabled/.editorconfig
- Explicit Debt Β· AnalyzerSeverityNone repeated across 21 files packages/Microsoft.CodeAnalysis.Analyzers/editorconfig/PortedFromFxCopRulesEnabled/.editorconfig
- Explicit Debt Β· AnalyzerSeverityNone repeated across 21 files packages/Microsoft.CodeAnalysis.Analyzers/editorconfig/PortedFromFxCopRulesEnabled/.editorconfig
- Explicit Debt Β· AnalyzerSeverityNone repeated across 21 files packages/Microsoft.CodeAnalysis.Analyzers/editorconfig/PortedFromFxCopRulesEnabled/.editorconfig
- Explicit Debt Β· AnalyzerSeverityNone repeated across 21 files packages/Microsoft.CodeAnalysis.Analyzers/editorconfig/PortedFromFxCopRulesEnabled/.editorconfig
- Explicit Debt Β· AnalyzerSeverityNone repeated across 21 files packages/Microsoft.CodeAnalysis.Analyzers/editorconfig/PortedFromFxCopRulesEnabled/.editorconfig
- Explicit Debt Β· AnalyzerSeverityNone repeated across 21 files packages/Microsoft.CodeAnalysis.Analyzers/editorconfig/PortedFromFxCopRulesEnabled/.editorconfig
- Explicit Debt Β· AnalyzerSeverityNone repeated across 21 files packages/Microsoft.CodeAnalysis.Analyzers/editorconfig/PortedFromFxCopRulesEnabled/.editorconfig
- Explicit Debt Β· AnalyzerSeverityNone repeated across 21 files packages/Microsoft.CodeAnalysis.Analyzers/editorconfig/PortedFromFxCopRulesEnabled/.editorconfig
- Explicit Debt Β· AnalyzerSeverityNone repeated across 21 files packages/Microsoft.CodeAnalysis.Analyzers/editorconfig/PortedFromFxCopRulesEnabled/.editorconfig
- Knowledge Freshness Β· Orphaned knowledge src/Deedle/FSharp.Data/Net/Http.fs
- Knowledge Freshness Β· Orphaned knowledge src/Deedle/Vectors/VirtualVector.fs
- Knowledge Freshness Β· Orphaned knowledge src/Deedle/VirtualFrame.fs
- Knowledge Freshness Β· Orphaned knowledge src/Deedle/Indices/VirtualIndex.fs
- Knowledge Freshness Β· Orphaned knowledge src/Deedle/Vectors/ArrayVector.fs
Rebuild cost: about β¬44,000 Β· Estimate
| Cost to rebuild | β¬14,000 to β¬73,000, for 241 to 764 hours of work, about 0.3 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 58. 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. |
| Size | Medium: 26,904 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture β module dependency graph
Architecture: which parts of the code depend on which
| uses β | 1 Deedle.Addressing | 2 Deedle.Internal | 3 FSharp.Data | 4 FSharp.Data.Runtime.StructuralTypes | 5 Deedle.Vectors | 6 FSharp.Data.Runtime.StructuralInference | 7 Deedle.Indices | 8 FSharp.Data.Runtime.CsvInference | 9 Deedle | 10 Deedle.Arrow | 11 Deedle.Arrow.Frame | 12 Deedle.Arrow.Implementation | 13 Deedle.Arrow.Series | 14 Deedle.Delayed | 15 Deedle.Indices.Linear | 16 Deedle.JoinHelpers | 17 Deedle.MathNetNumerics.LinearRegression.Fit.Summary | 18 Deedle.MicrosoftML | 19 Deedle.Ranges | 20 Deedle.Reflection | 21 Deedle.VectorHelpers | 22 Deedle.Vectors.ArrayVector | 23 Deedle.Vectors.VectorHelperExtensions | 24 Deedle.MathNetNumerics.LinearRegression.Fit | 25 Deedle.MicrosoftML.Extraction | 26 Deedle.Ranges.Ranges | 27 Deedle.Vectors.Virtual | 28 Deedle.Indices.Virtual | 29 Deedle.MathNetNumerics.LinearRegression | 30 Deedle.Vectors.Virtual.VirtualVectorSource | 31 Deedle.Virtual | 32 Deedle.Parquet.Virtual.Sources | 33 Deedle.Parquet.Virtual.Sources.VirtualParquetExtensions | 34 Deedle.Virtual.FloatBatchMaterialize | 35 Deedle.Virtual.LookupRangeExecutor | 36 Deedle.Virtual.Sources.VirtualCsvSource | 37 Deedle.Virtual.VirtualCsvExtensions | 38 Deedle.Virtual.VirtualFrameDiag | 39 Deedle.Parquet.Virtual.Sources.ParquetColumnSource | 40 Deedle.Parquet.Virtual.Sources.VirtualParquetSource |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Deedle.Addressing | ||||||||||||||||||||||||||||||||||||||||
| 2 Deedle.Internal | ||||||||||||||||||||||||||||||||||||||||
| 3 FSharp.Data | ||||||||||||||||||||||||||||||||||||||||
| 4 FSharp.Data.Runtime.StructuralTypes | ||||||||||||||||||||||||||||||||||||||||
| 5 Deedle.Vectors | 1 | 8 | ||||||||||||||||||||||||||||||||||||||
| 6 FSharp.Data.Runtime.StructuralInference | 3 | |||||||||||||||||||||||||||||||||||||||
| 7 Deedle.Indices | 2 | 2 | 8 | |||||||||||||||||||||||||||||||||||||
| 8 FSharp.Data.Runtime.CsvInference | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 9 Deedle | 2 | 4 | 9 | 15 | ||||||||||||||||||||||||||||||||||||
| 10 Deedle.Arrow | 2 | |||||||||||||||||||||||||||||||||||||||
| 11 Deedle.Arrow.Frame | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 Deedle.Arrow.Implementation | 3 | |||||||||||||||||||||||||||||||||||||||
| 13 Deedle.Arrow.Series | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 Deedle.Delayed | 4 | 4 | 7 | 14 | ||||||||||||||||||||||||||||||||||||
| 15 Deedle.Indices.Linear | 5 | 3 | 6 | 10 | ||||||||||||||||||||||||||||||||||||
| 16 Deedle.JoinHelpers | 1 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 17 Deedle.MathNetNumerics.LinearRegression.Fit.Summary | 2 | |||||||||||||||||||||||||||||||||||||||
| 18 Deedle.MicrosoftML | 3 | |||||||||||||||||||||||||||||||||||||||
| 19 Deedle.Ranges | 5 | |||||||||||||||||||||||||||||||||||||||
| 20 Deedle.Reflection | 1 | 1 | 5 | |||||||||||||||||||||||||||||||||||||
| 21 Deedle.VectorHelpers | 2 | 7 | 17 | |||||||||||||||||||||||||||||||||||||
| 22 Deedle.Vectors.ArrayVector | 2 | 3 | 8 | |||||||||||||||||||||||||||||||||||||
| 23 Deedle.Vectors.VectorHelperExtensions | 1 | 4 | 3 | |||||||||||||||||||||||||||||||||||||
| 24 Deedle.MathNetNumerics.LinearRegression.Fit | 4 | 1 | ||||||||||||||||||||||||||||||||||||||
| 25 Deedle.MicrosoftML.Extraction | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 26 Deedle.Ranges.Ranges | 3 | 2 | ||||||||||||||||||||||||||||||||||||||
| 27 Deedle.Vectors.Virtual | 6 | 3 | 12 | 1 | ||||||||||||||||||||||||||||||||||||
| 28 Deedle.Indices.Virtual | 4 | 2 | 6 | 10 | 1 | 2 | ||||||||||||||||||||||||||||||||||
| 29 Deedle.MathNetNumerics.LinearRegression | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 30 Deedle.Vectors.Virtual.VirtualVectorSource | 2 | 3 | 5 | 5 | ||||||||||||||||||||||||||||||||||||
| 31 Deedle.Virtual | 1 | 9 | 8 | |||||||||||||||||||||||||||||||||||||
| 32 Deedle.Parquet.Virtual.Sources | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 33 Deedle.Parquet.Virtual.Sources.VirtualParquetExtensions | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 34 Deedle.Virtual.FloatBatchMaterialize | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 35 Deedle.Virtual.LookupRangeExecutor | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 36 Deedle.Virtual.Sources.VirtualCsvSource | 1 | 3 | 3 | |||||||||||||||||||||||||||||||||||||
| 37 Deedle.Virtual.VirtualCsvExtensions | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 38 Deedle.Virtual.VirtualFrameDiag | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 39 Deedle.Parquet.Virtual.Sources.ParquetColumnSource | 1 | 1 | 2 | 3 | ||||||||||||||||||||||||||||||||||||
| 40 Deedle.Parquet.Virtual.Sources.VirtualParquetSource | 1 | 1 | 1 | 3 |
5β1 Deedle.Vectors uses Deedle.Addressing✕
- Connections
- 1 pair of types, where a type in Deedle.Vectors uses a type in Deedle.Addressing.
- The types involved
Deedle.Vectors.IVectorBuilderβDeedle.Addressing.IAddressingScheme
- Direction
- Deedle.Vectors uses Deedle.Addressing, so a change to Deedle.Addressing can break Deedle.Vectors, while a change to Deedle.Vectors can't break Deedle.Addressing.
- Position
- Below the diagonal: Deedle.Vectors uses a module listed above it, which is the healthy direction.
5β9 Deedle.Vectors uses Deedle part of a loop✕
- Connections
- 8 pairs of types, where a type in Deedle.Vectors uses a type in Deedle.
- The types involved
Deedle.Vectors.IVectorBuilderβDeedle.IVector`1Deedle.Vectors.IVectorBuilderβDeedle.OptionalValue`1Deedle.Vectors.KnownLocationβDeedle.IVectorLocationDeedle.Vectors.VectorβDeedle.IVector`1Deedle.Vectors.VectorβDeedle.OptionalValue`1Deedle.Vectors.VectorConstructionβDeedle.RangeRestriction`1Deedle.Vectors.VectorData`1βDeedle.OptionalValue`1Deedle.Vectors.VectorFillMissingβDeedle.Direction
- Direction
- Deedle.Vectors uses Deedle, so a change to Deedle can break Deedle.Vectors, while a change to Deedle.Vectors can't break Deedle.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6β4 FSharp.Data.Runtime.StructuralInference uses FSharp.Data.Runtime.StructuralTypes✕
- Connections
- 3 pairs of types, where a type in FSharp.Data.Runtime.StructuralInference uses a type in FSharp.Data.Runtime.StructuralTypes.
- The types involved
FSharp.Data.Runtime.StructuralInference.StructuralInferenceβFSharp.Data.Runtime.StructuralTypes.InferedPropertyFSharp.Data.Runtime.StructuralInference.StructuralInferenceβFSharp.Data.Runtime.StructuralTypes.InferedTypeFSharp.Data.Runtime.StructuralInference.StructuralInferenceβFSharp.Data.Runtime.StructuralTypes.InferedTypeTag
- Direction
- FSharp.Data.Runtime.StructuralInference uses FSharp.Data.Runtime.StructuralTypes, so a change to FSharp.Data.Runtime.StructuralTypes can break FSharp.Data.Runtime.StructuralInference, while a change to FSharp.Data.Runtime.StructuralInference can't break FSharp.Data.Runtime.StructuralTypes.
- Position
- Below the diagonal: FSharp.Data.Runtime.StructuralInference uses a module listed above it, which is the healthy direction.
7β1 Deedle.Indices uses Deedle.Addressing✕
- Connections
- 2 pairs of types, where a type in Deedle.Indices uses a type in Deedle.Addressing.
- The types involved
Deedle.Indices.IIndex`1βDeedle.Addressing.IAddressOperationsDeedle.Indices.IIndex`1βDeedle.Addressing.IAddressingScheme
- Direction
- Deedle.Indices uses Deedle.Addressing, so a change to Deedle.Addressing can break Deedle.Indices, while a change to Deedle.Indices can't break Deedle.Addressing.
- Position
- Below the diagonal: Deedle.Indices uses a module listed above it, which is the healthy direction.
7β5 Deedle.Indices uses Deedle.Vectors✕
- Connections
- 2 pairs of types, where a type in Deedle.Indices uses a type in Deedle.Vectors.
- The types involved
Deedle.Indices.IIndexBuilderβDeedle.Vectors.VectorConstructionDeedle.Indices.IIndexBuilderβDeedle.Vectors.VectorListTransform
- Direction
- Deedle.Indices uses Deedle.Vectors, so a change to Deedle.Vectors can break Deedle.Indices, while a change to Deedle.Indices can't break Deedle.Vectors.
- Position
- Below the diagonal: Deedle.Indices uses a module listed above it, which is the healthy direction.
7β9 Deedle.Indices uses Deedle part of a loop✕
- Connections
- 8 pairs of types, where a type in Deedle.Indices uses a type in Deedle.
- The types involved
Deedle.Indices.IIndexBuilderβDeedle.Aggregation`1Deedle.Indices.IIndexBuilderβDeedle.DirectionDeedle.Indices.IIndexBuilderβDeedle.ICustomLookup`1Deedle.Indices.IIndexBuilderβDeedle.IVector`1Deedle.Indices.IIndexBuilderβDeedle.LookupDeedle.Indices.IIndexBuilderβDeedle.RangeRestriction`1Deedle.Indices.IIndex`1βDeedle.LookupDeedle.Indices.IIndex`1βDeedle.OptionalValue`1
- Direction
- Deedle.Indices uses Deedle, so a change to Deedle can break Deedle.Indices, while a change to Deedle.Indices can't break Deedle.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8β4 FSharp.Data.Runtime.CsvInference uses FSharp.Data.Runtime.StructuralTypes✕
- Connections
- 1 pair of types, where a type in FSharp.Data.Runtime.CsvInference uses a type in FSharp.Data.Runtime.StructuralTypes.
- The types involved
FSharp.Data.Runtime.CsvInference.CsvInferenceβFSharp.Data.Runtime.StructuralTypes.PrimitiveInferedProperty
- Direction
- FSharp.Data.Runtime.CsvInference uses FSharp.Data.Runtime.StructuralTypes, so a change to FSharp.Data.Runtime.StructuralTypes can break FSharp.Data.Runtime.CsvInference, while a change to FSharp.Data.Runtime.CsvInference can't break FSharp.Data.Runtime.StructuralTypes.
- Position
- Below the diagonal: FSharp.Data.Runtime.CsvInference uses a module listed above it, which is the healthy direction.
8β6 FSharp.Data.Runtime.CsvInference uses FSharp.Data.Runtime.StructuralInference✕
- Connections
- 1 pair of types, where a type in FSharp.Data.Runtime.CsvInference uses a type in FSharp.Data.Runtime.StructuralInference.
- The types involved
FSharp.Data.Runtime.CsvInference.CsvInferenceβFSharp.Data.Runtime.StructuralInference.IUnitsOfMeasureProvider
- Direction
- FSharp.Data.Runtime.CsvInference uses FSharp.Data.Runtime.StructuralInference, so a change to FSharp.Data.Runtime.StructuralInference can break FSharp.Data.Runtime.CsvInference, while a change to FSharp.Data.Runtime.CsvInference can't break FSharp.Data.Runtime.StructuralInference.
- Position
- Below the diagonal: FSharp.Data.Runtime.CsvInference uses a module listed above it, which is the healthy direction.
9β1 Deedle uses Deedle.Addressing✕
- Connections
- 2 pairs of types, where a type in Deedle uses a type in Deedle.Addressing.
- The types involved
Deedle.DelayedSeriesβDeedle.Addressing.IAddressingSchemeDeedle.IVectorβDeedle.Addressing.IAddressingScheme
- Direction
- Deedle uses Deedle.Addressing, so a change to Deedle.Addressing can break Deedle, while a change to Deedle can't break Deedle.Addressing.
- Position
- Below the diagonal: Deedle uses a module listed above it, which is the healthy direction.
9β2 Deedle uses Deedle.Internal✕
- Connections
- 4 pairs of types, where a type in Deedle uses a type in Deedle.Internal.
- The types involved
Deedle.Frame`2βDeedle.Internal.IFrameFormattableDeedle.Frame`2βDeedle.Internal.IFsiFormattableDeedle.Series`2βDeedle.Internal.IFsiFormattableDeedle.Series`2βDeedle.Internal.ISeriesFormattable
- Direction
- Deedle uses Deedle.Internal, so a change to Deedle.Internal can break Deedle, while a change to Deedle can't break Deedle.Internal.
- Position
- Below the diagonal: Deedle uses a module listed above it, which is the healthy direction.
9β5 Deedle uses Deedle.Vectors✕
- Connections
- 9 pairs of types, where a type in Deedle uses a type in Deedle.Vectors.
- The types involved
Deedle.ColumnSeries`2βDeedle.Vectors.IVectorBuilderDeedle.DelayedSeriesβDeedle.Vectors.IVectorBuilderDeedle.FrameUtilsβDeedle.Vectors.IVectorBuilderDeedle.Frame`2βDeedle.Vectors.IVectorBuilderDeedle.ISeries`1βDeedle.Vectors.IVectorBuilderDeedle.IVector`1βDeedle.Vectors.VectorData`1Deedle.ObjectSeries`1βDeedle.Vectors.IVectorBuilderDeedle.RowSeries`2βDeedle.Vectors.IVectorBuilderDeedle.Series`2βDeedle.Vectors.IVectorBuilder
- Direction
- Deedle uses Deedle.Vectors, so a change to Deedle.Vectors can break Deedle, while a change to Deedle can't break Deedle.Vectors.
- Position
- Below the diagonal: Deedle uses a module listed above it, which is the healthy direction.
9β7 Deedle uses Deedle.Indices✕
- Connections
- 15 pairs of types, where a type in Deedle uses a type in Deedle.Indices.
- The types involved
Deedle.ColumnSeries`2βDeedle.Indices.IIndexBuilderDeedle.ColumnSeries`2βDeedle.Indices.IIndex`1Deedle.DelayedSeriesβDeedle.Indices.BoundaryBehaviorDeedle.DelayedSeriesβDeedle.Indices.IIndexBuilderDeedle.FrameUtilsβDeedle.Indices.IIndexBuilderDeedle.Frame`2βDeedle.Indices.IIndexBuilderDeedle.Frame`2βDeedle.Indices.IIndex`1Deedle.ISeries`1βDeedle.Indices.IIndex`1Deedle.IndexβDeedle.Indices.IIndex`1Deedle.ObjectSeries`1βDeedle.Indices.IIndexBuilderDeedle.ObjectSeries`1βDeedle.Indices.IIndex`1Deedle.RowSeries`2βDeedle.Indices.IIndexBuilderDeedle.RowSeries`2βDeedle.Indices.IIndex`1Deedle.Series`2βDeedle.Indices.IIndexBuilderDeedle.Series`2βDeedle.Indices.IIndex`1
- Direction
- Deedle uses Deedle.Indices, so a change to Deedle.Indices can break Deedle, while a change to Deedle can't break Deedle.Indices.
- Position
- Below the diagonal: Deedle uses a module listed above it, which is the healthy direction.
10β9 Deedle.Arrow uses Deedle✕
- Connections
- 2 pairs of types, where a type in Deedle.Arrow uses a type in Deedle.
- The types involved
Deedle.Arrow.ArrowFrameβDeedle.Frame`2Deedle.Arrow.FrameArrowExtensionsβDeedle.Frame`2
- Direction
- Deedle.Arrow uses Deedle, so a change to Deedle can break Deedle.Arrow, while a change to Deedle.Arrow can't break Deedle.
- Position
- Below the diagonal: Deedle.Arrow uses a module listed above it, which is the healthy direction.
11β9 Deedle.Arrow.Frame uses Deedle✕
- Connections
- 1 pair of types, where a type in Deedle.Arrow.Frame uses a type in Deedle.
- The types involved
Deedle.Arrow.Frame.FrameβDeedle.Frame`2
- Direction
- Deedle.Arrow.Frame uses Deedle, so a change to Deedle can break Deedle.Arrow.Frame, while a change to Deedle.Arrow.Frame can't break Deedle.
- Position
- Below the diagonal: Deedle.Arrow.Frame uses a module listed above it, which is the healthy direction.
12β9 Deedle.Arrow.Implementation uses Deedle✕
- Connections
- 3 pairs of types, where a type in Deedle.Arrow.Implementation uses a type in Deedle.
- The types involved
Deedle.Arrow.Implementation.ImplementationβDeedle.Frame`2Deedle.Arrow.Implementation.ImplementationβDeedle.IVector`1Deedle.Arrow.Implementation.ImplementationβDeedle.Series`2
- Direction
- Deedle.Arrow.Implementation uses Deedle, so a change to Deedle can break Deedle.Arrow.Implementation, while a change to Deedle.Arrow.Implementation can't break Deedle.
- Position
- Below the diagonal: Deedle.Arrow.Implementation uses a module listed above it, which is the healthy direction.
13β9 Deedle.Arrow.Series uses Deedle✕
- Connections
- 1 pair of types, where a type in Deedle.Arrow.Series uses a type in Deedle.
- The types involved
Deedle.Arrow.Series.SeriesβDeedle.Series`2
- Direction
- Deedle.Arrow.Series uses Deedle, so a change to Deedle can break Deedle.Arrow.Series, while a change to Deedle.Arrow.Series can't break Deedle.
- Position
- Below the diagonal: Deedle.Arrow.Series uses a module listed above it, which is the healthy direction.
14β1 Deedle.Delayed uses Deedle.Addressing✕
- Connections
- 4 pairs of types, where a type in Deedle.Delayed uses a type in Deedle.Addressing.
- The types involved
Deedle.Delayed.DelayedIndex`2βDeedle.Addressing.IAddressOperationsDeedle.Delayed.DelayedIndex`2βDeedle.Addressing.IAddressingSchemeDeedle.Delayed.DelayedSource`2βDeedle.Addressing.IAddressingSchemeDeedle.Delayed.DelayedVector`2βDeedle.Addressing.IAddressingScheme
- Direction
- Deedle.Delayed uses Deedle.Addressing, so a change to Deedle.Addressing can break Deedle.Delayed, while a change to Deedle.Delayed can't break Deedle.Addressing.
- Position
- Below the diagonal: Deedle.Delayed uses a module listed above it, which is the healthy direction.
14β5 Deedle.Delayed uses Deedle.Vectors✕
- Connections
- 4 pairs of types, where a type in Deedle.Delayed uses a type in Deedle.Vectors.
- The types involved
Deedle.Delayed.DelayedIndexBuilderβDeedle.Vectors.VectorConstructionDeedle.Delayed.DelayedIndexBuilderβDeedle.Vectors.VectorListTransformDeedle.Delayed.DelayedSource`2βDeedle.Vectors.IVectorBuilderDeedle.Delayed.DelayedVector`2βDeedle.Vectors.VectorData`1
- Direction
- Deedle.Delayed uses Deedle.Vectors, so a change to Deedle.Vectors can break Deedle.Delayed, while a change to Deedle.Delayed can't break Deedle.Vectors.
- Position
- Below the diagonal: Deedle.Delayed uses a module listed above it, which is the healthy direction.
14β7 Deedle.Delayed uses Deedle.Indices✕
- Connections
- 7 pairs of types, where a type in Deedle.Delayed uses a type in Deedle.Indices.
- The types involved
Deedle.Delayed.DelayedIndexBuilderβDeedle.Indices.IIndexBuilderDeedle.Delayed.DelayedIndexBuilderβDeedle.Indices.IIndex`1Deedle.Delayed.DelayedIndex`2βDeedle.Indices.IIndexBuilderDeedle.Delayed.DelayedIndex`2βDeedle.Indices.IIndex`1Deedle.Delayed.DelayedSource`2βDeedle.Indices.IIndexBuilderDeedle.Delayed.DelayedSource`2βDeedle.Indices.IIndex`1Deedle.Delayed.IDelayedIndex`1βDeedle.Indices.IIndex`1
- Direction
- Deedle.Delayed uses Deedle.Indices, so a change to Deedle.Indices can break Deedle.Delayed, while a change to Deedle.Delayed can't break Deedle.Indices.
- Position
- Below the diagonal: Deedle.Delayed uses a module listed above it, which is the healthy direction.
14β9 Deedle.Delayed uses Deedle✕
- Connections
- 14 pairs of types, where a type in Deedle.Delayed uses a type in Deedle.
- The types involved
Deedle.Delayed.DelayedIndexBuilderβDeedle.Aggregation`1Deedle.Delayed.DelayedIndexBuilderβDeedle.DirectionDeedle.Delayed.DelayedIndexBuilderβDeedle.ICustomLookup`1Deedle.Delayed.DelayedIndexBuilderβDeedle.IVector`1Deedle.Delayed.DelayedIndexBuilderβDeedle.LookupDeedle.Delayed.DelayedIndexBuilderβDeedle.RangeRestriction`1Deedle.Delayed.DelayedIndex`2βDeedle.LookupDeedle.Delayed.DelayedIndex`2βDeedle.OptionalValue`1Deedle.Delayed.DelayedSource`2βDeedle.IVector`1Deedle.Delayed.DelayedVector`2βDeedle.IVectorDeedle.Delayed.DelayedVector`2βDeedle.IVectorLocationDeedle.Delayed.DelayedVector`2βDeedle.IVector`1Deedle.Delayed.DelayedVector`2βDeedle.OptionalValue`1Deedle.Delayed.DelayedVector`2βDeedle.VectorCallSite`1
- Direction
- Deedle.Delayed uses Deedle, so a change to Deedle can break Deedle.Delayed, while a change to Deedle.Delayed can't break Deedle.
- Position
- Below the diagonal: Deedle.Delayed uses a module listed above it, which is the healthy direction.
15β1 Deedle.Indices.Linear uses Deedle.Addressing✕
- Connections
- 5 pairs of types, where a type in Deedle.Indices.Linear uses a type in Deedle.Addressing.
- The types involved
Deedle.Indices.Linear.LinearAddressOperationsβDeedle.Addressing.IAddressOperationsDeedle.Indices.Linear.LinearIndex`1βDeedle.Addressing.IAddressOperationsDeedle.Indices.Linear.LinearIndex`1βDeedle.Addressing.IAddressingSchemeDeedle.Indices.Linear.LinearRangeIndex`1βDeedle.Addressing.IAddressOperationsDeedle.Indices.Linear.LinearRangeIndex`1βDeedle.Addressing.IAddressingScheme
- Direction
- Deedle.Indices.Linear uses Deedle.Addressing, so a change to Deedle.Addressing can break Deedle.Indices.Linear, while a change to Deedle.Indices.Linear can't break Deedle.Addressing.
- Position
- Below the diagonal: Deedle.Indices.Linear uses a module listed above it, which is the healthy direction.
15β5 Deedle.Indices.Linear uses Deedle.Vectors✕
- Connections
- 3 pairs of types, where a type in Deedle.Indices.Linear uses a type in Deedle.Vectors.
- The types involved
Deedle.Indices.Linear.LinearIndexBuilderβDeedle.Vectors.IVectorBuilderDeedle.Indices.Linear.LinearIndexBuilderβDeedle.Vectors.VectorConstructionDeedle.Indices.Linear.LinearIndexBuilderβDeedle.Vectors.VectorListTransform
- Direction
- Deedle.Indices.Linear uses Deedle.Vectors, so a change to Deedle.Vectors can break Deedle.Indices.Linear, while a change to Deedle.Indices.Linear can't break Deedle.Vectors.
- Position
- Below the diagonal: Deedle.Indices.Linear uses a module listed above it, which is the healthy direction.
15β7 Deedle.Indices.Linear uses Deedle.Indices✕
- Connections
- 6 pairs of types, where a type in Deedle.Indices.Linear uses a type in Deedle.Indices.
- The types involved
Deedle.Indices.Linear.LinearIndexBuilderβDeedle.Indices.IIndexBuilderDeedle.Indices.Linear.LinearIndexBuilderβDeedle.Indices.IIndex`1Deedle.Indices.Linear.LinearIndex`1βDeedle.Indices.IIndexBuilderDeedle.Indices.Linear.LinearIndex`1βDeedle.Indices.IIndex`1Deedle.Indices.Linear.LinearRangeIndex`1βDeedle.Indices.IIndexBuilderDeedle.Indices.Linear.LinearRangeIndex`1βDeedle.Indices.IIndex`1
- Direction
- Deedle.Indices.Linear uses Deedle.Indices, so a change to Deedle.Indices can break Deedle.Indices.Linear, while a change to Deedle.Indices.Linear can't break Deedle.Indices.
- Position
- Below the diagonal: Deedle.Indices.Linear uses a module listed above it, which is the healthy direction.
15β9 Deedle.Indices.Linear uses Deedle✕
- Connections
- 10 pairs of types, where a type in Deedle.Indices.Linear uses a type in Deedle.
- The types involved
Deedle.Indices.Linear.LinearIndexBuilderβDeedle.Aggregation`1Deedle.Indices.Linear.LinearIndexBuilderβDeedle.DirectionDeedle.Indices.Linear.LinearIndexBuilderβDeedle.ICustomLookup`1Deedle.Indices.Linear.LinearIndexBuilderβDeedle.IVector`1Deedle.Indices.Linear.LinearIndexBuilderβDeedle.LookupDeedle.Indices.Linear.LinearIndexBuilderβDeedle.RangeRestriction`1Deedle.Indices.Linear.LinearIndex`1βDeedle.LookupDeedle.Indices.Linear.LinearIndex`1βDeedle.OptionalValue`1Deedle.Indices.Linear.LinearRangeIndex`1βDeedle.LookupDeedle.Indices.Linear.LinearRangeIndex`1βDeedle.OptionalValue`1
- Direction
- Deedle.Indices.Linear uses Deedle, so a change to Deedle can break Deedle.Indices.Linear, while a change to Deedle.Indices.Linear can't break Deedle.
- Position
- Below the diagonal: Deedle.Indices.Linear uses a module listed above it, which is the healthy direction.
16β5 Deedle.JoinHelpers uses Deedle.Vectors✕
- Connections
- 1 pair of types, where a type in Deedle.JoinHelpers uses a type in Deedle.Vectors.
- The types involved
Deedle.JoinHelpers.JoinHelpersβDeedle.Vectors.VectorConstruction
- Direction
- Deedle.JoinHelpers uses Deedle.Vectors, so a change to Deedle.Vectors can break Deedle.JoinHelpers, while a change to Deedle.JoinHelpers can't break Deedle.Vectors.
- Position
- Below the diagonal: Deedle.JoinHelpers uses a module listed above it, which is the healthy direction.
16β7 Deedle.JoinHelpers uses Deedle.Indices✕
- Connections
- 2 pairs of types, where a type in Deedle.JoinHelpers uses a type in Deedle.Indices.
- The types involved
Deedle.JoinHelpers.JoinHelpersβDeedle.Indices.IIndexBuilderDeedle.JoinHelpers.JoinHelpersβDeedle.Indices.IIndex`1
- Direction
- Deedle.JoinHelpers uses Deedle.Indices, so a change to Deedle.Indices can break Deedle.JoinHelpers, while a change to Deedle.JoinHelpers can't break Deedle.Indices.
- Position
- Below the diagonal: Deedle.JoinHelpers uses a module listed above it, which is the healthy direction.
16β9 Deedle.JoinHelpers uses Deedle✕
- Connections
- 2 pairs of types, where a type in Deedle.JoinHelpers uses a type in Deedle.
- The types involved
Deedle.JoinHelpers.JoinHelpersβDeedle.JoinKindDeedle.JoinHelpers.JoinHelpersβDeedle.Lookup
- Direction
- Deedle.JoinHelpers uses Deedle, so a change to Deedle can break Deedle.JoinHelpers, while a change to Deedle.JoinHelpers can't break Deedle.
- Position
- Below the diagonal: Deedle.JoinHelpers uses a module listed above it, which is the healthy direction.
17β9 Deedle.MathNetNumerics.LinearRegression.Fit.Summary uses Deedle✕
- Connections
- 2 pairs of types, where a type in Deedle.MathNetNumerics.LinearRegression.Fit.Summary uses a type in Deedle.
- The types involved
Deedle.MathNetNumerics.LinearRegression.Fit.Summary.tβDeedle.Frame`2Deedle.MathNetNumerics.LinearRegression.Fit.Summary.tβDeedle.Series`2
- Direction
- Deedle.MathNetNumerics.LinearRegression.Fit.Summary uses Deedle, so a change to Deedle can break Deedle.MathNetNumerics.LinearRegression.Fit.Summary, while a change to Deedle.MathNetNumerics.LinearRegression.Fit.Summary can't break Deedle.
- Position
- Below the diagonal: Deedle.MathNetNumerics.LinearRegression.Fit.Summary uses a module listed above it, which is the healthy direction.
18β9 Deedle.MicrosoftML uses Deedle✕
- Connections
- 3 pairs of types, where a type in Deedle.MicrosoftML uses a type in Deedle.
- The types involved
Deedle.MicrosoftML.FrameβDeedle.Frame`2Deedle.MicrosoftML.FrameMLExtensionsβDeedle.Frame`2Deedle.MicrosoftML.PipelineβDeedle.Frame`2
- Direction
- Deedle.MicrosoftML uses Deedle, so a change to Deedle can break Deedle.MicrosoftML, while a change to Deedle.MicrosoftML can't break Deedle.
- Position
- Below the diagonal: Deedle.MicrosoftML uses a module listed above it, which is the healthy direction.
19β9 Deedle.Ranges uses Deedle✕
- Connections
- 5 pairs of types, where a type in Deedle.Ranges uses a type in Deedle.
- The types involved
Deedle.Ranges.IRangeKeyOperations`1βDeedle.LookupDeedle.Ranges.IRangeKeyOperations`1βDeedle.OptionalValue`1Deedle.Ranges.Ranges`1βDeedle.LookupDeedle.Ranges.Ranges`1βDeedle.OptionalValue`1Deedle.Ranges.Ranges`1βDeedle.RangeRestriction`1
- Direction
- Deedle.Ranges uses Deedle, so a change to Deedle can break Deedle.Ranges, while a change to Deedle.Ranges can't break Deedle.
- Position
- Below the diagonal: Deedle.Ranges uses a module listed above it, which is the healthy direction.
20β5 Deedle.Reflection uses Deedle.Vectors✕
- Connections
- 1 pair of types, where a type in Deedle.Reflection uses a type in Deedle.Vectors.
- The types involved
Deedle.Reflection.ReflectionβDeedle.Vectors.IVectorBuilder
- Direction
- Deedle.Reflection uses Deedle.Vectors, so a change to Deedle.Vectors can break Deedle.Reflection, while a change to Deedle.Reflection can't break Deedle.Vectors.
- Position
- Below the diagonal: Deedle.Reflection uses a module listed above it, which is the healthy direction.
20β7 Deedle.Reflection uses Deedle.Indices✕
- Connections
- 1 pair of types, where a type in Deedle.Reflection uses a type in Deedle.Indices.
- The types involved
Deedle.Reflection.ReflectionβDeedle.Indices.IIndexBuilder
- Direction
- Deedle.Reflection uses Deedle.Indices, so a change to Deedle.Indices can break Deedle.Reflection, while a change to Deedle.Reflection can't break Deedle.Indices.
- Position
- Below the diagonal: Deedle.Reflection uses a module listed above it, which is the healthy direction.
20β9 Deedle.Reflection uses Deedle✕
- Connections
- 5 pairs of types, where a type in Deedle.Reflection uses a type in Deedle.
- The types involved
Deedle.Reflection.ConvertRecordHelperβDeedle.Frame`2Deedle.Reflection.ReflectionβDeedle.Frame`2Deedle.Reflection.ReflectionβDeedle.IVectorDeedle.Reflection.ReflectionβDeedle.IVector`1Deedle.Reflection.ReflectionβDeedle.OptionalValue`1
- Direction
- Deedle.Reflection uses Deedle, so a change to Deedle can break Deedle.Reflection, while a change to Deedle.Reflection can't break Deedle.
- Position
- Below the diagonal: Deedle.Reflection uses a module listed above it, which is the healthy direction.
21β1 Deedle.VectorHelpers uses Deedle.Addressing✕
- Connections
- 2 pairs of types, where a type in Deedle.VectorHelpers uses a type in Deedle.Addressing.
- The types involved
Deedle.VectorHelpers.RowReaderVector`1βDeedle.Addressing.IAddressingSchemeDeedle.VectorHelpers.VectorHelpersβDeedle.Addressing.IAddressingScheme
- Direction
- Deedle.VectorHelpers uses Deedle.Addressing, so a change to Deedle.Addressing can break Deedle.VectorHelpers, while a change to Deedle.VectorHelpers can't break Deedle.Addressing.
- Position
- Below the diagonal: Deedle.VectorHelpers uses a module listed above it, which is the healthy direction.
21β5 Deedle.VectorHelpers uses Deedle.Vectors✕
- Connections
- 7 pairs of types, where a type in Deedle.VectorHelpers uses a type in Deedle.Vectors.
- The types involved
Deedle.VectorHelpers.BinaryTransformβDeedle.Vectors.VectorListTransformDeedle.VectorHelpers.NaryTransformβDeedle.Vectors.VectorListTransformDeedle.VectorHelpers.RowReaderVector`1βDeedle.Vectors.IVectorBuilderDeedle.VectorHelpers.RowReaderVector`1βDeedle.Vectors.VectorData`1Deedle.VectorHelpers.VectorHelpersβDeedle.Vectors.IVectorBuilderDeedle.VectorHelpers.VectorHelpersβDeedle.Vectors.VectorConstructionDeedle.VectorHelpers.mapFrameRowVectorβDeedle.Vectors.IVectorBuilder
- Direction
- Deedle.VectorHelpers uses Deedle.Vectors, so a change to Deedle.Vectors can break Deedle.VectorHelpers, while a change to Deedle.VectorHelpers can't break Deedle.Vectors.
- Position
- Below the diagonal: Deedle.VectorHelpers uses a module listed above it, which is the healthy direction.
21β9 Deedle.VectorHelpers uses Deedle✕
- Connections
- 17 pairs of types, where a type in Deedle.VectorHelpers uses a type in Deedle.
- The types involved
Deedle.VectorHelpers.IBoxedVectorβDeedle.IVectorDeedle.VectorHelpers.IBoxedVectorβDeedle.IVector`1Deedle.VectorHelpers.IWrappedVector`1βDeedle.IVector`1Deedle.VectorHelpers.RowReaderVector`1βDeedle.IVectorDeedle.VectorHelpers.RowReaderVector`1βDeedle.IVectorLocationDeedle.VectorHelpers.RowReaderVector`1βDeedle.IVector`1Deedle.VectorHelpers.RowReaderVector`1βDeedle.OptionalValue`1Deedle.VectorHelpers.RowReaderVector`1βDeedle.VectorCallSite`1Deedle.VectorHelpers.TryValuesHelperβDeedle.IVectorDeedle.VectorHelpers.TryValuesHelperβDeedle.IVector`1Deedle.VectorHelpers.TryValuesHelperβDeedle.TryValue`1Deedle.VectorHelpers.VectorHelpersβDeedle.ConversionKindDeedle.VectorHelpers.VectorHelpersβDeedle.IVectorDeedle.VectorHelpers.VectorHelpersβDeedle.IVector`1Deedle.VectorHelpers.VectorHelpersβDeedle.OptionalValue`1Deedle.VectorHelpers.VectorHelpersβDeedle.TryValue`1Deedle.VectorHelpers.mapFrameRowVectorβDeedle.IVector`1
- Direction
- Deedle.VectorHelpers uses Deedle, so a change to Deedle can break Deedle.VectorHelpers, while a change to Deedle.VectorHelpers can't break Deedle.
- Position
- Below the diagonal: Deedle.VectorHelpers uses a module listed above it, which is the healthy direction.
22β1 Deedle.Vectors.ArrayVector uses Deedle.Addressing✕
- Connections
- 2 pairs of types, where a type in Deedle.Vectors.ArrayVector uses a type in Deedle.Addressing.
- The types involved
Deedle.Vectors.ArrayVector.ArrayVectorBuilderβDeedle.Addressing.IAddressingSchemeDeedle.Vectors.ArrayVector.ArrayVector`1βDeedle.Addressing.IAddressingScheme
- Direction
- Deedle.Vectors.ArrayVector uses Deedle.Addressing, so a change to Deedle.Addressing can break Deedle.Vectors.ArrayVector, while a change to Deedle.Vectors.ArrayVector can't break Deedle.Addressing.
- Position
- Below the diagonal: Deedle.Vectors.ArrayVector uses a module listed above it, which is the healthy direction.
22β5 Deedle.Vectors.ArrayVector uses Deedle.Vectors✕
- Connections
- 3 pairs of types, where a type in Deedle.Vectors.ArrayVector uses a type in Deedle.Vectors.
- The types involved
Deedle.Vectors.ArrayVector.ArrayVectorBuilderβDeedle.Vectors.IVectorBuilderDeedle.Vectors.ArrayVector.ArrayVectorBuilderβDeedle.Vectors.VectorConstructionDeedle.Vectors.ArrayVector.ArrayVector`1βDeedle.Vectors.VectorData`1
- Direction
- Deedle.Vectors.ArrayVector uses Deedle.Vectors, so a change to Deedle.Vectors can break Deedle.Vectors.ArrayVector, while a change to Deedle.Vectors.ArrayVector can't break Deedle.Vectors.
- Position
- Below the diagonal: Deedle.Vectors.ArrayVector uses a module listed above it, which is the healthy direction.
22β9 Deedle.Vectors.ArrayVector uses Deedle✕
- Connections
- 8 pairs of types, where a type in Deedle.Vectors.ArrayVector uses a type in Deedle.
- The types involved
Deedle.Vectors.ArrayVector.ArrayVectorBuilderβDeedle.IVector`1Deedle.Vectors.ArrayVector.ArrayVectorBuilderβDeedle.OptionalValue`1Deedle.Vectors.ArrayVector.ArrayVectorData`1βDeedle.OptionalValue`1Deedle.Vectors.ArrayVector.ArrayVector`1βDeedle.IVectorDeedle.Vectors.ArrayVector.ArrayVector`1βDeedle.IVectorLocationDeedle.Vectors.ArrayVector.ArrayVector`1βDeedle.IVector`1Deedle.Vectors.ArrayVector.ArrayVector`1βDeedle.OptionalValue`1Deedle.Vectors.ArrayVector.ArrayVector`1βDeedle.VectorCallSite`1
- Direction
- Deedle.Vectors.ArrayVector uses Deedle, so a change to Deedle can break Deedle.Vectors.ArrayVector, while a change to Deedle.Vectors.ArrayVector can't break Deedle.
- Position
- Below the diagonal: Deedle.Vectors.ArrayVector uses a module listed above it, which is the healthy direction.
23β1 Deedle.Vectors.VectorHelperExtensions uses Deedle.Addressing✕
- Connections
- 1 pair of types, where a type in Deedle.Vectors.VectorHelperExtensions uses a type in Deedle.Addressing.
- The types involved
Deedle.Vectors.VectorHelperExtensions.VectorHelperExtensionsβDeedle.Addressing.IAddressingScheme
- Direction
- Deedle.Vectors.VectorHelperExtensions uses Deedle.Addressing, so a change to Deedle.Addressing can break Deedle.Vectors.VectorHelperExtensions, while a change to Deedle.Vectors.VectorHelperExtensions can't break Deedle.Addressing.
- Position
- Below the diagonal: Deedle.Vectors.VectorHelperExtensions uses a module listed above it, which is the healthy direction.
23β5 Deedle.Vectors.VectorHelperExtensions uses Deedle.Vectors✕
- Connections
- 4 pairs of types, where a type in Deedle.Vectors.VectorHelperExtensions uses a type in Deedle.Vectors.
- The types involved
Deedle.Vectors.VectorHelperExtensions.RowReaderTransformβDeedle.Vectors.INaryTransformDeedle.Vectors.VectorHelperExtensions.RowReaderTransformβDeedle.Vectors.IRowReaderTransformDeedle.Vectors.VectorHelperExtensions.VectorHelperExtensionsβDeedle.Vectors.IVectorBuilderDeedle.Vectors.VectorHelperExtensions.VectorHelperExtensionsβDeedle.Vectors.VectorListTransform
- Direction
- Deedle.Vectors.VectorHelperExtensions uses Deedle.Vectors, so a change to Deedle.Vectors can break Deedle.Vectors.VectorHelperExtensions, while a change to Deedle.Vectors.VectorHelperExtensions can't break Deedle.Vectors.
- Position
- Below the diagonal: Deedle.Vectors.VectorHelperExtensions uses a module listed above it, which is the healthy direction.
23β9 Deedle.Vectors.VectorHelperExtensions uses Deedle✕
- Connections
- 3 pairs of types, where a type in Deedle.Vectors.VectorHelperExtensions uses a type in Deedle.
- The types involved
Deedle.Vectors.VectorHelperExtensions.VectorHelperExtensionsβDeedle.IVectorDeedle.Vectors.VectorHelperExtensions.VectorHelperExtensionsβDeedle.IVector`1Deedle.Vectors.VectorHelperExtensions.VectorHelperExtensionsβDeedle.OptionalValue`1
- Direction
- Deedle.Vectors.VectorHelperExtensions uses Deedle, so a change to Deedle can break Deedle.Vectors.VectorHelperExtensions, while a change to Deedle.Vectors.VectorHelperExtensions can't break Deedle.
- Position
- Below the diagonal: Deedle.Vectors.VectorHelperExtensions uses a module listed above it, which is the healthy direction.
24β9 Deedle.MathNetNumerics.LinearRegression.Fit uses Deedle✕
- Connections
- 4 pairs of types, where a type in Deedle.MathNetNumerics.LinearRegression.Fit uses a type in Deedle.
- The types involved
Deedle.MathNetNumerics.LinearRegression.Fit.FitβDeedle.Frame`2Deedle.MathNetNumerics.LinearRegression.Fit.FitβDeedle.Series`2Deedle.MathNetNumerics.LinearRegression.Fit.t`1βDeedle.Frame`2Deedle.MathNetNumerics.LinearRegression.Fit.t`1βDeedle.Series`2
- Direction
- Deedle.MathNetNumerics.LinearRegression.Fit uses Deedle, so a change to Deedle can break Deedle.MathNetNumerics.LinearRegression.Fit, while a change to Deedle.MathNetNumerics.LinearRegression.Fit can't break Deedle.
- Position
- Below the diagonal: Deedle.MathNetNumerics.LinearRegression.Fit uses a module listed above it, which is the healthy direction.
24β17 Deedle.MathNetNumerics.LinearRegression.Fit uses Deedle.MathNetNumerics.LinearRegression.Fit.Summary✕
- Connections
- 1 pair of types, where a type in Deedle.MathNetNumerics.LinearRegression.Fit uses a type in Deedle.MathNetNumerics.LinearRegression.Fit.Summary.
- The types involved
Deedle.MathNetNumerics.LinearRegression.Fit.FitβDeedle.MathNetNumerics.LinearRegression.Fit.Summary.t
- Direction
- Deedle.MathNetNumerics.LinearRegression.Fit uses Deedle.MathNetNumerics.LinearRegression.Fit.Summary, so a change to Deedle.MathNetNumerics.LinearRegression.Fit.Summary can break Deedle.MathNetNumerics.LinearRegression.Fit, while a change to Deedle.MathNetNumerics.LinearRegression.Fit can't break Deedle.MathNetNumerics.LinearRegression.Fit.Summary.
- Position
- Below the diagonal: Deedle.MathNetNumerics.LinearRegression.Fit uses a module listed above it, which is the healthy direction.
25β9 Deedle.MicrosoftML.Extraction uses Deedle✕
- Connections
- 2 pairs of types, where a type in Deedle.MicrosoftML.Extraction uses a type in Deedle.
- The types involved
Deedle.MicrosoftML.Extraction.ExtractionβDeedle.Frame`2Deedle.MicrosoftML.Extraction.ExtractionβDeedle.Series`2
- Direction
- Deedle.MicrosoftML.Extraction uses Deedle, so a change to Deedle can break Deedle.MicrosoftML.Extraction, while a change to Deedle.MicrosoftML.Extraction can't break Deedle.
- Position
- Below the diagonal: Deedle.MicrosoftML.Extraction uses a module listed above it, which is the healthy direction.
25β18 Deedle.MicrosoftML.Extraction uses Deedle.MicrosoftML✕
- Connections
- 1 pair of types, where a type in Deedle.MicrosoftML.Extraction uses a type in Deedle.MicrosoftML.
- The types involved
Deedle.MicrosoftML.Extraction.ExtractionβDeedle.MicrosoftML.ColData
- Direction
- Deedle.MicrosoftML.Extraction uses Deedle.MicrosoftML, so a change to Deedle.MicrosoftML can break Deedle.MicrosoftML.Extraction, while a change to Deedle.MicrosoftML.Extraction can't break Deedle.MicrosoftML.
- Position
- Below the diagonal: Deedle.MicrosoftML.Extraction uses a module listed above it, which is the healthy direction.
26β9 Deedle.Ranges.Ranges uses Deedle✕
- Connections
- 3 pairs of types, where a type in Deedle.Ranges.Ranges uses a type in Deedle.
- The types involved
Deedle.Ranges.Ranges.RangesβDeedle.LookupDeedle.Ranges.Ranges.RangesβDeedle.OptionalValue`1Deedle.Ranges.Ranges.RangesβDeedle.RangeRestriction`1
- Direction
- Deedle.Ranges.Ranges uses Deedle, so a change to Deedle can break Deedle.Ranges.Ranges, while a change to Deedle.Ranges.Ranges can't break Deedle.
- Position
- Below the diagonal: Deedle.Ranges.Ranges uses a module listed above it, which is the healthy direction.
26β19 Deedle.Ranges.Ranges uses Deedle.Ranges✕
- Connections
- 2 pairs of types, where a type in Deedle.Ranges.Ranges uses a type in Deedle.Ranges.
- The types involved
Deedle.Ranges.Ranges.RangesβDeedle.Ranges.IRangeKeyOperations`1Deedle.Ranges.Ranges.RangesβDeedle.Ranges.Ranges`1
- Direction
- Deedle.Ranges.Ranges uses Deedle.Ranges, so a change to Deedle.Ranges can break Deedle.Ranges.Ranges, while a change to Deedle.Ranges.Ranges can't break Deedle.Ranges.
- Position
- Below the diagonal: Deedle.Ranges.Ranges uses a module listed above it, which is the healthy direction.
27β1 Deedle.Vectors.Virtual uses Deedle.Addressing✕
- Connections
- 6 pairs of types, where a type in Deedle.Vectors.Virtual uses a type in Deedle.Addressing.
- The types involved
Deedle.Vectors.Virtual.DelayedLocationβDeedle.Addressing.IAddressOperationsDeedle.Vectors.Virtual.IVirtualVectorSourceβDeedle.Addressing.IAddressOperationsDeedle.Vectors.Virtual.RangesAddressOperations`1βDeedle.Addressing.IAddressOperationsDeedle.Vectors.Virtual.VirtualAddressingSchemeβDeedle.Addressing.IAddressingSchemeDeedle.Vectors.Virtual.VirtualVectorBuilderβDeedle.Addressing.IAddressingSchemeDeedle.Vectors.Virtual.VirtualVector`1βDeedle.Addressing.IAddressingScheme
- Direction
- Deedle.Vectors.Virtual uses Deedle.Addressing, so a change to Deedle.Addressing can break Deedle.Vectors.Virtual, while a change to Deedle.Vectors.Virtual can't break Deedle.Addressing.
- Position
- Below the diagonal: Deedle.Vectors.Virtual uses a module listed above it, which is the healthy direction.
27β5 Deedle.Vectors.Virtual uses Deedle.Vectors✕
- Connections
- 3 pairs of types, where a type in Deedle.Vectors.Virtual uses a type in Deedle.Vectors.
- The types involved
Deedle.Vectors.Virtual.VirtualVectorBuilderβDeedle.Vectors.IVectorBuilderDeedle.Vectors.Virtual.VirtualVectorBuilderβDeedle.Vectors.VectorConstructionDeedle.Vectors.Virtual.VirtualVector`1βDeedle.Vectors.VectorData`1
- Direction
- Deedle.Vectors.Virtual uses Deedle.Vectors, so a change to Deedle.Vectors can break Deedle.Vectors.Virtual, while a change to Deedle.Vectors.Virtual can't break Deedle.Vectors.
- Position
- Below the diagonal: Deedle.Vectors.Virtual uses a module listed above it, which is the healthy direction.
27β9 Deedle.Vectors.Virtual uses Deedle✕
- Connections
- 12 pairs of types, where a type in Deedle.Vectors.Virtual uses a type in Deedle.
- The types involved
Deedle.Vectors.Virtual.DelayedLocationβDeedle.IVectorLocationDeedle.Vectors.Virtual.IVirtualVectorSource`1βDeedle.IVectorLocationDeedle.Vectors.Virtual.IVirtualVectorSource`1βDeedle.LookupDeedle.Vectors.Virtual.IVirtualVectorSource`1βDeedle.OptionalValue`1Deedle.Vectors.Virtual.IVirtualVectorSource`1βDeedle.RangeRestriction`1Deedle.Vectors.Virtual.VirtualVectorBuilderβDeedle.IVector`1Deedle.Vectors.Virtual.VirtualVectorBuilderβDeedle.OptionalValue`1Deedle.Vectors.Virtual.VirtualVector`1βDeedle.IVectorDeedle.Vectors.Virtual.VirtualVector`1βDeedle.IVectorLocationDeedle.Vectors.Virtual.VirtualVector`1βDeedle.IVector`1Deedle.Vectors.Virtual.VirtualVector`1βDeedle.OptionalValue`1Deedle.Vectors.Virtual.VirtualVector`1βDeedle.VectorCallSite`1
- Direction
- Deedle.Vectors.Virtual uses Deedle, so a change to Deedle can break Deedle.Vectors.Virtual, while a change to Deedle.Vectors.Virtual can't break Deedle.
- Position
- Below the diagonal: Deedle.Vectors.Virtual uses a module listed above it, which is the healthy direction.
27β19 Deedle.Vectors.Virtual uses Deedle.Ranges✕
- Connections
- 1 pair of types, where a type in Deedle.Vectors.Virtual uses a type in Deedle.Ranges.
- The types involved
Deedle.Vectors.Virtual.RangesAddressOperations`1βDeedle.Ranges.Ranges`1
- Direction
- Deedle.Vectors.Virtual uses Deedle.Ranges, so a change to Deedle.Ranges can break Deedle.Vectors.Virtual, while a change to Deedle.Vectors.Virtual can't break Deedle.Ranges.
- Position
- Below the diagonal: Deedle.Vectors.Virtual uses a module listed above it, which is the healthy direction.
28β1 Deedle.Indices.Virtual uses Deedle.Addressing✕
- Connections
- 4 pairs of types, where a type in Deedle.Indices.Virtual uses a type in Deedle.Addressing.
- The types involved
Deedle.Indices.Virtual.VirtualOrderedIndex`1βDeedle.Addressing.IAddressOperationsDeedle.Indices.Virtual.VirtualOrderedIndex`1βDeedle.Addressing.IAddressingSchemeDeedle.Indices.Virtual.VirtualOrdinalIndexβDeedle.Addressing.IAddressOperationsDeedle.Indices.Virtual.VirtualOrdinalIndexβDeedle.Addressing.IAddressingScheme
- Direction
- Deedle.Indices.Virtual uses Deedle.Addressing, so a change to Deedle.Addressing can break Deedle.Indices.Virtual, while a change to Deedle.Indices.Virtual can't break Deedle.Addressing.
- Position
- Below the diagonal: Deedle.Indices.Virtual uses a module listed above it, which is the healthy direction.
28β5 Deedle.Indices.Virtual uses Deedle.Vectors✕
- Connections
- 2 pairs of types, where a type in Deedle.Indices.Virtual uses a type in Deedle.Vectors.
- The types involved
Deedle.Indices.Virtual.VirtualIndexBuilderβDeedle.Vectors.VectorConstructionDeedle.Indices.Virtual.VirtualIndexBuilderβDeedle.Vectors.VectorListTransform
- Direction
- Deedle.Indices.Virtual uses Deedle.Vectors, so a change to Deedle.Vectors can break Deedle.Indices.Virtual, while a change to Deedle.Indices.Virtual can't break Deedle.Vectors.
- Position
- Below the diagonal: Deedle.Indices.Virtual uses a module listed above it, which is the healthy direction.
28β7 Deedle.Indices.Virtual uses Deedle.Indices✕
- Connections
- 6 pairs of types, where a type in Deedle.Indices.Virtual uses a type in Deedle.Indices.
- The types involved
Deedle.Indices.Virtual.VirtualIndexBuilderβDeedle.Indices.IIndexBuilderDeedle.Indices.Virtual.VirtualIndexBuilderβDeedle.Indices.IIndex`1Deedle.Indices.Virtual.VirtualOrderedIndex`1βDeedle.Indices.IIndexBuilderDeedle.Indices.Virtual.VirtualOrderedIndex`1βDeedle.Indices.IIndex`1Deedle.Indices.Virtual.VirtualOrdinalIndexβDeedle.Indices.IIndexBuilderDeedle.Indices.Virtual.VirtualOrdinalIndexβDeedle.Indices.IIndex`1
- Direction
- Deedle.Indices.Virtual uses Deedle.Indices, so a change to Deedle.Indices can break Deedle.Indices.Virtual, while a change to Deedle.Indices.Virtual can't break Deedle.Indices.
- Position
- Below the diagonal: Deedle.Indices.Virtual uses a module listed above it, which is the healthy direction.
28β9 Deedle.Indices.Virtual uses Deedle✕
- Connections
- 10 pairs of types, where a type in Deedle.Indices.Virtual uses a type in Deedle.
- The types involved
Deedle.Indices.Virtual.VirtualIndexBuilderβDeedle.Aggregation`1Deedle.Indices.Virtual.VirtualIndexBuilderβDeedle.DirectionDeedle.Indices.Virtual.VirtualIndexBuilderβDeedle.ICustomLookup`1Deedle.Indices.Virtual.VirtualIndexBuilderβDeedle.IVector`1Deedle.Indices.Virtual.VirtualIndexBuilderβDeedle.LookupDeedle.Indices.Virtual.VirtualIndexBuilderβDeedle.RangeRestriction`1Deedle.Indices.Virtual.VirtualOrderedIndex`1βDeedle.LookupDeedle.Indices.Virtual.VirtualOrderedIndex`1βDeedle.OptionalValue`1Deedle.Indices.Virtual.VirtualOrdinalIndexβDeedle.LookupDeedle.Indices.Virtual.VirtualOrdinalIndexβDeedle.OptionalValue`1
- Direction
- Deedle.Indices.Virtual uses Deedle, so a change to Deedle can break Deedle.Indices.Virtual, while a change to Deedle.Indices.Virtual can't break Deedle.
- Position
- Below the diagonal: Deedle.Indices.Virtual uses a module listed above it, which is the healthy direction.
28β19 Deedle.Indices.Virtual uses Deedle.Ranges✕
- Connections
- 1 pair of types, where a type in Deedle.Indices.Virtual uses a type in Deedle.Ranges.
- The types involved
Deedle.Indices.Virtual.VirtualOrdinalIndexβDeedle.Ranges.Ranges`1
- Direction
- Deedle.Indices.Virtual uses Deedle.Ranges, so a change to Deedle.Ranges can break Deedle.Indices.Virtual, while a change to Deedle.Indices.Virtual can't break Deedle.Ranges.
- Position
- Below the diagonal: Deedle.Indices.Virtual uses a module listed above it, which is the healthy direction.
28β27 Deedle.Indices.Virtual uses Deedle.Vectors.Virtual✕
- Connections
- 2 pairs of types, where a type in Deedle.Indices.Virtual uses a type in Deedle.Vectors.Virtual.
- The types involved
Deedle.Indices.Virtual.VirtualOrderedIndex`1βDeedle.Vectors.Virtual.IVirtualVectorSource`1Deedle.Indices.Virtual.VirtualOrdinalIndexβDeedle.Vectors.Virtual.IVirtualVectorSource
- Direction
- Deedle.Indices.Virtual uses Deedle.Vectors.Virtual, so a change to Deedle.Vectors.Virtual can break Deedle.Indices.Virtual, while a change to Deedle.Indices.Virtual can't break Deedle.Vectors.Virtual.
- Position
- Below the diagonal: Deedle.Indices.Virtual uses a module listed above it, which is the healthy direction.
29β9 Deedle.MathNetNumerics.LinearRegression uses Deedle✕
- Connections
- 2 pairs of types, where a type in Deedle.MathNetNumerics.LinearRegression uses a type in Deedle.
- The types involved
Deedle.MathNetNumerics.LinearRegression.LinearRegressionβDeedle.Frame`2Deedle.MathNetNumerics.LinearRegression.LinearRegressionβDeedle.Series`2
- Direction
- Deedle.MathNetNumerics.LinearRegression uses Deedle, so a change to Deedle can break Deedle.MathNetNumerics.LinearRegression, while a change to Deedle.MathNetNumerics.LinearRegression can't break Deedle.
- Position
- Below the diagonal: Deedle.MathNetNumerics.LinearRegression uses a module listed above it, which is the healthy direction.
29β24 Deedle.MathNetNumerics.LinearRegression uses Deedle.MathNetNumerics.LinearRegression.Fit✕
- Connections
- 1 pair of types, where a type in Deedle.MathNetNumerics.LinearRegression uses a type in Deedle.MathNetNumerics.LinearRegression.Fit.
- The types involved
Deedle.MathNetNumerics.LinearRegression.LinearRegressionβDeedle.MathNetNumerics.LinearRegression.Fit.t`1
- Direction
- Deedle.MathNetNumerics.LinearRegression uses Deedle.MathNetNumerics.LinearRegression.Fit, so a change to Deedle.MathNetNumerics.LinearRegression.Fit can break Deedle.MathNetNumerics.LinearRegression, while a change to Deedle.MathNetNumerics.LinearRegression can't break Deedle.MathNetNumerics.LinearRegression.Fit.
- Position
- Below the diagonal: Deedle.MathNetNumerics.LinearRegression uses a module listed above it, which is the healthy direction.
30β1 Deedle.Vectors.Virtual.VirtualVectorSource uses Deedle.Addressing✕
- Connections
- 2 pairs of types, where a type in Deedle.Vectors.Virtual.VirtualVectorSource uses a type in Deedle.Addressing.
- The types involved
Deedle.Vectors.Virtual.VirtualVectorSource.ContiguousLinearAddressOperationsβDeedle.Addressing.IAddressOperationsDeedle.Vectors.Virtual.VirtualVectorSource.VirtualVectorSourceβDeedle.Addressing.IAddressOperations
- Direction
- Deedle.Vectors.Virtual.VirtualVectorSource uses Deedle.Addressing, so a change to Deedle.Addressing can break Deedle.Vectors.Virtual.VirtualVectorSource, while a change to Deedle.Vectors.Virtual.VirtualVectorSource can't break Deedle.Addressing.
- Position
- Below the diagonal: Deedle.Vectors.Virtual.VirtualVectorSource uses a module listed above it, which is the healthy direction.
30β5 Deedle.Vectors.Virtual.VirtualVectorSource uses Deedle.Vectors✕
- Connections
- 3 pairs of types, where a type in Deedle.Vectors.Virtual.VirtualVectorSource uses a type in Deedle.Vectors.
- The types involved
Deedle.Vectors.Virtual.VirtualVectorSource.VirtualVectorSourceβDeedle.Vectors.IRowReaderTransformDeedle.Vectors.Virtual.VirtualVectorSource.VirtualVectorSourceβDeedle.Vectors.IVectorBuilderDeedle.Vectors.Virtual.VirtualVectorSource.VirtualVectorSourceβDeedle.Vectors.VectorFillMissing
- Direction
- Deedle.Vectors.Virtual.VirtualVectorSource uses Deedle.Vectors, so a change to Deedle.Vectors can break Deedle.Vectors.Virtual.VirtualVectorSource, while a change to Deedle.Vectors.Virtual.VirtualVectorSource can't break Deedle.Vectors.
- Position
- Below the diagonal: Deedle.Vectors.Virtual.VirtualVectorSource uses a module listed above it, which is the healthy direction.
30β9 Deedle.Vectors.Virtual.VirtualVectorSource uses Deedle✕
- Connections
- 5 pairs of types, where a type in Deedle.Vectors.Virtual.VirtualVectorSource uses a type in Deedle.
- The types involved
Deedle.Vectors.Virtual.VirtualVectorSource.VirtualVectorSourceβDeedle.IVectorDeedle.Vectors.Virtual.VirtualVectorSource.VirtualVectorSourceβDeedle.IVector`1Deedle.Vectors.Virtual.VirtualVectorSource.VirtualVectorSourceβDeedle.LookupDeedle.Vectors.Virtual.VirtualVectorSource.VirtualVectorSourceβDeedle.OptionalValue`1Deedle.Vectors.Virtual.VirtualVectorSource.VirtualVectorSourceβDeedle.RangeRestriction`1
- Direction
- Deedle.Vectors.Virtual.VirtualVectorSource uses Deedle, so a change to Deedle can break Deedle.Vectors.Virtual.VirtualVectorSource, while a change to Deedle.Vectors.Virtual.VirtualVectorSource can't break Deedle.
- Position
- Below the diagonal: Deedle.Vectors.Virtual.VirtualVectorSource uses a module listed above it, which is the healthy direction.
30β27 Deedle.Vectors.Virtual.VirtualVectorSource uses Deedle.Vectors.Virtual✕
- Connections
- 5 pairs of types, where a type in Deedle.Vectors.Virtual.VirtualVectorSource uses a type in Deedle.Vectors.Virtual.
- The types involved
Deedle.Vectors.Virtual.VirtualVectorSource.IBoxedVectorSource`1βDeedle.Vectors.Virtual.IVirtualVectorSource`1Deedle.Vectors.Virtual.VirtualVectorSource.ICombinedVectorSource`1βDeedle.Vectors.Virtual.IVirtualVectorSource`1Deedle.Vectors.Virtual.VirtualVectorSource.ILinearAddressedSource`1βDeedle.Vectors.Virtual.IVirtualVectorSource`1Deedle.Vectors.Virtual.VirtualVectorSource.IMappedVectorSource`2βDeedle.Vectors.Virtual.IVirtualVectorSource`1Deedle.Vectors.Virtual.VirtualVectorSource.VirtualVectorSourceβDeedle.Vectors.Virtual.IVirtualVectorSource`1
- Direction
- Deedle.Vectors.Virtual.VirtualVectorSource uses Deedle.Vectors.Virtual, so a change to Deedle.Vectors.Virtual can break Deedle.Vectors.Virtual.VirtualVectorSource, while a change to Deedle.Vectors.Virtual.VirtualVectorSource can't break Deedle.Vectors.Virtual.
- Position
- Below the diagonal: Deedle.Vectors.Virtual.VirtualVectorSource uses a module listed above it, which is the healthy direction.
31β1 Deedle.Virtual uses Deedle.Addressing✕
- Connections
- 1 pair of types, where a type in Deedle.Virtual uses a type in Deedle.Addressing.
- The types involved
Deedle.Virtual.OrdinalVirtualSource`1βDeedle.Addressing.IAddressOperations
- Direction
- Deedle.Virtual uses Deedle.Addressing, so a change to Deedle.Addressing can break Deedle.Virtual, while a change to Deedle.Virtual can't break Deedle.Addressing.
- Position
- Below the diagonal: Deedle.Virtual uses a module listed above it, which is the healthy direction.
31β9 Deedle.Virtual uses Deedle✕
- Connections
- 9 pairs of types, where a type in Deedle.Virtual uses a type in Deedle.
- The types involved
Deedle.Virtual.IndexUtilsβDeedle.LookupDeedle.Virtual.IndexUtilsβDeedle.OptionalValue`1Deedle.Virtual.OrdinalVirtualSource`1βDeedle.IVectorLocationDeedle.Virtual.OrdinalVirtualSource`1βDeedle.LookupDeedle.Virtual.OrdinalVirtualSource`1βDeedle.OptionalValue`1Deedle.Virtual.OrdinalVirtualSource`1βDeedle.RangeRestriction`1Deedle.Virtual.StepRangeβDeedle.IRangeRestriction`1Deedle.Virtual.VirtualβDeedle.Frame`2Deedle.Virtual.VirtualβDeedle.Series`2
- Direction
- Deedle.Virtual uses Deedle, so a change to Deedle can break Deedle.Virtual, while a change to Deedle.Virtual can't break Deedle.
- Position
- Below the diagonal: Deedle.Virtual uses a module listed above it, which is the healthy direction.
31β27 Deedle.Virtual uses Deedle.Vectors.Virtual✕
- Connections
- 8 pairs of types, where a type in Deedle.Virtual uses a type in Deedle.Vectors.Virtual.
- The types involved
Deedle.Virtual.OrdinalVirtualSource`1βDeedle.Vectors.Virtual.IVirtualVectorSourceDeedle.Virtual.OrdinalVirtualSource`1βDeedle.Vectors.Virtual.IVirtualVectorSourceOperation`1Deedle.Virtual.OrdinalVirtualSource`1βDeedle.Vectors.Virtual.IVirtualVectorSource`1Deedle.Virtual.VirtualβDeedle.Vectors.Virtual.IVirtualVectorSourceDeedle.Virtual.VirtualβDeedle.Vectors.Virtual.IVirtualVectorSource`1Deedle.Virtual.VirtualVectorHelperβDeedle.Vectors.Virtual.IVirtualVectorSourceDeedle.Virtual.VirtualVectorHelperβDeedle.Vectors.Virtual.IVirtualVectorSource`1Deedle.Virtual.VirtualVectorHelperβDeedle.Vectors.Virtual.VirtualVector`1
- Direction
- Deedle.Virtual uses Deedle.Vectors.Virtual, so a change to Deedle.Vectors.Virtual can break Deedle.Virtual, while a change to Deedle.Virtual can't break Deedle.Vectors.Virtual.
- Position
- Below the diagonal: Deedle.Virtual uses a module listed above it, which is the healthy direction.
32β9 Deedle.Parquet.Virtual.Sources uses Deedle✕
- Connections
- 1 pair of types, where a type in Deedle.Parquet.Virtual.Sources uses a type in Deedle.
- The types involved
Deedle.Parquet.Virtual.Sources.ParquetFileIndexβDeedle.OptionalValue`1
- Direction
- Deedle.Parquet.Virtual.Sources uses Deedle, so a change to Deedle can break Deedle.Parquet.Virtual.Sources, while a change to Deedle.Parquet.Virtual.Sources can't break Deedle.
- Position
- Below the diagonal: Deedle.Parquet.Virtual.Sources uses a module listed above it, which is the healthy direction.
32β31 Deedle.Parquet.Virtual.Sources uses Deedle.Virtual✕
- Connections
- 1 pair of types, where a type in Deedle.Parquet.Virtual.Sources uses a type in Deedle.Virtual.
- The types involved
Deedle.Parquet.Virtual.Sources.VirtualReadParquetOptionsβDeedle.Virtual.VirtualSearchColumn
- Direction
- Deedle.Parquet.Virtual.Sources uses Deedle.Virtual, so a change to Deedle.Virtual can break Deedle.Parquet.Virtual.Sources, while a change to Deedle.Parquet.Virtual.Sources can't break Deedle.Virtual.
- Position
- Below the diagonal: Deedle.Parquet.Virtual.Sources uses a module listed above it, which is the healthy direction.
33β9 Deedle.Parquet.Virtual.Sources.VirtualParquetExtensions uses Deedle✕
- Connections
- 1 pair of types, where a type in Deedle.Parquet.Virtual.Sources.VirtualParquetExtensions uses a type in Deedle.
- The types involved
Deedle.Parquet.Virtual.Sources.VirtualParquetExtensions.VirtualParquetExtensionsβDeedle.Frame`2
- Direction
- Deedle.Parquet.Virtual.Sources.VirtualParquetExtensions uses Deedle, so a change to Deedle can break Deedle.Parquet.Virtual.Sources.VirtualParquetExtensions, while a change to Deedle.Parquet.Virtual.Sources.VirtualParquetExtensions can't break Deedle.
- Position
- Below the diagonal: Deedle.Parquet.Virtual.Sources.VirtualParquetExtensions uses a module listed above it, which is the healthy direction.
33β31 Deedle.Parquet.Virtual.Sources.VirtualParquetExtensions uses Deedle.Virtual✕
- Connections
- 1 pair of types, where a type in Deedle.Parquet.Virtual.Sources.VirtualParquetExtensions uses a type in Deedle.Virtual.
- The types involved
Deedle.Parquet.Virtual.Sources.VirtualParquetExtensions.VirtualParquetExtensionsβDeedle.Virtual.VirtualSearchColumn
- Direction
- Deedle.Parquet.Virtual.Sources.VirtualParquetExtensions uses Deedle.Virtual, so a change to Deedle.Virtual can break Deedle.Parquet.Virtual.Sources.VirtualParquetExtensions, while a change to Deedle.Parquet.Virtual.Sources.VirtualParquetExtensions can't break Deedle.Virtual.
- Position
- Below the diagonal: Deedle.Parquet.Virtual.Sources.VirtualParquetExtensions uses a module listed above it, which is the healthy direction.
34β9 Deedle.Virtual.FloatBatchMaterialize uses Deedle✕
- Connections
- 2 pairs of types, where a type in Deedle.Virtual.FloatBatchMaterialize uses a type in Deedle.
- The types involved
Deedle.Virtual.FloatBatchMaterialize.FloatBatchMaterializeβDeedle.Frame`2Deedle.Virtual.FloatBatchMaterialize.FloatBatchMaterializeβDeedle.Series`2
- Direction
- Deedle.Virtual.FloatBatchMaterialize uses Deedle, so a change to Deedle can break Deedle.Virtual.FloatBatchMaterialize, while a change to Deedle.Virtual.FloatBatchMaterialize can't break Deedle.
- Position
- Below the diagonal: Deedle.Virtual.FloatBatchMaterialize uses a module listed above it, which is the healthy direction.
34β31 Deedle.Virtual.FloatBatchMaterialize uses Deedle.Virtual✕
- Connections
- 2 pairs of types, where a type in Deedle.Virtual.FloatBatchMaterialize uses a type in Deedle.Virtual.
- The types involved
Deedle.Virtual.FloatBatchMaterialize.FloatBatchMaterializeβDeedle.Virtual.FloatBatchLayoutDeedle.Virtual.FloatBatchMaterialize.FloatBatchMaterializeβDeedle.Virtual.FloatBatchOrder
- Direction
- Deedle.Virtual.FloatBatchMaterialize uses Deedle.Virtual, so a change to Deedle.Virtual can break Deedle.Virtual.FloatBatchMaterialize, while a change to Deedle.Virtual.FloatBatchMaterialize can't break Deedle.Virtual.
- Position
- Below the diagonal: Deedle.Virtual.FloatBatchMaterialize uses a module listed above it, which is the healthy direction.
35β9 Deedle.Virtual.LookupRangeExecutor uses Deedle✕
- Connections
- 1 pair of types, where a type in Deedle.Virtual.LookupRangeExecutor uses a type in Deedle.
- The types involved
Deedle.Virtual.LookupRangeExecutor.LookupRangeExecutorβDeedle.RangeRestriction`1
- Direction
- Deedle.Virtual.LookupRangeExecutor uses Deedle, so a change to Deedle can break Deedle.Virtual.LookupRangeExecutor, while a change to Deedle.Virtual.LookupRangeExecutor can't break Deedle.
- Position
- Below the diagonal: Deedle.Virtual.LookupRangeExecutor uses a module listed above it, which is the healthy direction.
35β31 Deedle.Virtual.LookupRangeExecutor uses Deedle.Virtual✕
- Connections
- 2 pairs of types, where a type in Deedle.Virtual.LookupRangeExecutor uses a type in Deedle.Virtual.
- The types involved
Deedle.Virtual.LookupRangeExecutor.LookupRangeExecutorβDeedle.Virtual.LookupRangeMode`1Deedle.Virtual.LookupRangeExecutor.SubVectorSpec`1βDeedle.Virtual.LookupRangeMode`1
- Direction
- Deedle.Virtual.LookupRangeExecutor uses Deedle.Virtual, so a change to Deedle.Virtual can break Deedle.Virtual.LookupRangeExecutor, while a change to Deedle.Virtual.LookupRangeExecutor can't break Deedle.Virtual.
- Position
- Below the diagonal: Deedle.Virtual.LookupRangeExecutor uses a module listed above it, which is the healthy direction.
36β9 Deedle.Virtual.Sources.VirtualCsvSource uses Deedle✕
- Connections
- 1 pair of types, where a type in Deedle.Virtual.Sources.VirtualCsvSource uses a type in Deedle.
- The types involved
Deedle.Virtual.Sources.VirtualCsvSource.VirtualCsvSourceβDeedle.Frame`2
- Direction
- Deedle.Virtual.Sources.VirtualCsvSource uses Deedle, so a change to Deedle can break Deedle.Virtual.Sources.VirtualCsvSource, while a change to Deedle.Virtual.Sources.VirtualCsvSource can't break Deedle.
- Position
- Below the diagonal: Deedle.Virtual.Sources.VirtualCsvSource uses a module listed above it, which is the healthy direction.
36β27 Deedle.Virtual.Sources.VirtualCsvSource uses Deedle.Vectors.Virtual✕
- Connections
- 3 pairs of types, where a type in Deedle.Virtual.Sources.VirtualCsvSource uses a type in Deedle.Vectors.Virtual.
- The types involved
Deedle.Virtual.Sources.VirtualCsvSource.VirtualCsvFrameHelperβDeedle.Vectors.Virtual.IVirtualVectorSourceDeedle.Virtual.Sources.VirtualCsvSource.VirtualCsvFrameHelperβDeedle.Vectors.Virtual.IVirtualVectorSource`1Deedle.Virtual.Sources.VirtualCsvSource.VirtualCsvSourceβDeedle.Vectors.Virtual.IVirtualVectorSource
- Direction
- Deedle.Virtual.Sources.VirtualCsvSource uses Deedle.Vectors.Virtual, so a change to Deedle.Vectors.Virtual can break Deedle.Virtual.Sources.VirtualCsvSource, while a change to Deedle.Virtual.Sources.VirtualCsvSource can't break Deedle.Vectors.Virtual.
- Position
- Below the diagonal: Deedle.Virtual.Sources.VirtualCsvSource uses a module listed above it, which is the healthy direction.
36β31 Deedle.Virtual.Sources.VirtualCsvSource uses Deedle.Virtual✕
- Connections
- 3 pairs of types, where a type in Deedle.Virtual.Sources.VirtualCsvSource uses a type in Deedle.Virtual.
- The types involved
Deedle.Virtual.Sources.VirtualCsvSource.VirtualCsvSourceβDeedle.Virtual.LookupRangeMode`1Deedle.Virtual.Sources.VirtualCsvSource.VirtualCsvSourceβDeedle.Virtual.ResolvedColumnSearchDeedle.Virtual.Sources.VirtualCsvSource.VirtualCsvSourceβDeedle.Virtual.VirtualReadCsvOptions
- Direction
- Deedle.Virtual.Sources.VirtualCsvSource uses Deedle.Virtual, so a change to Deedle.Virtual can break Deedle.Virtual.Sources.VirtualCsvSource, while a change to Deedle.Virtual.Sources.VirtualCsvSource can't break Deedle.Virtual.
- Position
- Below the diagonal: Deedle.Virtual.Sources.VirtualCsvSource uses a module listed above it, which is the healthy direction.
37β9 Deedle.Virtual.VirtualCsvExtensions uses Deedle✕
- Connections
- 1 pair of types, where a type in Deedle.Virtual.VirtualCsvExtensions uses a type in Deedle.
- The types involved
Deedle.Virtual.VirtualCsvExtensions.VirtualCsvExtensionsβDeedle.Frame`2
- Direction
- Deedle.Virtual.VirtualCsvExtensions uses Deedle, so a change to Deedle can break Deedle.Virtual.VirtualCsvExtensions, while a change to Deedle.Virtual.VirtualCsvExtensions can't break Deedle.
- Position
- Below the diagonal: Deedle.Virtual.VirtualCsvExtensions uses a module listed above it, which is the healthy direction.
37β31 Deedle.Virtual.VirtualCsvExtensions uses Deedle.Virtual✕
- Connections
- 2 pairs of types, where a type in Deedle.Virtual.VirtualCsvExtensions uses a type in Deedle.Virtual.
- The types involved
Deedle.Virtual.VirtualCsvExtensions.VirtualCsvExtensionsβDeedle.Virtual.VirtualReadCsvOptionsDeedle.Virtual.VirtualCsvExtensions.VirtualCsvExtensionsβDeedle.Virtual.VirtualSearchColumn
- Direction
- Deedle.Virtual.VirtualCsvExtensions uses Deedle.Virtual, so a change to Deedle.Virtual can break Deedle.Virtual.VirtualCsvExtensions, while a change to Deedle.Virtual.VirtualCsvExtensions can't break Deedle.Virtual.
- Position
- Below the diagonal: Deedle.Virtual.VirtualCsvExtensions uses a module listed above it, which is the healthy direction.
38β9 Deedle.Virtual.VirtualFrameDiag uses Deedle✕
- Connections
- 2 pairs of types, where a type in Deedle.Virtual.VirtualFrameDiag uses a type in Deedle.
- The types involved
Deedle.Virtual.VirtualFrameDiag.VirtualFrameDiagβDeedle.Frame`2Deedle.Virtual.VirtualFrameDiag.VirtualFrameDiagβDeedle.IVector
- Direction
- Deedle.Virtual.VirtualFrameDiag uses Deedle, so a change to Deedle can break Deedle.Virtual.VirtualFrameDiag, while a change to Deedle.Virtual.VirtualFrameDiag can't break Deedle.
- Position
- Below the diagonal: Deedle.Virtual.VirtualFrameDiag uses a module listed above it, which is the healthy direction.
38β27 Deedle.Virtual.VirtualFrameDiag uses Deedle.Vectors.Virtual✕
- Connections
- 1 pair of types, where a type in Deedle.Virtual.VirtualFrameDiag uses a type in Deedle.Vectors.Virtual.
- The types involved
Deedle.Virtual.VirtualFrameDiag.VirtualFrameDiagβDeedle.Vectors.Virtual.IVirtualVectorSource
- Direction
- Deedle.Virtual.VirtualFrameDiag uses Deedle.Vectors.Virtual, so a change to Deedle.Vectors.Virtual can break Deedle.Virtual.VirtualFrameDiag, while a change to Deedle.Virtual.VirtualFrameDiag can't break Deedle.Vectors.Virtual.
- Position
- Below the diagonal: Deedle.Virtual.VirtualFrameDiag uses a module listed above it, which is the healthy direction.
38β31 Deedle.Virtual.VirtualFrameDiag uses Deedle.Virtual✕
- Connections
- 1 pair of types, where a type in Deedle.Virtual.VirtualFrameDiag uses a type in Deedle.Virtual.
- The types involved
Deedle.Virtual.VirtualFrameDiag.VirtualFrameDiagβDeedle.Virtual.IVirtualVectorSourceLookupDiagnostics
- Direction
- Deedle.Virtual.VirtualFrameDiag uses Deedle.Virtual, so a change to Deedle.Virtual can break Deedle.Virtual.VirtualFrameDiag, while a change to Deedle.Virtual.VirtualFrameDiag can't break Deedle.Virtual.
- Position
- Below the diagonal: Deedle.Virtual.VirtualFrameDiag uses a module listed above it, which is the healthy direction.
39β9 Deedle.Parquet.Virtual.Sources.ParquetColumnSource uses Deedle✕
- Connections
- 1 pair of types, where a type in Deedle.Parquet.Virtual.Sources.ParquetColumnSource uses a type in Deedle.
- The types involved
Deedle.Parquet.Virtual.Sources.ParquetColumnSource.ParquetColumnSourceβDeedle.OptionalValue`1
- Direction
- Deedle.Parquet.Virtual.Sources.ParquetColumnSource uses Deedle, so a change to Deedle can break Deedle.Parquet.Virtual.Sources.ParquetColumnSource, while a change to Deedle.Parquet.Virtual.Sources.ParquetColumnSource can't break Deedle.
- Position
- Below the diagonal: Deedle.Parquet.Virtual.Sources.ParquetColumnSource uses a module listed above it, which is the healthy direction.
39β27 Deedle.Parquet.Virtual.Sources.ParquetColumnSource uses Deedle.Vectors.Virtual✕
- Connections
- 1 pair of types, where a type in Deedle.Parquet.Virtual.Sources.ParquetColumnSource uses a type in Deedle.Vectors.Virtual.
- The types involved
Deedle.Parquet.Virtual.Sources.ParquetColumnSource.ParquetColumnSourceβDeedle.Vectors.Virtual.IVirtualVectorSource
- Direction
- Deedle.Parquet.Virtual.Sources.ParquetColumnSource uses Deedle.Vectors.Virtual, so a change to Deedle.Vectors.Virtual can break Deedle.Parquet.Virtual.Sources.ParquetColumnSource, while a change to Deedle.Parquet.Virtual.Sources.ParquetColumnSource can't break Deedle.Vectors.Virtual.
- Position
- Below the diagonal: Deedle.Parquet.Virtual.Sources.ParquetColumnSource uses a module listed above it, which is the healthy direction.
39β31 Deedle.Parquet.Virtual.Sources.ParquetColumnSource uses Deedle.Virtual✕
- Connections
- 2 pairs of types, where a type in Deedle.Parquet.Virtual.Sources.ParquetColumnSource uses a type in Deedle.Virtual.
- The types involved
Deedle.Parquet.Virtual.Sources.ParquetColumnSource.ParquetColumnSourceβDeedle.Virtual.LookupRangeMode`1Deedle.Parquet.Virtual.Sources.ParquetColumnSource.ParquetColumnSourceβDeedle.Virtual.ResolvedColumnSearch
- Direction
- Deedle.Parquet.Virtual.Sources.ParquetColumnSource uses Deedle.Virtual, so a change to Deedle.Virtual can break Deedle.Parquet.Virtual.Sources.ParquetColumnSource, while a change to Deedle.Parquet.Virtual.Sources.ParquetColumnSource can't break Deedle.Virtual.
- Position
- Below the diagonal: Deedle.Parquet.Virtual.Sources.ParquetColumnSource uses a module listed above it, which is the healthy direction.
39β32 Deedle.Parquet.Virtual.Sources.ParquetColumnSource uses Deedle.Parquet.Virtual.Sources✕
- Connections
- 3 pairs of types, where a type in Deedle.Parquet.Virtual.Sources.ParquetColumnSource uses a type in Deedle.Parquet.Virtual.Sources.
- The types involved
Deedle.Parquet.Virtual.Sources.ParquetColumnSource.ParquetColumnSourceβDeedle.Parquet.Virtual.Sources.ParquetColumnKindDeedle.Parquet.Virtual.Sources.ParquetColumnSource.ParquetColumnSourceβDeedle.Parquet.Virtual.Sources.ParquetFileIndexDeedle.Parquet.Virtual.Sources.ParquetColumnSource.ParquetColumnSourceβDeedle.Parquet.Virtual.Sources.VirtualReadParquetOptions
- Direction
- Deedle.Parquet.Virtual.Sources.ParquetColumnSource uses Deedle.Parquet.Virtual.Sources, so a change to Deedle.Parquet.Virtual.Sources can break Deedle.Parquet.Virtual.Sources.ParquetColumnSource, while a change to Deedle.Parquet.Virtual.Sources.ParquetColumnSource can't break Deedle.Parquet.Virtual.Sources.
- Position
- Below the diagonal: Deedle.Parquet.Virtual.Sources.ParquetColumnSource uses a module listed above it, which is the healthy direction.
40β9 Deedle.Parquet.Virtual.Sources.VirtualParquetSource uses Deedle✕
- Connections
- 1 pair of types, where a type in Deedle.Parquet.Virtual.Sources.VirtualParquetSource uses a type in Deedle.
- The types involved
Deedle.Parquet.Virtual.Sources.VirtualParquetSource.VirtualParquetSourceβDeedle.Frame`2
- Direction
- Deedle.Parquet.Virtual.Sources.VirtualParquetSource uses Deedle, so a change to Deedle can break Deedle.Parquet.Virtual.Sources.VirtualParquetSource, while a change to Deedle.Parquet.Virtual.Sources.VirtualParquetSource can't break Deedle.
- Position
- Below the diagonal: Deedle.Parquet.Virtual.Sources.VirtualParquetSource uses a module listed above it, which is the healthy direction.
40β27 Deedle.Parquet.Virtual.Sources.VirtualParquetSource uses Deedle.Vectors.Virtual✕
- Connections
- 1 pair of types, where a type in Deedle.Parquet.Virtual.Sources.VirtualParquetSource uses a type in Deedle.Vectors.Virtual.
- The types involved
Deedle.Parquet.Virtual.Sources.VirtualParquetSource.VirtualParquetSourceβDeedle.Vectors.Virtual.IVirtualVectorSource
- Direction
- Deedle.Parquet.Virtual.Sources.VirtualParquetSource uses Deedle.Vectors.Virtual, so a change to Deedle.Vectors.Virtual can break Deedle.Parquet.Virtual.Sources.VirtualParquetSource, while a change to Deedle.Parquet.Virtual.Sources.VirtualParquetSource can't break Deedle.Vectors.Virtual.
- Position
- Below the diagonal: Deedle.Parquet.Virtual.Sources.VirtualParquetSource uses a module listed above it, which is the healthy direction.
40β31 Deedle.Parquet.Virtual.Sources.VirtualParquetSource uses Deedle.Virtual✕
- Connections
- 1 pair of types, where a type in Deedle.Parquet.Virtual.Sources.VirtualParquetSource uses a type in Deedle.Virtual.
- The types involved
Deedle.Parquet.Virtual.Sources.VirtualParquetSource.VirtualParquetSourceβDeedle.Virtual.ResolvedColumnSearch
- Direction
- Deedle.Parquet.Virtual.Sources.VirtualParquetSource uses Deedle.Virtual, so a change to Deedle.Virtual can break Deedle.Parquet.Virtual.Sources.VirtualParquetSource, while a change to Deedle.Parquet.Virtual.Sources.VirtualParquetSource can't break Deedle.Virtual.
- Position
- Below the diagonal: Deedle.Parquet.Virtual.Sources.VirtualParquetSource uses a module listed above it, which is the healthy direction.
40β32 Deedle.Parquet.Virtual.Sources.VirtualParquetSource uses Deedle.Parquet.Virtual.Sources✕
- Connections
- 3 pairs of types, where a type in Deedle.Parquet.Virtual.Sources.VirtualParquetSource uses a type in Deedle.Parquet.Virtual.Sources.
- The types involved
Deedle.Parquet.Virtual.Sources.VirtualParquetSource.VirtualParquetSourceβDeedle.Parquet.Virtual.Sources.ParquetColumnKindDeedle.Parquet.Virtual.Sources.VirtualParquetSource.VirtualParquetSourceβDeedle.Parquet.Virtual.Sources.ParquetFileIndexDeedle.Parquet.Virtual.Sources.VirtualParquetSource.VirtualParquetSourceβDeedle.Parquet.Virtual.Sources.VirtualReadParquetOptions
- Direction
- Deedle.Parquet.Virtual.Sources.VirtualParquetSource uses Deedle.Parquet.Virtual.Sources, so a change to Deedle.Parquet.Virtual.Sources can break Deedle.Parquet.Virtual.Sources.VirtualParquetSource, while a change to Deedle.Parquet.Virtual.Sources.VirtualParquetSource can't break Deedle.Parquet.Virtual.Sources.
- Position
- Below the diagonal: Deedle.Parquet.Virtual.Sources.VirtualParquetSource uses a module listed above it, which is the healthy direction.
At a glance β Code Health
At a glance β Architecture
At a glance β Maturity
At a glance β Readiness
At a glance β Security
At a glance β Performance
Security & Compliance β OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 β Injection | 15 | High / Critical |
| A03:2025 β Software Supply Chain Failures | 7 | Medium |
Roadmap
Top priorities: Resolve the 1 Deprecated finding(s) in Dependency Hygiene; Resolve the 5 FileScopedPragmaDisable finding(s) in Explicit Debt β start with ArrowTests.cs, ExcelReaderTests.cs, Frame.cs; Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 Deprecated finding(s) in Dependency Hygiene. | +1.8 pts | Low | Dependency Hygiene |
| Resolve the 5 FileScopedPragmaDisable finding(s) in Explicit Debt β start with ArrowTests.cs, ExcelReaderTests.cs, Frame.cs. | +1.4 pts | Low | Explicit Debt |
| Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it. | +1.2 pts | Medium | Deployment & Rollback |
| Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) β start with REDACTED (3). | +0.6 pts | Low | Static Analysis (SAST) |
| 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.1 pts | Medium | Architecture documentation |
| Resolve the 25 Orphaned file finding(s) in Knowledge Freshness β start with VirtualIndex.fs, ArrayVector.fs, CsvRuntime.fs. | +0.8 pts | Medium | Knowledge Freshness |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) β start with REDACTED. | +0.4 pts | Low | Static Analysis (SAST) |
| Resolve the 1 CommentedOutCode finding(s) in Explicit Debt β start with Series.cs. | +0.3 pts | Low | Explicit Debt |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.4 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.6 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| tests/Deedle.CSharp.Tests/Series.cs | 5.8 | Mixed | Explicit Debt: FileScopedPragmaDisable |
| src/Deedle/Indices/LinearIndex.fs | 5.9 | Mixed | Cyclomatic Complexity: LinearIndexBuilder.Deedle.Indices.IIndexBuilder.Resample (cyclomatic 16) |
| src/Deedle.Arrow/Arrow.fs | 7.0 | Mixed | Cyclomatic Complexity: Implementation.batchesToFrame (cyclomatic 66) |
| src/Deedle.Parquet/Parquet.fs | 7.0 | Mixed | Cyclomatic Complexity: Implementation.columnToDataColumn (cyclomatic 42) |
| src/Deedle/FrameUtils.fs | 7.0 | Mixed | Cyclomatic Complexity: FrameUtilsModule.readCsv (cyclomatic 40) |
| src/Deedle/VirtualLookupRange.fs | 7.0 | Mixed | Cyclomatic Complexity: LookupRangeExecutor.remapLookupRangeAfterStep (cyclomatic 33) |
| src/Deedle/Stats.fs | 7.0 | Mixed | Cyclomatic Complexity: Stats.interpolateLinearWith (cyclomatic 17) |
| src/Deedle/FrameModule.fs | 7.0 | Mixed | Cognitive Complexity: FrameModule.MeltBy (cognitive 33) |
| src/Deedle/FSharp.Data/Net/Http.fs | 7.0 | Mixed | Cyclomatic Complexity: CookieHandling.getAllCookiesFromHeader (cyclomatic 23) |
| src/Deedle/Frame.fs | 7.1 | Mixed | Cyclomatic Complexity: Frame`2.FormatStrings (cyclomatic 26) |
| src/Deedle/Common/Common.fs | 7.1 | Mixed | Cyclomatic Complexity: Seq.alignOrdered (cyclomatic 25) |
| src/Deedle/VirtualFrame.fs | 7.1 | Mixed | Cyclomatic Complexity: IndexUtilsModule.binarySearch (cyclomatic 16) |
| src/Deedle/Vectors/VirtualVector.fs | 7.2 | Mixed | Cyclomatic Complexity: VirtualVectorBuilder.Deedle.Vectors.IVectorBuilder.Build (cyclomatic 28) |
| src/Deedle/Common/Ranges.fs | 7.2 | Mixed | Cyclomatic Complexity: Ranges.lookup (cyclomatic 27) |
| src/Deedle/VirtualCsvSource.fs | 7.2 | Mixed | Cyclomatic Complexity: VirtualCsvSource.isOrderedUniqueIndex (cyclomatic 22) |
| src/Deedle/Series.fs | 7.2 | Mixed | Cognitive Complexity: Series`2.FormatStrings (cognitive 27) |
| src/Deedle/FrameExtensions.fs | 7.2 | Mixed | God Classes: TooManyMethods: FrameExtensions |
How the grades work
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.
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.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository β a backup job that nothing shows was ever restored from proves nothing about restores β or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment β run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 38 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked β 38 dimensions across the health lenses
- 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, 189 of 265 do; the remainder are repo-wide signals β a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- 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.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | β deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | β deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | β deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | β deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | β deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 Β· 0.31.0 | β deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 Β· 0.69.3 | β deterministic |
Run transparency β what happened this run
- D8 Code Coverage β 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. 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. You can widen what we reach: add the `coverlet.collector` package to the test projects to enable coverage (or commit the Cobertura/OpenCover/lcov report your CI produces).
- D10 Test Quality β measured, with a gap in what it reached β We measured this, but not all of it. What we did not reach is a gap on our side β a collector, parser or image we have not built yet β so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 54 test(s) behind this row are the ones the C# collector could read, and this repository also carries at least 39 test source file(s) (.fs) that it cannot: it parses C# syntax and matches C# test attributes, so a vitest/jest/JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite β their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
- D14 License Compliance β not measured this run β We could not measure this here. That is a gap on our side β a collector, parser or image we have not built yet β and it is neither a defect in this repository nor evidence that the check would have passed. Not scored β this repository's projects are MSBuild/NuGet projects, whose package licenses are exactly what this dimension reads, but no license could be resolved for them (the .NET license collector did not run, or restore failed). A gap in the analysis run, NOT a finding that the repository's licenses are compliant.
- D15 Churn × Complexity Hotspots β measured, with a gap in what it reached β We measured this, but not all of it. What we did not reach is a gap on our side β a collector, parser or image we have not built yet β so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A hotspot's complexity is meant to be the worst body its churn actually touched. For src/Deedle/Frame.fs that could not be established β the complexity reader for the file reports no body extents, or the history carries no per-line attribution β so the row quotes the file's worst body, which the counted changes may never have touched. The churn count is unaffected.
- D17 Explicit Debt β measured, with a gap in what it reached β We measured this, but not all of it. What we did not reach is a gap on our side β a collector, parser or image we have not built yet β so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Cannot open project 'src/Deedle/Deedle.fsproj' because the file extension '.fsproj' is not associated with a language.
- D17 Explicit Debt β measured, with a gap in what it reached β We measured this, but not all of it. What we did not reach is a gap on our side β a collector, parser or image we have not built yet β so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 6 deducted marker(s) and the 2.0/KLoC density on this row were taken over this repository's .NET projects ALONE: .fs (26,904 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.
- D21 Naming Consistency β not measured this run β We could not measure this here. That is a gap on our side β a collector, parser or image we have not built yet β and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run β this says nothing about whether its names are consistent.
- 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.
- D24 Comment Value β not measured this run β We could not measure this here. That is a gap on our side β a collector, parser or image we have not built yet β and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- AX6 Interface segregation β not measured this run β We could not measure this here. That is a gap on our side β a collector, parser or image we have not built yet β and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach β not a finding that the repository is free of what this check looks for.
- C1 Data Protection β not measured this run β We could not measure this here. That is a gap on our side β a collector, parser or image we have not built yet β and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach β not a finding that the repository lacks personal data controls.
- C2 Access Controls β not measured this run β We could not measure this here. That is a gap on our side β a collector, parser or image we have not built yet β and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach β not a finding that the repository lacks authorization controls.
- C3 Audit Trail β not measured this run β We could not measure this here. That is a gap on our side β a collector, parser or image we have not built yet β and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach β not a finding that the repository lacks audit controls.
- C4 Data Retention β not measured this run β We could not measure this here. That is a gap on our side β a collector, parser or image we have not built yet β and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach β not a finding that the repository lacks retention controls.
- C5 Data-Subject Rights β not measured this run β We could not measure this here. That is a gap on our side β a collector, parser or image we have not built yet β and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach β not a finding that the repository lacks data-subject rights controls.
- M4 Documentation accuracy β measured, with a gap in what it reached β We measured this, but not all of it. What we did not reach is a gap on our side β a collector, parser or image we have not built yet β so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P5 DR & Backup β not measured this run β This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found β and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- S1 Web-Security Posture β not measured this run β We could not measure this here. That is a gap on our side β a collector, parser or image we have not built yet β and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach β not a finding that the repository lacks web-security controls.
- X1 Async correctness β not measured this run β We could not measure this here. That is a gap on our side β a collector, parser or image we have not built yet β and it is neither a defect in this repository nor evidence that the check would have passed. This check 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 β We could not measure this here. That is a gap on our side β a collector, parser or image we have not built yet β and it is neither a defect in this repository nor evidence that the check would have passed. This check is 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 β We could not measure this here. That is a gap on our side β a collector, parser or image we have not built yet β and it is neither a defect in this repository nor evidence that the check would have passed. This check is 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 β We could not measure this here. That is a gap on our side β a collector, parser or image we have not built yet β and it is neither a defect in this repository nor evidence that the check would have passed. This check is 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 β We could not measure this here. That is a gap on our side β a collector, parser or image we have not built yet β and it is neither a defect in this repository nor evidence that the check would have passed. This check is 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 β We could not measure this here. That is a gap on our side β a collector, parser or image we have not built yet β and it is neither a defect in this repository nor evidence that the check would have passed. This check is 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 β We could not measure this here. That is a gap on our side β a collector, parser or image we have not built yet β and it is neither a defect in this repository nor evidence that the check would have passed. This check is 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 β We could not measure this here. That is a gap on our side β a collector, parser or image we have not built yet β and it is neither a defect in this repository nor evidence that the check would have passed. This check is 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 β We could not measure this here. That is a gap on our side β a collector, parser or image we have not built yet β and it is neither a defect in this repository nor evidence that the check would have passed. This check is 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 β We could not measure this here. That is a gap on our side β a collector, parser or image we have not built yet β and it is neither a defect in this repository nor evidence that the check would have passed. This check is 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 β We could not measure this here. That is a gap on our side β a collector, parser or image we have not built yet β and it is neither a defect in this repository nor evidence that the check would have passed. This check is 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 β We could not measure this here. That is a gap on our side β a collector, parser or image we have not built yet β and it is neither a defect in this repository nor evidence that the check would have passed. This check is 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 β We could not measure this here. That is a gap on our side β a collector, parser or image we have not built yet β and it is neither a defect in this repository nor evidence that the check would have passed. This check is 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 β We could not measure this here. That is a gap on our side β a collector, parser or image we have not built yet β and it is neither a defect in this repository nor evidence that the check would have passed. This check is 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 β We could not measure this here. That is a gap on our side β a collector, parser or image we have not built yet β and it is neither a defect in this repository nor evidence that the check would have passed. This check is 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 β We could not measure this here. That is a gap on our side β a collector, parser or image we have not built yet β and it is neither a defect in this repository nor evidence that the check would have passed. This check is 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 β We could not measure this here. That is a gap on our side β a collector, parser or image we have not built yet β and it is neither a defect in this repository nor evidence that the check would have passed. This check is 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 β We could not measure this here. That is a gap on our side β a collector, parser or image we have not built yet β and it is neither a defect in this repository nor evidence that the check would have passed. This check is 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 β We could not measure this here. That is a gap on our side β a collector, parser or image we have not built yet β and it is neither a defect in this repository nor evidence that the check would have passed. This check is 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 β We could not measure this here. That is a gap on our side β a collector, parser or image we have not built yet β and it is neither a defect in this repository nor evidence that the check would have passed. This check is 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 β We could not measure this here. That is a gap on our side β a collector, parser or image we have not built yet β and it is neither a defect in this repository nor evidence that the check would have passed. This check is 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.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap β a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically β it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type β a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module β one class/IIFE β earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity β an in-process token-stream comparison over sliding windows, with type-aware normalization β so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED β its repetition is the tool's, not the team's β so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies β runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic β it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D10 Test Quality: Assertion density is structural β it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D11 Test Reliability: Flakiness is inferred from history/markers β we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- 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").
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history β a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension β pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual β undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded β it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D27 Navigability: Indirection/navigability is structural β it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns β a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) β it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases β a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension β code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS β files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- 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.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see β only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) β controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 Β· Cyclomatic Complexity
28 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was ArrayVectorBuilder.Deedle.Vectors.IVectorBuilder.Build at 73. A further 4 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being HttpHelpers.setHeaders at 43 β they are counted neither in the figure above nor in this dimension's score. 2 files carry no cyclomatic complexity row at all for this reason β every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: src/Deedle/FSharp.Data/CommonRuntime/StructuralInference.fs (StructuralInference.inferPrimitiveType at 17), src/Deedle.Parquet/VirtualParquetSource.fs (ParquetColumnSource.columnKind at 16). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 28 bodies over 15 down to 15 or less in Cyclomatic Complexity β start with ArrayVectorBuilder.Deedle.Vectors.IVectorBuilder.Build (cyclomatic 73), Implementation.batchesToFrame (cyclomatic 66), Implementation.columnToArrowArray (cyclomatic 52). β This score is capped by its worst body, so a finding fixed alone moves it by almost nothing β the next one down takes its place. Refactoring these 28 together lifts Cyclomatic Complexity from 6.3 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 Β· Cognitive Complexity
45 method(s) exceeded the cognitive complexity threshold of 15; the worst was Implementation.batchesToFrame at 284.
What to do
- Bring the 2 bodies over 120 down to 120 or less in Cognitive Complexity β start with Implementation.batchesToFrame (cognitive 284), ArrayVectorBuilder.Deedle.Vectors.IVectorBuilder.Build (cognitive 157). β This score is capped by its worst body, so a finding fixed alone moves it by almost nothing β the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 4.9 to about 5.8/10, projected with the scoring formula itself and assuming each lands exactly at 120; a cleaner split scores higher.
D3 Β· God Classes
17 god class(es) detected.
What to do
- Resolve the 12 FileTooLong finding(s) in God Classes β start with Frame.fs, Common.fs, FrameModule.fs. β One of this dimension's main actionable groups (12 warning-level).
- Resolve the 5 TooManyMethods finding(s) in God Classes β start with Frame.fs, Series.fs, FrameExtensions.fs. β One of this dimension's main actionable groups (5 warning-level).
D4 Β· Code Duplication
45 duplicated block group(s) detected.
What to do
- Resolve the 5 Duplicated block (7 lines × 2) finding(s) in Code Duplication β start with Arrow.fs, Finance.fs, FrameModule.fs. β One of this dimension's main actionable groups (5 warning-level).
- Resolve the 5 Duplicated block (5 lines × 2) finding(s) in Code Duplication β start with LinearAlgebra.fs, Frame.fs, Stats.fs. β One of this dimension's main actionable groups (5 warning-level).
- Resolve the 3 Duplicated block (9 lines × 2) finding(s) in Code Duplication β start with Http.fs, Stats.fs, Series.fs. β One of this dimension's main actionable groups (3 warning-level).
D5 Β· Coupling
1 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D6 Β· Cohesion (LCOM4)
1 of 16 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) β start with LinearIndex.fs. β One of this dimension's main actionable groups (1 warning-level).
D10 Β· Test Quality
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 54 tests. Measured on the C# suite only β at least 39 test source file(s) (.fs) went unread, so its test quality is unmeasured and is not in these counts.
D11 Β· Test Reliability
0 flaky across 1 measured tier(s). unit: measured (0 flaky).
D12 Β· Dependency Hygiene
66 outdated, 0 vulnerable, 1 deprecated packages.
What to do
- Resolve the 1 Deprecated finding(s) in Dependency Hygiene. β One of this dimension's main actionable groups (1 warning-level).
D13 Β· Secret Scanning
Secret scan ran and found no leaked secrets.
D15 Β· Churn × Complexity Hotspots
Top hotspots: src/Deedle/Frame.fs (3×26=78)
What to do
- Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots β start with Frame.fs. β One of this dimension's main actionable groups (1 warning-level).
D16 Β· Bus Factor
9 source file(s) have their living knowledge concentrated in one author (β₯90% of recent, decayed contribution). The largest is src/Deedle/FrameModule.fs. Counted over 46 of the 60 production source files in this repository: 8 are under the ~2,400-byte size floor this dimension measures over, and the remaining 6 have no attributable history left to measure.
D17 Β· Explicit Debt
6 deducted debt markers + unmeasured dead symbols across 0 LoC in the .NET projects (2.0/KLoC) β score 6.0. Dead code not measured: the solution did not load cleanly, so the reference search was skipped. Measured on the .NET source only: .fs (100% of production source) was not read, and carries at least 0 uncounted task marker(s) in 0 file(s).
What to do
- Resolve the 5 FileScopedPragmaDisable finding(s) in Explicit Debt β start with ArrowTests.cs, ExcelReaderTests.cs, Frame.cs. β One of this dimension's main actionable groups (5 issue-level).
- Resolve the 1 CommentedOutCode finding(s) in Explicit Debt β start with Series.cs. β One of this dimension's main actionable groups (1 warning-level).
D19 Β· Documentation Quality
1 of 1 documentation facets pass in full. 3 document(s) read across 1 unit(s).
D27 Β· Navigability
91 % of calls cross a namespace and 5 % go through an interface, but 100 % of collaborators are co-located β so a call's collaborators sit together and tracing stays easy. Baseline: small β navigation cost is tolerated.
D28 Β· Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 Β· Static Analysis (SAST)
16 finding(s): 0 critical, 16 high, 0 medium, 0 low. 10 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` β one pinning decision is charged once, not once per lens. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) β start with REDACTED (3). β One of this dimension's main actionable groups (3 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) β start with REDACTED. β One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) β all 10 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. β One of this dimension's main actionable groups (10 issue-level, 0 of them charged here).
D30 Β· Dependency Vulnerabilities
No known-vulnerable dependencies in any ecosystem this repository declares.
D34 Β· Knowledge Freshness
28 of 52 significant source file(s) are orphaned β their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/Deedle/FSharp.Data/Net/Http.fs. Counted over 52 of the 60 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 25 Orphaned file finding(s) in Knowledge Freshness β start with VirtualIndex.fs, ArrayVector.fs, CsvRuntime.fs. β One of this dimension's main actionable groups (25 recommendation-level).
- Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness β start with Http.fs, VirtualVector.fs, VirtualFrame.fs. β One of this dimension's main actionable groups (3 recommendation-level).
- Resolve the 1 Concentrated knowledge decay finding(s) in Knowledge Freshness. β One of this dimension's main actionable groups (1 recommendation-level).
D35 Β· Change Coupling
No strong hidden change-coupling between production files.
D36 Β· Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. β One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing β start with REDACTED. β One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. β One of this dimension's main actionable groups (1 warning-level).
D44 Β· Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 17 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.
Frontend & cross-cutting dimensions
AX10 Β· Code composition
AX3 Β· Project dependency cycles
AX4 Β· Dependency direction
GD1 Β· Unfinished & placeholder code
M1 Β· Documentation (README)
What to do
- Add a build/run (quick start) section to the root README β the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 Β· Architecture documentation
- 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 structure
M4 Β· Documentation accuracy
P1 Β· CI/CD gates
P3 Β· Security & performance tooling
- No static application security testing detected. For this repository's stack, add `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) as a CI step. What was searched, so you can tell an absence from a miss: the 3 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen β if that is your case the row is wrong, and saying so is more useful than adding a second scanner. β REDACTED:4
- `paket.dependencies` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices β including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. β paket.dependencies:3
What to do
- Add a SAST step to CI running what this repository's stack ships: `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) β so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 Β· Deployment & Rollback
- The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` β with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. β What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy β all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P6 Β· Release Hygiene
PF1 Β· Benchmark discipline
PF3 Β· Async & latency hygiene
X27 Β· Collection changed while being enumerated
X28 Β· Index access outside its own emptiness guard
Reference β by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 65% | Adequate | Acceptable, with room to improve. |
| Architecture | 56% | Adequate β gated by AX10 | Capped at Fair by a Critical contributor β resolve it before relying on this lens. |
| Maturity | 60% | Adequate β gated by M2 | Capped at Fair by a Critical contributor β resolve it before relying on this lens. |
| Readiness | 56% | Adequate β gated by P3 | Capped at Fair by a Critical contributor β resolve it before relying on this lens. |
| Security | 59% | Checked 4 of 10 | Capped at Fair by a Critical contributor β resolve it before relying on this lens. |
| Performance | 97% | Exemplary | Strongest area. |
Not evidenced β 4 control(s) we could not find positive evidence for
- C3 Audit Trail β Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository β because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C4 Data Retention β Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository β because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C5 Data-Subject Rights β Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository β because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- P5 DR & Backup β not evidenced β repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included β 71 check(s) not relevant to this codebase
- AC1 Text alternatives β No web markup found β accessibility is not applicable to this repository.
- AC2 Forms & labels β No web markup found β accessibility is not applicable to this repository.
- AC3 Page structure β No web markup found β accessibility is not applicable to this repository.
- AC4 Keyboard semantics β No web markup found β accessibility is not applicable to this repository.
- AC5 ARIA correctness β No web markup found β accessibility is not applicable to this repository.
- AC6 Visual & motion safety β No web markup found β accessibility is not applicable to this repository.
- AX1 Captive dependencies β Not applicable: this repository's F# imports no dependency-injection container and defines no container of its own β nothing that both registers and resolves bindings, and nothing that names two lifetimes β so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons β No container singleton was found, so there is no shared instance for concurrent requests to race on. No F# function in this code takes an ASP.NET Core or Suave HttpContext (a Giraffe, Saturn, Falco, Oxpecker or Suave handler) and no F# class is an ASP.NET Core controller, so no request handler shares module state between request threads.
- AX5 Architecture & structure β not assessed β architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation β not assessed β interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion β not applicable β not a vertical-slice architecture
- AX8 Test isolation β no test/production split to check
- 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.
- 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.
- D14 License Compliance β Package licences not resolved for an MSBuild/NuGet repository
- D18 Solution Shape β D18 scores the shape of a C#/VB .NET solution, but this repository's production source is mostly .fs, which the C#/VB workspace does not load β the projects that loaded are an immaterial minority, so solution shape was not assessed for this repository. Not scored β this is a gap in the analyzer's reach, not a verdict about this repository.
- D20 ADR Quality β N/A β ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency β Naming consistency is measured on C# and TypeScript only; F#, html not measured.
- D22 Internal API Consistency β No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling β single shared-core project β no cross-context coupling to assess
- D24 Comment Value β D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .fs source were not judged.
- D25 ADR Conformance β no ADRs to check
- D26 Project Cohesion β This repository is one project, `Deedle.CSharp.Tests` (0 LoC, 13 public types across 1 namespaces), within the size bounds. Not scored: a single unit of this size gives project cohesion nothing to grade.
- 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.
- D37 Vulnerability-disclosure Policy β No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement β No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement β No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement β No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D43 Malicious Dependencies β Not scored β no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a 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 β no coverage collector is wired up
- DM1 Domain Modelling β applicable but not scored (2 of 3 signals for this style β below the bar we score at): 41 value object(s); 2 domain event(s); its domain events are published by services or handlers β no domain entity raises one
- 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 β reported, not scored β this repository's C# declares no analysable method bodies (a constants, record or DTO assembly), and this score is a density of unfinished work per method, which has no denominator here. The file-level signals below were still collected and are shown in full
- P12 CI test-gate honesty β Reported, not scored β and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P2 Observability β This repository's F# source (7 module(s), 60 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service β it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- P7 Outbound HTTP resilience β not measured β the application kind could not be determined for this repo
- P8 Schema migrations β no EF Core usage detected
- P9 Domain vs controller coverage β coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here β Test coverage (D8) says why
- PF2 Allocation hygiene β Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- S1 Web-Security Posture β Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository β because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- X1 Async correctness β not 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 β not applicable β the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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 β not applicable β the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped β 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.
- 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
- X9 Subsumed condition operand β Advisory β this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A β Findings (grouped)
Critical β 20 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- FileScopedPragmaDisable tests/Deedle.CSharp.Tests/ArrowTests.cs:1
- FileScopedPragmaDisable tests/Deedle.CSharp.Tests/ExcelReaderTests.cs:1
- FileScopedPragmaDisable tests/Deedle.CSharp.Tests/Frame.cs:1
- FileScopedPragmaDisable tests/Deedle.CSharp.Tests/ParquetTests.cs:1
- FileScopedPragmaDisable tests/Deedle.CSharp.Tests/Series.cs:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious β 142 finding(s)
- FileTooLong: Deedle/Frame.fs src/Deedle/Frame.fs
- FileTooLong: Common/Common.fs src/Deedle/Common/Common.fs
- FileTooLong: Deedle/FrameModule.fs src/Deedle/FrameModule.fs
- FileTooLong: Net/Http.fs src/Deedle/FSharp.Data/Net/Http.fs
- FileTooLong: Deedle/Series.fs src/Deedle/Series.fs
- FileTooLong: Deedle/SeriesModule.fs src/Deedle/SeriesModule.fs
- FileTooLong: Deedle/FrameUtils.fs src/Deedle/FrameUtils.fs
- FileTooLong: Deedle/FrameExtensions.fs src/Deedle/FrameExtensions.fs
- FileTooLong: Deedle/Stats.fs src/Deedle/Stats.fs
- FileTooLong: Deedle.Arrow/Arrow.fs src/Deedle.Arrow/Arrow.fs
- FileTooLong: Vectors/VectorHelpers.fs src/Deedle/Vectors/VectorHelpers.fs
- FileTooLong: Deedle/VirtualLookupRange.fs src/Deedle/VirtualLookupRange.fs
- TooManyMethods: Frame`2 src/Deedle/Frame.fs:83
- TooManyMethods: Series`2 src/Deedle/Series.fs:58
- TooManyMethods: FrameExtensions src/Deedle/FrameExtensions.fs:849
- TooManyMethods: Stats src/Deedle/Stats.fs:417
- TooManyMethods: SeriesExtensions src/Deedle/SeriesExtensions.fs:213
- Duplicated block (7 lines × 2) src/Deedle.Arrow/Arrow.fs:219
- Duplicated block (7 lines × 2) src/Deedle.MathNetNumerics/Finance.fs:18
- Duplicated block (7 lines × 2) src/Deedle/FrameModule.fs:2025
- Duplicated block (7 lines × 2) src/Deedle/FrameUtils.fs:534
- Duplicated block (7 lines × 2) src/Deedle/Vectors/ArrayVector.fs:337
- Duplicated block (5 lines × 2) src/Deedle.MathNetNumerics/LinearAlgebra.fs:257
- Duplicated block (5 lines × 2) src/Deedle/Frame.fs:1377
- Duplicated block (5 lines × 2) src/Deedle/Stats.fs:948
- Duplicated block (5 lines × 2) src/Deedle.Arrow/Arrow.fs:580
- Duplicated block (5 lines × 2) src/Deedle/VirtualLookupRange.fs:316
- Duplicated block (9 lines × 2) src/Deedle/FSharp.Data/Net/Http.fs:1720
- Duplicated block (9 lines × 2) src/Deedle/Stats.fs:882
- Duplicated block (9 lines × 2) src/Deedle/Series.fs:846
- Duplicated block (8 lines × 2) src/Deedle/Common/Common.fs:1185
- Duplicated block (8 lines × 2) src/Deedle/FrameModule.fs:1201
- Duplicated block (8 lines × 2) src/Deedle/FrameModule.fs:1191
- Duplicated block (6 lines × 2) src/Deedle/DelayedSeries.fs:50
- Duplicated block (6 lines × 2) src/Deedle/Indices/LinearIndex.fs:150
- Duplicated block (6 lines × 2) src/Deedle/FrameExtensions.fs:114
- Duplicated block (5 lines × 3) src/Deedle.MathNetNumerics/Finance.fs:18
- Duplicated block (5 lines × 3) src/Deedle.MathNetNumerics/Stats.fs:218
- Duplicated block (5 lines × 3) src/Deedle/FrameExtensions.fs:1573
- Duplicated block (16 lines × 2) src/Deedle.Arrow/Arrow.fs:413
- Duplicated block (16 lines × 2) src/Deedle/FrameModule.fs:1881
- Duplicated block (15 lines × 2) src/Deedle/VirtualFrame.fs:265
- Duplicated block (15 lines × 2) src/Deedle/VirtualLookupRange.fs:213
- Duplicated block (5 lines × 10) src/Deedle.Arrow/Arrow.fs:52
- Duplicated block (5 lines × 10) src/Deedle.Parquet/Parquet.fs:52
- ArrayVectorBuilder.Deedle.Vectors.IVectorBuilder.Build (cyclomatic 73) src/Deedle/Vectors/ArrayVector.fs:97
- Implementation.batchesToFrame (cyclomatic 66) src/Deedle.Arrow/Arrow.fs:239
- Implementation.columnToArrowArray (cyclomatic 52) src/Deedle.Arrow/Arrow.fs:48
- Implementation.columnToDataColumn (cyclomatic 42) src/Deedle.Parquet/Parquet.fs:49
- Implementation.readColumn (cyclomatic 41) src/Deedle.Parquet/Parquet.fs:138
- FrameUtilsModule.readCsv (cyclomatic 40) src/Deedle/FrameUtils.fs:613
- Implementation.arrowArrayToVector (cyclomatic 33) src/Deedle.Arrow/Arrow.fs:147
- LookupRangeExecutor.remapLookupRangeAfterStep (cyclomatic 33) src/Deedle/VirtualLookupRange.fs:383
- VirtualVectorBuilder.Deedle.Vectors.IVectorBuilder.Build (cyclomatic 28) src/Deedle/Vectors/VirtualVector.fs:582
- Ranges.lookup (cyclomatic 27) src/Deedle/Common/Ranges.fs:248
- Frame`2.FormatStrings (cyclomatic 26) src/Deedle/Frame.fs:1345
- LookupRangeExecutor.intersect (cyclomatic 25) src/Deedle/VirtualLookupRange.fs:525
- Seq.alignOrdered (cyclomatic 25) src/Deedle/Common/Common.fs:1136
- FrameUtilsModule.writeCsv (cyclomatic 23) src/Deedle/FrameUtils.fs:297
- Ranges.restrictRanges (cyclomatic 23) src/Deedle/Common/Ranges.fs:174
- CookieHandling.getAllCookiesFromHeader (cyclomatic 23) src/Deedle/FSharp.Data/Net/Http.fs:1387
- Http.InnerRequest (cyclomatic 23) src/Deedle/FSharp.Data/Net/Http.fs:1505
- VirtualCsvSource.isOrderedUniqueIndex (cyclomatic 22) src/Deedle/VirtualCsvSource.fs:276
- LookupRangeExecutor.remapLookupRangeAfterAddresses (cyclomatic 21) src/Deedle/VirtualLookupRange.fs:446
- Reflection.expandVector (cyclomatic 20) src/Deedle/FrameUtils.fs:152
- Ranges.flattenRanges (cyclomatic 18) src/Deedle/DelayedSeries.fs:48
- Stats.interpolateLinearWith (cyclomatic 17) src/Deedle/Stats.fs:974
- JoinHelpers.createJoinTransformation (cyclomatic 17) src/Deedle/JoinHelpers.fs:68
- VirtualCsvSource.createConcatenatedFrame (cyclomatic 16) src/Deedle/VirtualCsvSource.fs:434
- IndexUtilsModule.binarySearch (cyclomatic 16) src/Deedle/VirtualFrame.fs:21
- FrameUtilsModule.jsonFormatValue (cyclomatic 16) src/Deedle/FrameUtils.fs:457
- FrameUtilsModule.writeJson (cyclomatic 16) src/Deedle/FrameUtils.fs:503
- LinearIndexBuilder.Deedle.Indices.IIndexBuilder.Resample (cyclomatic 16) src/Deedle/Indices/LinearIndex.fs:355
- Deprecated: Microsoft.Testing.Platform.MSBuild
- Hotspot: src/Deedle/Frame.fs src/Deedle/Frame.fs:1345
- CommentedOutCode tests/Deedle.CSharp.Tests/Series.cs:235
- Implementation.batchesToFrame (cognitive 284) src/Deedle.Arrow/Arrow.fs:239
- ArrayVectorBuilder.Deedle.Vectors.IVectorBuilder.Build (cognitive 157) src/Deedle/Vectors/ArrayVector.fs:97
- Implementation.readColumn (cognitive 104) src/Deedle.Parquet/Parquet.fs:138
- Implementation.columnToArrowArray (cognitive 78) src/Deedle.Arrow/Arrow.fs:48
- LookupRangeExecutor.remapLookupRangeAfterStep (cognitive 74) src/Deedle/VirtualLookupRange.fs:383
- VirtualCsvSource.isOrderedUniqueIndex (cognitive 71) src/Deedle/VirtualCsvSource.fs:276
- Ranges.lookup (cognitive 60) src/Deedle/Common/Ranges.fs:248
- FrameUtilsModule.readCsv (cognitive 57) src/Deedle/FrameUtils.fs:613
- Seq.alignOrdered (cognitive 49) src/Deedle/Common/Common.fs:1136
- Implementation.arrowArrayToVector (cognitive 45) src/Deedle.Arrow/Arrow.fs:147
- Frame`2.FormatStrings (cognitive 44) src/Deedle/Frame.fs:1345
- LinearIndexBuilder.Deedle.Indices.IIndexBuilder.Resample (cognitive 44) src/Deedle/Indices/LinearIndex.fs:355
- LookupRangeExecutor.intersect (cognitive 42) src/Deedle/VirtualLookupRange.fs:525
- Implementation.columnToDataColumn (cognitive 42) src/Deedle.Parquet/Parquet.fs:49
- Reflection.expandVector (cognitive 40) src/Deedle/FrameUtils.fs:152
- Ranges.restrictRanges (cognitive 39) src/Deedle/Common/Ranges.fs:174
- FrameUtilsModule.writeJson (cognitive 37) src/Deedle/FrameUtils.fs:503
- CookieHandling.getAllCookiesFromHeader (cognitive 37) src/Deedle/FSharp.Data/Net/Http.fs:1387
- Pluralizer.adjustCase (cognitive 35) src/Deedle/FSharp.Data/CommonRuntime/Pluralizer.fs:190
- FrameModule.MeltBy (cognitive 33) src/Deedle/FrameModule.fs:806
- LookupRangeExecutor.remapLookupRangeAfterAddresses (cognitive 30) src/Deedle/VirtualLookupRange.fs:446
- Seq.alignAllOrderedFew (cognitive 30) src/Deedle/Common/Common.fs:1247
- Implementation.rowGroupsToFrame (cognitive 29) src/Deedle.Parquet/Parquet.fs:296
- VirtualVectorBuilder.Deedle.Vectors.IVectorBuilder.Build (cognitive 28) src/Deedle/Vectors/VirtualVector.fs:582
- Extraction.extractColData (cognitive 28) src/Deedle.MicrosoftML/DataView.fs:80
- IndexUtilsModule.binarySearch (cognitive 27) src/Deedle/VirtualFrame.fs:21
- Series`2.FormatStrings (cognitive 27) src/Deedle/Series.fs:1268
- FrameUtilsModule.jsonFormatValue (cognitive 25) src/Deedle/FrameUtils.fs:457
- VirtualVectorSource.fillMissing (cognitive 25) src/Deedle/Vectors/VirtualVector.fs:449
- FrameUtilsModule.writeCsv (cognitive 24) src/Deedle/FrameUtils.fs:297
- VectorHelpers.createTypedRowCreator (cognitive 23) src/Deedle/Vectors/VectorHelpers.fs:575
- CsvFile`1..ctor (cognitive 23) src/Deedle/FSharp.Data/Csv/CsvRuntime.fs:245
- FrameModule.Unstack (cognitive 20) src/Deedle/FrameModule.fs:941
- Seq.startAndEnd (cognitive 20) src/Deedle/Common/Common.fs:808
- Reflection.expandDictionary (cognitive 19) src/Deedle/FrameUtils.fs:117
- Http.InnerRequest (cognitive 19) src/Deedle/FSharp.Data/Net/Http.fs:1505
- Stats.interpolateLinearWith (cognitive 18) src/Deedle/Stats.fs:974
- JoinHelpers.createJoinTransformation (cognitive 18) src/Deedle/JoinHelpers.fs:68
- CsvParsing.splitCsvLine (cognitive 17) src/Deedle/VirtualCsvSource.fs:14
- CycleInference.tryDetectOptional (cognitive 17) src/Deedle/VirtualLookupRange.fs:148
- LookupRangeExecutor.clipLookupRange (cognitive 17) src/Deedle/VirtualLookupRange.fs:351
- FrameUtilsModule.expandVectors (cognitive 17) src/Deedle/FrameUtils.fs:764
- Frame`2.Zip (cognitive 17) src/Deedle/Frame.fs:209
- Virtual.MaterializeFloatBatches (cognitive 16) src/Deedle/VirtualFrame.fs:383
- Stats.quantile (cognitive 16) src/Deedle/Stats.fs:816
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (23β24 lines × 2) src/Deedle.Parquet/Parquet.fs:394
- Duplicated block (19 lines × 2) src/Deedle/Stats.fs:608
- Duplicated block (15β16 lines × 2) src/Deedle/Vectors/VirtualVector.fs:326
- Duplicated block (14β15 lines × 3) src/Deedle/FrameModule.fs:2032
- Duplicated block (12β15 lines × 2) src/Deedle/FrameUtils.fs:332
- Duplicated block (14β15 lines × 2) src/Deedle/VirtualFrame.fs:281
- Duplicated block (13β14 lines × 6) src/Deedle/FSharp.Data/Net/Http.fs:1624
- Duplicated block (13 lines × 2) src/Deedle.MathNetNumerics/Finance.fs:89
- Duplicated block (11 lines × 2) src/Deedle/FrameModule.fs:2094
- Duplicated block (4β9 lines × 10) src/Deedle.Parquet/Parquet.fs:152
- Duplicated block (12β13 lines × 2) src/Deedle.Parquet/Parquet.fs:369
- Duplicated block (10 lines × 2) src/Deedle/Vectors/VectorHelpers.fs:70
- Duplicated block (8β9 lines × 2) src/Deedle/VirtualLookupRange.fs:149
- Duplicated block (7 lines × 3) src/Deedle.ExcelReader/ExcelReader.fs:36
- Duplicated block (11 lines × 10) src/Deedle.Parquet/Parquet.fs:152
- Duplicated block (6 lines × 9) src/Deedle.Arrow/Arrow.fs:52
- Duplicated block (6 lines × 3) src/Deedle.MathNetNumerics/Finance.fs:20
- Low cohesion: LinearIndexBuilder (LCOM4 12) src/Deedle/Indices/LinearIndex.fs:245
Minor β 37 finding(s)
- Orphaned file src/Deedle/Indices/VirtualIndex.fs:1
- Orphaned file src/Deedle/Vectors/ArrayVector.fs:1
- Orphaned file src/Deedle/FSharp.Data/Csv/CsvRuntime.fs:1
- Orphaned file src/Deedle/Common/Ranges.fs:1
- Orphaned file src/Deedle/FSharp.Data/CommonRuntime/StructuralInference.fs:1
- Orphaned file src/Deedle/Vectors/Vector.fs:1
- Orphaned file src/Deedle/FSharp.Data/CommonRuntime/Pluralizer.fs:1
- Orphaned file src/Deedle.MathNetNumerics/LinearRegression.fs:1
- Orphaned file src/Deedle/Indices/MultiKey.fs:1
- Orphaned file src/Deedle/FSharp.Data/CommonRuntime/IO.fs:1
- Orphaned file src/Deedle/Common/Address.fs:1
- Orphaned file src/Deedle.MathNetNumerics/Stats.fs:1
- Orphaned file src/Deedle/FSharp.Data/CommonRuntime/StructuralTypes.fs:1
- Orphaned file src/Deedle.MathNetNumerics/LinearAlgebra.fs:1
- Orphaned file src/Deedle/Vectors/VectorExtensions.fs:1
- Orphaned file src/Deedle/FSharp.Data/CommonRuntime/TextRuntime.fs:1
- Orphaned file src/Deedle/JoinHelpers.fs:1
- Orphaned file src/Deedle/FSharp.Data/Csv/CsvFile.fs:1
- Orphaned file src/Deedle/FSharp.Data/CommonRuntime/NameUtils.fs:1
- Orphaned file src/Deedle/FSharp.Data/CommonRuntime/Caching.fs:1
- Orphaned file src/Deedle/Common/Deque.fs:1
- Orphaned file src/Deedle/Common/BinomialHeap.fs:1
- Orphaned file src/Deedle.MathNetNumerics/Extensions.fs:1
- Orphaned file src/Deedle/FSharp.Data/Csv/CsvExtensions.fs:1
- Orphaned file src/Deedle.MathNetNumerics/PCA.fs:1
- Most significant orphaned file src/Deedle/FSharp.Data/Net/Http.fs:1
- Most significant orphaned file src/Deedle/Vectors/VirtualVector.fs:1
- Most significant orphaned file src/Deedle/VirtualFrame.fs:1
- Concentrated knowledge decay
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No SAST REDACTED:4
- No dependency-update automation paket.dependencies:3
- No release approval gate
Minor β 66 finding(s)
- Outdated: FSharp.Core
- Outdated: MathNet.Numerics.FSharp
- Outdated: System.Diagnostics.DiagnosticSource
- Outdated: Azure.Core
- Outdated: Azure.Monitor.OpenTelemetry.Exporter
- Outdated: FsCheck
- Outdated: FsUnit
- Outdated: Microsoft.ApplicationInsights
- Outdated: Microsoft.Bcl.AsyncInterfaces
- Outdated: Microsoft.CodeCoverage
- Outdated: Microsoft.Extensions.Configuration
- Outdated: Microsoft.Extensions.Configuration.Abstractions
- Outdated: Microsoft.Extensions.Configuration.Binder
- Outdated: Microsoft.Extensions.Configuration.EnvironmentVariables
- Outdated: Microsoft.Extensions.DependencyInjection
- Outdated: Microsoft.Extensions.DependencyInjection.Abstractions
- Outdated: Microsoft.Extensions.DependencyModel
- Outdated: Microsoft.Extensions.Diagnostics.Abstractions
- Outdated: Microsoft.Extensions.FileProviders.Abstractions
- Outdated: Microsoft.Extensions.Hosting.Abstractions
- Outdated: Microsoft.Extensions.Logging
- Outdated: Microsoft.Extensions.Logging.Abstractions
- Outdated: Microsoft.Extensions.Logging.Configuration
- Outdated: Microsoft.Extensions.Options
- Outdated: Microsoft.Extensions.Options.ConfigurationExtensions
Appendix B β Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 Β· Secrets (history) | gitleaks | β | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-aff7c30f4aa4425ab7c112b8b4c413b4/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 Β· Secrets (history) | gitleaks | β | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-aff7c30f4aa4425ab7c112b8b4c413b4/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 Β· Static Analysis (SAST) | semgrep | β | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 16 | artifacts/raw/semgrep.json |
| D30 Β· Dependency Vulnerabilities | dotnet | β | dotnet list Deedle.sln package --vulnerable --include-transitive --format json | 0 | artifacts/raw/dotnet-vulnerable.json |
| D31 Β· IaC & Container Security | trivy | β | 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 | β |
| D37 Β· Vulnerability-disclosure Policy | disclosure | β | 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 Confinement | runtime-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 Confinement | runtime-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 Enforcement | runtime-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 Dependencies | none (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 | β |