Executive summary
fsprojects/Rezoom.SQL falls short of our standard for production because we found no logging, tracing or health checks in the code and no automated security scanning of the code, its secrets or its dependencies. It scores 53 out of 100 and is rated Adequate, and two of its five critical findings are security problems in the build pipeline.
Production Readiness, at 40, is the weakest lens and counts most in the score. The best first step is encrypting the sensitive stored data and keeping its keys in a vault, worth about 10 points. Logging through a logging library would lift Production Readiness itself, worth about 5 points. Raising Production Readiness to 70 would lift the score to about 61.
Two pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Pinning each tool to an exact version would close this risk. The three sets of compiler warnings switched off in projects need turning back on in the build file.
The product code is 32,905 lines, about €54,000 to rebuild.
If Production Readiness rose from 40 to 70, the lowest score rated Strong, the score would rise from 53 to about 61.
Fixed since the last survey: 10 findings
- Code Coverage · Coverage not measured — no coverage collector is wired up
- Churn × Complexity Hotspots · Hotspot: src/Rezoom.SQL.Compiler/Postgres.fs src/Rezoom.SQL.Compiler/Postgres.fs
- Churn × Complexity Hotspots · Hotspot: src/Rezoom.SQL.Compiler/TypeSystem.fs src/Rezoom.SQL.Compiler/TypeSystem.fs
- Churn × Complexity Hotspots · Hotspot: src/Rezoom.SQL.Compiler/AST.fs src/Rezoom.SQL.Compiler/AST.fs
- Churn × Complexity Hotspots · Hotspot: src/Rezoom.SQL.Mapping/CommandBatch.fs src/Rezoom.SQL.Mapping/CommandBatch.fs
- Churn × Complexity Hotspots · Hotspot: src/Rezoom.SQL.Compiler/DefaultExprTranslator.fs src/Rezoom.SQL.Compiler/DefaultExprTranslator.fs
- Churn × Complexity Hotspots · Hotspot: src/Rezoom.SQL.Compiler/TSQL.Expression.fs src/Rezoom.SQL.Compiler/TSQL.Expression.fs
- Churn × Complexity Hotspots · Hotspot: src/Rezoom.SQL.Compiler/ASTMapping.fs src/Rezoom.SQL.Compiler/ASTMapping.fs
- One transaction, one aggregate · One operation mutates 2 aggregates: DemoSetup.SetUpDemoUser demos/FileSystem/FileSystem.EFVersion/DemoSetup.cs
- One transaction, one aggregate · One operation mutates 3 aggregates: DemoSetup.SetUpDemoGroup demos/FileSystem/FileSystem.EFVersion/DemoSetup.cs
Rebuild cost: about €54,000 · Estimate
| Cost to rebuild | €18,000 to €91,000, for 301 to 955 hours of work, about 0.4 person-years for one engineer |
|---|---|
| Difficulty of the problem | High, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 53. 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: 32,905 lines of product code |
| Comment lines | The estimate prices 32,798 lines. Comment lines count towards the size of 32,905 lines but aren't priced as work. |
| 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 — bounded-context dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 ProviderImplementation.ProvidedTypes | 2 Rezoom.SQL.Migrations | 3 TypeProviderUser.Postgres.UserTypes | 4 TypeProviderUser.TSQL.UserTypes | 5 Rezoom.SQL.Compiler.Utilities | 6 Rezoom.SQL.Mapping.FreezeDry | 7 Rezoom.SQL.Compiler.InferredTypes | 8 Rezoom.SQL.Mapping | 9 Rezoom.SQL | 10 Rezoom.SQL.CommandDataExtensions | 11 Rezoom.SQL.Compiler.BackendUtilities | 12 Rezoom.SQL.Compiler.Config | 13 Rezoom.SQL.Mapping.CodeGeneration | 14 Rezoom.SQL.Asynchronous | 15 Rezoom.SQL.Compiler | 16 TypeProviderUser.Postgres.Helpers | 17 TypeProviderUser.SQLite.Helpers | 18 TypeProviderUser.TSQL.Helpers | 19 Rezoom.SQL.Compiler.AggregateChecker | 20 Rezoom.SQL.Compiler.ComplexModelOps | 21 Rezoom.SQL.Compiler.CoreParser | 22 Rezoom.SQL.Compiler.DefaultFunctions | 23 Rezoom.SQL.Compiler.FunctionDeclarations | 24 Rezoom.SQL.Compiler.ModelOps | 25 Rezoom.SQL.Compiler.Parser | 26 Rezoom.SQL.Compiler.Postgres.PostgresFunctions | 27 Rezoom.SQL.Compiler.ReadWriteReferences | 28 Rezoom.SQL.Compiler.SQLite.SQLiteFunctions | 29 Rezoom.SQL.Compiler.SourceInfoModule | 30 Rezoom.SQL.Compiler.TSQL.TSQLFunctions | 31 Rezoom.SQL.Compiler.Translators | 32 Rezoom.SQL.Compiler.Translators.DefaultSQLTypeString | 33 Rezoom.SQL.Compiler.TypeInferenceExtensions | 34 Rezoom.SQL.Compiler.UserModelLoader | 35 Rezoom.SQL.Provider | 36 Rezoom.SQL.Provider.InterfaceImpls | 37 Rezoom.SQL.Compiler.Postgres | 38 Rezoom.SQL.Compiler.SQLite | 39 Rezoom.SQL.Compiler.TSQL | 40 Rezoom.SQL.Provider.TypeGeneration |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 ProviderImplementation.ProvidedTypes | ||||||||||||||||||||||||||||||||||||||||
| 2 Rezoom.SQL.Migrations | ||||||||||||||||||||||||||||||||||||||||
| 3 TypeProviderUser.Postgres.UserTypes | ||||||||||||||||||||||||||||||||||||||||
| 4 TypeProviderUser.TSQL.UserTypes | ||||||||||||||||||||||||||||||||||||||||
| 5 Rezoom.SQL.Compiler.Utilities | 3 | |||||||||||||||||||||||||||||||||||||||
| 6 Rezoom.SQL.Mapping.FreezeDry | 3 | |||||||||||||||||||||||||||||||||||||||
| 7 Rezoom.SQL.Compiler.InferredTypes | 3 | 29 | ||||||||||||||||||||||||||||||||||||||
| 8 Rezoom.SQL.Mapping | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 9 Rezoom.SQL | 38 | |||||||||||||||||||||||||||||||||||||||
| 10 Rezoom.SQL.CommandDataExtensions | 1 | |||||||||||||||||||||||||||||||||||||||
| 11 Rezoom.SQL.Compiler.BackendUtilities | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 12 Rezoom.SQL.Compiler.Config | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 13 Rezoom.SQL.Mapping.CodeGeneration | 22 | |||||||||||||||||||||||||||||||||||||||
| 14 Rezoom.SQL.Asynchronous | 2 | |||||||||||||||||||||||||||||||||||||||
| 15 Rezoom.SQL.Compiler | 1 | 4 | 18 | 11 | 1 | |||||||||||||||||||||||||||||||||||
| 16 TypeProviderUser.Postgres.Helpers | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 17 TypeProviderUser.SQLite.Helpers | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 18 TypeProviderUser.TSQL.Helpers | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 19 Rezoom.SQL.Compiler.AggregateChecker | 2 | 12 | ||||||||||||||||||||||||||||||||||||||
| 20 Rezoom.SQL.Compiler.ComplexModelOps | 11 | |||||||||||||||||||||||||||||||||||||||
| 21 Rezoom.SQL.Compiler.CoreParser | 3 | |||||||||||||||||||||||||||||||||||||||
| 22 Rezoom.SQL.Compiler.DefaultFunctions | 2 | |||||||||||||||||||||||||||||||||||||||
| 23 Rezoom.SQL.Compiler.FunctionDeclarations | 18 | |||||||||||||||||||||||||||||||||||||||
| 24 Rezoom.SQL.Compiler.ModelOps | 13 | |||||||||||||||||||||||||||||||||||||||
| 25 Rezoom.SQL.Compiler.Parser | 1 | |||||||||||||||||||||||||||||||||||||||
| 26 Rezoom.SQL.Compiler.Postgres.PostgresFunctions | 2 | |||||||||||||||||||||||||||||||||||||||
| 27 Rezoom.SQL.Compiler.ReadWriteReferences | 45 | |||||||||||||||||||||||||||||||||||||||
| 28 Rezoom.SQL.Compiler.SQLite.SQLiteFunctions | 2 | |||||||||||||||||||||||||||||||||||||||
| 29 Rezoom.SQL.Compiler.SourceInfoModule | 2 | |||||||||||||||||||||||||||||||||||||||
| 30 Rezoom.SQL.Compiler.TSQL.TSQLFunctions | 3 | |||||||||||||||||||||||||||||||||||||||
| 31 Rezoom.SQL.Compiler.Translators | 6 | 129 | ||||||||||||||||||||||||||||||||||||||
| 32 Rezoom.SQL.Compiler.Translators.DefaultSQLTypeString | 1 | |||||||||||||||||||||||||||||||||||||||
| 33 Rezoom.SQL.Compiler.TypeInferenceExtensions | 2 | 12 | ||||||||||||||||||||||||||||||||||||||
| 34 Rezoom.SQL.Compiler.UserModelLoader | 2 | 1 | 7 | |||||||||||||||||||||||||||||||||||||
| 35 Rezoom.SQL.Provider | 1 | 3 | ||||||||||||||||||||||||||||||||||||||
| 36 Rezoom.SQL.Provider.InterfaceImpls | 2 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 37 Rezoom.SQL.Compiler.Postgres | 5 | 1 | 22 | 6 | ||||||||||||||||||||||||||||||||||||
| 38 Rezoom.SQL.Compiler.SQLite | 5 | 1 | 16 | 6 | ||||||||||||||||||||||||||||||||||||
| 39 Rezoom.SQL.Compiler.TSQL | 5 | 1 | 43 | 7 | ||||||||||||||||||||||||||||||||||||
| 40 Rezoom.SQL.Provider.TypeGeneration | 3 | 1 | 1 | 9 | 1 |
5→15 Rezoom.SQL.Compiler.Utilities uses Rezoom.SQL.Compiler part of a loop✕
- Connections
- 3 pairs of types, where a type in Rezoom.SQL.Compiler.Utilities uses a type in Rezoom.SQL.Compiler.
- The types involved
Rezoom.SQL.Compiler.Utilities.Utilities→Rezoom.SQL.Compiler.SourceInfoRezoom.SQL.Compiler.Utilities.Utilities→Rezoom.SQL.Compiler.SourcePositionRezoom.SQL.Compiler.Utilities.Utilities→Rezoom.SQL.Compiler.WithSource`1
- Direction
- Rezoom.SQL.Compiler.Utilities uses Rezoom.SQL.Compiler, so a change to Rezoom.SQL.Compiler can break Rezoom.SQL.Compiler.Utilities, while a change to Rezoom.SQL.Compiler.Utilities can't break Rezoom.SQL.Compiler.
- 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→8 Rezoom.SQL.Mapping.FreezeDry uses Rezoom.SQL.Mapping part of a loop✕
- Connections
- 3 pairs of types, where a type in Rezoom.SQL.Mapping.FreezeDry uses a type in Rezoom.SQL.Mapping.
- The types involved
Rezoom.SQL.Mapping.FreezeDry.FreezeDriedUserPrimitiveType→Rezoom.SQL.Mapping.UserPrimitiveTypeRezoom.SQL.Mapping.FreezeDry.FreezeDriedUserTypeLibrary→Rezoom.SQL.Mapping.UserTypeLibraryRezoom.SQL.Mapping.FreezeDry.FreezeDry→Rezoom.SQL.Mapping.UserTypeLibrary
- Direction
- Rezoom.SQL.Mapping.FreezeDry uses Rezoom.SQL.Mapping, so a change to Rezoom.SQL.Mapping can break Rezoom.SQL.Mapping.FreezeDry, while a change to Rezoom.SQL.Mapping.FreezeDry can't break Rezoom.SQL.Mapping.
- 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.
7→5 Rezoom.SQL.Compiler.InferredTypes uses Rezoom.SQL.Compiler.Utilities✕
- Connections
- 3 pairs of types, where a type in Rezoom.SQL.Compiler.InferredTypes uses a type in Rezoom.SQL.Compiler.Utilities.
- The types involved
Rezoom.SQL.Compiler.InferredTypes.InferredFromClause→Rezoom.SQL.Compiler.Utilities.NameResolution`1Rezoom.SQL.Compiler.InferredTypes.InferredSelectScope→Rezoom.SQL.Compiler.Utilities.NameResolution`1Rezoom.SQL.Compiler.InferredTypes.InferredTypes→Rezoom.SQL.Compiler.Utilities.NameResolution`1
- Direction
- Rezoom.SQL.Compiler.InferredTypes uses Rezoom.SQL.Compiler.Utilities, so a change to Rezoom.SQL.Compiler.Utilities can break Rezoom.SQL.Compiler.InferredTypes, while a change to Rezoom.SQL.Compiler.InferredTypes can't break Rezoom.SQL.Compiler.Utilities.
- Position
- Below the diagonal: Rezoom.SQL.Compiler.InferredTypes uses a module listed above it, which is the healthy direction.
7→15 Rezoom.SQL.Compiler.InferredTypes uses Rezoom.SQL.Compiler part of a loop✕
- Connections
- 29 pairs of types, where a type in Rezoom.SQL.Compiler.InferredTypes uses a type in Rezoom.SQL.Compiler. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Rezoom.SQL.Compiler.InferredTypes.CoreInferredType→Rezoom.SQL.Compiler.CoreColumnTypeRezoom.SQL.Compiler.InferredTypes.ITypeInferenceContext→Rezoom.SQL.Compiler.BindParameterRezoom.SQL.Compiler.InferredTypes.ITypeInferenceContext→Rezoom.SQL.Compiler.ColumnTypeRezoom.SQL.Compiler.InferredTypes.ITypeInferenceContext→Rezoom.SQL.Compiler.SourceInfoRezoom.SQL.Compiler.InferredTypes.InferredFromClause→Rezoom.SQL.Compiler.ColumnName`1Rezoom.SQL.Compiler.InferredTypes.InferredFromClause→Rezoom.SQL.Compiler.NameRezoom.SQL.Compiler.InferredTypes.InferredFromClause→Rezoom.SQL.Compiler.ObjectInfo`1Rezoom.SQL.Compiler.InferredTypes.InferredFromClause→Rezoom.SQL.Compiler.ObjectName`1Rezoom.SQL.Compiler.InferredTypes.InferredSelectScope→Rezoom.SQL.Compiler.ColumnName`1Rezoom.SQL.Compiler.InferredTypes.InferredSelectScope→Rezoom.SQL.Compiler.ModelRezoom.SQL.Compiler.InferredTypes.InferredSelectScope→Rezoom.SQL.Compiler.NameRezoom.SQL.Compiler.InferredTypes.InferredSelectScope→Rezoom.SQL.Compiler.ObjectInfo`1Rezoom.SQL.Compiler.InferredTypes.InferredSelectScope→Rezoom.SQL.Compiler.ObjectName`1Rezoom.SQL.Compiler.InferredTypes.InferredSelectScope→Rezoom.SQL.Compiler.QueryExprInfo`1Rezoom.SQL.Compiler.InferredTypes.InferredSelectScope→Rezoom.SQL.Compiler.SchemaRezoom.SQL.Compiler.InferredTypes.InferredType→Rezoom.SQL.Compiler.ColumnTypeRezoom.SQL.Compiler.InferredTypes.InferredType→Rezoom.SQL.Compiler.CoreColumnTypeRezoom.SQL.Compiler.InferredTypes.InferredType→Rezoom.SQL.Compiler.LiteralRezoom.SQL.Compiler.InferredTypes.InferredType→Rezoom.SQL.Compiler.TypeNameRezoom.SQL.Compiler.InferredTypes.InferredTypes→Rezoom.SQL.Compiler.ASTMapping`4Rezoom.SQL.Compiler.InferredTypes.InferredTypes→Rezoom.SQL.Compiler.ColumnExprInfo`1Rezoom.SQL.Compiler.InferredTypes.InferredTypes→Rezoom.SQL.Compiler.ColumnTypeRezoom.SQL.Compiler.InferredTypes.InferredTypes→Rezoom.SQL.Compiler.ExprInfo`1Rezoom.SQL.Compiler.InferredTypes.InferredTypes→Rezoom.SQL.Compiler.NameRezoom.SQL.Compiler.InferredTypes.InferredTypes→Rezoom.SQL.Compiler.ObjectInfo`1
- Direction
- Rezoom.SQL.Compiler.InferredTypes uses Rezoom.SQL.Compiler, so a change to Rezoom.SQL.Compiler can break Rezoom.SQL.Compiler.InferredTypes, while a change to Rezoom.SQL.Compiler.InferredTypes can't break Rezoom.SQL.Compiler.
- 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→6 Rezoom.SQL.Mapping uses Rezoom.SQL.Mapping.FreezeDry✕
- Connections
- 1 pair of types, where a type in Rezoom.SQL.Mapping uses a type in Rezoom.SQL.Mapping.FreezeDry.
- The types involved
Rezoom.SQL.Mapping.CommandData→Rezoom.SQL.Mapping.FreezeDry.FreezeDriedUserTypeLibrary
- Direction
- Rezoom.SQL.Mapping uses Rezoom.SQL.Mapping.FreezeDry, so a change to Rezoom.SQL.Mapping.FreezeDry can break Rezoom.SQL.Mapping, while a change to Rezoom.SQL.Mapping can't break Rezoom.SQL.Mapping.FreezeDry.
- Position
- Below the diagonal: Rezoom.SQL.Mapping uses a module listed above it, which is the healthy direction.
8→9 Rezoom.SQL.Mapping uses Rezoom.SQL part of a loop✕
- Connections
- 1 pair of types, where a type in Rezoom.SQL.Mapping uses a type in Rezoom.SQL.
- The types involved
Rezoom.SQL.Mapping.CommandBatchBuilder→Rezoom.SQL.Command
- Direction
- Rezoom.SQL.Mapping uses Rezoom.SQL, so a change to Rezoom.SQL can break Rezoom.SQL.Mapping, while a change to Rezoom.SQL.Mapping can't break Rezoom.SQL.
- 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.
9→8 Rezoom.SQL uses Rezoom.SQL.Mapping✕
- Connections
- 38 pairs of types, where a type in Rezoom.SQL uses a type in Rezoom.SQL.Mapping. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Rezoom.SQL.Command→Rezoom.SQL.Mapping.BackendRezoom.SQL.Command→Rezoom.SQL.Mapping.CommandDataRezoom.SQL.Command→Rezoom.SQL.Mapping.CommandFragmentRezoom.SQL.Command→Rezoom.SQL.Mapping.CommandParameterRezoom.SQL.Command→Rezoom.SQL.Mapping.ResultSetProcessorRezoom.SQL.Command0→Rezoom.SQL.Mapping.CommandDataRezoom.SQL.Command0→Rezoom.SQL.Mapping.CommandParameterRezoom.SQL.Command0→Rezoom.SQL.Mapping.ResultSetProcessor`1Rezoom.SQL.Command1`1→Rezoom.SQL.Mapping.CommandDataRezoom.SQL.Command1`1→Rezoom.SQL.Mapping.CommandParameterRezoom.SQL.Command1`1→Rezoom.SQL.Mapping.ResultSetProcessor`1Rezoom.SQL.Command2`2→Rezoom.SQL.Mapping.CommandDataRezoom.SQL.Command2`2→Rezoom.SQL.Mapping.CommandParameterRezoom.SQL.Command2`2→Rezoom.SQL.Mapping.ResultSetProcessor`1Rezoom.SQL.Command3`3→Rezoom.SQL.Mapping.CommandDataRezoom.SQL.Command3`3→Rezoom.SQL.Mapping.CommandParameterRezoom.SQL.Command3`3→Rezoom.SQL.Mapping.ResultSetProcessor`1Rezoom.SQL.Command4`4→Rezoom.SQL.Mapping.CommandDataRezoom.SQL.Command4`4→Rezoom.SQL.Mapping.CommandParameterRezoom.SQL.Command4`4→Rezoom.SQL.Mapping.ResultSetProcessor`1Rezoom.SQL.CommandConstructor→Rezoom.SQL.Mapping.CommandDataRezoom.SQL.CommandConstructor→Rezoom.SQL.Mapping.CommandParameterRezoom.SQL.Command`1→Rezoom.SQL.Mapping.CommandDataRezoom.SQL.Command`1→Rezoom.SQL.Mapping.CommandParameterRezoom.SQL.Command`1→Rezoom.SQL.Mapping.ResultSetProcessor
- Direction
- Rezoom.SQL uses Rezoom.SQL.Mapping, so a change to Rezoom.SQL.Mapping can break Rezoom.SQL, while a change to Rezoom.SQL can't break Rezoom.SQL.Mapping.
- Position
- Below the diagonal: Rezoom.SQL uses a module listed above it, which is the healthy direction.
10→8 Rezoom.SQL.CommandDataExtensions uses Rezoom.SQL.Mapping✕
- Connections
- 1 pair of types, where a type in Rezoom.SQL.CommandDataExtensions uses a type in Rezoom.SQL.Mapping.
- The types involved
Rezoom.SQL.CommandDataExtensions.CommandDataExtensions→Rezoom.SQL.Mapping.EntityReader`1
- Direction
- Rezoom.SQL.CommandDataExtensions uses Rezoom.SQL.Mapping, so a change to Rezoom.SQL.Mapping can break Rezoom.SQL.CommandDataExtensions, while a change to Rezoom.SQL.CommandDataExtensions can't break Rezoom.SQL.Mapping.
- Position
- Below the diagonal: Rezoom.SQL.CommandDataExtensions uses a module listed above it, which is the healthy direction.
11→2 Rezoom.SQL.Compiler.BackendUtilities uses Rezoom.SQL.Migrations✕
- Connections
- 2 pairs of types, where a type in Rezoom.SQL.Compiler.BackendUtilities uses a type in Rezoom.SQL.Migrations.
- The types involved
Rezoom.SQL.Compiler.BackendUtilities.DefaultMigrationBackend→Rezoom.SQL.Migrations.IMigrationBackendRezoom.SQL.Compiler.BackendUtilities.DefaultMigrationBackend→Rezoom.SQL.Migrations.Migration`1
- Direction
- Rezoom.SQL.Compiler.BackendUtilities uses Rezoom.SQL.Migrations, so a change to Rezoom.SQL.Migrations can break Rezoom.SQL.Compiler.BackendUtilities, while a change to Rezoom.SQL.Compiler.BackendUtilities can't break Rezoom.SQL.Migrations.
- Position
- Below the diagonal: Rezoom.SQL.Compiler.BackendUtilities uses a module listed above it, which is the healthy direction.
11→8 Rezoom.SQL.Compiler.BackendUtilities uses Rezoom.SQL.Mapping✕
- Connections
- 2 pairs of types, where a type in Rezoom.SQL.Compiler.BackendUtilities uses a type in Rezoom.SQL.Mapping.
- The types involved
Rezoom.SQL.Compiler.BackendUtilities.BackendUtilities→Rezoom.SQL.Mapping.CommandFragmentRezoom.SQL.Compiler.BackendUtilities.DefaultMigrationBackend→Rezoom.SQL.Mapping.ConnectionInfo
- Direction
- Rezoom.SQL.Compiler.BackendUtilities uses Rezoom.SQL.Mapping, so a change to Rezoom.SQL.Mapping can break Rezoom.SQL.Compiler.BackendUtilities, while a change to Rezoom.SQL.Compiler.BackendUtilities can't break Rezoom.SQL.Mapping.
- Position
- Below the diagonal: Rezoom.SQL.Compiler.BackendUtilities uses a module listed above it, which is the healthy direction.
12→8 Rezoom.SQL.Compiler.Config uses Rezoom.SQL.Mapping✕
- Connections
- 1 pair of types, where a type in Rezoom.SQL.Compiler.Config uses a type in Rezoom.SQL.Mapping.
- The types involved
Rezoom.SQL.Compiler.Config.Config→Rezoom.SQL.Mapping.Backend
- Direction
- Rezoom.SQL.Compiler.Config uses Rezoom.SQL.Mapping, so a change to Rezoom.SQL.Mapping can break Rezoom.SQL.Compiler.Config, while a change to Rezoom.SQL.Compiler.Config can't break Rezoom.SQL.Mapping.
- Position
- Below the diagonal: Rezoom.SQL.Compiler.Config uses a module listed above it, which is the healthy direction.
12→15 Rezoom.SQL.Compiler.Config uses Rezoom.SQL.Compiler part of a loop✕
- Connections
- 1 pair of types, where a type in Rezoom.SQL.Compiler.Config uses a type in Rezoom.SQL.Compiler.
- The types involved
Rezoom.SQL.Compiler.Config.Config→Rezoom.SQL.Compiler.IBackend
- Direction
- Rezoom.SQL.Compiler.Config uses Rezoom.SQL.Compiler, so a change to Rezoom.SQL.Compiler can break Rezoom.SQL.Compiler.Config, while a change to Rezoom.SQL.Compiler.Config can't break Rezoom.SQL.Compiler.
- 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.
13→8 Rezoom.SQL.Mapping.CodeGeneration uses Rezoom.SQL.Mapping✕
- Connections
- 22 pairs of types, where a type in Rezoom.SQL.Mapping.CodeGeneration uses a type in Rezoom.SQL.Mapping.
- The types involved
Rezoom.SQL.Mapping.CodeGeneration.CompositeColumnGenerator→Rezoom.SQL.Mapping.ColumnRezoom.SQL.Mapping.CodeGeneration.CompositeColumnGenerator→Rezoom.SQL.Mapping.CompositeRezoom.SQL.Mapping.CodeGeneration.InternalReaderTemplateCacheForEnt`2→Rezoom.SQL.Mapping.EntityReaderTemplate`1Rezoom.SQL.Mapping.CodeGeneration.InternalReaderTemplateCacheForEnt`2→Rezoom.SQL.Mapping.UserTypeLibraryRezoom.SQL.Mapping.CodeGeneration.InternalReaderTemplateCache`1→Rezoom.SQL.Mapping.EntityReaderTemplate`1Rezoom.SQL.Mapping.CodeGeneration.InternalReaderTemplateCache`1→Rezoom.SQL.Mapping.UserTypeLibraryRezoom.SQL.Mapping.CodeGeneration.KeyColumns→Rezoom.SQL.Mapping.ColumnRezoom.SQL.Mapping.CodeGeneration.ManyColumnGenerator→Rezoom.SQL.Mapping.ColumnRezoom.SQL.Mapping.CodeGeneration.ManyColumnGenerator→Rezoom.SQL.Mapping.ElementBlueprintRezoom.SQL.Mapping.CodeGeneration.ManyColumnGeneratorCode`1→Rezoom.SQL.Mapping.EntityReader`1Rezoom.SQL.Mapping.CodeGeneration.ManyEntityColumnGenerator→Rezoom.SQL.Mapping.ColumnRezoom.SQL.Mapping.CodeGeneration.ManyEntityColumnGenerator→Rezoom.SQL.Mapping.ElementBlueprintRezoom.SQL.Mapping.CodeGeneration.PrimitiveColumnGenerator→Rezoom.SQL.Mapping.ColumnRezoom.SQL.Mapping.CodeGeneration.PrimitiveColumnGenerator→Rezoom.SQL.Mapping.PrimitiveRezoom.SQL.Mapping.CodeGeneration.ReaderTemplate`1→Rezoom.SQL.Mapping.EntityReaderTemplate`1Rezoom.SQL.Mapping.CodeGeneration.ReaderTemplate`1→Rezoom.SQL.Mapping.UserTypeLibraryRezoom.SQL.Mapping.CodeGeneration.StaticEntityReaderTemplate→Rezoom.SQL.Mapping.BlueprintRezoom.SQL.Mapping.CodeGeneration.StaticEntityReaderTemplate→Rezoom.SQL.Mapping.ColumnRezoom.SQL.Mapping.CodeGeneration.StaticEntityReaderTemplate→Rezoom.SQL.Mapping.CompositeRezoom.SQL.Mapping.CodeGeneration.StaticEntityReaderTemplate→Rezoom.SQL.Mapping.ElementBlueprintRezoom.SQL.Mapping.CodeGeneration.StaticEntityReaderTemplate→Rezoom.SQL.Mapping.PrimitiveRezoom.SQL.Mapping.CodeGeneration.StaticEntityReaderTemplate→Rezoom.SQL.Mapping.UserTypeLibrary
- Direction
- Rezoom.SQL.Mapping.CodeGeneration uses Rezoom.SQL.Mapping, so a change to Rezoom.SQL.Mapping can break Rezoom.SQL.Mapping.CodeGeneration, while a change to Rezoom.SQL.Mapping.CodeGeneration can't break Rezoom.SQL.Mapping.
- Position
- Below the diagonal: Rezoom.SQL.Mapping.CodeGeneration uses a module listed above it, which is the healthy direction.
14→9 Rezoom.SQL.Asynchronous uses Rezoom.SQL✕
- Connections
- 2 pairs of types, where a type in Rezoom.SQL.Asynchronous uses a type in Rezoom.SQL.
- The types involved
Rezoom.SQL.Asynchronous.Extensions→Rezoom.SQL.Command`1Rezoom.SQL.Asynchronous.Extensions→Rezoom.SQL.ConnectionContext
- Direction
- Rezoom.SQL.Asynchronous uses Rezoom.SQL, so a change to Rezoom.SQL can break Rezoom.SQL.Asynchronous, while a change to Rezoom.SQL.Asynchronous can't break Rezoom.SQL.
- Position
- Below the diagonal: Rezoom.SQL.Asynchronous uses a module listed above it, which is the healthy direction.
15→2 Rezoom.SQL.Compiler uses Rezoom.SQL.Migrations✕
- Connections
- 1 pair of types, where a type in Rezoom.SQL.Compiler uses a type in Rezoom.SQL.Migrations.
- The types involved
Rezoom.SQL.Compiler.UserModel→Rezoom.SQL.Migrations.MigrationTree`1
- Direction
- Rezoom.SQL.Compiler uses Rezoom.SQL.Migrations, so a change to Rezoom.SQL.Migrations can break Rezoom.SQL.Compiler, while a change to Rezoom.SQL.Compiler can't break Rezoom.SQL.Migrations.
- Position
- Below the diagonal: Rezoom.SQL.Compiler uses a module listed above it, which is the healthy direction.
15→5 Rezoom.SQL.Compiler uses Rezoom.SQL.Compiler.Utilities✕
- Connections
- 4 pairs of types, where a type in Rezoom.SQL.Compiler uses a type in Rezoom.SQL.Compiler.Utilities.
- The types involved
Rezoom.SQL.Compiler.CoreColumnType→Rezoom.SQL.Compiler.Utilities.Result`2Rezoom.SQL.Compiler.QueryExprInfo`1→Rezoom.SQL.Compiler.Utilities.NameResolution`1Rezoom.SQL.Compiler.QueryExprInfo`1→Rezoom.SQL.Compiler.Utilities.Result`2Rezoom.SQL.Compiler.TypeInferenceContext→Rezoom.SQL.Compiler.Utilities.Result`2
- Direction
- Rezoom.SQL.Compiler uses Rezoom.SQL.Compiler.Utilities, so a change to Rezoom.SQL.Compiler.Utilities can break Rezoom.SQL.Compiler, while a change to Rezoom.SQL.Compiler can't break Rezoom.SQL.Compiler.Utilities.
- Position
- Below the diagonal: Rezoom.SQL.Compiler uses a module listed above it, which is the healthy direction.
15→7 Rezoom.SQL.Compiler uses Rezoom.SQL.Compiler.InferredTypes✕
- Connections
- 18 pairs of types, where a type in Rezoom.SQL.Compiler uses a type in Rezoom.SQL.Compiler.InferredTypes.
- The types involved
Rezoom.SQL.Compiler.CommandEffectBuilder→Rezoom.SQL.Compiler.InferredTypes.InferredTypeRezoom.SQL.Compiler.ExprTypeChecker→Rezoom.SQL.Compiler.InferredTypes.ITypeInferenceContextRezoom.SQL.Compiler.ExprTypeChecker→Rezoom.SQL.Compiler.InferredTypes.InferredSelectScopeRezoom.SQL.Compiler.ExprTypeChecker→Rezoom.SQL.Compiler.InferredTypes.InferredTypeRezoom.SQL.Compiler.IQueryTypeChecker→Rezoom.SQL.Compiler.InferredTypes.InferredTypeRezoom.SQL.Compiler.ModelChange→Rezoom.SQL.Compiler.InferredTypes.ITypeInferenceContextRezoom.SQL.Compiler.ModelChange→Rezoom.SQL.Compiler.InferredTypes.InferredTypeRezoom.SQL.Compiler.NullabilityVariable→Rezoom.SQL.Compiler.InferredTypes.InferredNullableRezoom.SQL.Compiler.SelfQueryShape→Rezoom.SQL.Compiler.InferredTypes.InferredTypeRezoom.SQL.Compiler.TypeChecker→Rezoom.SQL.Compiler.InferredTypes.ITypeInferenceContextRezoom.SQL.Compiler.TypeChecker→Rezoom.SQL.Compiler.InferredTypes.InferredFromClauseRezoom.SQL.Compiler.TypeChecker→Rezoom.SQL.Compiler.InferredTypes.InferredSelectScopeRezoom.SQL.Compiler.TypeChecker→Rezoom.SQL.Compiler.InferredTypes.InferredTypeRezoom.SQL.Compiler.TypeInferenceContext→Rezoom.SQL.Compiler.InferredTypes.CoreInferredTypeRezoom.SQL.Compiler.TypeInferenceContext→Rezoom.SQL.Compiler.InferredTypes.ITypeInferenceContextRezoom.SQL.Compiler.TypeInferenceContext→Rezoom.SQL.Compiler.InferredTypes.InferredNullableRezoom.SQL.Compiler.TypeInferenceContext→Rezoom.SQL.Compiler.InferredTypes.InferredTypeRezoom.SQL.Compiler.TypeInferenceVariable→Rezoom.SQL.Compiler.InferredTypes.CoreInferredType
- Direction
- Rezoom.SQL.Compiler uses Rezoom.SQL.Compiler.InferredTypes, so a change to Rezoom.SQL.Compiler.InferredTypes can break Rezoom.SQL.Compiler, while a change to Rezoom.SQL.Compiler can't break Rezoom.SQL.Compiler.InferredTypes.
- Position
- Below the diagonal: Rezoom.SQL.Compiler uses a module listed above it, which is the healthy direction.
15→8 Rezoom.SQL.Compiler uses Rezoom.SQL.Mapping✕
- Connections
- 11 pairs of types, where a type in Rezoom.SQL.Compiler uses a type in Rezoom.SQL.Mapping.
- The types involved
Rezoom.SQL.Compiler.BackendBase→Rezoom.SQL.Mapping.CommandFragmentRezoom.SQL.Compiler.CommandEffect→Rezoom.SQL.Mapping.UserTypeLibraryRezoom.SQL.Compiler.CoreColumnType→Rezoom.SQL.Mapping.UserPrimitiveTypeRezoom.SQL.Compiler.DefaultBackend→Rezoom.SQL.Mapping.CommandFragmentRezoom.SQL.Compiler.IBackend→Rezoom.SQL.Mapping.CommandFragmentRezoom.SQL.Compiler.ParameterTransform→Rezoom.SQL.Mapping.XDbTypeRezoom.SQL.Compiler.QueryExprInfo`1→Rezoom.SQL.Mapping.UserRowTypeRezoom.SQL.Compiler.RowType→Rezoom.SQL.Mapping.UserRowTypeRezoom.SQL.Compiler.TypeName→Rezoom.SQL.Mapping.UserPrimitiveTypeRezoom.SQL.Compiler.UserModel→Rezoom.SQL.Mapping.UserTypeLibraryRezoom.SQL.Compiler.UserTypeResolutionPass→Rezoom.SQL.Mapping.UserTypeLibrary
- Direction
- Rezoom.SQL.Compiler uses Rezoom.SQL.Mapping, so a change to Rezoom.SQL.Mapping can break Rezoom.SQL.Compiler, while a change to Rezoom.SQL.Compiler can't break Rezoom.SQL.Mapping.
- Position
- Below the diagonal: Rezoom.SQL.Compiler uses a module listed above it, which is the healthy direction.
15→12 Rezoom.SQL.Compiler uses Rezoom.SQL.Compiler.Config✕
- Connections
- 1 pair of types, where a type in Rezoom.SQL.Compiler uses a type in Rezoom.SQL.Compiler.Config.
- The types involved
Rezoom.SQL.Compiler.UserModel→Rezoom.SQL.Compiler.Config.Config
- Direction
- Rezoom.SQL.Compiler uses Rezoom.SQL.Compiler.Config, so a change to Rezoom.SQL.Compiler.Config can break Rezoom.SQL.Compiler, while a change to Rezoom.SQL.Compiler can't break Rezoom.SQL.Compiler.Config.
- Position
- Below the diagonal: Rezoom.SQL.Compiler uses a module listed above it, which is the healthy direction.
16→8 TypeProviderUser.Postgres.Helpers uses Rezoom.SQL.Mapping✕
- Connections
- 1 pair of types, where a type in TypeProviderUser.Postgres.Helpers uses a type in Rezoom.SQL.Mapping.
- The types involved
TypeProviderUser.Postgres.Helpers.Helpers→Rezoom.SQL.Mapping.ConnectionProvider
- Direction
- TypeProviderUser.Postgres.Helpers uses Rezoom.SQL.Mapping, so a change to Rezoom.SQL.Mapping can break TypeProviderUser.Postgres.Helpers, while a change to TypeProviderUser.Postgres.Helpers can't break Rezoom.SQL.Mapping.
- Position
- Below the diagonal: TypeProviderUser.Postgres.Helpers uses a module listed above it, which is the healthy direction.
16→9 TypeProviderUser.Postgres.Helpers uses Rezoom.SQL✕
- Connections
- 1 pair of types, where a type in TypeProviderUser.Postgres.Helpers uses a type in Rezoom.SQL.
- The types involved
TypeProviderUser.Postgres.Helpers.Helpers→Rezoom.SQL.Command`1
- Direction
- TypeProviderUser.Postgres.Helpers uses Rezoom.SQL, so a change to Rezoom.SQL can break TypeProviderUser.Postgres.Helpers, while a change to TypeProviderUser.Postgres.Helpers can't break Rezoom.SQL.
- Position
- Below the diagonal: TypeProviderUser.Postgres.Helpers uses a module listed above it, which is the healthy direction.
17→8 TypeProviderUser.SQLite.Helpers uses Rezoom.SQL.Mapping✕
- Connections
- 1 pair of types, where a type in TypeProviderUser.SQLite.Helpers uses a type in Rezoom.SQL.Mapping.
- The types involved
TypeProviderUser.SQLite.Helpers.Helpers→Rezoom.SQL.Mapping.ConnectionProvider
- Direction
- TypeProviderUser.SQLite.Helpers uses Rezoom.SQL.Mapping, so a change to Rezoom.SQL.Mapping can break TypeProviderUser.SQLite.Helpers, while a change to TypeProviderUser.SQLite.Helpers can't break Rezoom.SQL.Mapping.
- Position
- Below the diagonal: TypeProviderUser.SQLite.Helpers uses a module listed above it, which is the healthy direction.
17→9 TypeProviderUser.SQLite.Helpers uses Rezoom.SQL✕
- Connections
- 1 pair of types, where a type in TypeProviderUser.SQLite.Helpers uses a type in Rezoom.SQL.
- The types involved
TypeProviderUser.SQLite.Helpers.Helpers→Rezoom.SQL.Command`1
- Direction
- TypeProviderUser.SQLite.Helpers uses Rezoom.SQL, so a change to Rezoom.SQL can break TypeProviderUser.SQLite.Helpers, while a change to TypeProviderUser.SQLite.Helpers can't break Rezoom.SQL.
- Position
- Below the diagonal: TypeProviderUser.SQLite.Helpers uses a module listed above it, which is the healthy direction.
18→8 TypeProviderUser.TSQL.Helpers uses Rezoom.SQL.Mapping✕
- Connections
- 1 pair of types, where a type in TypeProviderUser.TSQL.Helpers uses a type in Rezoom.SQL.Mapping.
- The types involved
TypeProviderUser.TSQL.Helpers.Helpers→Rezoom.SQL.Mapping.ConnectionProvider
- Direction
- TypeProviderUser.TSQL.Helpers uses Rezoom.SQL.Mapping, so a change to Rezoom.SQL.Mapping can break TypeProviderUser.TSQL.Helpers, while a change to TypeProviderUser.TSQL.Helpers can't break Rezoom.SQL.Mapping.
- Position
- Below the diagonal: TypeProviderUser.TSQL.Helpers uses a module listed above it, which is the healthy direction.
18→9 TypeProviderUser.TSQL.Helpers uses Rezoom.SQL✕
- Connections
- 1 pair of types, where a type in TypeProviderUser.TSQL.Helpers uses a type in Rezoom.SQL.
- The types involved
TypeProviderUser.TSQL.Helpers.Helpers→Rezoom.SQL.Command`1
- Direction
- TypeProviderUser.TSQL.Helpers uses Rezoom.SQL, so a change to Rezoom.SQL can break TypeProviderUser.TSQL.Helpers, while a change to TypeProviderUser.TSQL.Helpers can't break Rezoom.SQL.
- Position
- Below the diagonal: TypeProviderUser.TSQL.Helpers uses a module listed above it, which is the healthy direction.
19→7 Rezoom.SQL.Compiler.AggregateChecker uses Rezoom.SQL.Compiler.InferredTypes✕
- Connections
- 2 pairs of types, where a type in Rezoom.SQL.Compiler.AggregateChecker uses a type in Rezoom.SQL.Compiler.InferredTypes.
- The types involved
Rezoom.SQL.Compiler.AggregateChecker.AggReference→Rezoom.SQL.Compiler.InferredTypes.InferredTypeRezoom.SQL.Compiler.AggregateChecker.AggregateChecker→Rezoom.SQL.Compiler.InferredTypes.InferredType
- Direction
- Rezoom.SQL.Compiler.AggregateChecker uses Rezoom.SQL.Compiler.InferredTypes, so a change to Rezoom.SQL.Compiler.InferredTypes can break Rezoom.SQL.Compiler.AggregateChecker, while a change to Rezoom.SQL.Compiler.AggregateChecker can't break Rezoom.SQL.Compiler.InferredTypes.
- Position
- Below the diagonal: Rezoom.SQL.Compiler.AggregateChecker uses a module listed above it, which is the healthy direction.
19→15 Rezoom.SQL.Compiler.AggregateChecker uses Rezoom.SQL.Compiler✕
- Connections
- 12 pairs of types, where a type in Rezoom.SQL.Compiler.AggregateChecker uses a type in Rezoom.SQL.Compiler.
- The types involved
Rezoom.SQL.Compiler.AggregateChecker.AggReference→Rezoom.SQL.Compiler.ExprInfo`1Rezoom.SQL.Compiler.AggregateChecker.AggReference→Rezoom.SQL.Compiler.Expr`2Rezoom.SQL.Compiler.AggregateChecker.AggReference→Rezoom.SQL.Compiler.ObjectInfo`1Rezoom.SQL.Compiler.AggregateChecker.AggReference→Rezoom.SQL.Compiler.SourceInfoRezoom.SQL.Compiler.AggregateChecker.AggregateChecker→Rezoom.SQL.Compiler.CompoundExprCore`2Rezoom.SQL.Compiler.AggregateChecker.AggregateChecker→Rezoom.SQL.Compiler.CompoundTerm`2Rezoom.SQL.Compiler.AggregateChecker.AggregateChecker→Rezoom.SQL.Compiler.ExprInfo`1Rezoom.SQL.Compiler.AggregateChecker.AggregateChecker→Rezoom.SQL.Compiler.Expr`2Rezoom.SQL.Compiler.AggregateChecker.AggregateChecker→Rezoom.SQL.Compiler.ObjectInfo`1Rezoom.SQL.Compiler.AggregateChecker.AggregateChecker→Rezoom.SQL.Compiler.SelectCore`2Rezoom.SQL.Compiler.AggregateChecker.AggregateChecker→Rezoom.SQL.Compiler.SelectStmtCore`2Rezoom.SQL.Compiler.AggregateChecker.AggregateChecker→Rezoom.SQL.Compiler.WithSource`1
- Direction
- Rezoom.SQL.Compiler.AggregateChecker uses Rezoom.SQL.Compiler, so a change to Rezoom.SQL.Compiler can break Rezoom.SQL.Compiler.AggregateChecker, while a change to Rezoom.SQL.Compiler.AggregateChecker can't break Rezoom.SQL.Compiler.
- Position
- Below the diagonal: Rezoom.SQL.Compiler.AggregateChecker uses a module listed above it, which is the healthy direction.
20→15 Rezoom.SQL.Compiler.ComplexModelOps uses Rezoom.SQL.Compiler✕
- Connections
- 11 pairs of types, where a type in Rezoom.SQL.Compiler.ComplexModelOps uses a type in Rezoom.SQL.Compiler.
- The types involved
Rezoom.SQL.Compiler.ComplexModelOps.ComplexModelOps→Rezoom.SQL.Compiler.ColumnConstraint`2Rezoom.SQL.Compiler.ComplexModelOps.ComplexModelOps→Rezoom.SQL.Compiler.ColumnDef`2Rezoom.SQL.Compiler.ComplexModelOps.ComplexModelOps→Rezoom.SQL.Compiler.ColumnTypeRezoom.SQL.Compiler.ComplexModelOps.ComplexModelOps→Rezoom.SQL.Compiler.CreateTableDefinition`2Rezoom.SQL.Compiler.ComplexModelOps.ComplexModelOps→Rezoom.SQL.Compiler.Expr`2Rezoom.SQL.Compiler.ComplexModelOps.ComplexModelOps→Rezoom.SQL.Compiler.NameRezoom.SQL.Compiler.ComplexModelOps.ComplexModelOps→Rezoom.SQL.Compiler.ObjectName`1Rezoom.SQL.Compiler.ComplexModelOps.ComplexModelOps→Rezoom.SQL.Compiler.QualifiedObjectNameRezoom.SQL.Compiler.ComplexModelOps.ComplexModelOps→Rezoom.SQL.Compiler.QueryExprInfo`1Rezoom.SQL.Compiler.ComplexModelOps.ComplexModelOps→Rezoom.SQL.Compiler.TableConstraint`2Rezoom.SQL.Compiler.ComplexModelOps.ComplexModelOps→Rezoom.SQL.Compiler.WithSource`1
- Direction
- Rezoom.SQL.Compiler.ComplexModelOps uses Rezoom.SQL.Compiler, so a change to Rezoom.SQL.Compiler can break Rezoom.SQL.Compiler.ComplexModelOps, while a change to Rezoom.SQL.Compiler.ComplexModelOps can't break Rezoom.SQL.Compiler.
- Position
- Below the diagonal: Rezoom.SQL.Compiler.ComplexModelOps uses a module listed above it, which is the healthy direction.
21→15 Rezoom.SQL.Compiler.CoreParser uses Rezoom.SQL.Compiler✕
- Connections
- 3 pairs of types, where a type in Rezoom.SQL.Compiler.CoreParser uses a type in Rezoom.SQL.Compiler.
- The types involved
Rezoom.SQL.Compiler.CoreParser.CoreParser→Rezoom.SQL.Compiler.BinaryOperatorRezoom.SQL.Compiler.CoreParser.CoreParser→Rezoom.SQL.Compiler.Expr`2Rezoom.SQL.Compiler.CoreParser.CoreParser→Rezoom.SQL.Compiler.UnaryOperator
- Direction
- Rezoom.SQL.Compiler.CoreParser uses Rezoom.SQL.Compiler, so a change to Rezoom.SQL.Compiler can break Rezoom.SQL.Compiler.CoreParser, while a change to Rezoom.SQL.Compiler.CoreParser can't break Rezoom.SQL.Compiler.
- Position
- Below the diagonal: Rezoom.SQL.Compiler.CoreParser uses a module listed above it, which is the healthy direction.
22→15 Rezoom.SQL.Compiler.DefaultFunctions uses Rezoom.SQL.Compiler✕
- Connections
- 2 pairs of types, where a type in Rezoom.SQL.Compiler.DefaultFunctions uses a type in Rezoom.SQL.Compiler.
- The types involved
Rezoom.SQL.Compiler.DefaultFunctions.DefaultFunctions→Rezoom.SQL.Compiler.FunctionTypeRezoom.SQL.Compiler.DefaultFunctions.DefaultFunctions→Rezoom.SQL.Compiler.Name
- Direction
- Rezoom.SQL.Compiler.DefaultFunctions uses Rezoom.SQL.Compiler, so a change to Rezoom.SQL.Compiler can break Rezoom.SQL.Compiler.DefaultFunctions, while a change to Rezoom.SQL.Compiler.DefaultFunctions can't break Rezoom.SQL.Compiler.
- Position
- Below the diagonal: Rezoom.SQL.Compiler.DefaultFunctions uses a module listed above it, which is the healthy direction.
23→15 Rezoom.SQL.Compiler.FunctionDeclarations uses Rezoom.SQL.Compiler✕
- Connections
- 18 pairs of types, where a type in Rezoom.SQL.Compiler.FunctionDeclarations uses a type in Rezoom.SQL.Compiler.
- The types involved
Rezoom.SQL.Compiler.FunctionDeclarations.AggregateFunction→Rezoom.SQL.Compiler.AggregateTypeRezoom.SQL.Compiler.FunctionDeclarations.AggregateFunction→Rezoom.SQL.Compiler.FunctionArguments`2Rezoom.SQL.Compiler.FunctionDeclarations.AggregateFunction→Rezoom.SQL.Compiler.FunctionTermTypeRezoom.SQL.Compiler.FunctionDeclarations.AggregateFunction→Rezoom.SQL.Compiler.FunctionTypeRezoom.SQL.Compiler.FunctionDeclarations.AggregateFunction→Rezoom.SQL.Compiler.NameRezoom.SQL.Compiler.FunctionDeclarations.ErasedFunction→Rezoom.SQL.Compiler.AggregateTypeRezoom.SQL.Compiler.FunctionDeclarations.ErasedFunction→Rezoom.SQL.Compiler.FunctionArguments`2Rezoom.SQL.Compiler.FunctionDeclarations.ErasedFunction→Rezoom.SQL.Compiler.FunctionTermTypeRezoom.SQL.Compiler.FunctionDeclarations.ErasedFunction→Rezoom.SQL.Compiler.FunctionTypeRezoom.SQL.Compiler.FunctionDeclarations.ErasedFunction→Rezoom.SQL.Compiler.NameRezoom.SQL.Compiler.FunctionDeclarations.FunctionDeclarations→Rezoom.SQL.Compiler.CoreColumnTypeRezoom.SQL.Compiler.FunctionDeclarations.FunctionDeclarations→Rezoom.SQL.Compiler.FunctionTermTypeRezoom.SQL.Compiler.FunctionDeclarations.FunctionDeclarations→Rezoom.SQL.Compiler.FunctionTypeRezoom.SQL.Compiler.FunctionDeclarations.NonAggregateFunction→Rezoom.SQL.Compiler.AggregateTypeRezoom.SQL.Compiler.FunctionDeclarations.NonAggregateFunction→Rezoom.SQL.Compiler.FunctionArguments`2Rezoom.SQL.Compiler.FunctionDeclarations.NonAggregateFunction→Rezoom.SQL.Compiler.FunctionTermTypeRezoom.SQL.Compiler.FunctionDeclarations.NonAggregateFunction→Rezoom.SQL.Compiler.FunctionTypeRezoom.SQL.Compiler.FunctionDeclarations.NonAggregateFunction→Rezoom.SQL.Compiler.Name
- Direction
- Rezoom.SQL.Compiler.FunctionDeclarations uses Rezoom.SQL.Compiler, so a change to Rezoom.SQL.Compiler can break Rezoom.SQL.Compiler.FunctionDeclarations, while a change to Rezoom.SQL.Compiler.FunctionDeclarations can't break Rezoom.SQL.Compiler.
- Position
- Below the diagonal: Rezoom.SQL.Compiler.FunctionDeclarations uses a module listed above it, which is the healthy direction.
24→15 Rezoom.SQL.Compiler.ModelOps uses Rezoom.SQL.Compiler✕
- Connections
- 13 pairs of types, where a type in Rezoom.SQL.Compiler.ModelOps uses a type in Rezoom.SQL.Compiler.
- The types involved
Rezoom.SQL.Compiler.ModelOps.AddingColumn→Rezoom.SQL.Compiler.Expr`2Rezoom.SQL.Compiler.ModelOps.AddingColumn→Rezoom.SQL.Compiler.NameRezoom.SQL.Compiler.ModelOps.AddingColumn→Rezoom.SQL.Compiler.TypeNameRezoom.SQL.Compiler.ModelOps.AddingColumn→Rezoom.SQL.Compiler.WithSource`1Rezoom.SQL.Compiler.ModelOps.ModelOps→Rezoom.SQL.Compiler.CreateViewStmt`2Rezoom.SQL.Compiler.ModelOps.ModelOps→Rezoom.SQL.Compiler.Expr`2Rezoom.SQL.Compiler.ModelOps.ModelOps→Rezoom.SQL.Compiler.NameRezoom.SQL.Compiler.ModelOps.ModelOps→Rezoom.SQL.Compiler.QualifiedObjectNameRezoom.SQL.Compiler.ModelOps.ModelOps→Rezoom.SQL.Compiler.SchemaRezoom.SQL.Compiler.ModelOps.ModelOps→Rezoom.SQL.Compiler.SchemaConstraintTypeRezoom.SQL.Compiler.ModelOps.ModelOps→Rezoom.SQL.Compiler.SchemaObjectRezoom.SQL.Compiler.ModelOps.ModelOps→Rezoom.SQL.Compiler.TypeNameRezoom.SQL.Compiler.ModelOps.ModelOps→Rezoom.SQL.Compiler.WithSource`1
- Direction
- Rezoom.SQL.Compiler.ModelOps uses Rezoom.SQL.Compiler, so a change to Rezoom.SQL.Compiler can break Rezoom.SQL.Compiler.ModelOps, while a change to Rezoom.SQL.Compiler.ModelOps can't break Rezoom.SQL.Compiler.
- Position
- Below the diagonal: Rezoom.SQL.Compiler.ModelOps uses a module listed above it, which is the healthy direction.
25→15 Rezoom.SQL.Compiler.Parser uses Rezoom.SQL.Compiler✕
- Connections
- 1 pair of types, where a type in Rezoom.SQL.Compiler.Parser uses a type in Rezoom.SQL.Compiler.
- The types involved
Rezoom.SQL.Compiler.Parser.Parser→Rezoom.SQL.Compiler.TotalStmt`2
- Direction
- Rezoom.SQL.Compiler.Parser uses Rezoom.SQL.Compiler, so a change to Rezoom.SQL.Compiler can break Rezoom.SQL.Compiler.Parser, while a change to Rezoom.SQL.Compiler.Parser can't break Rezoom.SQL.Compiler.
- Position
- Below the diagonal: Rezoom.SQL.Compiler.Parser uses a module listed above it, which is the healthy direction.
26→15 Rezoom.SQL.Compiler.Postgres.PostgresFunctions uses Rezoom.SQL.Compiler✕
- Connections
- 2 pairs of types, where a type in Rezoom.SQL.Compiler.Postgres.PostgresFunctions uses a type in Rezoom.SQL.Compiler.
- The types involved
Rezoom.SQL.Compiler.Postgres.PostgresFunctions.PostgresFunctions→Rezoom.SQL.Compiler.FunctionTypeRezoom.SQL.Compiler.Postgres.PostgresFunctions.PostgresFunctions→Rezoom.SQL.Compiler.Name
- Direction
- Rezoom.SQL.Compiler.Postgres.PostgresFunctions uses Rezoom.SQL.Compiler, so a change to Rezoom.SQL.Compiler can break Rezoom.SQL.Compiler.Postgres.PostgresFunctions, while a change to Rezoom.SQL.Compiler.Postgres.PostgresFunctions can't break Rezoom.SQL.Compiler.
- Position
- Below the diagonal: Rezoom.SQL.Compiler.Postgres.PostgresFunctions uses a module listed above it, which is the healthy direction.
27→15 Rezoom.SQL.Compiler.ReadWriteReferences uses Rezoom.SQL.Compiler✕
- Connections
- 45 pairs of types, where a type in Rezoom.SQL.Compiler.ReadWriteReferences uses a type in Rezoom.SQL.Compiler. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Rezoom.SQL.Compiler.ReadWriteReferences.ReadWriteReferences→Rezoom.SQL.Compiler.ColumnTypeRezoom.SQL.Compiler.ReadWriteReferences.ReadWriteReferences→Rezoom.SQL.Compiler.ExprInfo`1Rezoom.SQL.Compiler.ReadWriteReferences.ReadWriteReferences→Rezoom.SQL.Compiler.ModelRezoom.SQL.Compiler.ReadWriteReferences.ReadWriteReferences→Rezoom.SQL.Compiler.ObjectInfo`1Rezoom.SQL.Compiler.ReadWriteReferences.ReadWriteReferences→Rezoom.SQL.Compiler.Stmt`2Rezoom.SQL.Compiler.ReadWriteReferences.ReferenceFinder→Rezoom.SQL.Compiler.BetweenExpr`2Rezoom.SQL.Compiler.ReadWriteReferences.ReferenceFinder→Rezoom.SQL.Compiler.BinaryExpr`2Rezoom.SQL.Compiler.ReadWriteReferences.ReferenceFinder→Rezoom.SQL.Compiler.CaseExpr`2Rezoom.SQL.Compiler.ReadWriteReferences.ReferenceFinder→Rezoom.SQL.Compiler.CastExpr`2Rezoom.SQL.Compiler.ReadWriteReferences.ReferenceFinder→Rezoom.SQL.Compiler.CollationExpr`2Rezoom.SQL.Compiler.ReadWriteReferences.ReferenceFinder→Rezoom.SQL.Compiler.ColumnName`1Rezoom.SQL.Compiler.ReadWriteReferences.ReferenceFinder→Rezoom.SQL.Compiler.ColumnTypeRezoom.SQL.Compiler.ReadWriteReferences.ReferenceFinder→Rezoom.SQL.Compiler.CommonTableExpression`2Rezoom.SQL.Compiler.ReadWriteReferences.ReferenceFinder→Rezoom.SQL.Compiler.CompoundExprCore`2Rezoom.SQL.Compiler.ReadWriteReferences.ReferenceFinder→Rezoom.SQL.Compiler.CompoundTerm`2Rezoom.SQL.Compiler.ReadWriteReferences.ReferenceFinder→Rezoom.SQL.Compiler.DeleteStmt`2Rezoom.SQL.Compiler.ReadWriteReferences.ReferenceFinder→Rezoom.SQL.Compiler.ExprInfo`1Rezoom.SQL.Compiler.ReadWriteReferences.ReferenceFinder→Rezoom.SQL.Compiler.ExprType`2Rezoom.SQL.Compiler.ReadWriteReferences.ReferenceFinder→Rezoom.SQL.Compiler.Expr`2Rezoom.SQL.Compiler.ReadWriteReferences.ReferenceFinder→Rezoom.SQL.Compiler.FunctionInvocationExpr`2Rezoom.SQL.Compiler.ReadWriteReferences.ReferenceFinder→Rezoom.SQL.Compiler.GroupBy`2Rezoom.SQL.Compiler.ReadWriteReferences.ReferenceFinder→Rezoom.SQL.Compiler.InExpr`2Rezoom.SQL.Compiler.ReadWriteReferences.ReferenceFinder→Rezoom.SQL.Compiler.InsertStmt`2Rezoom.SQL.Compiler.ReadWriteReferences.ReferenceFinder→Rezoom.SQL.Compiler.JoinConstraint`2Rezoom.SQL.Compiler.ReadWriteReferences.ReferenceFinder→Rezoom.SQL.Compiler.Join`2
- Direction
- Rezoom.SQL.Compiler.ReadWriteReferences uses Rezoom.SQL.Compiler, so a change to Rezoom.SQL.Compiler can break Rezoom.SQL.Compiler.ReadWriteReferences, while a change to Rezoom.SQL.Compiler.ReadWriteReferences can't break Rezoom.SQL.Compiler.
- Position
- Below the diagonal: Rezoom.SQL.Compiler.ReadWriteReferences uses a module listed above it, which is the healthy direction.
28→15 Rezoom.SQL.Compiler.SQLite.SQLiteFunctions uses Rezoom.SQL.Compiler✕
- Connections
- 2 pairs of types, where a type in Rezoom.SQL.Compiler.SQLite.SQLiteFunctions uses a type in Rezoom.SQL.Compiler.
- The types involved
Rezoom.SQL.Compiler.SQLite.SQLiteFunctions.SQLiteFunctions→Rezoom.SQL.Compiler.FunctionTypeRezoom.SQL.Compiler.SQLite.SQLiteFunctions.SQLiteFunctions→Rezoom.SQL.Compiler.Name
- Direction
- Rezoom.SQL.Compiler.SQLite.SQLiteFunctions uses Rezoom.SQL.Compiler, so a change to Rezoom.SQL.Compiler can break Rezoom.SQL.Compiler.SQLite.SQLiteFunctions, while a change to Rezoom.SQL.Compiler.SQLite.SQLiteFunctions can't break Rezoom.SQL.Compiler.
- Position
- Below the diagonal: Rezoom.SQL.Compiler.SQLite.SQLiteFunctions uses a module listed above it, which is the healthy direction.
29→15 Rezoom.SQL.Compiler.SourceInfoModule uses Rezoom.SQL.Compiler✕
- Connections
- 2 pairs of types, where a type in Rezoom.SQL.Compiler.SourceInfoModule uses a type in Rezoom.SQL.Compiler.
- The types involved
Rezoom.SQL.Compiler.SourceInfoModule.SourceInfoModule→Rezoom.SQL.Compiler.SourceInfoRezoom.SQL.Compiler.SourceInfoModule.SourceInfoModule→Rezoom.SQL.Compiler.WithSource`1
- Direction
- Rezoom.SQL.Compiler.SourceInfoModule uses Rezoom.SQL.Compiler, so a change to Rezoom.SQL.Compiler can break Rezoom.SQL.Compiler.SourceInfoModule, while a change to Rezoom.SQL.Compiler.SourceInfoModule can't break Rezoom.SQL.Compiler.
- Position
- Below the diagonal: Rezoom.SQL.Compiler.SourceInfoModule uses a module listed above it, which is the healthy direction.
30→15 Rezoom.SQL.Compiler.TSQL.TSQLFunctions uses Rezoom.SQL.Compiler✕
- Connections
- 3 pairs of types, where a type in Rezoom.SQL.Compiler.TSQL.TSQLFunctions uses a type in Rezoom.SQL.Compiler.
- The types involved
Rezoom.SQL.Compiler.TSQL.TSQLFunctions.TSQLFunctions→Rezoom.SQL.Compiler.FunctionTermTypeRezoom.SQL.Compiler.TSQL.TSQLFunctions.TSQLFunctions→Rezoom.SQL.Compiler.FunctionTypeRezoom.SQL.Compiler.TSQL.TSQLFunctions.TSQLFunctions→Rezoom.SQL.Compiler.Name
- Direction
- Rezoom.SQL.Compiler.TSQL.TSQLFunctions uses Rezoom.SQL.Compiler, so a change to Rezoom.SQL.Compiler can break Rezoom.SQL.Compiler.TSQL.TSQLFunctions, while a change to Rezoom.SQL.Compiler.TSQL.TSQLFunctions can't break Rezoom.SQL.Compiler.
- Position
- Below the diagonal: Rezoom.SQL.Compiler.TSQL.TSQLFunctions uses a module listed above it, which is the healthy direction.
31→8 Rezoom.SQL.Compiler.Translators uses Rezoom.SQL.Mapping✕
- Connections
- 6 pairs of types, where a type in Rezoom.SQL.Compiler.Translators uses a type in Rezoom.SQL.Mapping.
- The types involved
Rezoom.SQL.Compiler.Translators.DefaultExprTranslator→Rezoom.SQL.Mapping.CommandFragmentRezoom.SQL.Compiler.Translators.DefaultLiteralTranslator→Rezoom.SQL.Mapping.CommandFragmentRezoom.SQL.Compiler.Translators.DefaultStatementTranslator→Rezoom.SQL.Mapping.CommandFragmentRezoom.SQL.Compiler.Translators.ExprTranslator→Rezoom.SQL.Mapping.CommandFragmentRezoom.SQL.Compiler.Translators.LiteralTranslator→Rezoom.SQL.Mapping.CommandFragmentRezoom.SQL.Compiler.Translators.StatementTranslator→Rezoom.SQL.Mapping.CommandFragment
- Direction
- Rezoom.SQL.Compiler.Translators uses Rezoom.SQL.Mapping, so a change to Rezoom.SQL.Mapping can break Rezoom.SQL.Compiler.Translators, while a change to Rezoom.SQL.Compiler.Translators can't break Rezoom.SQL.Mapping.
- Position
- Below the diagonal: Rezoom.SQL.Compiler.Translators uses a module listed above it, which is the healthy direction.
31→15 Rezoom.SQL.Compiler.Translators uses Rezoom.SQL.Compiler✕
- Connections
- 129 pairs of types, where a type in Rezoom.SQL.Compiler.Translators uses a type in Rezoom.SQL.Compiler. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Rezoom.SQL.Compiler.Translators.DefaultExprTranslator→Rezoom.SQL.Compiler.BetweenExpr`2Rezoom.SQL.Compiler.Translators.DefaultExprTranslator→Rezoom.SQL.Compiler.BinaryExpr`2Rezoom.SQL.Compiler.Translators.DefaultExprTranslator→Rezoom.SQL.Compiler.BinaryOperatorRezoom.SQL.Compiler.Translators.DefaultExprTranslator→Rezoom.SQL.Compiler.BindParameterRezoom.SQL.Compiler.Translators.DefaultExprTranslator→Rezoom.SQL.Compiler.CaseExpr`2Rezoom.SQL.Compiler.Translators.DefaultExprTranslator→Rezoom.SQL.Compiler.CastExpr`2Rezoom.SQL.Compiler.Translators.DefaultExprTranslator→Rezoom.SQL.Compiler.ColumnName`1Rezoom.SQL.Compiler.Translators.DefaultExprTranslator→Rezoom.SQL.Compiler.ColumnTypeRezoom.SQL.Compiler.Translators.DefaultExprTranslator→Rezoom.SQL.Compiler.ExprInfo`1Rezoom.SQL.Compiler.Translators.DefaultExprTranslator→Rezoom.SQL.Compiler.Expr`2Rezoom.SQL.Compiler.Translators.DefaultExprTranslator→Rezoom.SQL.Compiler.FunctionInvocationExpr`2Rezoom.SQL.Compiler.Translators.DefaultExprTranslator→Rezoom.SQL.Compiler.IParameterIndexerRezoom.SQL.Compiler.Translators.DefaultExprTranslator→Rezoom.SQL.Compiler.InExpr`2Rezoom.SQL.Compiler.Translators.DefaultExprTranslator→Rezoom.SQL.Compiler.NameRezoom.SQL.Compiler.Translators.DefaultExprTranslator→Rezoom.SQL.Compiler.ObjectInfo`1Rezoom.SQL.Compiler.Translators.DefaultExprTranslator→Rezoom.SQL.Compiler.ObjectName`1Rezoom.SQL.Compiler.Translators.DefaultExprTranslator→Rezoom.SQL.Compiler.SelectStmtCore`2Rezoom.SQL.Compiler.Translators.DefaultExprTranslator→Rezoom.SQL.Compiler.SimilarityExpr`2Rezoom.SQL.Compiler.Translators.DefaultExprTranslator→Rezoom.SQL.Compiler.SimilarityOperatorRezoom.SQL.Compiler.Translators.DefaultExprTranslator→Rezoom.SQL.Compiler.TableInvocation`2Rezoom.SQL.Compiler.Translators.DefaultExprTranslator→Rezoom.SQL.Compiler.TypeNameRezoom.SQL.Compiler.Translators.DefaultExprTranslator→Rezoom.SQL.Compiler.UnaryExpr`2Rezoom.SQL.Compiler.Translators.DefaultExprTranslator→Rezoom.SQL.Compiler.UnaryOperatorRezoom.SQL.Compiler.Translators.DefaultExprTranslator→Rezoom.SQL.Compiler.WithSource`1Rezoom.SQL.Compiler.Translators.DefaultLiteralTranslator→Rezoom.SQL.Compiler.Literal
- Direction
- Rezoom.SQL.Compiler.Translators uses Rezoom.SQL.Compiler, so a change to Rezoom.SQL.Compiler can break Rezoom.SQL.Compiler.Translators, while a change to Rezoom.SQL.Compiler.Translators can't break Rezoom.SQL.Compiler.
- Position
- Below the diagonal: Rezoom.SQL.Compiler.Translators uses a module listed above it, which is the healthy direction.
32→15 Rezoom.SQL.Compiler.Translators.DefaultSQLTypeString uses Rezoom.SQL.Compiler✕
- Connections
- 1 pair of types, where a type in Rezoom.SQL.Compiler.Translators.DefaultSQLTypeString uses a type in Rezoom.SQL.Compiler.
- The types involved
Rezoom.SQL.Compiler.Translators.DefaultSQLTypeString.DefaultSQLTypeString→Rezoom.SQL.Compiler.TypeName
- Direction
- Rezoom.SQL.Compiler.Translators.DefaultSQLTypeString uses Rezoom.SQL.Compiler, so a change to Rezoom.SQL.Compiler can break Rezoom.SQL.Compiler.Translators.DefaultSQLTypeString, while a change to Rezoom.SQL.Compiler.Translators.DefaultSQLTypeString can't break Rezoom.SQL.Compiler.
- Position
- Below the diagonal: Rezoom.SQL.Compiler.Translators.DefaultSQLTypeString uses a module listed above it, which is the healthy direction.
33→7 Rezoom.SQL.Compiler.TypeInferenceExtensions uses Rezoom.SQL.Compiler.InferredTypes✕
- Connections
- 2 pairs of types, where a type in Rezoom.SQL.Compiler.TypeInferenceExtensions uses a type in Rezoom.SQL.Compiler.InferredTypes.
- The types involved
Rezoom.SQL.Compiler.TypeInferenceExtensions.TypeInferenceExtensions→Rezoom.SQL.Compiler.InferredTypes.CoreInferredTypeRezoom.SQL.Compiler.TypeInferenceExtensions.TypeInferenceExtensions→Rezoom.SQL.Compiler.InferredTypes.InferredType
- Direction
- Rezoom.SQL.Compiler.TypeInferenceExtensions uses Rezoom.SQL.Compiler.InferredTypes, so a change to Rezoom.SQL.Compiler.InferredTypes can break Rezoom.SQL.Compiler.TypeInferenceExtensions, while a change to Rezoom.SQL.Compiler.TypeInferenceExtensions can't break Rezoom.SQL.Compiler.InferredTypes.
- Position
- Below the diagonal: Rezoom.SQL.Compiler.TypeInferenceExtensions uses a module listed above it, which is the healthy direction.
33→15 Rezoom.SQL.Compiler.TypeInferenceExtensions uses Rezoom.SQL.Compiler✕
- Connections
- 12 pairs of types, where a type in Rezoom.SQL.Compiler.TypeInferenceExtensions uses a type in Rezoom.SQL.Compiler.
- The types involved
Rezoom.SQL.Compiler.TypeInferenceExtensions.TypeInferenceExtensions→Rezoom.SQL.Compiler.BinaryOperatorRezoom.SQL.Compiler.TypeInferenceExtensions.TypeInferenceExtensions→Rezoom.SQL.Compiler.CoreColumnTypeRezoom.SQL.Compiler.TypeInferenceExtensions.TypeInferenceExtensions→Rezoom.SQL.Compiler.ExprInfo`1Rezoom.SQL.Compiler.TypeInferenceExtensions.TypeInferenceExtensions→Rezoom.SQL.Compiler.ExprType`2Rezoom.SQL.Compiler.TypeInferenceExtensions.TypeInferenceExtensions→Rezoom.SQL.Compiler.FunctionArguments`2Rezoom.SQL.Compiler.TypeInferenceExtensions.TypeInferenceExtensions→Rezoom.SQL.Compiler.FunctionTypeRezoom.SQL.Compiler.TypeInferenceExtensions.TypeInferenceExtensions→Rezoom.SQL.Compiler.NameRezoom.SQL.Compiler.TypeInferenceExtensions.TypeInferenceExtensions→Rezoom.SQL.Compiler.ObjectInfo`1Rezoom.SQL.Compiler.TypeInferenceExtensions.TypeInferenceExtensions→Rezoom.SQL.Compiler.QueryExprInfo`1Rezoom.SQL.Compiler.TypeInferenceExtensions.TypeInferenceExtensions→Rezoom.SQL.Compiler.SourceInfoRezoom.SQL.Compiler.TypeInferenceExtensions.TypeInferenceExtensions→Rezoom.SQL.Compiler.UnaryOperatorRezoom.SQL.Compiler.TypeInferenceExtensions.TypeInferenceExtensions→Rezoom.SQL.Compiler.WithSource`1
- Direction
- Rezoom.SQL.Compiler.TypeInferenceExtensions uses Rezoom.SQL.Compiler, so a change to Rezoom.SQL.Compiler can break Rezoom.SQL.Compiler.TypeInferenceExtensions, while a change to Rezoom.SQL.Compiler.TypeInferenceExtensions can't break Rezoom.SQL.Compiler.
- Position
- Below the diagonal: Rezoom.SQL.Compiler.TypeInferenceExtensions uses a module listed above it, which is the healthy direction.
34→2 Rezoom.SQL.Compiler.UserModelLoader uses Rezoom.SQL.Migrations✕
- Connections
- 2 pairs of types, where a type in Rezoom.SQL.Compiler.UserModelLoader uses a type in Rezoom.SQL.Migrations.
- The types involved
Rezoom.SQL.Compiler.UserModelLoader.UserModelLoader→Rezoom.SQL.Migrations.MigrationFileNameRezoom.SQL.Compiler.UserModelLoader.UserModelLoader→Rezoom.SQL.Migrations.MigrationTree`1
- Direction
- Rezoom.SQL.Compiler.UserModelLoader uses Rezoom.SQL.Migrations, so a change to Rezoom.SQL.Migrations can break Rezoom.SQL.Compiler.UserModelLoader, while a change to Rezoom.SQL.Compiler.UserModelLoader can't break Rezoom.SQL.Migrations.
- Position
- Below the diagonal: Rezoom.SQL.Compiler.UserModelLoader uses a module listed above it, which is the healthy direction.
34→8 Rezoom.SQL.Compiler.UserModelLoader uses Rezoom.SQL.Mapping✕
- Connections
- 1 pair of types, where a type in Rezoom.SQL.Compiler.UserModelLoader uses a type in Rezoom.SQL.Mapping.
- The types involved
Rezoom.SQL.Compiler.UserModelLoader.UserModelLoader→Rezoom.SQL.Mapping.UserTypeLibrary
- Direction
- Rezoom.SQL.Compiler.UserModelLoader uses Rezoom.SQL.Mapping, so a change to Rezoom.SQL.Mapping can break Rezoom.SQL.Compiler.UserModelLoader, while a change to Rezoom.SQL.Compiler.UserModelLoader can't break Rezoom.SQL.Mapping.
- Position
- Below the diagonal: Rezoom.SQL.Compiler.UserModelLoader uses a module listed above it, which is the healthy direction.
34→15 Rezoom.SQL.Compiler.UserModelLoader uses Rezoom.SQL.Compiler✕
- Connections
- 7 pairs of types, where a type in Rezoom.SQL.Compiler.UserModelLoader uses a type in Rezoom.SQL.Compiler.
- The types involved
Rezoom.SQL.Compiler.UserModelLoader.UserModelLoader→Rezoom.SQL.Compiler.ColumnTypeRezoom.SQL.Compiler.UserModelLoader.UserModelLoader→Rezoom.SQL.Compiler.ExprInfo`1Rezoom.SQL.Compiler.UserModelLoader.UserModelLoader→Rezoom.SQL.Compiler.IBackendRezoom.SQL.Compiler.UserModelLoader.UserModelLoader→Rezoom.SQL.Compiler.ModelRezoom.SQL.Compiler.UserModelLoader.UserModelLoader→Rezoom.SQL.Compiler.ObjectInfo`1Rezoom.SQL.Compiler.UserModelLoader.UserModelLoader→Rezoom.SQL.Compiler.QualifiedObjectNameRezoom.SQL.Compiler.UserModelLoader.UserModelLoader→Rezoom.SQL.Compiler.TotalStmt`2
- Direction
- Rezoom.SQL.Compiler.UserModelLoader uses Rezoom.SQL.Compiler, so a change to Rezoom.SQL.Compiler can break Rezoom.SQL.Compiler.UserModelLoader, while a change to Rezoom.SQL.Compiler.UserModelLoader can't break Rezoom.SQL.Compiler.
- Position
- Below the diagonal: Rezoom.SQL.Compiler.UserModelLoader uses a module listed above it, which is the healthy direction.
35→1 Rezoom.SQL.Provider uses ProviderImplementation.ProvidedTypes✕
- Connections
- 1 pair of types, where a type in Rezoom.SQL.Provider uses a type in ProviderImplementation.ProvidedTypes.
- The types involved
Rezoom.SQL.Provider.Provider→ProviderImplementation.ProvidedTypes.TypeProviderForNamespaces
- Direction
- Rezoom.SQL.Provider uses ProviderImplementation.ProvidedTypes, so a change to ProviderImplementation.ProvidedTypes can break Rezoom.SQL.Provider, while a change to Rezoom.SQL.Provider can't break ProviderImplementation.ProvidedTypes.
- Position
- Below the diagonal: Rezoom.SQL.Provider uses a module listed above it, which is the healthy direction.
35→15 Rezoom.SQL.Provider uses Rezoom.SQL.Compiler✕
- Connections
- 3 pairs of types, where a type in Rezoom.SQL.Provider uses a type in Rezoom.SQL.Compiler.
- The types involved
Rezoom.SQL.Provider.CompileTimeColumnMap→Rezoom.SQL.Compiler.ColumnExprInfo`1Rezoom.SQL.Provider.CompileTimeColumnMap→Rezoom.SQL.Compiler.ColumnTypeRezoom.SQL.Provider.UserModelCache→Rezoom.SQL.Compiler.UserModel
- Direction
- Rezoom.SQL.Provider uses Rezoom.SQL.Compiler, so a change to Rezoom.SQL.Compiler can break Rezoom.SQL.Provider, while a change to Rezoom.SQL.Provider can't break Rezoom.SQL.Compiler.
- Position
- Below the diagonal: Rezoom.SQL.Provider uses a module listed above it, which is the healthy direction.
36→1 Rezoom.SQL.Provider.InterfaceImpls uses ProviderImplementation.ProvidedTypes✕
- Connections
- 2 pairs of types, where a type in Rezoom.SQL.Provider.InterfaceImpls uses a type in ProviderImplementation.ProvidedTypes.
- The types involved
Rezoom.SQL.Provider.InterfaceImpls.InterfaceImpls→ProviderImplementation.ProvidedTypes.ProvidedTypeDefinitionRezoom.SQL.Provider.InterfaceImpls.ProvidedPropertyMeta→ProviderImplementation.ProvidedTypes.ProvidedProperty
- Direction
- Rezoom.SQL.Provider.InterfaceImpls uses ProviderImplementation.ProvidedTypes, so a change to ProviderImplementation.ProvidedTypes can break Rezoom.SQL.Provider.InterfaceImpls, while a change to Rezoom.SQL.Provider.InterfaceImpls can't break ProviderImplementation.ProvidedTypes.
- Position
- Below the diagonal: Rezoom.SQL.Provider.InterfaceImpls uses a module listed above it, which is the healthy direction.
36→12 Rezoom.SQL.Provider.InterfaceImpls uses Rezoom.SQL.Compiler.Config✕
- Connections
- 1 pair of types, where a type in Rezoom.SQL.Provider.InterfaceImpls uses a type in Rezoom.SQL.Compiler.Config.
- The types involved
Rezoom.SQL.Provider.InterfaceImpls.InterfaceImpls→Rezoom.SQL.Compiler.Config.ConfigOptionalStyle
- Direction
- Rezoom.SQL.Provider.InterfaceImpls uses Rezoom.SQL.Compiler.Config, so a change to Rezoom.SQL.Compiler.Config can break Rezoom.SQL.Provider.InterfaceImpls, while a change to Rezoom.SQL.Provider.InterfaceImpls can't break Rezoom.SQL.Compiler.Config.
- Position
- Below the diagonal: Rezoom.SQL.Provider.InterfaceImpls uses a module listed above it, which is the healthy direction.
36→15 Rezoom.SQL.Provider.InterfaceImpls uses Rezoom.SQL.Compiler✕
- Connections
- 2 pairs of types, where a type in Rezoom.SQL.Provider.InterfaceImpls uses a type in Rezoom.SQL.Compiler.
- The types involved
Rezoom.SQL.Provider.InterfaceImpls.InterfaceImpls→Rezoom.SQL.Compiler.ResultColumnNavCardinalityRezoom.SQL.Provider.InterfaceImpls.InterfaceImpls→Rezoom.SQL.Compiler.SourceInfo
- Direction
- Rezoom.SQL.Provider.InterfaceImpls uses Rezoom.SQL.Compiler, so a change to Rezoom.SQL.Compiler can break Rezoom.SQL.Provider.InterfaceImpls, while a change to Rezoom.SQL.Provider.InterfaceImpls can't break Rezoom.SQL.Compiler.
- Position
- Below the diagonal: Rezoom.SQL.Provider.InterfaceImpls uses a module listed above it, which is the healthy direction.
37→8 Rezoom.SQL.Compiler.Postgres uses Rezoom.SQL.Mapping✕
- Connections
- 5 pairs of types, where a type in Rezoom.SQL.Compiler.Postgres uses a type in Rezoom.SQL.Mapping.
- The types involved
Rezoom.SQL.Compiler.Postgres.PostgresBackend→Rezoom.SQL.Mapping.CommandFragmentRezoom.SQL.Compiler.Postgres.PostgresExpression→Rezoom.SQL.Mapping.CommandFragmentRezoom.SQL.Compiler.Postgres.PostgresLiteral→Rezoom.SQL.Mapping.CommandFragmentRezoom.SQL.Compiler.Postgres.PostgresMigrationBackend→Rezoom.SQL.Mapping.ConnectionInfoRezoom.SQL.Compiler.Postgres.PostgresStatement→Rezoom.SQL.Mapping.CommandFragment
- Direction
- Rezoom.SQL.Compiler.Postgres uses Rezoom.SQL.Mapping, so a change to Rezoom.SQL.Mapping can break Rezoom.SQL.Compiler.Postgres, while a change to Rezoom.SQL.Compiler.Postgres can't break Rezoom.SQL.Mapping.
- Position
- Below the diagonal: Rezoom.SQL.Compiler.Postgres uses a module listed above it, which is the healthy direction.
37→11 Rezoom.SQL.Compiler.Postgres uses Rezoom.SQL.Compiler.BackendUtilities✕
- Connections
- 1 pair of types, where a type in Rezoom.SQL.Compiler.Postgres uses a type in Rezoom.SQL.Compiler.BackendUtilities.
- The types involved
Rezoom.SQL.Compiler.Postgres.PostgresMigrationBackend→Rezoom.SQL.Compiler.BackendUtilities.DefaultMigrationBackend
- Direction
- Rezoom.SQL.Compiler.Postgres uses Rezoom.SQL.Compiler.BackendUtilities, so a change to Rezoom.SQL.Compiler.BackendUtilities can break Rezoom.SQL.Compiler.Postgres, while a change to Rezoom.SQL.Compiler.Postgres can't break Rezoom.SQL.Compiler.BackendUtilities.
- Position
- Below the diagonal: Rezoom.SQL.Compiler.Postgres uses a module listed above it, which is the healthy direction.
37→15 Rezoom.SQL.Compiler.Postgres uses Rezoom.SQL.Compiler✕
- Connections
- 22 pairs of types, where a type in Rezoom.SQL.Compiler.Postgres uses a type in Rezoom.SQL.Compiler.
- The types involved
Rezoom.SQL.Compiler.Postgres.PostgresBackend→Rezoom.SQL.Compiler.BackendBaseRezoom.SQL.Compiler.Postgres.PostgresBackend→Rezoom.SQL.Compiler.ColumnTypeRezoom.SQL.Compiler.Postgres.PostgresBackend→Rezoom.SQL.Compiler.ExprInfo`1Rezoom.SQL.Compiler.Postgres.PostgresBackend→Rezoom.SQL.Compiler.IParameterIndexerRezoom.SQL.Compiler.Postgres.PostgresBackend→Rezoom.SQL.Compiler.ModelRezoom.SQL.Compiler.Postgres.PostgresBackend→Rezoom.SQL.Compiler.ObjectInfo`1Rezoom.SQL.Compiler.Postgres.PostgresBackend→Rezoom.SQL.Compiler.TotalStmt`2Rezoom.SQL.Compiler.Postgres.PostgresBackend→Rezoom.SQL.Compiler.TypeNameRezoom.SQL.Compiler.Postgres.PostgresExpression→Rezoom.SQL.Compiler.BinaryOperatorRezoom.SQL.Compiler.Postgres.PostgresExpression→Rezoom.SQL.Compiler.ColumnTypeRezoom.SQL.Compiler.Postgres.PostgresExpression→Rezoom.SQL.Compiler.IParameterIndexerRezoom.SQL.Compiler.Postgres.PostgresExpression→Rezoom.SQL.Compiler.NameRezoom.SQL.Compiler.Postgres.PostgresExpression→Rezoom.SQL.Compiler.ObjectInfo`1Rezoom.SQL.Compiler.Postgres.PostgresExpression→Rezoom.SQL.Compiler.ObjectName`1Rezoom.SQL.Compiler.Postgres.PostgresExpression→Rezoom.SQL.Compiler.SimilarityOperatorRezoom.SQL.Compiler.Postgres.PostgresExpression→Rezoom.SQL.Compiler.TypeNameRezoom.SQL.Compiler.Postgres.PostgresStatement→Rezoom.SQL.Compiler.AlterTableStmt`2Rezoom.SQL.Compiler.Postgres.PostgresStatement→Rezoom.SQL.Compiler.ColumnTypeRezoom.SQL.Compiler.Postgres.PostgresStatement→Rezoom.SQL.Compiler.ExprInfo`1Rezoom.SQL.Compiler.Postgres.PostgresStatement→Rezoom.SQL.Compiler.IParameterIndexerRezoom.SQL.Compiler.Postgres.PostgresStatement→Rezoom.SQL.Compiler.ObjectInfo`1Rezoom.SQL.Compiler.Postgres.PostgresStatement→Rezoom.SQL.Compiler.PrimaryKeyClause
- Direction
- Rezoom.SQL.Compiler.Postgres uses Rezoom.SQL.Compiler, so a change to Rezoom.SQL.Compiler can break Rezoom.SQL.Compiler.Postgres, while a change to Rezoom.SQL.Compiler.Postgres can't break Rezoom.SQL.Compiler.
- Position
- Below the diagonal: Rezoom.SQL.Compiler.Postgres uses a module listed above it, which is the healthy direction.
37→31 Rezoom.SQL.Compiler.Postgres uses Rezoom.SQL.Compiler.Translators✕
- Connections
- 6 pairs of types, where a type in Rezoom.SQL.Compiler.Postgres uses a type in Rezoom.SQL.Compiler.Translators.
- The types involved
Rezoom.SQL.Compiler.Postgres.PostgresExpression→Rezoom.SQL.Compiler.Translators.DefaultExprTranslatorRezoom.SQL.Compiler.Postgres.PostgresExpression→Rezoom.SQL.Compiler.Translators.LiteralTranslatorRezoom.SQL.Compiler.Postgres.PostgresExpression→Rezoom.SQL.Compiler.Translators.StatementTranslatorRezoom.SQL.Compiler.Postgres.PostgresLiteral→Rezoom.SQL.Compiler.Translators.DefaultLiteralTranslatorRezoom.SQL.Compiler.Postgres.PostgresStatement→Rezoom.SQL.Compiler.Translators.DefaultStatementTranslatorRezoom.SQL.Compiler.Postgres.PostgresStatement→Rezoom.SQL.Compiler.Translators.ExprTranslator
- Direction
- Rezoom.SQL.Compiler.Postgres uses Rezoom.SQL.Compiler.Translators, so a change to Rezoom.SQL.Compiler.Translators can break Rezoom.SQL.Compiler.Postgres, while a change to Rezoom.SQL.Compiler.Postgres can't break Rezoom.SQL.Compiler.Translators.
- Position
- Below the diagonal: Rezoom.SQL.Compiler.Postgres uses a module listed above it, which is the healthy direction.
38→8 Rezoom.SQL.Compiler.SQLite uses Rezoom.SQL.Mapping✕
- Connections
- 5 pairs of types, where a type in Rezoom.SQL.Compiler.SQLite uses a type in Rezoom.SQL.Mapping.
- The types involved
Rezoom.SQL.Compiler.SQLite.SQLiteBackend→Rezoom.SQL.Mapping.CommandFragmentRezoom.SQL.Compiler.SQLite.SQLiteExpression→Rezoom.SQL.Mapping.CommandFragmentRezoom.SQL.Compiler.SQLite.SQLiteLiteral→Rezoom.SQL.Mapping.CommandFragmentRezoom.SQL.Compiler.SQLite.SQLiteMigrationBackend→Rezoom.SQL.Mapping.ConnectionInfoRezoom.SQL.Compiler.SQLite.SQLiteStatement→Rezoom.SQL.Mapping.CommandFragment
- Direction
- Rezoom.SQL.Compiler.SQLite uses Rezoom.SQL.Mapping, so a change to Rezoom.SQL.Mapping can break Rezoom.SQL.Compiler.SQLite, while a change to Rezoom.SQL.Compiler.SQLite can't break Rezoom.SQL.Mapping.
- Position
- Below the diagonal: Rezoom.SQL.Compiler.SQLite uses a module listed above it, which is the healthy direction.
38→11 Rezoom.SQL.Compiler.SQLite uses Rezoom.SQL.Compiler.BackendUtilities✕
- Connections
- 1 pair of types, where a type in Rezoom.SQL.Compiler.SQLite uses a type in Rezoom.SQL.Compiler.BackendUtilities.
- The types involved
Rezoom.SQL.Compiler.SQLite.SQLiteMigrationBackend→Rezoom.SQL.Compiler.BackendUtilities.DefaultMigrationBackend
- Direction
- Rezoom.SQL.Compiler.SQLite uses Rezoom.SQL.Compiler.BackendUtilities, so a change to Rezoom.SQL.Compiler.BackendUtilities can break Rezoom.SQL.Compiler.SQLite, while a change to Rezoom.SQL.Compiler.SQLite can't break Rezoom.SQL.Compiler.BackendUtilities.
- Position
- Below the diagonal: Rezoom.SQL.Compiler.SQLite uses a module listed above it, which is the healthy direction.
38→15 Rezoom.SQL.Compiler.SQLite uses Rezoom.SQL.Compiler✕
- Connections
- 16 pairs of types, where a type in Rezoom.SQL.Compiler.SQLite uses a type in Rezoom.SQL.Compiler.
- The types involved
Rezoom.SQL.Compiler.SQLite.SQLiteBackend→Rezoom.SQL.Compiler.BackendBaseRezoom.SQL.Compiler.SQLite.SQLiteBackend→Rezoom.SQL.Compiler.ColumnTypeRezoom.SQL.Compiler.SQLite.SQLiteBackend→Rezoom.SQL.Compiler.ExprInfo`1Rezoom.SQL.Compiler.SQLite.SQLiteBackend→Rezoom.SQL.Compiler.IParameterIndexerRezoom.SQL.Compiler.SQLite.SQLiteBackend→Rezoom.SQL.Compiler.ModelRezoom.SQL.Compiler.SQLite.SQLiteBackend→Rezoom.SQL.Compiler.ObjectInfo`1Rezoom.SQL.Compiler.SQLite.SQLiteBackend→Rezoom.SQL.Compiler.ParameterTransformRezoom.SQL.Compiler.SQLite.SQLiteBackend→Rezoom.SQL.Compiler.TotalStmt`2Rezoom.SQL.Compiler.SQLite.SQLiteBackend→Rezoom.SQL.Compiler.TypeNameRezoom.SQL.Compiler.SQLite.SQLiteExpression→Rezoom.SQL.Compiler.IParameterIndexerRezoom.SQL.Compiler.SQLite.SQLiteExpression→Rezoom.SQL.Compiler.TypeNameRezoom.SQL.Compiler.SQLite.SQLiteStatement→Rezoom.SQL.Compiler.AlterTableStmt`2Rezoom.SQL.Compiler.SQLite.SQLiteStatement→Rezoom.SQL.Compiler.ColumnTypeRezoom.SQL.Compiler.SQLite.SQLiteStatement→Rezoom.SQL.Compiler.ExprInfo`1Rezoom.SQL.Compiler.SQLite.SQLiteStatement→Rezoom.SQL.Compiler.IParameterIndexerRezoom.SQL.Compiler.SQLite.SQLiteStatement→Rezoom.SQL.Compiler.ObjectInfo`1
- Direction
- Rezoom.SQL.Compiler.SQLite uses Rezoom.SQL.Compiler, so a change to Rezoom.SQL.Compiler can break Rezoom.SQL.Compiler.SQLite, while a change to Rezoom.SQL.Compiler.SQLite can't break Rezoom.SQL.Compiler.
- Position
- Below the diagonal: Rezoom.SQL.Compiler.SQLite uses a module listed above it, which is the healthy direction.
38→31 Rezoom.SQL.Compiler.SQLite uses Rezoom.SQL.Compiler.Translators✕
- Connections
- 6 pairs of types, where a type in Rezoom.SQL.Compiler.SQLite uses a type in Rezoom.SQL.Compiler.Translators.
- The types involved
Rezoom.SQL.Compiler.SQLite.SQLiteExpression→Rezoom.SQL.Compiler.Translators.DefaultExprTranslatorRezoom.SQL.Compiler.SQLite.SQLiteExpression→Rezoom.SQL.Compiler.Translators.LiteralTranslatorRezoom.SQL.Compiler.SQLite.SQLiteExpression→Rezoom.SQL.Compiler.Translators.StatementTranslatorRezoom.SQL.Compiler.SQLite.SQLiteLiteral→Rezoom.SQL.Compiler.Translators.DefaultLiteralTranslatorRezoom.SQL.Compiler.SQLite.SQLiteStatement→Rezoom.SQL.Compiler.Translators.DefaultStatementTranslatorRezoom.SQL.Compiler.SQLite.SQLiteStatement→Rezoom.SQL.Compiler.Translators.ExprTranslator
- Direction
- Rezoom.SQL.Compiler.SQLite uses Rezoom.SQL.Compiler.Translators, so a change to Rezoom.SQL.Compiler.Translators can break Rezoom.SQL.Compiler.SQLite, while a change to Rezoom.SQL.Compiler.SQLite can't break Rezoom.SQL.Compiler.Translators.
- Position
- Below the diagonal: Rezoom.SQL.Compiler.SQLite uses a module listed above it, which is the healthy direction.
39→8 Rezoom.SQL.Compiler.TSQL uses Rezoom.SQL.Mapping✕
- Connections
- 5 pairs of types, where a type in Rezoom.SQL.Compiler.TSQL uses a type in Rezoom.SQL.Mapping.
- The types involved
Rezoom.SQL.Compiler.TSQL.TSQLBackend→Rezoom.SQL.Mapping.CommandFragmentRezoom.SQL.Compiler.TSQL.TSQLExpression→Rezoom.SQL.Mapping.CommandFragmentRezoom.SQL.Compiler.TSQL.TSQLLiteral→Rezoom.SQL.Mapping.CommandFragmentRezoom.SQL.Compiler.TSQL.TSQLMigrationBackend→Rezoom.SQL.Mapping.ConnectionInfoRezoom.SQL.Compiler.TSQL.TSQLStatement→Rezoom.SQL.Mapping.CommandFragment
- Direction
- Rezoom.SQL.Compiler.TSQL uses Rezoom.SQL.Mapping, so a change to Rezoom.SQL.Mapping can break Rezoom.SQL.Compiler.TSQL, while a change to Rezoom.SQL.Compiler.TSQL can't break Rezoom.SQL.Mapping.
- Position
- Below the diagonal: Rezoom.SQL.Compiler.TSQL uses a module listed above it, which is the healthy direction.
39→11 Rezoom.SQL.Compiler.TSQL uses Rezoom.SQL.Compiler.BackendUtilities✕
- Connections
- 1 pair of types, where a type in Rezoom.SQL.Compiler.TSQL uses a type in Rezoom.SQL.Compiler.BackendUtilities.
- The types involved
Rezoom.SQL.Compiler.TSQL.TSQLMigrationBackend→Rezoom.SQL.Compiler.BackendUtilities.DefaultMigrationBackend
- Direction
- Rezoom.SQL.Compiler.TSQL uses Rezoom.SQL.Compiler.BackendUtilities, so a change to Rezoom.SQL.Compiler.BackendUtilities can break Rezoom.SQL.Compiler.TSQL, while a change to Rezoom.SQL.Compiler.TSQL can't break Rezoom.SQL.Compiler.BackendUtilities.
- Position
- Below the diagonal: Rezoom.SQL.Compiler.TSQL uses a module listed above it, which is the healthy direction.
39→15 Rezoom.SQL.Compiler.TSQL uses Rezoom.SQL.Compiler✕
- Connections
- 43 pairs of types, where a type in Rezoom.SQL.Compiler.TSQL uses a type in Rezoom.SQL.Compiler. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Rezoom.SQL.Compiler.TSQL.TSQLBackend→Rezoom.SQL.Compiler.BackendBaseRezoom.SQL.Compiler.TSQL.TSQLBackend→Rezoom.SQL.Compiler.ColumnTypeRezoom.SQL.Compiler.TSQL.TSQLBackend→Rezoom.SQL.Compiler.ExprInfo`1Rezoom.SQL.Compiler.TSQL.TSQLBackend→Rezoom.SQL.Compiler.IParameterIndexerRezoom.SQL.Compiler.TSQL.TSQLBackend→Rezoom.SQL.Compiler.ModelRezoom.SQL.Compiler.TSQL.TSQLBackend→Rezoom.SQL.Compiler.ObjectInfo`1Rezoom.SQL.Compiler.TSQL.TSQLBackend→Rezoom.SQL.Compiler.TotalStmt`2Rezoom.SQL.Compiler.TSQL.TSQLBackend→Rezoom.SQL.Compiler.TypeNameRezoom.SQL.Compiler.TSQL.TSQLExpression→Rezoom.SQL.Compiler.BinaryExpr`2Rezoom.SQL.Compiler.TSQL.TSQLExpression→Rezoom.SQL.Compiler.BinaryOperatorRezoom.SQL.Compiler.TSQL.TSQLExpression→Rezoom.SQL.Compiler.ColumnTypeRezoom.SQL.Compiler.TSQL.TSQLExpression→Rezoom.SQL.Compiler.ExprInfo`1Rezoom.SQL.Compiler.TSQL.TSQLExpression→Rezoom.SQL.Compiler.Expr`2Rezoom.SQL.Compiler.TSQL.TSQLExpression→Rezoom.SQL.Compiler.FunctionInvocationExpr`2Rezoom.SQL.Compiler.TSQL.TSQLExpression→Rezoom.SQL.Compiler.IParameterIndexerRezoom.SQL.Compiler.TSQL.TSQLExpression→Rezoom.SQL.Compiler.NameRezoom.SQL.Compiler.TSQL.TSQLExpression→Rezoom.SQL.Compiler.ObjectInfo`1Rezoom.SQL.Compiler.TSQL.TSQLExpression→Rezoom.SQL.Compiler.ObjectName`1Rezoom.SQL.Compiler.TSQL.TSQLExpression→Rezoom.SQL.Compiler.SimilarityOperatorRezoom.SQL.Compiler.TSQL.TSQLExpression→Rezoom.SQL.Compiler.TypeNameRezoom.SQL.Compiler.TSQL.TSQLExpression→Rezoom.SQL.Compiler.UnaryOperatorRezoom.SQL.Compiler.TSQL.TSQLStatement→Rezoom.SQL.Compiler.AlterTableStmt`2Rezoom.SQL.Compiler.TSQL.TSQLStatement→Rezoom.SQL.Compiler.ColumnDef`2Rezoom.SQL.Compiler.TSQL.TSQLStatement→Rezoom.SQL.Compiler.ColumnTypeRezoom.SQL.Compiler.TSQL.TSQLStatement→Rezoom.SQL.Compiler.CompoundExprCore`2
- Direction
- Rezoom.SQL.Compiler.TSQL uses Rezoom.SQL.Compiler, so a change to Rezoom.SQL.Compiler can break Rezoom.SQL.Compiler.TSQL, while a change to Rezoom.SQL.Compiler.TSQL can't break Rezoom.SQL.Compiler.
- Position
- Below the diagonal: Rezoom.SQL.Compiler.TSQL uses a module listed above it, which is the healthy direction.
39→31 Rezoom.SQL.Compiler.TSQL uses Rezoom.SQL.Compiler.Translators✕
- Connections
- 7 pairs of types, where a type in Rezoom.SQL.Compiler.TSQL uses a type in Rezoom.SQL.Compiler.Translators.
- The types involved
Rezoom.SQL.Compiler.TSQL.TSQLExpression→Rezoom.SQL.Compiler.Translators.DefaultExprTranslatorRezoom.SQL.Compiler.TSQL.TSQLExpression→Rezoom.SQL.Compiler.Translators.ExprTranslationContextRezoom.SQL.Compiler.TSQL.TSQLExpression→Rezoom.SQL.Compiler.Translators.LiteralTranslatorRezoom.SQL.Compiler.TSQL.TSQLExpression→Rezoom.SQL.Compiler.Translators.StatementTranslatorRezoom.SQL.Compiler.TSQL.TSQLLiteral→Rezoom.SQL.Compiler.Translators.DefaultLiteralTranslatorRezoom.SQL.Compiler.TSQL.TSQLStatement→Rezoom.SQL.Compiler.Translators.DefaultStatementTranslatorRezoom.SQL.Compiler.TSQL.TSQLStatement→Rezoom.SQL.Compiler.Translators.ExprTranslator
- Direction
- Rezoom.SQL.Compiler.TSQL uses Rezoom.SQL.Compiler.Translators, so a change to Rezoom.SQL.Compiler.Translators can break Rezoom.SQL.Compiler.TSQL, while a change to Rezoom.SQL.Compiler.TSQL can't break Rezoom.SQL.Compiler.Translators.
- Position
- Below the diagonal: Rezoom.SQL.Compiler.TSQL uses a module listed above it, which is the healthy direction.
40→1 Rezoom.SQL.Provider.TypeGeneration uses ProviderImplementation.ProvidedTypes✕
- Connections
- 3 pairs of types, where a type in Rezoom.SQL.Provider.TypeGeneration uses a type in ProviderImplementation.ProvidedTypes.
- The types involved
Rezoom.SQL.Provider.TypeGeneration.TypeGeneration→ProviderImplementation.ProvidedTypes.ProvidedFieldRezoom.SQL.Provider.TypeGeneration.TypeGeneration→ProviderImplementation.ProvidedTypes.ProvidedMethodRezoom.SQL.Provider.TypeGeneration.TypeGeneration→ProviderImplementation.ProvidedTypes.ProvidedTypeDefinition
- Direction
- Rezoom.SQL.Provider.TypeGeneration uses ProviderImplementation.ProvidedTypes, so a change to ProviderImplementation.ProvidedTypes can break Rezoom.SQL.Provider.TypeGeneration, while a change to Rezoom.SQL.Provider.TypeGeneration can't break ProviderImplementation.ProvidedTypes.
- Position
- Below the diagonal: Rezoom.SQL.Provider.TypeGeneration uses a module listed above it, which is the healthy direction.
40→8 Rezoom.SQL.Provider.TypeGeneration uses Rezoom.SQL.Mapping✕
- Connections
- 1 pair of types, where a type in Rezoom.SQL.Provider.TypeGeneration uses a type in Rezoom.SQL.Mapping.
- The types involved
Rezoom.SQL.Provider.TypeGeneration.TypeGeneration→Rezoom.SQL.Mapping.CommandFragment
- Direction
- Rezoom.SQL.Provider.TypeGeneration uses Rezoom.SQL.Mapping, so a change to Rezoom.SQL.Mapping can break Rezoom.SQL.Provider.TypeGeneration, while a change to Rezoom.SQL.Provider.TypeGeneration can't break Rezoom.SQL.Mapping.
- Position
- Below the diagonal: Rezoom.SQL.Provider.TypeGeneration uses a module listed above it, which is the healthy direction.
40→12 Rezoom.SQL.Provider.TypeGeneration uses Rezoom.SQL.Compiler.Config✕
- Connections
- 1 pair of types, where a type in Rezoom.SQL.Provider.TypeGeneration uses a type in Rezoom.SQL.Compiler.Config.
- The types involved
Rezoom.SQL.Provider.TypeGeneration.TypeGeneration→Rezoom.SQL.Compiler.Config.Config
- Direction
- Rezoom.SQL.Provider.TypeGeneration uses Rezoom.SQL.Compiler.Config, so a change to Rezoom.SQL.Compiler.Config can break Rezoom.SQL.Provider.TypeGeneration, while a change to Rezoom.SQL.Provider.TypeGeneration can't break Rezoom.SQL.Compiler.Config.
- Position
- Below the diagonal: Rezoom.SQL.Provider.TypeGeneration uses a module listed above it, which is the healthy direction.
40→15 Rezoom.SQL.Provider.TypeGeneration uses Rezoom.SQL.Compiler✕
- Connections
- 9 pairs of types, where a type in Rezoom.SQL.Provider.TypeGeneration uses a type in Rezoom.SQL.Compiler.
- The types involved
Rezoom.SQL.Provider.TypeGeneration.GenerateType→Rezoom.SQL.Compiler.UserModelRezoom.SQL.Provider.TypeGeneration.TypeGeneration→Rezoom.SQL.Compiler.BindParameterRezoom.SQL.Provider.TypeGeneration.TypeGeneration→Rezoom.SQL.Compiler.ColumnTypeRezoom.SQL.Provider.TypeGeneration.TypeGeneration→Rezoom.SQL.Compiler.CommandEffectRezoom.SQL.Provider.TypeGeneration.TypeGeneration→Rezoom.SQL.Compiler.IBackendRezoom.SQL.Provider.TypeGeneration.TypeGeneration→Rezoom.SQL.Compiler.IParameterIndexerRezoom.SQL.Provider.TypeGeneration.TypeGeneration→Rezoom.SQL.Compiler.QualifiedObjectNameRezoom.SQL.Provider.TypeGeneration.TypeGeneration→Rezoom.SQL.Compiler.QueryExprInfo`1Rezoom.SQL.Provider.TypeGeneration.TypeGeneration→Rezoom.SQL.Compiler.UserModel
- Direction
- Rezoom.SQL.Provider.TypeGeneration uses Rezoom.SQL.Compiler, so a change to Rezoom.SQL.Compiler can break Rezoom.SQL.Provider.TypeGeneration, while a change to Rezoom.SQL.Provider.TypeGeneration can't break Rezoom.SQL.Compiler.
- Position
- Below the diagonal: Rezoom.SQL.Provider.TypeGeneration uses a module listed above it, which is the healthy direction.
40→35 Rezoom.SQL.Provider.TypeGeneration uses Rezoom.SQL.Provider✕
- Connections
- 1 pair of types, where a type in Rezoom.SQL.Provider.TypeGeneration uses a type in Rezoom.SQL.Provider.
- The types involved
Rezoom.SQL.Provider.TypeGeneration.TypeGeneration→Rezoom.SQL.Provider.CompileTimeColumnMap
- Direction
- Rezoom.SQL.Provider.TypeGeneration uses Rezoom.SQL.Provider, so a change to Rezoom.SQL.Provider can break Rezoom.SQL.Provider.TypeGeneration, while a change to Rezoom.SQL.Provider.TypeGeneration can't break Rezoom.SQL.Provider.
- Position
- Below the diagonal: Rezoom.SQL.Provider.TypeGeneration 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 — Domain Modelling
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 2 | High / Critical |
Roadmap
Top priorities: Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.); Log through `ILogger` (Microsoft.Extensions.Logging, or Serilog with a JSON sink) at meaningful points in the programs and services you run; Replace each EnsureCreated() in production code with the migrations the rest of the repository already uses (`Database.Migrate()` or a migrations bundle), so every database gets its schema from the one versioned path.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.). | +9.8 pts | Medium | Data Protection |
| Log through `ILogger` (Microsoft.Extensions.Logging, or Serilog with a JSON sink) at meaningful points in the programs and services you run. | +4.8 pts | Medium | Observability |
| Replace each EnsureCreated() in production code with the migrations the rest of the repository already uses (`Database.Migrate()` or a migrations bundle), so every database gets its schema from the one versioned path. | +3.2 pts | Medium | Schema migrations |
| Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. | +1.4 pts | Low | Documentation Quality |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +2.3 pts | Medium | Architecture documentation |
| Resolve the 3 NoWarnInCsproj finding(s) in Explicit Debt — start with Rezoom.SQL.Provider.Postgres.csproj, Rezoom.SQL.Provider.SQLite.csproj, Rezoom.SQL.Provider.TSQL.csproj. | +1.0 pts | Low | Explicit Debt |
| 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. | +0.7 pts | Medium | Documentation (README) |
| Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with Rezoom.SQL.Annotations.csproj. | +0.1 pts | Low | Project Cohesion |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| src/Rezoom.SQL.Provider/ProvidedTypes.fs | 5.7 | Mixed | Cyclomatic Complexity: UncheckedQuotations.|ShapeCombinationUnchecked|ShapeVarUnchecked|ShapeLambdaUnchecked| (cyclomatic 42) |
| src/Rezoom.SQL.Compiler/ASTMapping.fs | 7.0 | Mixed | God Classes: TooManyMethods: ASTMapping`4 |
| src/Rezoom.SQL.Compiler/TypeChecker.fs | 7.1 | Mixed | Cyclomatic Complexity: TypeChecker.ResultColumn (cyclomatic 18) |
| src/Rezoom.SQL.Provider.Postgres/Rezoom.SQL.Provider.Postgres.csproj | 7.6 | Mixed | Explicit Debt: NoWarnInCsproj |
| src/Rezoom.SQL.Provider.SQLite/Rezoom.SQL.Provider.SQLite.csproj | 7.6 | Mixed | Explicit Debt: NoWarnInCsproj |
| src/Rezoom.SQL.Provider.TSQL/Rezoom.SQL.Provider.TSQL.csproj | 7.6 | Mixed | Explicit Debt: NoWarnInCsproj |
| src/Rezoom.SQL.Compiler/AggregateChecker.fs | 7.8 | Mixed | Cyclomatic Complexity: AggregateChecker.aggReferences (cyclomatic 25) |
| src/Rezoom.SQL.Compiler/InferredTypes.fs | 7.8 | Mixed | Cyclomatic Complexity: InferredFromClause.ResolveColumnReference (cyclomatic 18) |
| src/Rezoom.SQL.Mapping/StaticEntityReaderTemplate.fs | 7.8 | Mixed | Cyclomatic Complexity: StaticEntityReaderTemplate.ImplementComposite (cyclomatic 18) |
| src/Rezoom.SQL.Provider/TypeGeneration.fs | 7.8 | Mixed | Cyclomatic Complexity: TypeGeneration.generateRowTypeFromColumns (cyclomatic 16) |
| src/Rezoom.SQL.Mapping/CommandBatch.fs | 7.8 | Mixed | Cognitive Complexity: CommandBatchBuilder.EvaluateAsync (cognitive 35) |
| src/Rezoom.SQL.Compiler/ModelOps.fs | 7.8 | Mixed | Cognitive Complexity: ModelOps.dropColumn (cognitive 28) |
| src/Rezoom.SQL.Mapping/BlueprintModule.fs | 7.8 | Mixed | Cognitive Complexity: BlueprintModule.pickIdentity (cognitive 22) |
| src/Rezoom.SQL.Compiler/DefaultStatementTranslator.fs | 7.8 | Mixed | God Classes: TooManyMethods: DefaultStatementTranslator |
| src/Rezoom.SQL.Compiler/DefaultBackend.fs | 7.8 | Mixed | Change Coupling: Change coupling: DefaultBackend.fs ↔ SQLite.fs |
| src/Rezoom.SQL.Mapping/UserTypeAnnotations.fs | 8.5 | Near-clean | Cognitive Complexity: UserTypeAnnotations.readMember (cognitive 26) |
| src/Rezoom.SQL.Compiler/TypeInferenceContext.fs | 8.5 | Near-clean | Cognitive Complexity: TypeInferenceExtensions.ITypeInferenceContext.Function (cognitive 23) |
| src/Rezoom.SQL.Compiler/Utilities.fs | 8.5 | Near-clean | Cognitive Complexity: Utilities.appendDicts (cognitive 21) |
| src/Rezoom.SQL.Mapping/PrimitiveConverters.fs | 8.5 | Near-clean | Cognitive Complexity: PrimitiveConverters.genericConverter (cognitive 20) |
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 44 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 44 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, 62 of 68 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
- D4 Code Duplication — 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. Code Duplication couldn't be assessed within its 6-minute budget on a solution this large — not included in 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 16 test(s) behind this row are the ones the C# collector could read, and this repository also carries at least 59 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.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT MEASURED: the test run produced no results for any test tier, so no test ever ran and flakiness could not be exercised. The cause could not be attributed, so it is excluded from the score rather than read as an absence of tests.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: src/Rezoom.SQL.Provider.Tests/Rezoom.SQL.Provider.Test.csproj : error NU1605: Warning As Error: Detected package downgrade: FSharp.Core from 10.1.400 to 10.1.300. Reference the package directly from the project to select a different version. [/tm….
- D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems), but the licence verdict published here was taken over its NuGet package dependencies. Nothing was read about its Bundler dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- 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/Rezoom.SQL.Provider/TypeGeneration.fs, src/Rezoom.SQL.Compiler/InferredTypes.fs, src/Rezoom.SQL.Compiler/TypeChecker.fs, src/Rezoom.SQL.Provider/ProvidedTypes.fs, src/Rezoom.SQL.Mapping/StaticEntityReaderTemplate.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.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (4 contributor(s) across 1043 commit(s) sampled, automation and bot accounts excluded). One of them holds 98% of the history; the other 3 hold 0.7% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- 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/Rezoom.SQL.Mapping/Rezoom.SQL.Mapping.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 3 deducted marker(s) and the 1.0/KLoC density on this row were taken over this repository's .NET projects ALONE: .fs (29,188 lines, 92% 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.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- 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.
- D23 Boundary Type-Coupling — 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. Large codebase (32,675 production LoC in the .NET projects) with no declared bounded contexts — cross-boundary type coupling is unassessed Bounded contexts cannot be inferred from a codebase that is not physically organised by them (D-321), so with none declared there are no boundaries for the coupling pass to measure across. You can widen what we reach: name this codebase's bounded contexts (≥2 module groups, e.g. per subsystem) so cross-boundary type coupling can be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- 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.
- D28 Secrets (history) — 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. D28's config-credential rule (WD-SECRET-0002) parses each committed `.json` config as a document and reads credential-named values; `src/TypeProviderUsers/TypeProviderUser.SQLite/rzsql.json` did not parse (JSON5, a template, several concatenated documents), so a credential bound there is UNMEASURED by that rule. gitleaks still scanned the same files as text.
- D30 Dependency Vulnerabilities — measured, with a gap in what it reached — 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 solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan. 1 of 2 declared ecosystem(s) (osv) WERE scanned and every vulnerability they reported is included in this result; nuget was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that nuget is free of known-vulnerable dependencies.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `demos/SQLFiddle/SQLFiddle.Website/Controllers/FiddleApiController.cs` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- DM8 Value-object opportunities — 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 finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- DM9 Scattered domain decisions — 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. Some of this repository's production types come from a frontend that does not bind comparison operands to the members they read, which arm one needs, and those types were not walked for this dimension. The counts above speak for the languages that declare it.
- 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.
- 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's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X18 Disposal-pattern correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X27 Collection changed while being enumerated — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- 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's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- Package restore incomplete — third-party types were unresolved in part of the solution — NuGet restore did not complete for src/Rezoom.SQL.Provider.Tests/Rezoom.SQL.Provider.Test.csproj, so those projects were analysed with framework references only: every check keyed on a third-party type saw an error type there and reported nothing. Findings on those projects are a lower bound; run `dotnet restore` on them and rescan.
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.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- 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.
- DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
- M4 Documentation accuracy: 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.
- 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
7 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was UncheckedQuotations.|ShapeCombinationUnchecked|ShapeVarUnchecked|ShapeLambdaUnchecked| at 42. A further 11 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 CoreColumnType.ToString at 23 — they are counted neither in the figure above nor in this dimension's score. 6 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/Rezoom.SQL.Compiler/TypeSystem.fs (CoreColumnType.ToString at 23), src/Rezoom.SQL.Compiler/DefaultExprTranslator.fs (DefaultExprTranslator.BinaryOperator at 21), src/Rezoom.SQL.Compiler/Postgres.fs (PostgresExpression.BinaryOperator at 21), src/Rezoom.SQL.Compiler/TSQL.Expression.fs (TSQLExpression.BinaryOperator at 19), src/Rezoom.SQL.Compiler/AST.fs (TypeName.ToString at 17), and 1 more not listed here. 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 1 body over 30 down to 30 or less in Cyclomatic Complexity — start with UncheckedQuotations.|ShapeCombinationUnchecked|ShapeVarUnchecked|ShapeLambdaUnchecked| (cyclomatic 42). — Refactoring it lifts Cyclomatic Complexity from 8.4 to about 8.7/10.
D2 · Cognitive Complexity
22 method(s) exceeded the cognitive complexity threshold of 15; the worst was UncheckedQuotations.|ShapeCombinationUnchecked|ShapeVarUnchecked|ShapeLambdaUnchecked| at 59.
What to do
- Bring the 3 bodies over 30 down to 30 or less in Cognitive Complexity — start with UncheckedQuotations.|ShapeCombinationUnchecked|ShapeVarUnchecked|ShapeLambdaUnchecked| (cognitive 59), CommandBatchBuilder.EvaluateAsync (cognitive 35), CommandBatchBuilder.EvaluateSync (cognitive 35). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cognitive Complexity from 6.8 to about 7.5/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
D3 · God Classes
10 god class(es) detected.
What to do
- Resolve the 5 TooManyMethods finding(s) in God Classes — start with ASTMapping.fs, TypeChecker.fs, DefaultStatementTranslator.fs. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 4 FileTooLong finding(s) in God Classes — start with ProvidedTypes.fs, TypeChecker.fs, AST.fs. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 1 TooManyFunctions finding(s) in God Classes — start with Error.fs. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
9 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D6 · Cohesion (LCOM4)
1 of 40 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with ProvidedTypes.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 16 tests. Measured on the C# suite only — at least 59 test source file(s) (.fs) went unread, so its test quality is unmeasured and is not in these counts.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 235 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 28 direct `PackageReference`(s), and 162 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution. ★ COVERAGE OF THIS VERDICT: it grades this repository's NuGet package dependencies and nothing else. The repository also declares a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems), and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D15 · Churn × Complexity Hotspots
Top hotspots: src/Rezoom.SQL.Provider/TypeGeneration.fs (21×16=336); src/Rezoom.SQL.Provider/ProvidedTypes.fs (3×42=126); demos/FileSystem/FileSystem/Program.fs (5×25=125)
What to do
- Resolve the 6 Hotspot finding(s) in Churn × Complexity Hotspots — start with TypeGeneration.fs, ProvidedTypes.fs, Program.fs. — One of this dimension's main actionable groups (6 warning-level).
D17 · Explicit Debt
3 deducted debt markers + unmeasured dead symbols across 1152 LoC in the .NET projects (1.0/KLoC) → score 8.1. Dead code not measured: the solution did not load cleanly, so the reference search was skipped. Measured on the .NET source only: .fs (92% of production source) was not read, and carries at least 0 uncounted task marker(s) in 0 file(s).
What to do
- Resolve the 3 NoWarnInCsproj finding(s) in Explicit Debt — start with Rezoom.SQL.Provider.Postgres.csproj, Rezoom.SQL.Provider.SQLite.csproj, Rezoom.SQL.Provider.TSQL.csproj. — One of this dimension's main actionable groups (3 issue-level).
D19 · Documentation Quality
1 of 2 documentation facets pass in full; short on: F2 example. 58 document(s) read across 7 unit(s).
D26 · Project Cohesion
1 of 7 projects flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with Rezoom.SQL.Annotations.csproj. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
87 % of calls cross a namespace and 1 % 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)
2 finding(s): 0 critical, 2 high, 0 medium, 0 low. 2 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 2 file(s) — `demos/SQLFiddle/SQLFiddle.Website/Controllers/FiddleApiController.cs` (line 11), `demos/SQLFiddle/SQLFiddle.Website/wwwroot/Scripts/ace.js` — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. In 1 of those file(s) — `demos/SQLFiddle/SQLFiddle.Website/Controllers/FiddleApiController.cs` — the break is a C# primary constructor, which semgrep's grammar cannot parse and which hides the type from every rule scoped to it; those files were re-scanned from a shadow copy with the constructor's parameter list blanked (line and column preserving), which restores the type to the rules, and 0 additional row(s) came from that pass. Only the header's own parameter list is unread in them.
What to do
- No action in Static Analysis (SAST) — all 2 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 (2 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in the 1 ecosystem(s) that were scanned (osv). No known-vulnerable gem among the 3 declared gem(s) osv.dev was asked about. This repository commits no Gemfile.lock — which a published gem correctly does not — so osv-scanner had no resolved graph to read, and the question was put to osv.dev instead over the releases `bundle install` resolves this repository's 3 declared requirement(s) to. The verdict therefore covers the DIRECT declarations at their resolved releases, not the transitive graph a lock would close over. Partial dependency scan: 1 of 2 declared ecosystem(s) were scanned (osv), and the findings above are real and complete for them. nuget was not scanned (nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan), so this is not the whole dependency surface and the result is reported at reduced confidence.
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 85 of the 119 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
Strongest change-coupling: DefaultBackend.fs↔SQLite.fs 91%; ASTMapping.fs↔TypeChecker.fs 86%; DefaultBackend.fs↔TSQL.fs 82%
What to do
- Resolve the 4 Change coupling finding(s) in Change Coupling — start with DefaultBackend.fs (2), ASTMapping.fs, CompositeColumnGenerator.fs. — One of this dimension's main actionable groups (4 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious. No known-vulnerable gem among the 3 declared gem(s) osv.dev was asked about. This repository commits no Gemfile.lock — which a published gem correctly does not — so osv-scanner had no resolved graph to read, and the question was put to osv.dev instead over the releases `bundle install` resolves this repository's 3 declared requirement(s) to. The verdict therefore covers the DIRECT declarations at their resolved releases, not the transitive graph a lock would close over.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 21 platform declaration(s) and 3 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
AX5 · Architecture & structure
AX8 · Test isolation
C1 · Data Protection
- No data-protection or encryption usage (ASP.NET Data Protection, AES, column encryption, PBKDF2) was found — sensitive data at rest may be unprotected. If TDE/KMS/vault is delegated to infrastructure, ignore.
What to do
- Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.).
- Enforce HTTPS (UseHttpsRedirection / RequireHttpsMetadata) so data in transit is always encrypted.
DM1 · Aggregate boundaries
DM10 · One transaction, one aggregate
- `DemoSetup.SetUpFolders` saves `Folder`, `File` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event. — demos/FileSystem/FileSystem.EFVersion/DemoSetup.cs:137
What to do
- Mutate one aggregate per operation and let the others follow from a domain event — the second aggregate reaching consistency a moment later is the design, not a compromise.
DM12 · Ambient inputs in the domain
DM6 · Domain ↔ infrastructure boundary
DM9 · Scattered domain decisions
GD1 · Unfinished & placeholder code
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture 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
P10 · Library API & versioning
P2 · Observability
- No logging call was found in the 96 Python, F# production file(s) this check read across 8 module(s). Each was searched for its ecosystem's logging libraries (Python: logging, structlog, loguru; F#: Microsoft.Extensions.Logging (ILogger), Serilog, NLog, log4net, Logary) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.
What to do
- Log through `ILogger` (Microsoft.Extensions.Logging, or Serilog with a JSON sink) at meaningful points in the programs and services you run.
- Add a health-check endpoint (ASP.NET Core's MapHealthChecks, or a /health route in your Giraffe/Suave app) so orchestrators and load balancers can probe liveness/readiness.
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 1 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:6
- `demos/FileSystem/FileSystem.EFVersion/FileSystem.EFVersion.csproj` 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`. — demos/FileSystem/FileSystem.EFVersion/FileSystem.EFVersion.csproj:15
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.
P6 · Release Hygiene
P8 · Schema migrations
- This repository evolves its schema with versioned migrations, but `EnsureCreated()` here builds a schema straight from the model instead — with no migrations-history row, so a database it creates can't be upgraded by `Migrate()` afterwards and the two paths can disagree about the shape. Apply the migrations here (`Migrate()` / a migrations bundle) rather than creating the schema. — demos/FileSystem/FileSystem.EFVersion/DemoSetup.cs:111
What to do
- Replace each EnsureCreated() in production code with the migrations the rest of the repository already uses (`Database.Migrate()` or a migrations bundle), so every database gets its schema from the one versioned path.
PF3 · Async & latency hygiene
X5 · Nullable reference types
- ~1.2 `!` suppressions per 1k syntax nodes — 8 suppression(s) across the 6424 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
What to do
- Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 83% | Strong | Solid. |
| Architecture | 94% | Exemplary | Solid. |
| Maturity | 72% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 40% | Weak — gated by P2, P3, P8 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 43% | Weak — gated by C1 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 94% | Exemplary | Solid. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 2 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Not evidenced — 5 control(s) we could not find positive evidence for
- C3 Audit Trail — Repo shows no audit-logging mechanism (IAuditable, an immutable audit log, an EF SaveChanges interceptor) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
- C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, so this dimension can be scored.
- C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 78 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 — AX1 reached only 4% of this repository's production lines — fsharp (30,301 lines), python (1,222 lines), javascript (230 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- AX2 Stateful singletons — no singleton implementations detected
- AX6 Interface segregation — no public interfaces
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C2 Access Controls — No access-control surface detected in the analyzed source — no web/app surface to authorize (no HTTP API or web-UI project) and no authorization code at all (no [Authorize]/policies, no imperative guard methods). Access control is therefore N/A here — this is a library/CLI, which is authorized by its CALLER, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- D11 Test Reliability — Test reliability not measured — no test run produced results
- D12 Dependency Hygiene — Dependency hygiene not measured
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution, but this repository's production source is mostly .fs, .py, 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#, Python not measured.
- D22 Internal API Consistency — N/A — too few peer members to establish a convention across 3 exposed C# types.
- D23 Boundary Type-Coupling — Cross-context type coupling could not be assessed — this codebase's bounded contexts are neither declared nor inferable.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .fs, .py source were not judged.
- D25 ADR Conformance — no ADRs to check
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 1 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D4 Code Duplication — Code Duplication not included (time budget)
- 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.
- 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
- DM11 Constructible invalid state — no entities detected — construction-time invariants not assessable
- DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
- DM3 Integration-event coupling — no integration events detected — coupling check not applicable
- DM4 Rich vs anemic model — no data-bearing entities detected — rich-vs-anemic model not assessable
- DM5 Encapsulated state — no domain entities found — DM5 grades how entities protect their state, and this repository declares none
- DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
- DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show 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'.
- P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HttpClient/IHttpClientFactory/AddHttpClient in source, and no Refit/RestSharp/Flurl.Http namespace or package reference
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found by the two searches this check runs — a BenchmarkDotNet package reference in any project file (loaded, or on disk), and a script whose name contains `benchmark` that this repository's CI runs. Neither can see a suite in another ecosystem's idiom, so this is not a verdict that the repository has none. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted, and nothing is asked of a repository that has none.
- 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 — No web surface detected in the analyzed source — no HTTP API or web-UI project (no controllers/minimal-API endpoints, no Razor/Blazor views) and no web middleware (HTTPS redirection, HSTS, security headers, cookies). Transport security, security headers, secure cookies, CSRF/input-validation and middleware-order controls are therefore N/A here — this is a library/CLI/worker, not a web app. Crypto hygiene was still checked and found nothing to flag. If this codebase becomes web-facing, the dimension reactivates automatically.
- X1 Async correctness — X1 reached only 4% of this repository's production lines — fsharp (30,301 lines), python (1,222 lines), javascript (230 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — X12 reached only 4% of this repository's production lines — fsharp (30,301 lines), python (1,222 lines), javascript (230 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X16 Unfloored truncation loop — X16 reached only 4% of this repository's production lines — fsharp (30,301 lines), python (1,222 lines), javascript (230 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — X18 reached only 4% of this repository's production lines — fsharp (30,301 lines), python (1,222 lines), javascript (230 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — X2 reached only 4% of this repository's production lines — fsharp (30,301 lines), python (1,222 lines), javascript (230 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- 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 — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X27 Collection changed while being enumerated — X27 reached only 4% of this repository's production lines — fsharp (30,301 lines), python (1,222 lines), javascript (230 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X3 Exception handling — X3 reached only 4% of this repository's production lines — fsharp (30,301 lines), python (1,222 lines), javascript (230 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X4 Structured logging — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 5 finding(s)
- NoWarnInCsproj src/Rezoom.SQL.Provider.Postgres/Rezoom.SQL.Provider.Postgres.csproj:15
- NoWarnInCsproj src/Rezoom.SQL.Provider.SQLite/Rezoom.SQL.Provider.SQLite.csproj:15
- NoWarnInCsproj src/Rezoom.SQL.Provider.TSQL/Rezoom.SQL.Provider.TSQL.csproj:15
- REDACTED
- REDACTED
Serious — 56 finding(s)
- Hotspot: src/Rezoom.SQL.Provider/TypeGeneration.fs src/Rezoom.SQL.Provider/TypeGeneration.fs:109
- Hotspot: src/Rezoom.SQL.Provider/ProvidedTypes.fs src/Rezoom.SQL.Provider/ProvidedTypes.fs:525
- Hotspot: demos/FileSystem/FileSystem/Program.fs demos/FileSystem/FileSystem/Program.fs:93
- Hotspot: src/Rezoom.SQL.Mapping/StaticEntityReaderTemplate.fs src/Rezoom.SQL.Mapping/StaticEntityReaderTemplate.fs:132
- Hotspot: src/Rezoom.SQL.Compiler/TypeChecker.fs src/Rezoom.SQL.Compiler/TypeChecker.fs:105
- Hotspot: src/Rezoom.SQL.Compiler/InferredTypes.fs src/Rezoom.SQL.Compiler/InferredTypes.fs:207
- TooManyMethods: ASTMapping`4 src/Rezoom.SQL.Compiler/ASTMapping.fs:5
- TooManyMethods: TypeChecker src/Rezoom.SQL.Compiler/TypeChecker.fs:20
- TooManyMethods: DefaultStatementTranslator src/Rezoom.SQL.Compiler/DefaultStatementTranslator.fs:6
- TooManyMethods: StatementTranslator src/Rezoom.SQL.Compiler/Translators.fs:34
- TooManyMethods: ReferenceFinder src/Rezoom.SQL.Compiler/ReadWriteReferences.fs:10
- FileTooLong: Rezoom.SQL.Provider/ProvidedTypes.fs src/Rezoom.SQL.Provider/ProvidedTypes.fs
- FileTooLong: Rezoom.SQL.Compiler/TypeChecker.fs src/Rezoom.SQL.Compiler/TypeChecker.fs
- FileTooLong: Rezoom.SQL.Compiler/AST.fs src/Rezoom.SQL.Compiler/AST.fs
- FileTooLong: Rezoom.SQL.Compiler/DefaultStatementTranslator.fs src/Rezoom.SQL.Compiler/DefaultStatementTranslator.fs
- Change coupling: DefaultBackend.fs ↔ SQLite.fs src/Rezoom.SQL.Compiler/DefaultBackend.fs:1
- Change coupling: ASTMapping.fs ↔ TypeChecker.fs src/Rezoom.SQL.Compiler/ASTMapping.fs:1
- Change coupling: DefaultBackend.fs ↔ TSQL.fs src/Rezoom.SQL.Compiler/DefaultBackend.fs:1
- Change coupling: CompositeColumnGenerator.fs ↔ ManyColumnGenerator.fs src/Rezoom.SQL.Mapping/CompositeColumnGenerator.fs:1
- No data-protection/encryption
- UncheckedQuotations.|ShapeCombinationUnchecked|ShapeVarUnchecked|ShapeLambdaUnchecked| (cyclomatic 42) src/Rezoom.SQL.Provider/ProvidedTypes.fs:525
- AggregateChecker.aggReferences (cyclomatic 25) src/Rezoom.SQL.Compiler/AggregateChecker.fs:74
- TypeChecker.ResultColumn (cyclomatic 18) src/Rezoom.SQL.Compiler/TypeChecker.fs:105
- InferredFromClause.ResolveColumnReference (cyclomatic 18) src/Rezoom.SQL.Compiler/InferredTypes.fs:207
- StaticEntityReaderTemplate.ImplementComposite (cyclomatic 18) src/Rezoom.SQL.Mapping/StaticEntityReaderTemplate.fs:132
- TypeChecker.SelectCore (cyclomatic 17) src/Rezoom.SQL.Compiler/TypeChecker.fs:222
- TypeGeneration.generateRowTypeFromColumns (cyclomatic 16) src/Rezoom.SQL.Provider/TypeGeneration.fs:109
- UncheckedQuotations.|ShapeCombinationUnchecked|ShapeVarUnchecked|ShapeLambdaUnchecked| (cognitive 59) src/Rezoom.SQL.Provider/ProvidedTypes.fs:525
- CommandBatchBuilder.EvaluateAsync (cognitive 35) src/Rezoom.SQL.Mapping/CommandBatch.fs:236
- CommandBatchBuilder.EvaluateSync (cognitive 35) src/Rezoom.SQL.Mapping/CommandBatch.fs:195
- ModelOps.dropColumn (cognitive 28) src/Rezoom.SQL.Compiler/ModelOps.fs:291
- UserTypeAnnotations.readMember (cognitive 26) src/Rezoom.SQL.Mapping/UserTypeAnnotations.fs:58
- StaticEntityReaderTemplate.ImplementComposite (cognitive 25) src/Rezoom.SQL.Mapping/StaticEntityReaderTemplate.fs:132
- TypeInferenceExtensions.ITypeInferenceContext.Function (cognitive 23) src/Rezoom.SQL.Compiler/TypeInferenceContext.fs:211
- InferredFromClause.ResolveColumnReference (cognitive 23) src/Rezoom.SQL.Compiler/InferredTypes.fs:207
- BlueprintModule.pickIdentity (cognitive 22) src/Rezoom.SQL.Mapping/BlueprintModule.fs:50
- TypeChecker.ResultColumn (cognitive 21) src/Rezoom.SQL.Compiler/TypeChecker.fs:105
- Utilities.appendDicts (cognitive 21) src/Rezoom.SQL.Compiler/Utilities.fs:94
- TypeChecker.SelectCore (cognitive 20) src/Rezoom.SQL.Compiler/TypeChecker.fs:222
- PrimitiveConverters.genericConverter (cognitive 20) src/Rezoom.SQL.Mapping/PrimitiveConverters.fs:322
- BlueprintModule.cardinalityOfType (cognitive 20) src/Rezoom.SQL.Mapping/BlueprintModule.fs:166
- InterfaceImpls.implementInterface (cognitive 20) src/Rezoom.SQL.Provider/InterfaceImpls.fs:54
- BackendBase.ParameterTransform (cognitive 19) src/Rezoom.SQL.Compiler/Backend.fs:44
- ModelOps.addConstraint (cognitive 18) src/Rezoom.SQL.Compiler/ModelOps.fs:166
- MigrationUtilities.runMigrations (cognitive 18) src/Rezoom.SQL.Mapping/Migrations.fs:170
- TypeGeneration.generateRowTypeFromColumns (cognitive 17) src/Rezoom.SQL.Provider/TypeGeneration.fs:109
- AggregateChecker.aggReferences (cognitive 16) src/Rezoom.SQL.Compiler/AggregateChecker.fs:74
- FunctionType.ValidateArgs (cognitive 16) src/Rezoom.SQL.Compiler/TypeSystem.fs:248
- ProvidedTypeDefinition.AddAssemblyTypesAsNestedTypesDelayed (cognitive 16) src/Rezoom.SQL.Provider/ProvidedTypes.fs:1832
- TooManyFunctions: Error src/Rezoom.SQL.Compiler/Error.fs:1
- REDACTED
- Low cohesion: TypeProviderForNamespaces (LCOM4 4) src/Rezoom.SQL.Provider/ProvidedTypes.fs:16158
- One operation mutates 2 aggregates: DemoSetup.SetUpFolders demos/FileSystem/FileSystem.EFVersion/DemoSetup.cs:137
- No structured logging
- Schema created with EnsureCreated() outside the migrations demos/FileSystem/FileSystem.EFVersion/DemoSetup.cs:111
- NuGet dependencies are not locked
Minor — 7 finding(s)
- Documentation: no build, run or usage example src/Rezoom.SQL.Annotations/README.md:1
- Projects may be oversized for their cohesion src/Rezoom.SQL.Annotations/Rezoom.SQL.Annotations.csproj:1
- REDACTED
- No ADRs
- No SAST REDACTED:6
- No dependency-update automation demos/FileSystem/FileSystem.EFVersion/FileSystem.EFVersion.csproj:15
- Null-forgiving operator (`!`) suppressions override nullable warnings
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-ac58add5fa7c4fa38b5fc9cefaea81a3/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-ac58add5fa7c4fa38b5fc9cefaea81a3/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 . | 2 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | nuget | — | nuget: not applicable — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan | 0 | — |
| 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. semgrep could not parse 1 file(s) — `demos/SQLFiddle/SQLFiddle.Website/Controllers/FiddleApiController.cs` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D37 · Vulnerability-disclosure 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 | — |
Appendix C — Personal-data map
Email — 1 field(s)
- User.Email demos/FileSystem/FileSystem.EFVersion/Entities.cs:7