Executive summary
JordanMarr/SqlHydra is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back 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 55 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 35, is the weakest lens and counts most in the score. The best first step for the work it takes is recording design decisions, worth about 5 points. Adding a diagnostic log would lift Production Readiness itself, worth about 7 points. Raising Production Readiness to 70 would lift the score to about 69.
Six known security holes in the packages the code depends on can be used by attackers. Five pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and one package carries licence risk. Updating the vulnerable packages, pinning each tool to an exact version and replacing or clearing the banned-licence packages would close these risks.
The product code is 13,804 lines, about €72,000 to rebuild.
If Production Readiness rose from 35 to 70, the lowest score rated Strong, the score would rise from 55 to about 69.
New since the last survey: 3 findings
- Code Duplication · Edited copy of a member (103 corresponding lines) src/SqlHydra.Query/SqlServerExtensions.fs
- Code Duplication · Edited copy of a member (81 corresponding lines) src/SqlHydra.Query/MySqlExtensions.fs
- Code Duplication · Edited copies of one member (3 members, 52+ corresponding lines) src/SampleApp/DapperExample.fs
Fixed since the last survey: 10 findings
- Code Duplication · Duplicated block (3–8 lines × 3) src/SqlHydra.Query/SelectBuilders.fs
- Code Duplication · Duplicated block (6 lines × 2) src/SqlHydra.Query/NpgsqlExtensions.fs
- Code Coverage · Coverage not measured — no coverage collector is wired up
- Secret Scanning · Leaked secret: hardcoded-credential src/SampleApp/sqlhydra-mssql.toml
- Secret Scanning · Leaked secret: hardcoded-credential src/SampleApp/ReaderExample.fs
- Secret Scanning · Leaked secret: hardcoded-credential src/SampleApp/DonaldExample.fs
- Secret Scanning · Leaked secret: hardcoded-credential src/SampleApp/DapperFSharpExample.fs
- Secret Scanning · Leaked secret: hardcoded-credential src/SampleApp/DapperExample.fs
- Secret Scanning · Leaked secret: hardcoded-credential REDACTED
- Secret Scanning · Leaked secret: hardcoded-credential REDACTED
Rebuild cost: about €72,000 · Estimate
| Cost to rebuild | €24,000 to €120,000, for 397 to 1,260 hours of work, about 0.5 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 55. 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 | Small: 13,804 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 SqlHydra.Domain | 2 SqlHydra.Query.AtLeastOne | 3 SqlHydra.Query.ExpressionNormalizer | 4 SqlHydra.Version | 5 SampleApp.AdventureWorks.HumanResources | 6 SampleApp.AdventureWorks.Person | 7 SampleApp.AdventureWorks.Production | 8 SampleApp.AdventureWorks.Purchasing | 9 SampleApp.AdventureWorks.Sales | 10 SampleApp.AdventureWorks.dbo | 11 SampleApp.AdventureWorks.ext | 12 SqlHydra.Console | 13 SqlHydra.Extensions | 14 SqlHydra.Fsproj | 15 SqlHydra.MySql.MySqlDataTypes | 16 SqlHydra.MySql.MySqlSchemaProvider | 17 SqlHydra.MySql.Provider | 18 SqlHydra.Npgsql.NpgsqlDataTypes | 19 SqlHydra.Npgsql.NpgsqlSchemaProvider | 20 SqlHydra.Npgsql.Provider | 21 SqlHydra.Oracle.OracleDataTypes | 22 SqlHydra.Oracle.OracleSchemaProvider | 23 SqlHydra.Oracle.Provider | 24 SqlHydra.Program | 25 SqlHydra.Query | 26 SqlHydra.Query.Hydration | 27 SqlHydra.SchemaTemplate | 28 SampleApp.AdventureWorks | 29 SampleApp.DapperExample | 30 SampleApp.DonaldExample | 31 SampleApp.ReaderExample | 32 SqlHydra.Query.FQ | 33 SqlHydra.Query.LinqExpressionVisitors | 34 SqlHydra.Query.SelectBuilders.ResultModifier | 35 SqlHydra.Query.SelectBuilders | 36 SqlHydra.Query.DeleteBuilders | 37 SqlHydra.Query.InsertBuilders | 38 SqlHydra.Query.SelectBuilders.ContextTypeResolver | 39 SqlHydra.Query.SelectBuilders.ContextUtils | 40 SqlHydra.Query.UpdateBuilders |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 SqlHydra.Domain | ||||||||||||||||||||||||||||||||||||||||
| 2 SqlHydra.Query.AtLeastOne | ||||||||||||||||||||||||||||||||||||||||
| 3 SqlHydra.Query.ExpressionNormalizer | ||||||||||||||||||||||||||||||||||||||||
| 4 SqlHydra.Version | ||||||||||||||||||||||||||||||||||||||||
| 5 SampleApp.AdventureWorks.HumanResources | 21 | |||||||||||||||||||||||||||||||||||||||
| 6 SampleApp.AdventureWorks.Person | 19 | |||||||||||||||||||||||||||||||||||||||
| 7 SampleApp.AdventureWorks.Production | 41 | |||||||||||||||||||||||||||||||||||||||
| 8 SampleApp.AdventureWorks.Purchasing | 12 | |||||||||||||||||||||||||||||||||||||||
| 9 SampleApp.AdventureWorks.Sales | 40 | |||||||||||||||||||||||||||||||||||||||
| 10 SampleApp.AdventureWorks.dbo | 5 | |||||||||||||||||||||||||||||||||||||||
| 11 SampleApp.AdventureWorks.ext | 2 | |||||||||||||||||||||||||||||||||||||||
| 12 SqlHydra.Console | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 13 SqlHydra.Extensions | 5 | |||||||||||||||||||||||||||||||||||||||
| 14 SqlHydra.Fsproj | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 SqlHydra.MySql.MySqlDataTypes | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 SqlHydra.MySql.MySqlSchemaProvider | 3 | |||||||||||||||||||||||||||||||||||||||
| 17 SqlHydra.MySql.Provider | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 SqlHydra.Npgsql.NpgsqlDataTypes | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 SqlHydra.Npgsql.NpgsqlSchemaProvider | 3 | |||||||||||||||||||||||||||||||||||||||
| 20 SqlHydra.Npgsql.Provider | 1 | |||||||||||||||||||||||||||||||||||||||
| 21 SqlHydra.Oracle.OracleDataTypes | 2 | |||||||||||||||||||||||||||||||||||||||
| 22 SqlHydra.Oracle.OracleSchemaProvider | 3 | |||||||||||||||||||||||||||||||||||||||
| 23 SqlHydra.Oracle.Provider | 1 | |||||||||||||||||||||||||||||||||||||||
| 24 SqlHydra.Program | 1 | |||||||||||||||||||||||||||||||||||||||
| 25 SqlHydra.Query | 7 | |||||||||||||||||||||||||||||||||||||||
| 26 SqlHydra.Query.Hydration | 2 | |||||||||||||||||||||||||||||||||||||||
| 27 SqlHydra.SchemaTemplate | 6 | 1 | ||||||||||||||||||||||||||||||||||||||
| 28 SampleApp.AdventureWorks | 12 | 15 | 28 | 7 | 26 | 3 | 2 | |||||||||||||||||||||||||||||||||
| 29 SampleApp.DapperExample | 1 | |||||||||||||||||||||||||||||||||||||||
| 30 SampleApp.DonaldExample | 1 | |||||||||||||||||||||||||||||||||||||||
| 31 SampleApp.ReaderExample | 1 | |||||||||||||||||||||||||||||||||||||||
| 32 SqlHydra.Query.FQ | 2 | |||||||||||||||||||||||||||||||||||||||
| 33 SqlHydra.Query.LinqExpressionVisitors | 1 | 4 | ||||||||||||||||||||||||||||||||||||||
| 34 SqlHydra.Query.SelectBuilders.ResultModifier | 6 | |||||||||||||||||||||||||||||||||||||||
| 35 SqlHydra.Query.SelectBuilders | 15 | 7 | ||||||||||||||||||||||||||||||||||||||
| 36 SqlHydra.Query.DeleteBuilders | 10 | 2 | ||||||||||||||||||||||||||||||||||||||
| 37 SqlHydra.Query.InsertBuilders | 1 | 9 | 2 | |||||||||||||||||||||||||||||||||||||
| 38 SqlHydra.Query.SelectBuilders.ContextTypeResolver | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 39 SqlHydra.Query.SelectBuilders.ContextUtils | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 40 SqlHydra.Query.UpdateBuilders | 10 | 2 |
5→28 SampleApp.AdventureWorks.HumanResources uses SampleApp.AdventureWorks part of a loop✕
- Connections
- 21 pairs of types, where a type in SampleApp.AdventureWorks.HumanResources uses a type in SampleApp.AdventureWorks.
- The types involved
SampleApp.AdventureWorks.HumanResources.DepartmentReader→SampleApp.AdventureWorks.RequiredColumn`2SampleApp.AdventureWorks.HumanResources.EmployeeDepartmentHistoryReader→SampleApp.AdventureWorks.OptionalColumn`2SampleApp.AdventureWorks.HumanResources.EmployeeDepartmentHistoryReader→SampleApp.AdventureWorks.RequiredColumn`2SampleApp.AdventureWorks.HumanResources.EmployeePayHistoryReader→SampleApp.AdventureWorks.RequiredColumn`2SampleApp.AdventureWorks.HumanResources.EmployeeReader→SampleApp.AdventureWorks.OptionalColumn`2SampleApp.AdventureWorks.HumanResources.EmployeeReader→SampleApp.AdventureWorks.RequiredColumn`2SampleApp.AdventureWorks.HumanResources.JobCandidateReader→SampleApp.AdventureWorks.OptionalColumn`2SampleApp.AdventureWorks.HumanResources.JobCandidateReader→SampleApp.AdventureWorks.RequiredColumn`2SampleApp.AdventureWorks.HumanResources.ShiftReader→SampleApp.AdventureWorks.RequiredColumn`2SampleApp.AdventureWorks.HumanResources.vEmployeeDepartmentHistoryReader→SampleApp.AdventureWorks.OptionalColumn`2SampleApp.AdventureWorks.HumanResources.vEmployeeDepartmentHistoryReader→SampleApp.AdventureWorks.RequiredColumn`2SampleApp.AdventureWorks.HumanResources.vEmployeeDepartmentReader→SampleApp.AdventureWorks.OptionalColumn`2SampleApp.AdventureWorks.HumanResources.vEmployeeDepartmentReader→SampleApp.AdventureWorks.RequiredColumn`2SampleApp.AdventureWorks.HumanResources.vEmployeeReader→SampleApp.AdventureWorks.OptionalColumn`2SampleApp.AdventureWorks.HumanResources.vEmployeeReader→SampleApp.AdventureWorks.RequiredColumn`2SampleApp.AdventureWorks.HumanResources.vJobCandidateEducationReader→SampleApp.AdventureWorks.OptionalColumn`2SampleApp.AdventureWorks.HumanResources.vJobCandidateEducationReader→SampleApp.AdventureWorks.RequiredColumn`2SampleApp.AdventureWorks.HumanResources.vJobCandidateEmploymentReader→SampleApp.AdventureWorks.OptionalColumn`2SampleApp.AdventureWorks.HumanResources.vJobCandidateEmploymentReader→SampleApp.AdventureWorks.RequiredColumn`2SampleApp.AdventureWorks.HumanResources.vJobCandidateReader→SampleApp.AdventureWorks.OptionalColumn`2SampleApp.AdventureWorks.HumanResources.vJobCandidateReader→SampleApp.AdventureWorks.RequiredColumn`2
- Direction
- SampleApp.AdventureWorks.HumanResources uses SampleApp.AdventureWorks, so a change to SampleApp.AdventureWorks can break SampleApp.AdventureWorks.HumanResources, while a change to SampleApp.AdventureWorks.HumanResources can't break SampleApp.AdventureWorks.
- 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→28 SampleApp.AdventureWorks.Person uses SampleApp.AdventureWorks part of a loop✕
- Connections
- 19 pairs of types, where a type in SampleApp.AdventureWorks.Person uses a type in SampleApp.AdventureWorks.
- The types involved
SampleApp.AdventureWorks.Person.AddressReader→SampleApp.AdventureWorks.OptionalColumn`2SampleApp.AdventureWorks.Person.AddressReader→SampleApp.AdventureWorks.RequiredColumn`2SampleApp.AdventureWorks.Person.AddressTypeReader→SampleApp.AdventureWorks.RequiredColumn`2SampleApp.AdventureWorks.Person.BusinessEntityAddressReader→SampleApp.AdventureWorks.RequiredColumn`2SampleApp.AdventureWorks.Person.BusinessEntityContactReader→SampleApp.AdventureWorks.RequiredColumn`2SampleApp.AdventureWorks.Person.BusinessEntityReader→SampleApp.AdventureWorks.RequiredColumn`2SampleApp.AdventureWorks.Person.ContactTypeReader→SampleApp.AdventureWorks.RequiredColumn`2SampleApp.AdventureWorks.Person.CountryRegionReader→SampleApp.AdventureWorks.RequiredColumn`2SampleApp.AdventureWorks.Person.EmailAddressReader→SampleApp.AdventureWorks.OptionalColumn`2SampleApp.AdventureWorks.Person.EmailAddressReader→SampleApp.AdventureWorks.RequiredColumn`2SampleApp.AdventureWorks.Person.PasswordReader→SampleApp.AdventureWorks.RequiredColumn`2SampleApp.AdventureWorks.Person.PersonPhoneReader→SampleApp.AdventureWorks.RequiredColumn`2SampleApp.AdventureWorks.Person.PersonReader→SampleApp.AdventureWorks.OptionalColumn`2SampleApp.AdventureWorks.Person.PersonReader→SampleApp.AdventureWorks.RequiredColumn`2SampleApp.AdventureWorks.Person.PhoneNumberTypeReader→SampleApp.AdventureWorks.RequiredColumn`2SampleApp.AdventureWorks.Person.StateProvinceReader→SampleApp.AdventureWorks.RequiredColumn`2SampleApp.AdventureWorks.Person.vAdditionalContactInfoReader→SampleApp.AdventureWorks.OptionalColumn`2SampleApp.AdventureWorks.Person.vAdditionalContactInfoReader→SampleApp.AdventureWorks.RequiredColumn`2SampleApp.AdventureWorks.Person.vStateProvinceCountryRegionReader→SampleApp.AdventureWorks.RequiredColumn`2
- Direction
- SampleApp.AdventureWorks.Person uses SampleApp.AdventureWorks, so a change to SampleApp.AdventureWorks can break SampleApp.AdventureWorks.Person, while a change to SampleApp.AdventureWorks.Person can't break SampleApp.AdventureWorks.
- 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→28 SampleApp.AdventureWorks.Production uses SampleApp.AdventureWorks part of a loop✕
- Connections
- 41 pairs of types, where a type in SampleApp.AdventureWorks.Production uses a type in SampleApp.AdventureWorks. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
SampleApp.AdventureWorks.Production.BillOfMaterialsReader→SampleApp.AdventureWorks.OptionalColumn`2SampleApp.AdventureWorks.Production.BillOfMaterialsReader→SampleApp.AdventureWorks.RequiredColumn`2SampleApp.AdventureWorks.Production.CultureReader→SampleApp.AdventureWorks.RequiredColumn`2SampleApp.AdventureWorks.Production.DocumentReader→SampleApp.AdventureWorks.OptionalBinaryColumn`2SampleApp.AdventureWorks.Production.DocumentReader→SampleApp.AdventureWorks.OptionalColumn`2SampleApp.AdventureWorks.Production.DocumentReader→SampleApp.AdventureWorks.RequiredColumn`2SampleApp.AdventureWorks.Production.IllustrationReader→SampleApp.AdventureWorks.RequiredColumn`2SampleApp.AdventureWorks.Production.LocationReader→SampleApp.AdventureWorks.RequiredColumn`2SampleApp.AdventureWorks.Production.ProductCategoryReader→SampleApp.AdventureWorks.RequiredColumn`2SampleApp.AdventureWorks.Production.ProductCostHistoryReader→SampleApp.AdventureWorks.OptionalColumn`2SampleApp.AdventureWorks.Production.ProductCostHistoryReader→SampleApp.AdventureWorks.RequiredColumn`2SampleApp.AdventureWorks.Production.ProductDescriptionReader→SampleApp.AdventureWorks.RequiredColumn`2SampleApp.AdventureWorks.Production.ProductDocumentReader→SampleApp.AdventureWorks.RequiredColumn`2SampleApp.AdventureWorks.Production.ProductInventoryReader→SampleApp.AdventureWorks.RequiredColumn`2SampleApp.AdventureWorks.Production.ProductListPriceHistoryReader→SampleApp.AdventureWorks.OptionalColumn`2SampleApp.AdventureWorks.Production.ProductListPriceHistoryReader→SampleApp.AdventureWorks.RequiredColumn`2SampleApp.AdventureWorks.Production.ProductModelIllustrationReader→SampleApp.AdventureWorks.RequiredColumn`2SampleApp.AdventureWorks.Production.ProductModelProductDescriptionCultureReader→SampleApp.AdventureWorks.RequiredColumn`2SampleApp.AdventureWorks.Production.ProductModelReader→SampleApp.AdventureWorks.RequiredColumn`2SampleApp.AdventureWorks.Production.ProductPhotoReader→SampleApp.AdventureWorks.OptionalBinaryColumn`2SampleApp.AdventureWorks.Production.ProductPhotoReader→SampleApp.AdventureWorks.OptionalColumn`2SampleApp.AdventureWorks.Production.ProductPhotoReader→SampleApp.AdventureWorks.RequiredColumn`2SampleApp.AdventureWorks.Production.ProductProductPhotoReader→SampleApp.AdventureWorks.RequiredColumn`2SampleApp.AdventureWorks.Production.ProductReader→SampleApp.AdventureWorks.OptionalColumn`2SampleApp.AdventureWorks.Production.ProductReader→SampleApp.AdventureWorks.RequiredColumn`2
- Direction
- SampleApp.AdventureWorks.Production uses SampleApp.AdventureWorks, so a change to SampleApp.AdventureWorks can break SampleApp.AdventureWorks.Production, while a change to SampleApp.AdventureWorks.Production can't break SampleApp.AdventureWorks.
- 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→28 SampleApp.AdventureWorks.Purchasing uses SampleApp.AdventureWorks part of a loop✕
- Connections
- 12 pairs of types, where a type in SampleApp.AdventureWorks.Purchasing uses a type in SampleApp.AdventureWorks.
- The types involved
SampleApp.AdventureWorks.Purchasing.ProductVendorReader→SampleApp.AdventureWorks.OptionalColumn`2SampleApp.AdventureWorks.Purchasing.ProductVendorReader→SampleApp.AdventureWorks.RequiredColumn`2SampleApp.AdventureWorks.Purchasing.PurchaseOrderDetailReader→SampleApp.AdventureWorks.RequiredColumn`2SampleApp.AdventureWorks.Purchasing.PurchaseOrderHeaderReader→SampleApp.AdventureWorks.OptionalColumn`2SampleApp.AdventureWorks.Purchasing.PurchaseOrderHeaderReader→SampleApp.AdventureWorks.RequiredColumn`2SampleApp.AdventureWorks.Purchasing.ShipMethodReader→SampleApp.AdventureWorks.RequiredColumn`2SampleApp.AdventureWorks.Purchasing.VendorReader→SampleApp.AdventureWorks.OptionalColumn`2SampleApp.AdventureWorks.Purchasing.VendorReader→SampleApp.AdventureWorks.RequiredColumn`2SampleApp.AdventureWorks.Purchasing.vVendorWithAddressesReader→SampleApp.AdventureWorks.OptionalColumn`2SampleApp.AdventureWorks.Purchasing.vVendorWithAddressesReader→SampleApp.AdventureWorks.RequiredColumn`2SampleApp.AdventureWorks.Purchasing.vVendorWithContactsReader→SampleApp.AdventureWorks.OptionalColumn`2SampleApp.AdventureWorks.Purchasing.vVendorWithContactsReader→SampleApp.AdventureWorks.RequiredColumn`2
- Direction
- SampleApp.AdventureWorks.Purchasing uses SampleApp.AdventureWorks, so a change to SampleApp.AdventureWorks can break SampleApp.AdventureWorks.Purchasing, while a change to SampleApp.AdventureWorks.Purchasing can't break SampleApp.AdventureWorks.
- 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→28 SampleApp.AdventureWorks.Sales uses SampleApp.AdventureWorks part of a loop✕
- Connections
- 40 pairs of types, where a type in SampleApp.AdventureWorks.Sales uses a type in SampleApp.AdventureWorks. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
SampleApp.AdventureWorks.Sales.CountryRegionCurrencyReader→SampleApp.AdventureWorks.RequiredColumn`2SampleApp.AdventureWorks.Sales.CreditCardReader→SampleApp.AdventureWorks.RequiredColumn`2SampleApp.AdventureWorks.Sales.CurrencyRateReader→SampleApp.AdventureWorks.RequiredColumn`2SampleApp.AdventureWorks.Sales.CurrencyReader→SampleApp.AdventureWorks.RequiredColumn`2SampleApp.AdventureWorks.Sales.CustomerReader→SampleApp.AdventureWorks.OptionalColumn`2SampleApp.AdventureWorks.Sales.CustomerReader→SampleApp.AdventureWorks.RequiredColumn`2SampleApp.AdventureWorks.Sales.PersonCreditCardReader→SampleApp.AdventureWorks.RequiredColumn`2SampleApp.AdventureWorks.Sales.SalesOrderDetailReader→SampleApp.AdventureWorks.OptionalColumn`2SampleApp.AdventureWorks.Sales.SalesOrderDetailReader→SampleApp.AdventureWorks.RequiredColumn`2SampleApp.AdventureWorks.Sales.SalesOrderHeaderReader→SampleApp.AdventureWorks.OptionalColumn`2SampleApp.AdventureWorks.Sales.SalesOrderHeaderReader→SampleApp.AdventureWorks.RequiredColumn`2SampleApp.AdventureWorks.Sales.SalesOrderHeaderSalesReasonReader→SampleApp.AdventureWorks.RequiredColumn`2SampleApp.AdventureWorks.Sales.SalesPersonQuotaHistoryReader→SampleApp.AdventureWorks.RequiredColumn`2SampleApp.AdventureWorks.Sales.SalesPersonReader→SampleApp.AdventureWorks.OptionalColumn`2SampleApp.AdventureWorks.Sales.SalesPersonReader→SampleApp.AdventureWorks.RequiredColumn`2SampleApp.AdventureWorks.Sales.SalesReasonReader→SampleApp.AdventureWorks.RequiredColumn`2SampleApp.AdventureWorks.Sales.SalesTaxRateReader→SampleApp.AdventureWorks.RequiredColumn`2SampleApp.AdventureWorks.Sales.SalesTerritoryHistoryReader→SampleApp.AdventureWorks.OptionalColumn`2SampleApp.AdventureWorks.Sales.SalesTerritoryHistoryReader→SampleApp.AdventureWorks.RequiredColumn`2SampleApp.AdventureWorks.Sales.SalesTerritoryReader→SampleApp.AdventureWorks.RequiredColumn`2SampleApp.AdventureWorks.Sales.ShoppingCartItemReader→SampleApp.AdventureWorks.RequiredColumn`2SampleApp.AdventureWorks.Sales.SpecialOfferProductReader→SampleApp.AdventureWorks.RequiredColumn`2SampleApp.AdventureWorks.Sales.SpecialOfferReader→SampleApp.AdventureWorks.OptionalColumn`2SampleApp.AdventureWorks.Sales.SpecialOfferReader→SampleApp.AdventureWorks.RequiredColumn`2SampleApp.AdventureWorks.Sales.StoreReader→SampleApp.AdventureWorks.OptionalColumn`2
- Direction
- SampleApp.AdventureWorks.Sales uses SampleApp.AdventureWorks, so a change to SampleApp.AdventureWorks can break SampleApp.AdventureWorks.Sales, while a change to SampleApp.AdventureWorks.Sales can't break SampleApp.AdventureWorks.
- 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.
10→28 SampleApp.AdventureWorks.dbo uses SampleApp.AdventureWorks part of a loop✕
- Connections
- 5 pairs of types, where a type in SampleApp.AdventureWorks.dbo uses a type in SampleApp.AdventureWorks.
- The types involved
SampleApp.AdventureWorks.dbo.AWBuildVersionReader→SampleApp.AdventureWorks.RequiredColumn`2SampleApp.AdventureWorks.dbo.DatabaseLogReader→SampleApp.AdventureWorks.OptionalColumn`2SampleApp.AdventureWorks.dbo.DatabaseLogReader→SampleApp.AdventureWorks.RequiredColumn`2SampleApp.AdventureWorks.dbo.ErrorLogReader→SampleApp.AdventureWorks.OptionalColumn`2SampleApp.AdventureWorks.dbo.ErrorLogReader→SampleApp.AdventureWorks.RequiredColumn`2
- Direction
- SampleApp.AdventureWorks.dbo uses SampleApp.AdventureWorks, so a change to SampleApp.AdventureWorks can break SampleApp.AdventureWorks.dbo, while a change to SampleApp.AdventureWorks.dbo can't break SampleApp.AdventureWorks.
- 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.
11→28 SampleApp.AdventureWorks.ext uses SampleApp.AdventureWorks part of a loop✕
- Connections
- 2 pairs of types, where a type in SampleApp.AdventureWorks.ext uses a type in SampleApp.AdventureWorks.
- The types involved
SampleApp.AdventureWorks.ext.DateTime2SupportReader→SampleApp.AdventureWorks.RequiredColumn`2SampleApp.AdventureWorks.ext.GetIdGuidReproReader→SampleApp.AdventureWorks.RequiredColumn`2
- Direction
- SampleApp.AdventureWorks.ext uses SampleApp.AdventureWorks, so a change to SampleApp.AdventureWorks can break SampleApp.AdventureWorks.ext, while a change to SampleApp.AdventureWorks.ext can't break SampleApp.AdventureWorks.
- 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.
12→1 SqlHydra.Console uses SqlHydra.Domain✕
- Connections
- 3 pairs of types, where a type in SqlHydra.Console uses a type in SqlHydra.Domain.
- The types involved
SqlHydra.Console.Args→SqlHydra.Domain.ISqlHydraDbProviderSqlHydra.Console.Console→SqlHydra.Domain.ConfigSqlHydra.Console.LoadConfigResult→SqlHydra.Domain.Config
- Direction
- SqlHydra.Console uses SqlHydra.Domain, so a change to SqlHydra.Domain can break SqlHydra.Console, while a change to SqlHydra.Console can't break SqlHydra.Domain.
- Position
- Below the diagonal: SqlHydra.Console uses a module listed above it, which is the healthy direction.
12→4 SqlHydra.Console uses SqlHydra.Version✕
- Connections
- 1 pair of types, where a type in SqlHydra.Console uses a type in SqlHydra.Version.
- The types involved
SqlHydra.Console.Args→SqlHydra.Version.InformationalVersion
- Direction
- SqlHydra.Console uses SqlHydra.Version, so a change to SqlHydra.Version can break SqlHydra.Console, while a change to SqlHydra.Console can't break SqlHydra.Version.
- Position
- Below the diagonal: SqlHydra.Console uses a module listed above it, which is the healthy direction.
13→1 SqlHydra.Extensions uses SqlHydra.Domain✕
- Connections
- 5 pairs of types, where a type in SqlHydra.Extensions uses a type in SqlHydra.Domain.
- The types involved
SqlHydra.Extensions.Extensions→SqlHydra.Domain.IContributeColumnsSqlHydra.Extensions.Extensions→SqlHydra.Domain.ISqlHydraDbProviderSqlHydra.Extensions.Extensions→SqlHydra.Domain.ISqlHydraExtensionSqlHydra.Extensions.Extensions→SqlHydra.Domain.ProviderTypeSqlHydra.Extensions.Extensions→SqlHydra.Domain.Schema
- Direction
- SqlHydra.Extensions uses SqlHydra.Domain, so a change to SqlHydra.Domain can break SqlHydra.Extensions, while a change to SqlHydra.Extensions can't break SqlHydra.Domain.
- Position
- Below the diagonal: SqlHydra.Extensions uses a module listed above it, which is the healthy direction.
14→1 SqlHydra.Fsproj uses SqlHydra.Domain✕
- Connections
- 1 pair of types, where a type in SqlHydra.Fsproj uses a type in SqlHydra.Domain.
- The types involved
SqlHydra.Fsproj.Fsproj→SqlHydra.Domain.Config
- Direction
- SqlHydra.Fsproj uses SqlHydra.Domain, so a change to SqlHydra.Domain can break SqlHydra.Fsproj, while a change to SqlHydra.Fsproj can't break SqlHydra.Domain.
- Position
- Below the diagonal: SqlHydra.Fsproj uses a module listed above it, which is the healthy direction.
15→1 SqlHydra.MySql.MySqlDataTypes uses SqlHydra.Domain✕
- Connections
- 1 pair of types, where a type in SqlHydra.MySql.MySqlDataTypes uses a type in SqlHydra.Domain.
- The types involved
SqlHydra.MySql.MySqlDataTypes.MySqlDataTypes→SqlHydra.Domain.TypeMapping
- Direction
- SqlHydra.MySql.MySqlDataTypes uses SqlHydra.Domain, so a change to SqlHydra.Domain can break SqlHydra.MySql.MySqlDataTypes, while a change to SqlHydra.MySql.MySqlDataTypes can't break SqlHydra.Domain.
- Position
- Below the diagonal: SqlHydra.MySql.MySqlDataTypes uses a module listed above it, which is the healthy direction.
16→1 SqlHydra.MySql.MySqlSchemaProvider uses SqlHydra.Domain✕
- Connections
- 3 pairs of types, where a type in SqlHydra.MySql.MySqlSchemaProvider uses a type in SqlHydra.Domain.
- The types involved
SqlHydra.MySql.MySqlSchemaProvider.MySqlSchemaProvider→SqlHydra.Domain.ConfigSqlHydra.MySql.MySqlSchemaProvider.MySqlSchemaProvider→SqlHydra.Domain.IExtendTypeMappingSqlHydra.MySql.MySqlSchemaProvider.MySqlSchemaProvider→SqlHydra.Domain.Schema
- Direction
- SqlHydra.MySql.MySqlSchemaProvider uses SqlHydra.Domain, so a change to SqlHydra.Domain can break SqlHydra.MySql.MySqlSchemaProvider, while a change to SqlHydra.MySql.MySqlSchemaProvider can't break SqlHydra.Domain.
- Position
- Below the diagonal: SqlHydra.MySql.MySqlSchemaProvider uses a module listed above it, which is the healthy direction.
17→1 SqlHydra.MySql.Provider uses SqlHydra.Domain✕
- Connections
- 1 pair of types, where a type in SqlHydra.MySql.Provider uses a type in SqlHydra.Domain.
- The types involved
SqlHydra.MySql.Provider.Provider→SqlHydra.Domain.ISqlHydraDbProvider
- Direction
- SqlHydra.MySql.Provider uses SqlHydra.Domain, so a change to SqlHydra.Domain can break SqlHydra.MySql.Provider, while a change to SqlHydra.MySql.Provider can't break SqlHydra.Domain.
- Position
- Below the diagonal: SqlHydra.MySql.Provider uses a module listed above it, which is the healthy direction.
18→1 SqlHydra.Npgsql.NpgsqlDataTypes uses SqlHydra.Domain✕
- Connections
- 1 pair of types, where a type in SqlHydra.Npgsql.NpgsqlDataTypes uses a type in SqlHydra.Domain.
- The types involved
SqlHydra.Npgsql.NpgsqlDataTypes.NpgsqlDataTypes→SqlHydra.Domain.TypeMapping
- Direction
- SqlHydra.Npgsql.NpgsqlDataTypes uses SqlHydra.Domain, so a change to SqlHydra.Domain can break SqlHydra.Npgsql.NpgsqlDataTypes, while a change to SqlHydra.Npgsql.NpgsqlDataTypes can't break SqlHydra.Domain.
- Position
- Below the diagonal: SqlHydra.Npgsql.NpgsqlDataTypes uses a module listed above it, which is the healthy direction.
19→1 SqlHydra.Npgsql.NpgsqlSchemaProvider uses SqlHydra.Domain✕
- Connections
- 3 pairs of types, where a type in SqlHydra.Npgsql.NpgsqlSchemaProvider uses a type in SqlHydra.Domain.
- The types involved
SqlHydra.Npgsql.NpgsqlSchemaProvider.NpgsqlSchemaProvider→SqlHydra.Domain.ConfigSqlHydra.Npgsql.NpgsqlSchemaProvider.NpgsqlSchemaProvider→SqlHydra.Domain.IExtendTypeMappingSqlHydra.Npgsql.NpgsqlSchemaProvider.NpgsqlSchemaProvider→SqlHydra.Domain.Schema
- Direction
- SqlHydra.Npgsql.NpgsqlSchemaProvider uses SqlHydra.Domain, so a change to SqlHydra.Domain can break SqlHydra.Npgsql.NpgsqlSchemaProvider, while a change to SqlHydra.Npgsql.NpgsqlSchemaProvider can't break SqlHydra.Domain.
- Position
- Below the diagonal: SqlHydra.Npgsql.NpgsqlSchemaProvider uses a module listed above it, which is the healthy direction.
20→1 SqlHydra.Npgsql.Provider uses SqlHydra.Domain✕
- Connections
- 1 pair of types, where a type in SqlHydra.Npgsql.Provider uses a type in SqlHydra.Domain.
- The types involved
SqlHydra.Npgsql.Provider.Provider→SqlHydra.Domain.ISqlHydraDbProvider
- Direction
- SqlHydra.Npgsql.Provider uses SqlHydra.Domain, so a change to SqlHydra.Domain can break SqlHydra.Npgsql.Provider, while a change to SqlHydra.Npgsql.Provider can't break SqlHydra.Domain.
- Position
- Below the diagonal: SqlHydra.Npgsql.Provider uses a module listed above it, which is the healthy direction.
21→1 SqlHydra.Oracle.OracleDataTypes uses SqlHydra.Domain✕
- Connections
- 2 pairs of types, where a type in SqlHydra.Oracle.OracleDataTypes uses a type in SqlHydra.Domain.
- The types involved
SqlHydra.Oracle.OracleDataTypes.OracleDataTypes→SqlHydra.Domain.TypeMappingSqlHydra.Oracle.OracleDataTypes.OracleDataTypes→SqlHydra.Domain.TypeMappingContext
- Direction
- SqlHydra.Oracle.OracleDataTypes uses SqlHydra.Domain, so a change to SqlHydra.Domain can break SqlHydra.Oracle.OracleDataTypes, while a change to SqlHydra.Oracle.OracleDataTypes can't break SqlHydra.Domain.
- Position
- Below the diagonal: SqlHydra.Oracle.OracleDataTypes uses a module listed above it, which is the healthy direction.
22→1 SqlHydra.Oracle.OracleSchemaProvider uses SqlHydra.Domain✕
- Connections
- 3 pairs of types, where a type in SqlHydra.Oracle.OracleSchemaProvider uses a type in SqlHydra.Domain.
- The types involved
SqlHydra.Oracle.OracleSchemaProvider.OracleSchemaProvider→SqlHydra.Domain.ConfigSqlHydra.Oracle.OracleSchemaProvider.OracleSchemaProvider→SqlHydra.Domain.IExtendTypeMappingSqlHydra.Oracle.OracleSchemaProvider.OracleSchemaProvider→SqlHydra.Domain.Schema
- Direction
- SqlHydra.Oracle.OracleSchemaProvider uses SqlHydra.Domain, so a change to SqlHydra.Domain can break SqlHydra.Oracle.OracleSchemaProvider, while a change to SqlHydra.Oracle.OracleSchemaProvider can't break SqlHydra.Domain.
- Position
- Below the diagonal: SqlHydra.Oracle.OracleSchemaProvider uses a module listed above it, which is the healthy direction.
23→1 SqlHydra.Oracle.Provider uses SqlHydra.Domain✕
- Connections
- 1 pair of types, where a type in SqlHydra.Oracle.Provider uses a type in SqlHydra.Domain.
- The types involved
SqlHydra.Oracle.Provider.Provider→SqlHydra.Domain.ISqlHydraDbProvider
- Direction
- SqlHydra.Oracle.Provider uses SqlHydra.Domain, so a change to SqlHydra.Domain can break SqlHydra.Oracle.Provider, while a change to SqlHydra.Oracle.Provider can't break SqlHydra.Domain.
- Position
- Below the diagonal: SqlHydra.Oracle.Provider uses a module listed above it, which is the healthy direction.
24→1 SqlHydra.Program uses SqlHydra.Domain✕
- Connections
- 1 pair of types, where a type in SqlHydra.Program uses a type in SqlHydra.Domain.
- The types involved
SqlHydra.Program.Program→SqlHydra.Domain.ISqlHydraDbProvider
- Direction
- SqlHydra.Program uses SqlHydra.Domain, so a change to SqlHydra.Domain can break SqlHydra.Program, while a change to SqlHydra.Program can't break SqlHydra.Domain.
- Position
- Below the diagonal: SqlHydra.Program uses a module listed above it, which is the healthy direction.
25→1 SqlHydra.Query uses SqlHydra.Domain✕
- Connections
- 7 pairs of types, where a type in SqlHydra.Query uses a type in SqlHydra.Domain.
- The types involved
SqlHydra.Query.ISqlEmitter→SqlHydra.Domain.ProviderTypeSqlHydra.Query.MySqlEmitter→SqlHydra.Domain.ProviderTypeSqlHydra.Query.OracleEmitter→SqlHydra.Domain.ProviderTypeSqlHydra.Query.PostgresEmitter→SqlHydra.Domain.ProviderTypeSqlHydra.Query.QueryContext→SqlHydra.Domain.ProviderTypeSqlHydra.Query.SqlServerEmitter→SqlHydra.Domain.ProviderTypeSqlHydra.Query.SqliteEmitter→SqlHydra.Domain.ProviderType
- Direction
- SqlHydra.Query uses SqlHydra.Domain, so a change to SqlHydra.Domain can break SqlHydra.Query, while a change to SqlHydra.Query can't break SqlHydra.Domain.
- Position
- Below the diagonal: SqlHydra.Query uses a module listed above it, which is the healthy direction.
26→1 SqlHydra.Query.Hydration uses SqlHydra.Domain✕
- Connections
- 2 pairs of types, where a type in SqlHydra.Query.Hydration uses a type in SqlHydra.Domain.
- The types involved
SqlHydra.Query.Hydration.ColumnReadMethods→SqlHydra.Domain.ProviderTypeSqlHydra.Query.Hydration.Hydration→SqlHydra.Domain.ProviderType
- Direction
- SqlHydra.Query.Hydration uses SqlHydra.Domain, so a change to SqlHydra.Domain can break SqlHydra.Query.Hydration, while a change to SqlHydra.Query.Hydration can't break SqlHydra.Domain.
- Position
- Below the diagonal: SqlHydra.Query.Hydration uses a module listed above it, which is the healthy direction.
27→1 SqlHydra.SchemaTemplate uses SqlHydra.Domain✕
- Connections
- 6 pairs of types, where a type in SqlHydra.SchemaTemplate uses a type in SqlHydra.Domain.
- The types involved
SqlHydra.SchemaTemplate.SchemaTemplate→SqlHydra.Domain.ColumnSqlHydra.SchemaTemplate.SchemaTemplate→SqlHydra.Domain.ConfigSqlHydra.SchemaTemplate.SchemaTemplate→SqlHydra.Domain.IExtendNamingSqlHydra.SchemaTemplate.SchemaTemplate→SqlHydra.Domain.ISqlHydraDbProviderSqlHydra.SchemaTemplate.SchemaTemplate→SqlHydra.Domain.SchemaSqlHydra.SchemaTemplate.SchemaTemplate→SqlHydra.Domain.Table
- Direction
- SqlHydra.SchemaTemplate uses SqlHydra.Domain, so a change to SqlHydra.Domain can break SqlHydra.SchemaTemplate, while a change to SqlHydra.SchemaTemplate can't break SqlHydra.Domain.
- Position
- Below the diagonal: SqlHydra.SchemaTemplate uses a module listed above it, which is the healthy direction.
27→4 SqlHydra.SchemaTemplate uses SqlHydra.Version✕
- Connections
- 1 pair of types, where a type in SqlHydra.SchemaTemplate uses a type in SqlHydra.Version.
- The types involved
SqlHydra.SchemaTemplate.SchemaTemplate→SqlHydra.Version.InformationalVersion
- Direction
- SqlHydra.SchemaTemplate uses SqlHydra.Version, so a change to SqlHydra.Version can break SqlHydra.SchemaTemplate, while a change to SqlHydra.SchemaTemplate can't break SqlHydra.Version.
- Position
- Below the diagonal: SqlHydra.SchemaTemplate uses a module listed above it, which is the healthy direction.
28→5 SampleApp.AdventureWorks uses SampleApp.AdventureWorks.HumanResources✕
- Connections
- 12 pairs of types, where a type in SampleApp.AdventureWorks uses a type in SampleApp.AdventureWorks.HumanResources.
- The types involved
SampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.HumanResources.DepartmentReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.HumanResources.EmployeeDepartmentHistoryReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.HumanResources.EmployeePayHistoryReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.HumanResources.EmployeeReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.HumanResources.JobCandidateReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.HumanResources.ShiftReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.HumanResources.vEmployeeDepartmentHistoryReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.HumanResources.vEmployeeDepartmentReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.HumanResources.vEmployeeReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.HumanResources.vJobCandidateEducationReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.HumanResources.vJobCandidateEmploymentReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.HumanResources.vJobCandidateReader
- Direction
- SampleApp.AdventureWorks uses SampleApp.AdventureWorks.HumanResources, so a change to SampleApp.AdventureWorks.HumanResources can break SampleApp.AdventureWorks, while a change to SampleApp.AdventureWorks can't break SampleApp.AdventureWorks.HumanResources.
- Position
- Below the diagonal: SampleApp.AdventureWorks uses a module listed above it, which is the healthy direction.
28→6 SampleApp.AdventureWorks uses SampleApp.AdventureWorks.Person✕
- Connections
- 15 pairs of types, where a type in SampleApp.AdventureWorks uses a type in SampleApp.AdventureWorks.Person.
- The types involved
SampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Person.AddressReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Person.AddressTypeReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Person.BusinessEntityAddressReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Person.BusinessEntityContactReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Person.BusinessEntityReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Person.ContactTypeReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Person.CountryRegionReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Person.EmailAddressReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Person.PasswordReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Person.PersonPhoneReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Person.PersonReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Person.PhoneNumberTypeReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Person.StateProvinceReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Person.vAdditionalContactInfoReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Person.vStateProvinceCountryRegionReader
- Direction
- SampleApp.AdventureWorks uses SampleApp.AdventureWorks.Person, so a change to SampleApp.AdventureWorks.Person can break SampleApp.AdventureWorks, while a change to SampleApp.AdventureWorks can't break SampleApp.AdventureWorks.Person.
- Position
- Below the diagonal: SampleApp.AdventureWorks uses a module listed above it, which is the healthy direction.
28→7 SampleApp.AdventureWorks uses SampleApp.AdventureWorks.Production✕
- Connections
- 28 pairs of types, where a type in SampleApp.AdventureWorks uses a type in SampleApp.AdventureWorks.Production. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
SampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Production.BillOfMaterialsReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Production.CultureReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Production.DocumentReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Production.IllustrationReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Production.LocationReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Production.ProductCategoryReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Production.ProductCostHistoryReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Production.ProductDescriptionReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Production.ProductDocumentReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Production.ProductInventoryReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Production.ProductListPriceHistoryReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Production.ProductModelIllustrationReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Production.ProductModelProductDescriptionCultureReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Production.ProductModelReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Production.ProductPhotoReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Production.ProductProductPhotoReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Production.ProductReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Production.ProductReviewReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Production.ProductSubcategoryReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Production.ScrapReasonReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Production.TransactionHistoryArchiveReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Production.TransactionHistoryReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Production.UnitMeasureReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Production.WorkOrderReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Production.WorkOrderRoutingReader
- Direction
- SampleApp.AdventureWorks uses SampleApp.AdventureWorks.Production, so a change to SampleApp.AdventureWorks.Production can break SampleApp.AdventureWorks, while a change to SampleApp.AdventureWorks can't break SampleApp.AdventureWorks.Production.
- Position
- Below the diagonal: SampleApp.AdventureWorks uses a module listed above it, which is the healthy direction.
28→8 SampleApp.AdventureWorks uses SampleApp.AdventureWorks.Purchasing✕
- Connections
- 7 pairs of types, where a type in SampleApp.AdventureWorks uses a type in SampleApp.AdventureWorks.Purchasing.
- The types involved
SampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Purchasing.ProductVendorReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Purchasing.PurchaseOrderDetailReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Purchasing.PurchaseOrderHeaderReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Purchasing.ShipMethodReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Purchasing.VendorReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Purchasing.vVendorWithAddressesReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Purchasing.vVendorWithContactsReader
- Direction
- SampleApp.AdventureWorks uses SampleApp.AdventureWorks.Purchasing, so a change to SampleApp.AdventureWorks.Purchasing can break SampleApp.AdventureWorks, while a change to SampleApp.AdventureWorks can't break SampleApp.AdventureWorks.Purchasing.
- Position
- Below the diagonal: SampleApp.AdventureWorks uses a module listed above it, which is the healthy direction.
28→9 SampleApp.AdventureWorks uses SampleApp.AdventureWorks.Sales✕
- Connections
- 26 pairs of types, where a type in SampleApp.AdventureWorks uses a type in SampleApp.AdventureWorks.Sales. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
SampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Sales.CountryRegionCurrencyReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Sales.CreditCardReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Sales.CurrencyRateReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Sales.CurrencyReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Sales.CustomerReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Sales.PersonCreditCardReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Sales.SalesOrderDetailReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Sales.SalesOrderHeaderReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Sales.SalesOrderHeaderSalesReasonReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Sales.SalesPersonQuotaHistoryReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Sales.SalesPersonReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Sales.SalesReasonReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Sales.SalesTaxRateReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Sales.SalesTerritoryHistoryReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Sales.SalesTerritoryReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Sales.ShoppingCartItemReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Sales.SpecialOfferProductReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Sales.SpecialOfferReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Sales.StoreReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Sales.vIndividualCustomerReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Sales.vPersonDemographicsReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Sales.vSalesPersonReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Sales.vSalesPersonSalesByFiscalYearsReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Sales.vStoreWithAddressesReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.Sales.vStoreWithContactsReader
- Direction
- SampleApp.AdventureWorks uses SampleApp.AdventureWorks.Sales, so a change to SampleApp.AdventureWorks.Sales can break SampleApp.AdventureWorks, while a change to SampleApp.AdventureWorks can't break SampleApp.AdventureWorks.Sales.
- Position
- Below the diagonal: SampleApp.AdventureWorks uses a module listed above it, which is the healthy direction.
28→10 SampleApp.AdventureWorks uses SampleApp.AdventureWorks.dbo✕
- Connections
- 3 pairs of types, where a type in SampleApp.AdventureWorks uses a type in SampleApp.AdventureWorks.dbo.
- The types involved
SampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.dbo.AWBuildVersionReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.dbo.DatabaseLogReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.dbo.ErrorLogReader
- Direction
- SampleApp.AdventureWorks uses SampleApp.AdventureWorks.dbo, so a change to SampleApp.AdventureWorks.dbo can break SampleApp.AdventureWorks, while a change to SampleApp.AdventureWorks can't break SampleApp.AdventureWorks.dbo.
- Position
- Below the diagonal: SampleApp.AdventureWorks uses a module listed above it, which is the healthy direction.
28→11 SampleApp.AdventureWorks uses SampleApp.AdventureWorks.ext✕
- Connections
- 2 pairs of types, where a type in SampleApp.AdventureWorks uses a type in SampleApp.AdventureWorks.ext.
- The types involved
SampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.ext.DateTime2SupportReaderSampleApp.AdventureWorks.HydraReader→SampleApp.AdventureWorks.ext.GetIdGuidReproReader
- Direction
- SampleApp.AdventureWorks uses SampleApp.AdventureWorks.ext, so a change to SampleApp.AdventureWorks.ext can break SampleApp.AdventureWorks, while a change to SampleApp.AdventureWorks can't break SampleApp.AdventureWorks.ext.
- Position
- Below the diagonal: SampleApp.AdventureWorks uses a module listed above it, which is the healthy direction.
29→7 SampleApp.DapperExample uses SampleApp.AdventureWorks.Production✕
- Connections
- 1 pair of types, where a type in SampleApp.DapperExample uses a type in SampleApp.AdventureWorks.Production.
- The types involved
SampleApp.DapperExample.DapperExample→SampleApp.AdventureWorks.Production.Product
- Direction
- SampleApp.DapperExample uses SampleApp.AdventureWorks.Production, so a change to SampleApp.AdventureWorks.Production can break SampleApp.DapperExample, while a change to SampleApp.DapperExample can't break SampleApp.AdventureWorks.Production.
- Position
- Below the diagonal: SampleApp.DapperExample uses a module listed above it, which is the healthy direction.
30→7 SampleApp.DonaldExample uses SampleApp.AdventureWorks.Production✕
- Connections
- 1 pair of types, where a type in SampleApp.DonaldExample uses a type in SampleApp.AdventureWorks.Production.
- The types involved
SampleApp.DonaldExample.DonaldExample→SampleApp.AdventureWorks.Production.Product
- Direction
- SampleApp.DonaldExample uses SampleApp.AdventureWorks.Production, so a change to SampleApp.AdventureWorks.Production can break SampleApp.DonaldExample, while a change to SampleApp.DonaldExample can't break SampleApp.AdventureWorks.Production.
- Position
- Below the diagonal: SampleApp.DonaldExample uses a module listed above it, which is the healthy direction.
31→7 SampleApp.ReaderExample uses SampleApp.AdventureWorks.Production✕
- Connections
- 1 pair of types, where a type in SampleApp.ReaderExample uses a type in SampleApp.AdventureWorks.Production.
- The types involved
SampleApp.ReaderExample.ReaderExample→SampleApp.AdventureWorks.Production.Product
- Direction
- SampleApp.ReaderExample uses SampleApp.AdventureWorks.Production, so a change to SampleApp.AdventureWorks.Production can break SampleApp.ReaderExample, while a change to SampleApp.ReaderExample can't break SampleApp.AdventureWorks.Production.
- Position
- Below the diagonal: SampleApp.ReaderExample uses a module listed above it, which is the healthy direction.
32→25 SqlHydra.Query.FQ uses SqlHydra.Query✕
- Connections
- 2 pairs of types, where a type in SqlHydra.Query.FQ uses a type in SqlHydra.Query.
- The types involved
SqlHydra.Query.FQ.FQ→SqlHydra.Query.TableMappingSqlHydra.Query.FQ.FQ→SqlHydra.Query.TableMappingKey
- Direction
- SqlHydra.Query.FQ uses SqlHydra.Query, so a change to SqlHydra.Query can break SqlHydra.Query.FQ, while a change to SqlHydra.Query.FQ can't break SqlHydra.Query.
- Position
- Below the diagonal: SqlHydra.Query.FQ uses a module listed above it, which is the healthy direction.
33→3 SqlHydra.Query.LinqExpressionVisitors uses SqlHydra.Query.ExpressionNormalizer✕
- Connections
- 1 pair of types, where a type in SqlHydra.Query.LinqExpressionVisitors uses a type in SqlHydra.Query.ExpressionNormalizer.
- The types involved
SqlHydra.Query.LinqExpressionVisitors.LinqExpressionVisitors→SqlHydra.Query.ExpressionNormalizer.NormalizedExpression
- Direction
- SqlHydra.Query.LinqExpressionVisitors uses SqlHydra.Query.ExpressionNormalizer, so a change to SqlHydra.Query.ExpressionNormalizer can break SqlHydra.Query.LinqExpressionVisitors, while a change to SqlHydra.Query.LinqExpressionVisitors can't break SqlHydra.Query.ExpressionNormalizer.
- Position
- Below the diagonal: SqlHydra.Query.LinqExpressionVisitors uses a module listed above it, which is the healthy direction.
33→25 SqlHydra.Query.LinqExpressionVisitors uses SqlHydra.Query✕
- Connections
- 4 pairs of types, where a type in SqlHydra.Query.LinqExpressionVisitors uses a type in SqlHydra.Query.
- The types involved
SqlHydra.Query.LinqExpressionVisitors.LinqExpressionVisitors→SqlHydra.Query.ComparisonOpSqlHydra.Query.LinqExpressionVisitors.LinqExpressionVisitors→SqlHydra.Query.SqlHydraFunctionAttributeSqlHydra.Query.LinqExpressionVisitors.LinqExpressionVisitors→SqlHydra.Query.TableMappingSqlHydra.Query.LinqExpressionVisitors.LinqExpressionVisitors→SqlHydra.Query.WhereClause
- Direction
- SqlHydra.Query.LinqExpressionVisitors uses SqlHydra.Query, so a change to SqlHydra.Query can break SqlHydra.Query.LinqExpressionVisitors, while a change to SqlHydra.Query.LinqExpressionVisitors can't break SqlHydra.Query.
- Position
- Below the diagonal: SqlHydra.Query.LinqExpressionVisitors uses a module listed above it, which is the healthy direction.
34→25 SqlHydra.Query.SelectBuilders.ResultModifier uses SqlHydra.Query✕
- Connections
- 6 pairs of types, where a type in SqlHydra.Query.SelectBuilders.ResultModifier uses a type in SqlHydra.Query.
- The types involved
SqlHydra.Query.SelectBuilders.ResultModifier.Count`1→SqlHydra.Query.QuerySource`2SqlHydra.Query.SelectBuilders.ResultModifier.Count`1→SqlHydra.Query.SelectQueryIRSqlHydra.Query.SelectBuilders.ResultModifier.Head`1→SqlHydra.Query.QuerySource`2SqlHydra.Query.SelectBuilders.ResultModifier.Head`1→SqlHydra.Query.SelectQueryIRSqlHydra.Query.SelectBuilders.ResultModifier.ModifierBase`1→SqlHydra.Query.QuerySource`2SqlHydra.Query.SelectBuilders.ResultModifier.ModifierBase`1→SqlHydra.Query.SelectQueryIR
- Direction
- SqlHydra.Query.SelectBuilders.ResultModifier uses SqlHydra.Query, so a change to SqlHydra.Query can break SqlHydra.Query.SelectBuilders.ResultModifier, while a change to SqlHydra.Query.SelectBuilders.ResultModifier can't break SqlHydra.Query.
- Position
- Below the diagonal: SqlHydra.Query.SelectBuilders.ResultModifier uses a module listed above it, which is the healthy direction.
35→25 SqlHydra.Query.SelectBuilders uses SqlHydra.Query✕
- Connections
- 15 pairs of types, where a type in SqlHydra.Query.SelectBuilders uses a type in SqlHydra.Query.
- The types involved
SqlHydra.Query.SelectBuilders.ContextType→SqlHydra.Query.QueryContextSqlHydra.Query.SelectBuilders.SelectAsyncBuilder`2→SqlHydra.Query.QuerySource`2SqlHydra.Query.SelectBuilders.SelectAsyncBuilder`2→SqlHydra.Query.SelectQueryIRSqlHydra.Query.SelectBuilders.SelectBuilder`2→SqlHydra.Query.LeftViewQuerySource`2SqlHydra.Query.SelectBuilders.SelectBuilder`2→SqlHydra.Query.NullsOrderingSqlHydra.Query.SelectBuilders.SelectBuilder`2→SqlHydra.Query.PendingJoinSqlHydra.Query.SelectBuilders.SelectBuilder`2→SqlHydra.Query.QuerySource`1SqlHydra.Query.SelectBuilders.SelectBuilder`2→SqlHydra.Query.QuerySource`2SqlHydra.Query.SelectBuilders.SelectBuilder`2→SqlHydra.Query.SelectQuerySqlHydra.Query.SelectBuilders.SelectBuilder`2→SqlHydra.Query.SelectQueryIRSqlHydra.Query.SelectBuilders.SelectQueryBuilder`2→SqlHydra.Query.QuerySource`2SqlHydra.Query.SelectBuilders.SelectQueryBuilder`2→SqlHydra.Query.SelectQueryIRSqlHydra.Query.SelectBuilders.SelectQueryBuilder`2→SqlHydra.Query.SelectQuery`1SqlHydra.Query.SelectBuilders.SelectTaskBuilder`2→SqlHydra.Query.QuerySource`2SqlHydra.Query.SelectBuilders.SelectTaskBuilder`2→SqlHydra.Query.SelectQueryIR
- Direction
- SqlHydra.Query.SelectBuilders uses SqlHydra.Query, so a change to SqlHydra.Query can break SqlHydra.Query.SelectBuilders, while a change to SqlHydra.Query.SelectBuilders can't break SqlHydra.Query.
- Position
- Below the diagonal: SqlHydra.Query.SelectBuilders uses a module listed above it, which is the healthy direction.
35→34 SqlHydra.Query.SelectBuilders uses SqlHydra.Query.SelectBuilders.ResultModifier✕
- Connections
- 7 pairs of types, where a type in SqlHydra.Query.SelectBuilders uses a type in SqlHydra.Query.SelectBuilders.ResultModifier.
- The types involved
SqlHydra.Query.SelectBuilders.SelectAsyncBuilder`2→SqlHydra.Query.SelectBuilders.ResultModifier.Count`1SqlHydra.Query.SelectBuilders.SelectAsyncBuilder`2→SqlHydra.Query.SelectBuilders.ResultModifier.Head`1SqlHydra.Query.SelectBuilders.SelectBuilder`2→SqlHydra.Query.SelectBuilders.ResultModifier.Count`1SqlHydra.Query.SelectBuilders.SelectBuilder`2→SqlHydra.Query.SelectBuilders.ResultModifier.Head`1SqlHydra.Query.SelectBuilders.SelectQueryBuilder`2→SqlHydra.Query.SelectBuilders.ResultModifier.Count`1SqlHydra.Query.SelectBuilders.SelectTaskBuilder`2→SqlHydra.Query.SelectBuilders.ResultModifier.Count`1SqlHydra.Query.SelectBuilders.SelectTaskBuilder`2→SqlHydra.Query.SelectBuilders.ResultModifier.Head`1
- Direction
- SqlHydra.Query.SelectBuilders uses SqlHydra.Query.SelectBuilders.ResultModifier, so a change to SqlHydra.Query.SelectBuilders.ResultModifier can break SqlHydra.Query.SelectBuilders, while a change to SqlHydra.Query.SelectBuilders can't break SqlHydra.Query.SelectBuilders.ResultModifier.
- Position
- Below the diagonal: SqlHydra.Query.SelectBuilders uses a module listed above it, which is the healthy direction.
36→25 SqlHydra.Query.DeleteBuilders uses SqlHydra.Query✕
- Connections
- 10 pairs of types, where a type in SqlHydra.Query.DeleteBuilders uses a type in SqlHydra.Query.
- The types involved
SqlHydra.Query.DeleteBuilders.DeleteAsyncBuilder`1→SqlHydra.Query.DeleteQuerySpec`1SqlHydra.Query.DeleteBuilders.DeleteAsyncBuilder`1→SqlHydra.Query.QuerySource`2SqlHydra.Query.DeleteBuilders.DeleteBuilder`1→SqlHydra.Query.DeleteQuerySpec`1SqlHydra.Query.DeleteBuilders.DeleteBuilder`1→SqlHydra.Query.DeleteQuery`1SqlHydra.Query.DeleteBuilders.DeleteBuilder`1→SqlHydra.Query.QuerySource`1SqlHydra.Query.DeleteBuilders.DeleteBuilder`1→SqlHydra.Query.QuerySource`2SqlHydra.Query.DeleteBuilders.DeleteBuilders→SqlHydra.Query.DeleteQuerySpec`1SqlHydra.Query.DeleteBuilders.DeleteBuilders→SqlHydra.Query.DeleteQuery`1SqlHydra.Query.DeleteBuilders.DeleteTaskBuilder`1→SqlHydra.Query.DeleteQuerySpec`1SqlHydra.Query.DeleteBuilders.DeleteTaskBuilder`1→SqlHydra.Query.QuerySource`2
- Direction
- SqlHydra.Query.DeleteBuilders uses SqlHydra.Query, so a change to SqlHydra.Query can break SqlHydra.Query.DeleteBuilders, while a change to SqlHydra.Query.DeleteBuilders can't break SqlHydra.Query.
- Position
- Below the diagonal: SqlHydra.Query.DeleteBuilders uses a module listed above it, which is the healthy direction.
36→35 SqlHydra.Query.DeleteBuilders uses SqlHydra.Query.SelectBuilders✕
- Connections
- 2 pairs of types, where a type in SqlHydra.Query.DeleteBuilders uses a type in SqlHydra.Query.SelectBuilders.
- The types involved
SqlHydra.Query.DeleteBuilders.DeleteAsyncBuilder`1→SqlHydra.Query.SelectBuilders.ContextTypeSqlHydra.Query.DeleteBuilders.DeleteTaskBuilder`1→SqlHydra.Query.SelectBuilders.ContextType
- Direction
- SqlHydra.Query.DeleteBuilders uses SqlHydra.Query.SelectBuilders, so a change to SqlHydra.Query.SelectBuilders can break SqlHydra.Query.DeleteBuilders, while a change to SqlHydra.Query.DeleteBuilders can't break SqlHydra.Query.SelectBuilders.
- Position
- Below the diagonal: SqlHydra.Query.DeleteBuilders uses a module listed above it, which is the healthy direction.
37→2 SqlHydra.Query.InsertBuilders uses SqlHydra.Query.AtLeastOne✕
- Connections
- 1 pair of types, where a type in SqlHydra.Query.InsertBuilders uses a type in SqlHydra.Query.AtLeastOne.
- The types involved
SqlHydra.Query.InsertBuilders.InsertBuilder`3→SqlHydra.Query.AtLeastOne.AtLeastOne`1
- Direction
- SqlHydra.Query.InsertBuilders uses SqlHydra.Query.AtLeastOne, so a change to SqlHydra.Query.AtLeastOne can break SqlHydra.Query.InsertBuilders, while a change to SqlHydra.Query.InsertBuilders can't break SqlHydra.Query.AtLeastOne.
- Position
- Below the diagonal: SqlHydra.Query.InsertBuilders uses a module listed above it, which is the healthy direction.
37→25 SqlHydra.Query.InsertBuilders uses SqlHydra.Query✕
- Connections
- 9 pairs of types, where a type in SqlHydra.Query.InsertBuilders uses a type in SqlHydra.Query.
- The types involved
SqlHydra.Query.InsertBuilders.InsertAsyncBuilder`3→SqlHydra.Query.InsertQuerySpec`2SqlHydra.Query.InsertBuilders.InsertAsyncBuilder`3→SqlHydra.Query.QuerySource`2SqlHydra.Query.InsertBuilders.InsertBuilder`3→SqlHydra.Query.InsertQuerySpec`2SqlHydra.Query.InsertBuilders.InsertBuilder`3→SqlHydra.Query.InsertQuery`2SqlHydra.Query.InsertBuilders.InsertBuilder`3→SqlHydra.Query.QuerySource`1SqlHydra.Query.InsertBuilders.InsertBuilder`3→SqlHydra.Query.QuerySource`2SqlHydra.Query.InsertBuilders.InsertBuilder`3→SqlHydra.Query.SelectQuerySqlHydra.Query.InsertBuilders.InsertTaskBuilder`3→SqlHydra.Query.InsertQuerySpec`2SqlHydra.Query.InsertBuilders.InsertTaskBuilder`3→SqlHydra.Query.QuerySource`2
- Direction
- SqlHydra.Query.InsertBuilders uses SqlHydra.Query, so a change to SqlHydra.Query can break SqlHydra.Query.InsertBuilders, while a change to SqlHydra.Query.InsertBuilders can't break SqlHydra.Query.
- Position
- Below the diagonal: SqlHydra.Query.InsertBuilders uses a module listed above it, which is the healthy direction.
37→35 SqlHydra.Query.InsertBuilders uses SqlHydra.Query.SelectBuilders✕
- Connections
- 2 pairs of types, where a type in SqlHydra.Query.InsertBuilders uses a type in SqlHydra.Query.SelectBuilders.
- The types involved
SqlHydra.Query.InsertBuilders.InsertAsyncBuilder`3→SqlHydra.Query.SelectBuilders.ContextTypeSqlHydra.Query.InsertBuilders.InsertTaskBuilder`3→SqlHydra.Query.SelectBuilders.ContextType
- Direction
- SqlHydra.Query.InsertBuilders uses SqlHydra.Query.SelectBuilders, so a change to SqlHydra.Query.SelectBuilders can break SqlHydra.Query.InsertBuilders, while a change to SqlHydra.Query.InsertBuilders can't break SqlHydra.Query.SelectBuilders.
- Position
- Below the diagonal: SqlHydra.Query.InsertBuilders uses a module listed above it, which is the healthy direction.
38→25 SqlHydra.Query.SelectBuilders.ContextTypeResolver uses SqlHydra.Query✕
- Connections
- 2 pairs of types, where a type in SqlHydra.Query.SelectBuilders.ContextTypeResolver uses a type in SqlHydra.Query.
- The types involved
SqlHydra.Query.SelectBuilders.ContextTypeResolver.Resolver→SqlHydra.Query.IQueryContextFactorySqlHydra.Query.SelectBuilders.ContextTypeResolver.Resolver→SqlHydra.Query.QueryContext
- Direction
- SqlHydra.Query.SelectBuilders.ContextTypeResolver uses SqlHydra.Query, so a change to SqlHydra.Query can break SqlHydra.Query.SelectBuilders.ContextTypeResolver, while a change to SqlHydra.Query.SelectBuilders.ContextTypeResolver can't break SqlHydra.Query.
- Position
- Below the diagonal: SqlHydra.Query.SelectBuilders.ContextTypeResolver uses a module listed above it, which is the healthy direction.
38→35 SqlHydra.Query.SelectBuilders.ContextTypeResolver uses SqlHydra.Query.SelectBuilders✕
- Connections
- 2 pairs of types, where a type in SqlHydra.Query.SelectBuilders.ContextTypeResolver uses a type in SqlHydra.Query.SelectBuilders.
- The types involved
SqlHydra.Query.SelectBuilders.ContextTypeResolver.ContextTypeResolver→SqlHydra.Query.SelectBuilders.ContextTypeSqlHydra.Query.SelectBuilders.ContextTypeResolver.Resolver→SqlHydra.Query.SelectBuilders.ContextType
- Direction
- SqlHydra.Query.SelectBuilders.ContextTypeResolver uses SqlHydra.Query.SelectBuilders, so a change to SqlHydra.Query.SelectBuilders can break SqlHydra.Query.SelectBuilders.ContextTypeResolver, while a change to SqlHydra.Query.SelectBuilders.ContextTypeResolver can't break SqlHydra.Query.SelectBuilders.
- Position
- Below the diagonal: SqlHydra.Query.SelectBuilders.ContextTypeResolver uses a module listed above it, which is the healthy direction.
39→25 SqlHydra.Query.SelectBuilders.ContextUtils uses SqlHydra.Query✕
- Connections
- 1 pair of types, where a type in SqlHydra.Query.SelectBuilders.ContextUtils uses a type in SqlHydra.Query.
- The types involved
SqlHydra.Query.SelectBuilders.ContextUtils.ContextUtils→SqlHydra.Query.QueryContext
- Direction
- SqlHydra.Query.SelectBuilders.ContextUtils uses SqlHydra.Query, so a change to SqlHydra.Query can break SqlHydra.Query.SelectBuilders.ContextUtils, while a change to SqlHydra.Query.SelectBuilders.ContextUtils can't break SqlHydra.Query.
- Position
- Below the diagonal: SqlHydra.Query.SelectBuilders.ContextUtils uses a module listed above it, which is the healthy direction.
39→35 SqlHydra.Query.SelectBuilders.ContextUtils uses SqlHydra.Query.SelectBuilders✕
- Connections
- 1 pair of types, where a type in SqlHydra.Query.SelectBuilders.ContextUtils uses a type in SqlHydra.Query.SelectBuilders.
- The types involved
SqlHydra.Query.SelectBuilders.ContextUtils.ContextUtils→SqlHydra.Query.SelectBuilders.ContextType
- Direction
- SqlHydra.Query.SelectBuilders.ContextUtils uses SqlHydra.Query.SelectBuilders, so a change to SqlHydra.Query.SelectBuilders can break SqlHydra.Query.SelectBuilders.ContextUtils, while a change to SqlHydra.Query.SelectBuilders.ContextUtils can't break SqlHydra.Query.SelectBuilders.
- Position
- Below the diagonal: SqlHydra.Query.SelectBuilders.ContextUtils uses a module listed above it, which is the healthy direction.
40→25 SqlHydra.Query.UpdateBuilders uses SqlHydra.Query✕
- Connections
- 10 pairs of types, where a type in SqlHydra.Query.UpdateBuilders uses a type in SqlHydra.Query.
- The types involved
SqlHydra.Query.UpdateBuilders.UpdateAsyncBuilder`2→SqlHydra.Query.QuerySource`2SqlHydra.Query.UpdateBuilders.UpdateAsyncBuilder`2→SqlHydra.Query.UpdateQuerySpec`2SqlHydra.Query.UpdateBuilders.UpdateBuilder`2→SqlHydra.Query.QuerySource`1SqlHydra.Query.UpdateBuilders.UpdateBuilder`2→SqlHydra.Query.QuerySource`2SqlHydra.Query.UpdateBuilders.UpdateBuilder`2→SqlHydra.Query.UpdateQuerySpec`2SqlHydra.Query.UpdateBuilders.UpdateBuilder`2→SqlHydra.Query.UpdateQuery`2SqlHydra.Query.UpdateBuilders.UpdateBuilders→SqlHydra.Query.UpdateQuerySpec`2SqlHydra.Query.UpdateBuilders.UpdateBuilders→SqlHydra.Query.UpdateQuery`2SqlHydra.Query.UpdateBuilders.UpdateTaskBuilder`2→SqlHydra.Query.QuerySource`2SqlHydra.Query.UpdateBuilders.UpdateTaskBuilder`2→SqlHydra.Query.UpdateQuerySpec`2
- Direction
- SqlHydra.Query.UpdateBuilders uses SqlHydra.Query, so a change to SqlHydra.Query can break SqlHydra.Query.UpdateBuilders, while a change to SqlHydra.Query.UpdateBuilders can't break SqlHydra.Query.
- Position
- Below the diagonal: SqlHydra.Query.UpdateBuilders uses a module listed above it, which is the healthy direction.
40→35 SqlHydra.Query.UpdateBuilders uses SqlHydra.Query.SelectBuilders✕
- Connections
- 2 pairs of types, where a type in SqlHydra.Query.UpdateBuilders uses a type in SqlHydra.Query.SelectBuilders.
- The types involved
SqlHydra.Query.UpdateBuilders.UpdateAsyncBuilder`2→SqlHydra.Query.SelectBuilders.ContextTypeSqlHydra.Query.UpdateBuilders.UpdateTaskBuilder`2→SqlHydra.Query.SelectBuilders.ContextType
- Direction
- SqlHydra.Query.UpdateBuilders uses SqlHydra.Query.SelectBuilders, so a change to SqlHydra.Query.SelectBuilders can break SqlHydra.Query.UpdateBuilders, while a change to SqlHydra.Query.UpdateBuilders can't break SqlHydra.Query.SelectBuilders.
- Position
- Below the diagonal: SqlHydra.Query.UpdateBuilders uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 16 | High / Critical |
| A02:2025 — Security Misconfiguration | 12 | Medium |
| A05:2025 — Injection | 5 | High / Critical |
Roadmap
Top priorities: Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce; Resolve the 1 No ADRs found finding(s) in ADR Quality — start with REDACTED; Resolve the 1 Banned license finding(s) in License Compliance — start with REDACTED.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with REDACTED. | +5.1 pts | Low | ADR Quality |
| Resolve the 1 Banned license finding(s) in License Compliance — start with REDACTED. | +4.6 pts | Low | License Compliance |
| Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce. | +7.2 pts | Medium | Observability |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +4.2 pts | Medium | Architecture documentation |
| Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery). | +3.3 pts | Medium | DR & Backup |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +2.6 pts | Medium | Release Hygiene |
| 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. | +1.8 pts | Medium | Documentation (README) |
| Resolve the 3 Hotspot finding(s) in Churn × Complexity Hotspots — start with LinqExpressionVisitors.fs, SchemaTemplate.fs, TomlConfigParser.fs. | +1.4 pts | High | Churn × Complexity Hotspots |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.8 | Slop | License Compliance: Banned license: MySql.Data |
| REDACTED | 1.4 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/SqlHydra.Query/SelectBuilders.fs | 5.5 | Mixed | God Classes: TooManyMethods: SelectBuilder`2 |
| src/SqlHydra.Query/LinqExpressionVisitors.fs | 7.0 | Mixed | Cyclomatic Complexity: LinqExpressionVisitors.visitWhere (cyclomatic 108) |
| src/SqlHydra.Query/SqlEmitters.fs | 7.0 | Mixed | Code Duplication: Duplicated block (3–7 lines × 5) |
| src/SqlHydra.Cli/MySql/MySqlSchemaProvider.fs | 7.0 | Mixed | Code Duplication: Members sharing a duplicated core (5 members, 50+ identical tokens) |
| src/SqlHydra.Query/SqlEmitterBase.fs | 7.1 | Mixed | Cyclomatic Complexity: SqlEmitterBase.EmitSelectInto (cyclomatic 29) |
| src/SqlHydra.Query/MySqlExtensions.fs | 7.1 | Mixed | God Classes: TooManyMethods: SqlFn |
| src/SqlHydra.Query/NpgsqlExtensions.fs | 7.2 | Mixed | God Classes: TooManyMethods: SqlFn |
| src/SqlHydra.Cli/SchemaTemplate.fs | 7.4 | Mixed | Cyclomatic Complexity: SchemaTemplate.mkTable (cyclomatic 21) |
| src/SqlHydra.Query/QueryContext.fs | 7.4 | Mixed | Cognitive Complexity: QueryContext.PrepareInsertCommand (cognitive 27) |
| src/SampleApp/DapperExample.fs | 7.4 | Mixed | Code Duplication: Edited copies of one member (3 members, 52+ corresponding lines) |
| src/SqlHydra.Query/SqlServerExtensions.fs | 7.8 | Mixed | God Classes: TooManyMethods: SqlFn |
| src/SqlHydra.Cli/TomlConfigParser.fs | 8.5 | Near-clean | Cyclomatic Complexity: TomlConfigParser.read (cyclomatic 16) |
| src/SqlHydra.Query/Hydration.fs | 8.5 | Near-clean | Cognitive Complexity: ColumnReadMethods.ConvertOracleProviderType (cognitive 21) |
| src/SqlHydra.Query/OracleExtensions.fs | 8.5 | Near-clean | God Classes: TooManyMethods: SqlFn |
| src/SqlHydra.Query/SqliteExtensions.fs | 8.5 | Near-clean | God Classes: TooManyMethods: SqlFn |
| src/SqlHydra.Cli/MySql/MySqlDataTypes.fs | 8.5 | Near-clean | Code Duplication: Duplicated block (16 lines × 3) |
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 37 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 37 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, 113 of 123 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 · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Coverage NOT MEASURED: `--collect:"XPlat Code Coverage"` names a data collector that ships in the `coverlet.collector` package, and this repository wires up none — no test project references it and no runsettings declares one. The absence of coverage here is therefore not evidence about the suite or about our analyzer environment: without a collector, `--collect` produces nothing even from a suite that builds and passes. Add a `coverlet.collector` PackageReference to the test project(s) (or commit the Cobertura/OpenCover/lcov report your CI produces) and real coverage will be measured. It is excluded from the score rather than counted as a near-zero defect. You can widen what we reach: add the `coverlet.collector` package to the test projects to enable coverage (or commit the Cobertura/OpenCover/lcov report your CI produces).
- 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: `dotnet list package` exited 1 with no output.
- 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/SqlHydra.Cli/TomlConfigParser.fs, src/SqlHydra.Cli/SchemaTemplate.fs, src/SqlHydra.Query/LinqExpressionVisitors.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 (16 contributor(s) across 1283 commit(s) sampled, automation and bot accounts excluded). One of them holds 90% of the history; the other 15 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.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. This repository's source is written only in languages whose packages are published through a manifest, and no manifest in the tree makes a publication act: either there is no package manifest of any ecosystem (no package.json, pyproject.toml, setup.py, gemspec, Cargo.toml, pom.xml, build.gradle, composer.json, pubspec.yaml or mix.exs), or every one present declares in its package manager's own terms that it is not published (an npm package marked "private": true, a Cargo package with publish = false, a pubspec with publish_to: none, a Composer "project", a Poetry project with package-mode = false, or the "Private :: Do Not Upload" classifier). With no publication act there is no intentionally-exposed surface for API consistency to be judged over.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D31 IaC & Container Security — 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. Src/.devcontainer/Dockerfile carries no `FROM` instruction, so it declares no build stage and every REDACTED rule this engine owns — the runtime-hardening, key-material, mutable-clone, no-op-shim, build-context, trust-anchor, install-guard, setuid and world-writable-path rules — is outside its own premise there and returned nothing. That silence is deliberate and correct: with no base image there is no image to reason about. It is reported here because it is NOT the same fact as a clean file, and coverage is stated as 3 of 4 Infrastructure-as-Code manifest(s) fully judged rather than as 100%. The vendor scanners (trivy, checkov) do read these files and their findings above stand; only this engine's own stage-keyed rules are absent. No owner action: a build file with no FROM is a legitimate include fragment.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 17 — an image could not be built) — failed to solve: process "/bin/sh -c apt-get update" did not complete successfully: exit code: 100; runtime evidence skipped.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
- C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
- C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- P8 Schema migrations — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads EF Core usage in C# and the schema tooling its file scan recognises only, and no .NET project was loaded, and this repository's language is not one the scan models, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X13 Undrained process stream — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X14 Bypassable address classification — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X15 Unvalidated length from an untrusted reader — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X18 Disposal-pattern correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X19 Unrestored process-global state — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X21 Side-effecting pattern guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X22 Contradicted release guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X25 Inert configuration knob — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X26 Unsynchronised callback handoff — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X29 Per-element action decided by a fixed element — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X3 Exception handling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X30 Support guard that admits what it rejects — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X32 Type resolved by simple name across every loaded assembly — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X5 Nullable reference types — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X6 Hand-rolled structured-format parsing — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Python, JavaScript/TypeScript, Go, Java/Kotlin/Scala, Ruby, PHP, Rust, Swift, Erlang, Elixir and Dart source only, and no C# was loaded and none of those languages was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X7 Silent fallback defaults — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C#, Python, TypeScript/JavaScript, Rust, Go, Java, Kotlin, Scala, PHP, Ruby, Swift and Dart syntax only, and no C#, Python, TypeScript/JavaScript, Rust, Go, Java, Kotlin, Scala, PHP, Ruby, Swift or Dart was loaded for this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- 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.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- 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.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- 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 REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
- 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
10 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was LinqExpressionVisitors.visitWhere at 108. A further 1 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 SqlEmitterBase.EmitWhereInner at 23 — they are counted neither in the figure above nor in this dimension's score.
What to do
- Bring the 1 body over 60 down to 60 or less in Cyclomatic Complexity — start with LinqExpressionVisitors.visitWhere (cyclomatic 108). — Refactoring it lifts Cyclomatic Complexity from 7.1 to about 7.7/10.
D2 · Cognitive Complexity
12 method(s) exceeded the cognitive complexity threshold of 15; the worst was LinqExpressionVisitors.visitWhere at 128.
What to do
- Bring the 2 bodies over 60 down to 60 or less in Cognitive Complexity — start with LinqExpressionVisitors.visitWhere (cognitive 128), LinqExpressionVisitors.visitSelect (cognitive 67). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 6.8 to about 7.6/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
D3 · God Classes
10 god class(es) detected.
What to do
- Resolve the 8 TooManyMethods finding(s) in God Classes — start with NpgsqlExtensions.fs, MySqlExtensions.fs, OracleExtensions.fs. — One of this dimension's main actionable groups (8 warning-level).
- Resolve the 2 FileTooLong finding(s) in God Classes — start with LinqExpressionVisitors.fs, SelectBuilders.fs. — One of this dimension's main actionable groups (2 warning-level).
D4 · Code Duplication
37 duplicated block group(s) detected. A further 4 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
What to do
- Resolve the 5 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with LinqExpressionVisitors.fs (2), SelectBuilders.fs (2), SqlEmitterBase.fs. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 4 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with LinqExpressionVisitors.fs, DeleteBuilders.fs, SelectBuilders.fs. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 4 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with LinqExpressionVisitors.fs, MySqlExtensions.fs, NpgsqlExtensions.fs. — One of this dimension's main actionable groups (4 warning-level).
D5 · Coupling
6 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D6 · Cohesion (LCOM4)
2 of 103 classes have LCOM4 above 3.
What to do
- Resolve the 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with SelectBuilders.fs, SqlEmitters.fs. — One of this dimension's main actionable groups (2 warning-level).
D11 · Test Reliability
0 flaky across 1 measured tier(s). unit: measured (0 flaky).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets. 7 detection(s) were excluded as holding no minted credential in material that runs: a name, reference or comparison rather than a value, a readable phrase or pattern, a value that declares itself fake, or development, test, example, mock or demo material.
D14 · License Compliance
1 of 255 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 27 direct `PackageReference`(s), and 223 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.
What to do
- Resolve the 1 Banned license finding(s) in License Compliance — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D15 · Churn × Complexity Hotspots
Top hotspots: src/SqlHydra.Query/LinqExpressionVisitors.fs (18×108=1944); src/SqlHydra.Cli/SchemaTemplate.fs (8×21=168); src/SqlHydra.Cli/TomlConfigParser.fs (3×16=48)
What to do
- Resolve the 3 Hotspot finding(s) in Churn × Complexity Hotspots — start with LinqExpressionVisitors.fs, SchemaTemplate.fs, TomlConfigParser.fs. — One of this dimension's main actionable groups (3 warning-level).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 5 build units (MSBuild) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
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)
5 finding(s): 0 critical, 5 high, 0 medium, 0 low. 5 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 1 file(s) — `src/.devcontainer/library-scripts/azcli-debian.sh` (line 24) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- No action in Static Analysis (SAST) — all 5 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 (5 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
10 finding(s): 2 critical, 4 high, 4 medium, 0 low.
What to do
- Resolve the 4 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3), REDACTED. — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 4 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 2 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
D31 · IaC & Container Security
12 finding(s): 0 critical, 0 high, 0 medium, 12 low.
What to do
- Resolve the 12 Low IaC finding(s) in IaC & Container Security — start with REDACTED (11), REDACTED. — One of this dimension's main actionable groups (12 recommendation-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 40 of the 67 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 6 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX8 · Test isolation
GD1 · Unfinished & placeholder code
- A shipped binding's whole body still raises a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface. (×2) — src/SqlHydra.Query/LinqExpressionVisitors.fs:8, src/SqlHydra.Query/QuotationVisitor.fs:7
What to do
- Finish or delete the bindings that still raise "not implemented", and replace placeholder text before shipping.
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
P1 · CI/CD gates
P2 · Observability
- No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
What to do
- Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
P3 · Security & performance 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 2 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:9
- `REDACTED` 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`. — REDACTED:17
What to do
- Add a SAST step to CI running what this repository's stack ships: `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P5 · DR & Backup
What to do
- Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
- No persistence guard on critical data stores — use Docker named volumes (or your orchestrator's persistent-volume equivalent) so the data store can't be wiped by a container recreate (or, in cloud, set purge-protection / soft-delete / prevent_destroy).
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF3 · Async & latency hygiene
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 75% | Checked 4 of 11 | Solid. |
| Architecture | 98% | Exemplary | Solid. |
| Maturity | 62% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 35% | Weak — gated by P2, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 75% | Checked 5 of 11 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 2 check(s) recorded observations but carry no score
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 3 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
Not included — 75 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: this repository's F# imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No F# function in this code takes an ASP.NET Core or Suave HttpContext (a Giraffe, Saturn, Falco, Oxpecker or Suave handler) and no F# class is an ASP.NET Core controller, so no request handler shares module state between request threads.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — compose up failed (exit 17 — an image could not be built) — failed to solve: process "/bin/sh -c apt-get update" did not complete successfully: exit code: 100; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- D10 Test Quality — ~58262 lines of test source are present (.fs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D12 Dependency Hygiene — Dependency hygiene not measured
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D17 Explicit Debt — the C# workspace loaded 0 projects, so explicit-debt density could not be measured
- D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution; this repository's .NET projects are all F# (.fsproj), which the C#/VB workspace does not load, so the dimension does not apply.
- D19 Documentation Quality — No runnable or published unit to look for an example in, and no multi-project root README to look for a map in; the other documentation kinds are withheld (see the gaps), so documentation quality is not applicable here.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; F# not measured.
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .fs, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- D8 Code Coverage — Coverage not measured — no coverage collector is wired up
- DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 724 value object(s); a Domain/Aggregates/ValueObjects layer
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- M4 Documentation accuracy — Not applicable: the 2 current-state document(s) make no claim of a kind M4 checks.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not measured — the application kind could not be determined for this repo
- P8 Schema migrations — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for a BenchmarkDotNet reference in an .fsproj or .vbproj, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X12 Unreachable branch — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X13 Undrained process stream — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X14 Bypassable address classification — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X15 Unvalidated length from an untrusted reader — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X16 Unfloored truncation loop — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X17 Uncapped recursion over a caller-supplied document — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X18 Disposal-pattern correctness — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X19 Unrestored process-global state — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X21 Side-effecting pattern guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X22 Contradicted release guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X25 Inert configuration knob — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X26 Unsynchronised callback handoff — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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 — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X3 Exception handling — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X30 Support guard that admits what it rejects — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X32 Type resolved by simple name across every loaded assembly — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X7 Silent fallback defaults — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 12 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Banned license: MySql.Data REDACTED:60
Serious — 88 finding(s)
- TooManyMethods: SqlFn src/SqlHydra.Query/NpgsqlExtensions.fs:8
- TooManyMethods: SqlFn src/SqlHydra.Query/MySqlExtensions.fs:8
- TooManyMethods: SqlFn src/SqlHydra.Query/OracleExtensions.fs:8
- TooManyMethods: SqlFn src/SqlHydra.Query/SqlServerExtensions.fs:8
- TooManyMethods: SqlFn src/SqlHydra.Query/SqliteExtensions.fs:8
- TooManyMethods: SelectBuilder`2 src/SqlHydra.Query/SelectBuilders.fs:112
- TooManyMethods: QueryContext src/SqlHydra.Query/QueryContext.fs:19
- TooManyMethods: SqlEmitterBase src/SqlHydra.Query/SqlEmitterBase.fs:24
- Duplicated block (6 lines × 2) src/SqlHydra.Query/LinqExpressionVisitors.fs:898
- Duplicated block (6 lines × 2) src/SqlHydra.Query/LinqExpressionVisitors.fs:917
- Duplicated block (6 lines × 2) src/SqlHydra.Query/SelectBuilders.fs:246
- Duplicated block (6 lines × 2) src/SqlHydra.Query/SelectBuilders.fs:695
- Duplicated block (6 lines × 2) src/SqlHydra.Query/SqlEmitterBase.fs:141
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (8 lines × 2) src/SqlHydra.Query/LinqExpressionVisitors.fs:1238
- Duplicated block (8 lines × 2) src/SqlHydra.Query/DeleteBuilders.fs:34
- Duplicated block (8 lines × 2) src/SqlHydra.Query/SelectBuilders.fs:790
- Duplicated block (8 lines × 2) src/SqlHydra.Query/MySqlExtensions.fs:27
- Duplicated block (5 lines × 2) src/SqlHydra.Query/LinqExpressionVisitors.fs:972
- Duplicated block (5 lines × 2) src/SqlHydra.Query/MySqlExtensions.fs:51
- Duplicated block (5 lines × 2) src/SqlHydra.Query/NpgsqlExtensions.fs:214
- Duplicated block (5 lines × 2) src/SqlHydra.Query/InsertBuilders.fs:94
- Hotspot: src/SqlHydra.Query/LinqExpressionVisitors.fs src/SqlHydra.Query/LinqExpressionVisitors.fs:768
- Hotspot: src/SqlHydra.Cli/SchemaTemplate.fs src/SqlHydra.Cli/SchemaTemplate.fs:80
- Hotspot: src/SqlHydra.Cli/TomlConfigParser.fs src/SqlHydra.Cli/TomlConfigParser.fs:53
- FileTooLong: SqlHydra.Query/LinqExpressionVisitors.fs src/SqlHydra.Query/LinqExpressionVisitors.fs
- FileTooLong: SqlHydra.Query/SelectBuilders.fs src/SqlHydra.Query/SelectBuilders.fs
- Duplicated block (11 lines × 2) src/SqlHydra.Cli/MySql/MySqlSchemaProvider.fs:88
- Duplicated block (11 lines × 2) src/SqlHydra.Cli/MySql/MySqlSchemaProvider.fs:33
- Low cohesion: SelectBuilder`2 (LCOM4 14) src/SqlHydra.Query/SelectBuilders.fs:112
- Low cohesion: SqlServerEmitter (LCOM4 4) src/SqlHydra.Query/SqlEmitters.fs:9
- Unfinished stub — raises a "not implemented" error src/SqlHydra.Query/LinqExpressionVisitors.fs:8
- Unfinished stub — raises a "not implemented" error src/SqlHydra.Query/QuotationVisitor.fs:7
- LinqExpressionVisitors.visitWhere (cyclomatic 108) src/SqlHydra.Query/LinqExpressionVisitors.fs:768
- LinqExpressionVisitors.visitSelect (cyclomatic 57) src/SqlHydra.Query/LinqExpressionVisitors.fs:1648
- LinqExpressionVisitors.visitJoinPredicate (cyclomatic 42) src/SqlHydra.Query/LinqExpressionVisitors.fs:1425
- LinqExpressionVisitors.visitSqlFn (cyclomatic 40) src/SqlHydra.Query/LinqExpressionVisitors.fs:634
- LinqExpressionVisitors.visitHaving (cyclomatic 32) src/SqlHydra.Query/LinqExpressionVisitors.fs:1158
- SqlEmitterBase.EmitSelectInto (cyclomatic 29) src/SqlHydra.Query/SqlEmitterBase.fs:261
- SchemaTemplate.mkTable (cyclomatic 21) src/SqlHydra.Cli/SchemaTemplate.fs:80
- LinqExpressionVisitors.visitOrderByPropertySelector (cyclomatic 18) src/SqlHydra.Query/LinqExpressionVisitors.fs:1308
- TomlConfigParser.read (cyclomatic 16) src/SqlHydra.Cli/TomlConfigParser.fs:53
- LinqExpressionVisitors.sqlTypeForClrType (cyclomatic 16) src/SqlHydra.Query/LinqExpressionVisitors.fs:62
- LinqExpressionVisitors.visitWhere (cognitive 128) src/SqlHydra.Query/LinqExpressionVisitors.fs:768
- LinqExpressionVisitors.visitSelect (cognitive 67) src/SqlHydra.Query/LinqExpressionVisitors.fs:1648
- LinqExpressionVisitors.visitJoinPredicate (cognitive 41) src/SqlHydra.Query/LinqExpressionVisitors.fs:1425
- LinqExpressionVisitors.visitHaving (cognitive 40) src/SqlHydra.Query/LinqExpressionVisitors.fs:1158
- LinqExpressionVisitors.visitSqlFn (cognitive 33) src/SqlHydra.Query/LinqExpressionVisitors.fs:634
- QueryContext.PrepareInsertCommand (cognitive 27) src/SqlHydra.Query/QueryContext.fs:324
- SchemaTemplate.mkTable (cognitive 26) src/SqlHydra.Cli/SchemaTemplate.fs:80
- QueryContext.ReadReturningValues (cognitive 24) src/SqlHydra.Query/QueryContext.fs:232
- SqlEmitterBase.EmitSelectInto (cognitive 24) src/SqlHydra.Query/SqlEmitterBase.fs:261
- SchemaTemplate.generate (cognitive 21) src/SqlHydra.Cli/SchemaTemplate.fs:299
- ColumnReadMethods.ConvertOracleProviderType (cognitive 21) src/SqlHydra.Query/Hydration.fs:45
- LinqExpressionVisitors.sqlTypeForClrType (cognitive 17) src/SqlHydra.Query/LinqExpressionVisitors.fs:62
- REDACTED
- REDACTED
- Members sharing a duplicated core (5 members, 50+ identical tokens) src/SqlHydra.Cli/MySql/MySqlSchemaProvider.fs:1
- Edited copy of a member (103 corresponding lines) src/SqlHydra.Query/SqlServerExtensions.fs:1
- Edited copy of a member (81 corresponding lines) src/SqlHydra.Query/MySqlExtensions.fs:1
- Edited copies of one member (3 members, 52+ corresponding lines) src/SampleApp/DapperExample.fs:1
- Duplicated block (49 lines × 2) src/SqlHydra.Query/SelectBuilders.fs:729
- Duplicated block (41 lines × 2) src/SqlHydra.Query/LinqExpressionVisitors.fs:813
- Duplicated block (34 lines × 4) src/SqlHydra.Cli/MySql/MySqlSchemaProvider.fs:105
- Duplicated block (20 lines × 2) src/SqlHydra.Query/SelectBuilders.fs:403
- Duplicated block (19 lines × 2) src/SqlHydra.Query/LinqExpressionVisitors.fs:1538
- Duplicated block (21–29 lines × 3) src/SqlHydra.Query/SelectBuilders.fs:367
- Duplicated block (18 lines × 2) src/SqlHydra.Cli/MySql/MySqlSchemaProvider.fs:58
- Duplicated block (2–18 lines × 3) src/SqlHydra.Query/NpgsqlExtensions.fs:275
- Duplicated block (16 lines × 3) src/SqlHydra.Cli/MySql/MySqlDataTypes.fs:61
- Duplicated block (16 lines × 2) src/SampleApp/DapperExample.fs:41
- Duplicated block (12–13 lines × 5) src/SqlHydra.Cli/MySql/MySqlSchemaProvider.fs:122
- Duplicated block (12–13 lines × 2) src/SqlHydra.Query/LinqExpressionVisitors.fs:1329
- Duplicated block (11–12 lines × 2) src/SqlHydra.Query/SqlEmitterBase.fs:90
- Duplicated block (9–11 lines × 2) src/SqlHydra.Query/LinqExpressionVisitors.fs:1264
- Duplicated block (9 lines × 5) src/SqlHydra.Cli/MySql/MySqlSchemaProvider.fs:107
- Duplicated block (6–9 lines × 3) src/SqlHydra.Query/LinqExpressionVisitors.fs:769
- Duplicated block (10 lines × 2) src/SqlHydra.Query/LinqExpressionVisitors.fs:856
- Duplicated block (8 lines × 3) src/SqlHydra.Query/LinqExpressionVisitors.fs:985
- Duplicated block (3–7 lines × 5) src/SqlHydra.Query/SqlEmitters.fs:83
- Duplicated block (31 lines × 2) src/SqlHydra.Query/NpgsqlExtensions.fs:256
- Duplicated block (12 lines × 3) src/SampleApp/DapperExample.fs:43
- Duplicated block (5 lines × 3) src/SqlHydra.Query/MySqlExtensions.fs:13
- No structured logging
- NuGet dependencies are not locked
Minor — 23 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs found REDACTED:4
- Projects may be oversized for their cohesion
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No SAST REDACTED:9
- No dependency-update automation REDACTED:17
- No changelog
- Duplicated predicate src/SqlHydra.Query/QueryContext.fs:206
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-02deae327b7b40f2ad74263c4f6fbdc5/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-02deae327b7b40f2ad74263c4f6fbdc5/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 . | 5 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list src/SqlHydra.sln package --vulnerable --include-transitive --format json | 10 | artifacts/raw/dotnet-vulnerable.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 12 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-acfad01828b645a6aa170184ed23f188 | 0 | artifacts/raw/osv-scanner.json |