Executive summary
cmeeren/Facil falls short of our standard for production because we found no automated security scanning of the code, its secrets or its dependencies. It scores 65 out of 100 and is rated Adequate, and 11 of its 13 critical findings are security problems.
Production Readiness, at 58, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 5 points. Adding a release approval would lift Production Readiness itself, worth about 3 points. Raising Production Readiness to 70 would lift the score to about 69.
Five pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Three settings leave the servers or containers unsafe, and two passwords or keys are open to anyone who can read the repository. Pinning each tool to an exact version, correcting the unsafe settings and replacing each exposed password or key would close these risks. Limiting each secret to its own step would fix the secret exposed to more of the pipeline than needed. The two errors that are caught and ignored need handling or logging instead of being ignored.
The product code is 44,282 lines, about €72,000 to rebuild.
If Production Readiness rose from 58 to 70, the lowest score rated Strong, the score would rise from 65 to about 69.
Rebuild cost: about €72,000 · Estimate
| Cost to rebuild | €24,000 to €120,000, for 396 to 1,256 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.9 at a score of 65. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 44,282 lines of product code |
| Comment lines | The estimate prices 44,260 lines. Comment lines count towards the size of 44,282 lines but aren't priced as work. |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 Config | 2 Config.FacilConfig | 3 Md5 | 4 Program | 5 Runtime | 6 Runtime.CSharp | 7 Runtime.GeneratedCodeUtils.Option | 8 Runtime.GeneratedCodeUtils.Task | 9 Runtime.GeneratedCodeUtils.ValueOption | 10 ScriptIncludes | 11 Utils | 12 Utils.List | 13 Config.EffectiveProcedureOrScriptRuleModule | 14 Config.EffectiveProcedureRuleModule | 15 Config.EffectiveScriptRuleModule | 16 Config.EffectiveTableDtoRuleModule | 17 Config.EffectiveTableScriptTypeRuleModule | 18 Config.ProcedureColumnModule | 19 Config.ProcedureOrScriptColumnModule | 20 Config.ProcedureOrScriptParameterModule | 21 Config.ProcedureParameterModule | 22 Config.ProcedureRuleModule | 23 Config.RuleSetModule | 24 Config.ScriptColumnModule | 25 Config.ScriptParameterModule | 26 Config.ScriptRuleModule | 27 Config.TableDtoColumnDtoModule | 28 Config.TableDtoColumnModule | 29 Config.TableDtoRuleModule | 30 Config.TableScriptColumnModule | 31 Config.TableScriptRuleModule | 32 Config.TableScriptTypeRuleModule | 33 Config.TableTypeRuleModule | 34 Config.TempTableRuleModule | 35 Domain | 36 Runtime.GeneratedCodeUtils | 37 Db | 38 Domain.TableColumnModule | 39 Domain.TableDtoModule | 40 Render |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Config | ||||||||||||||||||||||||||||||||||||||||
| 2 Config.FacilConfig | ||||||||||||||||||||||||||||||||||||||||
| 3 Md5 | ||||||||||||||||||||||||||||||||||||||||
| 4 Program | ||||||||||||||||||||||||||||||||||||||||
| 5 Runtime | ||||||||||||||||||||||||||||||||||||||||
| 6 Runtime.CSharp | ||||||||||||||||||||||||||||||||||||||||
| 7 Runtime.GeneratedCodeUtils.Option | ||||||||||||||||||||||||||||||||||||||||
| 8 Runtime.GeneratedCodeUtils.Task | ||||||||||||||||||||||||||||||||||||||||
| 9 Runtime.GeneratedCodeUtils.ValueOption | ||||||||||||||||||||||||||||||||||||||||
| 10 ScriptIncludes | ||||||||||||||||||||||||||||||||||||||||
| 11 Utils | ||||||||||||||||||||||||||||||||||||||||
| 12 Utils.List | ||||||||||||||||||||||||||||||||||||||||
| 13 Config.EffectiveProcedureOrScriptRuleModule | 4 | |||||||||||||||||||||||||||||||||||||||
| 14 Config.EffectiveProcedureRuleModule | 3 | |||||||||||||||||||||||||||||||||||||||
| 15 Config.EffectiveScriptRuleModule | 3 | |||||||||||||||||||||||||||||||||||||||
| 16 Config.EffectiveTableDtoRuleModule | 2 | |||||||||||||||||||||||||||||||||||||||
| 17 Config.EffectiveTableScriptTypeRuleModule | 2 | |||||||||||||||||||||||||||||||||||||||
| 18 Config.ProcedureColumnModule | 2 | |||||||||||||||||||||||||||||||||||||||
| 19 Config.ProcedureOrScriptColumnModule | 3 | |||||||||||||||||||||||||||||||||||||||
| 20 Config.ProcedureOrScriptParameterModule | 3 | |||||||||||||||||||||||||||||||||||||||
| 21 Config.ProcedureParameterModule | 2 | |||||||||||||||||||||||||||||||||||||||
| 22 Config.ProcedureRuleModule | 3 | |||||||||||||||||||||||||||||||||||||||
| 23 Config.RuleSetModule | 8 | |||||||||||||||||||||||||||||||||||||||
| 24 Config.ScriptColumnModule | 2 | |||||||||||||||||||||||||||||||||||||||
| 25 Config.ScriptParameterModule | 2 | |||||||||||||||||||||||||||||||||||||||
| 26 Config.ScriptRuleModule | 3 | |||||||||||||||||||||||||||||||||||||||
| 27 Config.TableDtoColumnDtoModule | 1 | |||||||||||||||||||||||||||||||||||||||
| 28 Config.TableDtoColumnModule | 2 | |||||||||||||||||||||||||||||||||||||||
| 29 Config.TableDtoRuleModule | 3 | |||||||||||||||||||||||||||||||||||||||
| 30 Config.TableScriptColumnModule | 2 | |||||||||||||||||||||||||||||||||||||||
| 31 Config.TableScriptRuleModule | 5 | |||||||||||||||||||||||||||||||||||||||
| 32 Config.TableScriptTypeRuleModule | 3 | |||||||||||||||||||||||||||||||||||||||
| 33 Config.TableTypeRuleModule | 3 | |||||||||||||||||||||||||||||||||||||||
| 34 Config.TempTableRuleModule | 2 | |||||||||||||||||||||||||||||||||||||||
| 35 Domain | 1 | |||||||||||||||||||||||||||||||||||||||
| 36 Runtime.GeneratedCodeUtils | 1 | |||||||||||||||||||||||||||||||||||||||
| 37 Db | 1 | 9 | ||||||||||||||||||||||||||||||||||||||
| 38 Domain.TableColumnModule | 2 | |||||||||||||||||||||||||||||||||||||||
| 39 Domain.TableDtoModule | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 40 Render | 1 | 7 |
13→1 Config.EffectiveProcedureOrScriptRuleModule uses Config✕
- Connections
- 4 pairs of types, where a type in Config.EffectiveProcedureOrScriptRuleModule uses a type in Config.
- The types involved
Facil.Config.EffectiveProcedureOrScriptRuleModule.EffectiveProcedureOrScriptRuleModule→Facil.Config.EffectiveProcedureOrScriptRuleFacil.Config.EffectiveProcedureOrScriptRuleModule.EffectiveProcedureOrScriptRuleModule→Facil.Config.EffectiveProcedureRuleFacil.Config.EffectiveProcedureOrScriptRuleModule.EffectiveProcedureOrScriptRuleModule→Facil.Config.EffectiveScriptRuleFacil.Config.EffectiveProcedureOrScriptRuleModule.EffectiveProcedureOrScriptRuleModule→Facil.Config.ProcedureOrScriptParameter
- Direction
- Config.EffectiveProcedureOrScriptRuleModule uses Config, so a change to Config can break Config.EffectiveProcedureOrScriptRuleModule, while a change to Config.EffectiveProcedureOrScriptRuleModule can't break Config.
- Position
- Below the diagonal: Config.EffectiveProcedureOrScriptRuleModule uses a module listed above it, which is the healthy direction.
14→1 Config.EffectiveProcedureRuleModule uses Config✕
- Connections
- 3 pairs of types, where a type in Config.EffectiveProcedureRuleModule uses a type in Config.
- The types involved
Facil.Config.EffectiveProcedureRuleModule.EffectiveProcedureRuleModule→Facil.Config.EffectiveProcedureRuleFacil.Config.EffectiveProcedureRuleModule.EffectiveProcedureRuleModule→Facil.Config.ProcedureColumnFacil.Config.EffectiveProcedureRuleModule.EffectiveProcedureRuleModule→Facil.Config.ProcedureParameter
- Direction
- Config.EffectiveProcedureRuleModule uses Config, so a change to Config can break Config.EffectiveProcedureRuleModule, while a change to Config.EffectiveProcedureRuleModule can't break Config.
- Position
- Below the diagonal: Config.EffectiveProcedureRuleModule uses a module listed above it, which is the healthy direction.
15→1 Config.EffectiveScriptRuleModule uses Config✕
- Connections
- 3 pairs of types, where a type in Config.EffectiveScriptRuleModule uses a type in Config.
- The types involved
Facil.Config.EffectiveScriptRuleModule.EffectiveScriptRuleModule→Facil.Config.EffectiveScriptRuleFacil.Config.EffectiveScriptRuleModule.EffectiveScriptRuleModule→Facil.Config.ScriptColumnFacil.Config.EffectiveScriptRuleModule.EffectiveScriptRuleModule→Facil.Config.ScriptParameter
- Direction
- Config.EffectiveScriptRuleModule uses Config, so a change to Config can break Config.EffectiveScriptRuleModule, while a change to Config.EffectiveScriptRuleModule can't break Config.
- Position
- Below the diagonal: Config.EffectiveScriptRuleModule uses a module listed above it, which is the healthy direction.
16→1 Config.EffectiveTableDtoRuleModule uses Config✕
- Connections
- 2 pairs of types, where a type in Config.EffectiveTableDtoRuleModule uses a type in Config.
- The types involved
Facil.Config.EffectiveTableDtoRuleModule.EffectiveTableDtoRuleModule→Facil.Config.EffectiveTableDtoRuleFacil.Config.EffectiveTableDtoRuleModule.EffectiveTableDtoRuleModule→Facil.Config.TableDtoColumn
- Direction
- Config.EffectiveTableDtoRuleModule uses Config, so a change to Config can break Config.EffectiveTableDtoRuleModule, while a change to Config.EffectiveTableDtoRuleModule can't break Config.
- Position
- Below the diagonal: Config.EffectiveTableDtoRuleModule uses a module listed above it, which is the healthy direction.
17→1 Config.EffectiveTableScriptTypeRuleModule uses Config✕
- Connections
- 2 pairs of types, where a type in Config.EffectiveTableScriptTypeRuleModule uses a type in Config.
- The types involved
Facil.Config.EffectiveTableScriptTypeRuleModule.EffectiveTableScriptTypeRuleModule→Facil.Config.EffectiveTableScriptTypeRuleFacil.Config.EffectiveTableScriptTypeRuleModule.EffectiveTableScriptTypeRuleModule→Facil.Config.TableScriptColumn
- Direction
- Config.EffectiveTableScriptTypeRuleModule uses Config, so a change to Config can break Config.EffectiveTableScriptTypeRuleModule, while a change to Config.EffectiveTableScriptTypeRuleModule can't break Config.
- Position
- Below the diagonal: Config.EffectiveTableScriptTypeRuleModule uses a module listed above it, which is the healthy direction.
18→1 Config.ProcedureColumnModule uses Config✕
- Connections
- 2 pairs of types, where a type in Config.ProcedureColumnModule uses a type in Config.
- The types involved
Facil.Config.ProcedureColumnModule.ProcedureColumnModule→Facil.Config.ProcedureColumnFacil.Config.ProcedureColumnModule.ProcedureColumnModule→Facil.Config.ProcedureColumnDto
- Direction
- Config.ProcedureColumnModule uses Config, so a change to Config can break Config.ProcedureColumnModule, while a change to Config.ProcedureColumnModule can't break Config.
- Position
- Below the diagonal: Config.ProcedureColumnModule uses a module listed above it, which is the healthy direction.
19→1 Config.ProcedureOrScriptColumnModule uses Config✕
- Connections
- 3 pairs of types, where a type in Config.ProcedureOrScriptColumnModule uses a type in Config.
- The types involved
Facil.Config.ProcedureOrScriptColumnModule.ProcedureOrScriptColumnModule→Facil.Config.ProcedureColumnFacil.Config.ProcedureOrScriptColumnModule.ProcedureOrScriptColumnModule→Facil.Config.ProcedureOrScriptColumnFacil.Config.ProcedureOrScriptColumnModule.ProcedureOrScriptColumnModule→Facil.Config.ScriptColumn
- Direction
- Config.ProcedureOrScriptColumnModule uses Config, so a change to Config can break Config.ProcedureOrScriptColumnModule, while a change to Config.ProcedureOrScriptColumnModule can't break Config.
- Position
- Below the diagonal: Config.ProcedureOrScriptColumnModule uses a module listed above it, which is the healthy direction.
20→1 Config.ProcedureOrScriptParameterModule uses Config✕
- Connections
- 3 pairs of types, where a type in Config.ProcedureOrScriptParameterModule uses a type in Config.
- The types involved
Facil.Config.ProcedureOrScriptParameterModule.ProcedureOrScriptParameterModule→Facil.Config.ProcedureOrScriptParameterFacil.Config.ProcedureOrScriptParameterModule.ProcedureOrScriptParameterModule→Facil.Config.ProcedureParameterFacil.Config.ProcedureOrScriptParameterModule.ProcedureOrScriptParameterModule→Facil.Config.ScriptParameter
- Direction
- Config.ProcedureOrScriptParameterModule uses Config, so a change to Config can break Config.ProcedureOrScriptParameterModule, while a change to Config.ProcedureOrScriptParameterModule can't break Config.
- Position
- Below the diagonal: Config.ProcedureOrScriptParameterModule uses a module listed above it, which is the healthy direction.
21→1 Config.ProcedureParameterModule uses Config✕
- Connections
- 2 pairs of types, where a type in Config.ProcedureParameterModule uses a type in Config.
- The types involved
Facil.Config.ProcedureParameterModule.ProcedureParameterModule→Facil.Config.ProcedureParameterFacil.Config.ProcedureParameterModule.ProcedureParameterModule→Facil.Config.ProcedureParameterDto
- Direction
- Config.ProcedureParameterModule uses Config, so a change to Config can break Config.ProcedureParameterModule, while a change to Config.ProcedureParameterModule can't break Config.
- Position
- Below the diagonal: Config.ProcedureParameterModule uses a module listed above it, which is the healthy direction.
22→1 Config.ProcedureRuleModule uses Config✕
- Connections
- 3 pairs of types, where a type in Config.ProcedureRuleModule uses a type in Config.
- The types involved
Facil.Config.ProcedureRuleModule.ProcedureRuleModule→Facil.Config.EffectiveProcedureRuleFacil.Config.ProcedureRuleModule.ProcedureRuleModule→Facil.Config.ProcedureRuleFacil.Config.ProcedureRuleModule.ProcedureRuleModule→Facil.Config.ProcedureRuleDto
- Direction
- Config.ProcedureRuleModule uses Config, so a change to Config can break Config.ProcedureRuleModule, while a change to Config.ProcedureRuleModule can't break Config.
- Position
- Below the diagonal: Config.ProcedureRuleModule uses a module listed above it, which is the healthy direction.
23→1 Config.RuleSetModule uses Config✕
- Connections
- 8 pairs of types, where a type in Config.RuleSetModule uses a type in Config.
- The types involved
Facil.Config.RuleSetModule.RuleSetModule→Facil.Config.EffectiveProcedureRuleFacil.Config.RuleSetModule.RuleSetModule→Facil.Config.EffectiveScriptRuleFacil.Config.RuleSetModule.RuleSetModule→Facil.Config.EffectiveTableDtoRuleFacil.Config.RuleSetModule.RuleSetModule→Facil.Config.EffectiveTableScriptRuleFacil.Config.RuleSetModule.RuleSetModule→Facil.Config.EffectiveTableTypeRuleFacil.Config.RuleSetModule.RuleSetModule→Facil.Config.RuleSetFacil.Config.RuleSetModule.RuleSetModule→Facil.Config.RuleSetDtoFacil.Config.RuleSetModule.RuleSetModule→Facil.Config.SqlDateType
- Direction
- Config.RuleSetModule uses Config, so a change to Config can break Config.RuleSetModule, while a change to Config.RuleSetModule can't break Config.
- Position
- Below the diagonal: Config.RuleSetModule uses a module listed above it, which is the healthy direction.
24→1 Config.ScriptColumnModule uses Config✕
- Connections
- 2 pairs of types, where a type in Config.ScriptColumnModule uses a type in Config.
- The types involved
Facil.Config.ScriptColumnModule.ScriptColumnModule→Facil.Config.ScriptColumnFacil.Config.ScriptColumnModule.ScriptColumnModule→Facil.Config.ScriptColumnDto
- Direction
- Config.ScriptColumnModule uses Config, so a change to Config can break Config.ScriptColumnModule, while a change to Config.ScriptColumnModule can't break Config.
- Position
- Below the diagonal: Config.ScriptColumnModule uses a module listed above it, which is the healthy direction.
25→1 Config.ScriptParameterModule uses Config✕
- Connections
- 2 pairs of types, where a type in Config.ScriptParameterModule uses a type in Config.
- The types involved
Facil.Config.ScriptParameterModule.ScriptParameterModule→Facil.Config.ScriptParameterFacil.Config.ScriptParameterModule.ScriptParameterModule→Facil.Config.ScriptParameterDto
- Direction
- Config.ScriptParameterModule uses Config, so a change to Config can break Config.ScriptParameterModule, while a change to Config.ScriptParameterModule can't break Config.
- Position
- Below the diagonal: Config.ScriptParameterModule uses a module listed above it, which is the healthy direction.
26→1 Config.ScriptRuleModule uses Config✕
- Connections
- 3 pairs of types, where a type in Config.ScriptRuleModule uses a type in Config.
- The types involved
Facil.Config.ScriptRuleModule.ScriptRuleModule→Facil.Config.EffectiveScriptRuleFacil.Config.ScriptRuleModule.ScriptRuleModule→Facil.Config.ScriptRuleFacil.Config.ScriptRuleModule.ScriptRuleModule→Facil.Config.ScriptRuleDto
- Direction
- Config.ScriptRuleModule uses Config, so a change to Config can break Config.ScriptRuleModule, while a change to Config.ScriptRuleModule can't break Config.
- Position
- Below the diagonal: Config.ScriptRuleModule uses a module listed above it, which is the healthy direction.
27→1 Config.TableDtoColumnDtoModule uses Config✕
- Connections
- 1 pair of types, where a type in Config.TableDtoColumnDtoModule uses a type in Config.
- The types involved
Facil.Config.TableDtoColumnDtoModule.TableDtoColumnDtoModule→Facil.Config.TableDtoColumnDto
- Direction
- Config.TableDtoColumnDtoModule uses Config, so a change to Config can break Config.TableDtoColumnDtoModule, while a change to Config.TableDtoColumnDtoModule can't break Config.
- Position
- Below the diagonal: Config.TableDtoColumnDtoModule uses a module listed above it, which is the healthy direction.
28→1 Config.TableDtoColumnModule uses Config✕
- Connections
- 2 pairs of types, where a type in Config.TableDtoColumnModule uses a type in Config.
- The types involved
Facil.Config.TableDtoColumnModule.TableDtoColumnModule→Facil.Config.TableDtoColumnFacil.Config.TableDtoColumnModule.TableDtoColumnModule→Facil.Config.TableDtoColumnDto
- Direction
- Config.TableDtoColumnModule uses Config, so a change to Config can break Config.TableDtoColumnModule, while a change to Config.TableDtoColumnModule can't break Config.
- Position
- Below the diagonal: Config.TableDtoColumnModule uses a module listed above it, which is the healthy direction.
29→1 Config.TableDtoRuleModule uses Config✕
- Connections
- 3 pairs of types, where a type in Config.TableDtoRuleModule uses a type in Config.
- The types involved
Facil.Config.TableDtoRuleModule.TableDtoRuleModule→Facil.Config.EffectiveTableDtoRuleFacil.Config.TableDtoRuleModule.TableDtoRuleModule→Facil.Config.TableDtoRuleFacil.Config.TableDtoRuleModule.TableDtoRuleModule→Facil.Config.TableDtoRuleDto
- Direction
- Config.TableDtoRuleModule uses Config, so a change to Config can break Config.TableDtoRuleModule, while a change to Config.TableDtoRuleModule can't break Config.
- Position
- Below the diagonal: Config.TableDtoRuleModule uses a module listed above it, which is the healthy direction.
30→1 Config.TableScriptColumnModule uses Config✕
- Connections
- 2 pairs of types, where a type in Config.TableScriptColumnModule uses a type in Config.
- The types involved
Facil.Config.TableScriptColumnModule.TableScriptColumnModule→Facil.Config.TableScriptColumnFacil.Config.TableScriptColumnModule.TableScriptColumnModule→Facil.Config.TableScriptColumnDto
- Direction
- Config.TableScriptColumnModule uses Config, so a change to Config can break Config.TableScriptColumnModule, while a change to Config.TableScriptColumnModule can't break Config.
- Position
- Below the diagonal: Config.TableScriptColumnModule uses a module listed above it, which is the healthy direction.
31→1 Config.TableScriptRuleModule uses Config✕
- Connections
- 5 pairs of types, where a type in Config.TableScriptRuleModule uses a type in Config.
- The types involved
Facil.Config.TableScriptRuleModule.TableScriptRuleModule→Facil.Config.EffectiveTableScriptRuleFacil.Config.TableScriptRuleModule.TableScriptRuleModule→Facil.Config.EffectiveTableScriptTypeRuleFacil.Config.TableScriptRuleModule.TableScriptRuleModule→Facil.Config.TableScriptRuleFacil.Config.TableScriptRuleModule.TableScriptRuleModule→Facil.Config.TableScriptRuleDtoFacil.Config.TableScriptRuleModule.TableScriptRuleModule→Facil.Config.TableScriptType
- Direction
- Config.TableScriptRuleModule uses Config, so a change to Config can break Config.TableScriptRuleModule, while a change to Config.TableScriptRuleModule can't break Config.
- Position
- Below the diagonal: Config.TableScriptRuleModule uses a module listed above it, which is the healthy direction.
32→1 Config.TableScriptTypeRuleModule uses Config✕
- Connections
- 3 pairs of types, where a type in Config.TableScriptTypeRuleModule uses a type in Config.
- The types involved
Facil.Config.TableScriptTypeRuleModule.TableScriptTypeRuleModule→Facil.Config.EffectiveTableScriptTypeRuleFacil.Config.TableScriptTypeRuleModule.TableScriptTypeRuleModule→Facil.Config.TableScriptTypeRuleFacil.Config.TableScriptTypeRuleModule.TableScriptTypeRuleModule→Facil.Config.TableScriptTypeRuleDto
- Direction
- Config.TableScriptTypeRuleModule uses Config, so a change to Config can break Config.TableScriptTypeRuleModule, while a change to Config.TableScriptTypeRuleModule can't break Config.
- Position
- Below the diagonal: Config.TableScriptTypeRuleModule uses a module listed above it, which is the healthy direction.
33→1 Config.TableTypeRuleModule uses Config✕
- Connections
- 3 pairs of types, where a type in Config.TableTypeRuleModule uses a type in Config.
- The types involved
Facil.Config.TableTypeRuleModule.TableTypeRuleModule→Facil.Config.EffectiveTableTypeRuleFacil.Config.TableTypeRuleModule.TableTypeRuleModule→Facil.Config.TableTypeRuleFacil.Config.TableTypeRuleModule.TableTypeRuleModule→Facil.Config.TableTypeRuleDto
- Direction
- Config.TableTypeRuleModule uses Config, so a change to Config can break Config.TableTypeRuleModule, while a change to Config.TableTypeRuleModule can't break Config.
- Position
- Below the diagonal: Config.TableTypeRuleModule uses a module listed above it, which is the healthy direction.
34→1 Config.TempTableRuleModule uses Config✕
- Connections
- 2 pairs of types, where a type in Config.TempTableRuleModule uses a type in Config.
- The types involved
Facil.Config.TempTableRuleModule.TempTableRuleModule→Facil.Config.TempTableRuleFacil.Config.TempTableRuleModule.TempTableRuleModule→Facil.Config.TempTableRuleDto
- Direction
- Config.TempTableRuleModule uses Config, so a change to Config can break Config.TempTableRuleModule, while a change to Config.TempTableRuleModule can't break Config.
- Position
- Below the diagonal: Config.TempTableRuleModule uses a module listed above it, which is the healthy direction.
35→1 Domain uses Config✕
- Connections
- 1 pair of types, where a type in Domain uses a type in Config.
- The types involved
Facil.Domain.Domain→Facil.Config.SqlDateType
- Direction
- Domain uses Config, so a change to Config can break Domain, while a change to Domain can't break Config.
- Position
- Below the diagonal: Domain uses a module listed above it, which is the healthy direction.
36→5 Runtime.GeneratedCodeUtils uses Runtime✕
- Connections
- 1 pair of types, where a type in Runtime.GeneratedCodeUtils uses a type in Runtime.
- The types involved
Facil.Runtime.GeneratedCodeUtils.GeneratedCodeUtils→Facil.Runtime.FacilReaderDisposer
- Direction
- Runtime.GeneratedCodeUtils uses Runtime, so a change to Runtime can break Runtime.GeneratedCodeUtils, while a change to Runtime.GeneratedCodeUtils can't break Runtime.
- Position
- Below the diagonal: Runtime.GeneratedCodeUtils uses a module listed above it, which is the healthy direction.
37→1 Db uses Config✕
- Connections
- 1 pair of types, where a type in Db uses a type in Config.
- The types involved
Facil.Db.Db→Facil.Config.RuleSet
- Direction
- Db uses Config, so a change to Config can break Db, while a change to Db can't break Config.
- Position
- Below the diagonal: Db uses a module listed above it, which is the healthy direction.
37→35 Db uses Domain✕
- Connections
- 9 pairs of types, where a type in Db uses a type in Domain.
- The types involved
Facil.Db.Db→Facil.Domain.EverythingFacil.Db.Db→Facil.Domain.OutputColumnFacil.Db.Db→Facil.Domain.ParameterFacil.Db.Db→Facil.Domain.ScriptFacil.Db.Db→Facil.Domain.SqlTypeInfoFacil.Db.Db→Facil.Domain.StoredProcedureFacil.Db.Db→Facil.Domain.TableDtoFacil.Db.Db→Facil.Domain.TableTypeFacil.Db.Db→Facil.Domain.TempTable
- Direction
- Db uses Domain, so a change to Domain can break Db, while a change to Db can't break Domain.
- Position
- Below the diagonal: Db uses a module listed above it, which is the healthy direction.
38→35 Domain.TableColumnModule uses Domain✕
- Connections
- 2 pairs of types, where a type in Domain.TableColumnModule uses a type in Domain.
- The types involved
Facil.Domain.TableColumnModule.TableColumnModule→Facil.Domain.OutputColumnFacil.Domain.TableColumnModule.TableColumnModule→Facil.Domain.TableColumn
- Direction
- Domain.TableColumnModule uses Domain, so a change to Domain can break Domain.TableColumnModule, while a change to Domain.TableColumnModule can't break Domain.
- Position
- Below the diagonal: Domain.TableColumnModule uses a module listed above it, which is the healthy direction.
39→1 Domain.TableDtoModule uses Config✕
- Connections
- 2 pairs of types, where a type in Domain.TableDtoModule uses a type in Config.
- The types involved
Facil.Domain.TableDtoModule.TableDtoModule→Facil.Config.EffectiveProcedureOrScriptRuleFacil.Domain.TableDtoModule.TableDtoModule→Facil.Config.RuleSet
- Direction
- Domain.TableDtoModule uses Config, so a change to Config can break Domain.TableDtoModule, while a change to Domain.TableDtoModule can't break Config.
- Position
- Below the diagonal: Domain.TableDtoModule uses a module listed above it, which is the healthy direction.
39→35 Domain.TableDtoModule uses Domain✕
- Connections
- 2 pairs of types, where a type in Domain.TableDtoModule uses a type in Domain.
- The types involved
Facil.Domain.TableDtoModule.TableDtoModule→Facil.Domain.OutputColumnFacil.Domain.TableDtoModule.TableDtoModule→Facil.Domain.TableDto
- Direction
- Domain.TableDtoModule uses Domain, so a change to Domain can break Domain.TableDtoModule, while a change to Domain.TableDtoModule can't break Domain.
- Position
- Below the diagonal: Domain.TableDtoModule uses a module listed above it, which is the healthy direction.
40→1 Render uses Config✕
- Connections
- 1 pair of types, where a type in Render uses a type in Config.
- The types involved
Facil.Render.Render→Facil.Config.RuleSet
- Direction
- Render uses Config, so a change to Config can break Render, while a change to Render can't break Config.
- Position
- Below the diagonal: Render uses a module listed above it, which is the healthy direction.
40→35 Render uses Domain✕
- Connections
- 7 pairs of types, where a type in Render uses a type in Domain.
- The types involved
Facil.Render.Render→Facil.Domain.EverythingFacil.Render.Render→Facil.Domain.ParameterFacil.Render.Render→Facil.Domain.ScriptFacil.Render.Render→Facil.Domain.SqlTypeInfoFacil.Render.Render→Facil.Domain.StoredProcedureFacil.Render.Render→Facil.Domain.TableDtoFacil.Render.Render→Facil.Domain.TableType
- Direction
- Render uses Domain, so a change to Domain can break Render, while a change to Render can't break Domain.
- Position
- Below the diagonal: Render uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 7 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 6 | Medium |
| A02:2025 — Security Misconfiguration | 5 | High / Critical |
| A07:2025 — Authentication Failures | 3 | High / Critical |
Roadmap
Top priorities: Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Facil.Generator.fsproj; 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; Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Facil.Generator.fsproj. | +4.9 pts | Low | ADR Quality |
| Resolve the 3 Outdated finding(s) in Dependency Hygiene — start with DbTests.fsproj (3). | +3.0 pts | Low | Dependency Hygiene |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +3.9 pts | Medium | Architecture documentation |
| Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it. | +3.3 pts | Medium | Deployment & Rollback |
| Resolve the 2 EmptyCatchBlock finding(s) in Explicit Debt — start with GeneratedCodeUtils.cs (2). | +1.5 pts | Low | Explicit Debt |
| Resolve the 1 Deprecated finding(s) in Dependency Hygiene — start with DbTests.fsproj. | +1.3 pts | Low | Dependency Hygiene |
| Resolve the 1 Prerelease dependency finding(s) in Dependency Hygiene. | +1.3 pts | Low | Dependency 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. | +2.2 pts | Medium | Documentation (README) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| src/Facil.Runtime.CSharp/GeneratedCodeUtils.cs | 2.2 | Slop | Explicit Debt: EmptyCatchBlock |
| REDACTED | 2.3 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.4 | Mixed | Secrets (history): REDACTED: REDACTED |
| src/Facil.Generator/Db.fs | 7.0 | Mixed | Cyclomatic Complexity: Db.getEverything (cyclomatic 201) |
| src/Facil.Generator/Render.fs | 7.2 | Mixed | Cyclomatic Complexity: Render.renderProcOrScript (cyclomatic 137) |
| src/DbTests/DbTests.fsproj | 7.6 | Mixed | Dependency Hygiene: Deprecated: Hedgehog.Experimental |
| src/Facil.Generator/Program.fs | 7.8 | Mixed | Cyclomatic Complexity: Program.main (cyclomatic 34) |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| src/Facil.Generator/ScriptIncludes.fs | 8.5 | Near-clean | Cognitive Complexity: ScriptIncludes.readSource (cognitive 36) |
| src/Facil.Generator/Config.fs | 8.5 | Near-clean | God Classes: FileTooLong: Facil.Generator/Config.fs |
| src/Facil.Generator/Facil.Generator.fsproj | 9.5 | Near-clean | ADR Quality: No ADRs found |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 38 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 38 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 65 of 88 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
- D4 Code Duplication — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Code Duplication couldn't be assessed within its 7-minute budget on a solution this large — not included in this run.
- D8 Code Coverage — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Coverage NOT MEASURED: `--collect:"XPlat Code Coverage"` names a data collector that ships in the `coverlet.collector` package, and this repository wires up none — no test project references it and no runsettings declares one. The absence of coverage here is therefore not evidence about the suite or about our analyzer environment: without a collector, `--collect` produces nothing even from a suite that builds and passes. Add a `coverlet.collector` PackageReference to the test project(s) (or commit the Cobertura/OpenCover/lcov report your CI produces) and real coverage will be measured. It is excluded from the score rather than counted as a near-zero defect. You can widen what we reach: add the `coverlet.collector` package to the test projects to enable coverage (or commit the Cobertura/OpenCover/lcov report your CI produces).
- 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 (2 contributor(s) across 553 commit(s) sampled, automation and bot accounts excluded). One of them holds 99% of the history; the other 1 hold 1% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D17 Explicit Debt — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Cannot open project 'src/Facil.Generator/Facil.Generator.fsproj' because the file extension '.fsproj' is not associated with a language.
- D17 Explicit Debt — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 4 deducted marker(s) and the 1.1/KLoC density on this row were taken over this repository's .NET projects ALONE: .fs (43,440 lines, 98% of production source) went unread, because every marker collector on this path is reached through a C# workspace. D17's marker collectors need a compiler we do not have for that language, so none of its nine marker kinds were read there. The debt in that source is UNMEASURED — its absence from the score above is a gap in this analyzer's language coverage, not a finding that the code carries none.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D26 Project Cohesion — 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. `Facil.Runtime.CSharp` (842 LoC, 689 public types across 131 namespaces) is over its size bounds, and whether one unit is a coherent whole or a grab-bag is read from its type references: the parts of it that reach the rest only through its shared core. Those are read over the C#/VB code model, which this unit's source did not supply. Its size alone is no verdict on its cohesion, so none is published.
- 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 Dockerfile (REDACTED). docker build failed (exit 1) — 8 | -------------------- ERROR: failed to solve: process "/bin/sh -c apt-get update && apt-get install -y --no-install-recommends curl ca-certificates gnupg && curl -fsSL https://packages.microsoft.com/keys/microsoft.asc | gpg --dearmor -o /usr/share/keyrings/microsoft.gpg" did not complete successfully: exit code: 2; runtime evidence skipped.
- 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's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X18 Disposal-pattern correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X27 Collection changed while being enumerated — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X3 Exception handling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- 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.
- 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 Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
8 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was Db.getEverything at 201. 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 TableScriptTypeRuleModule.defaultEffectiveRuleFor at 20 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: src/Facil.Generator/Config.fs (TableScriptTypeRuleModule.defaultEffectiveRuleFor at 20). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 3 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with Db.getEverything (cyclomatic 201), Render.renderProcOrScript (cyclomatic 137), Program.main (cyclomatic 34). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cyclomatic Complexity from 5.4 to about 8.3/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
D2 · Cognitive Complexity
9 method(s) exceeded the cognitive complexity threshold of 15; the worst was Db.getEverything at 326.
What to do
- Bring the 3 bodies over 60 down to 60 or less in Cognitive Complexity — start with Db.getEverything (cognitive 326), Render.renderProcOrScript (cognitive 261), Program.main (cognitive 65). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cognitive Complexity from 4.0 to about 6.9/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
D3 · God Classes
4 god class(es) detected.
What to do
- Resolve the 3 FileTooLong finding(s) in God Classes — start with Db.fs, Render.fs, Config.fs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 ClassTooLong finding(s) in God Classes — start with GeneratedCodeUtils.cs. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
1 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D6 · Cohesion (LCOM4)
0 of 463 classes have LCOM4 above 3.
D11 · Test Reliability
0 flaky across 2 measured tier(s). unit: measured (0 flaky); other: measured (0 flaky).
D12 · Dependency Hygiene
15 outdated, 0 vulnerable, 1 deprecated, 1 prerelease packages.
What to do
- Resolve the 3 Outdated finding(s) in Dependency Hygiene — start with DbTests.fsproj (3). — One of this dimension's main actionable groups (3 recommendation-level).
- Resolve the 1 Deprecated finding(s) in Dependency Hygiene — start with DbTests.fsproj. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Prerelease dependency finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 warning-level).
D13 · REDACTED Scanning
REDACTED scan ran and found no leaked secrets.
D14 · License Compliance
0 of 172 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 18 direct `PackageReference`(s), and 143 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.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
4 deducted debt markers + unmeasured dead symbols across 842 LoC in the .NET projects (1.1/KLoC) → score 7.9. Dead code not measured: the solution did not load cleanly, so the reference search was skipped. Measured on the .NET source only: .fs (98% of production source) was not read, and carries at least 0 uncounted task marker(s) in 0 file(s).
What to do
- Resolve the 2 EmptyCatchBlock finding(s) in Explicit Debt — start with GeneratedCodeUtils.cs (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 2 BareSuppressMessage finding(s) in Explicit Debt — start with GeneratedCodeUtils.cs (2). — One of this dimension's main actionable groups (2 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 1 document(s) read across 2 unit(s).
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 Facil.Generator.fsproj. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
61 % of calls cross a namespace and 0 % go through an interface, but 98 % 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)
2 finding(s): 0 critical, 2 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 2 REDACTED finding(s) in Secrets (history) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
7 finding(s): 0 critical, 6 high, 1 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.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- 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
No known-vulnerable dependencies in any ecosystem this repository declares.
D31 · IaC & Container Security
5 finding(s): 0 critical, 3 high, 1 medium, 1 low.
What to do
- Resolve the 3 High IaC finding(s) in IaC & Container Security — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 1 Medium IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Low IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 14 of the 15 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. — 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 9 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
AX5 · Architecture & structure
AX8 · Test isolation
GD1 · Unfinished & placeholder code
- A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface. (×19) — src/Facil.Runtime.CSharp/TempTableLoader.cs:46, src/Facil.Runtime.CSharp/TempTableLoader.cs:74, src/Facil.Runtime.CSharp/TempTableLoader.cs:79, …
What to do
- Finish or delete NotImplementedException stubs and replace placeholder literals 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
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) as a CI step. What was searched, so you can tell an absence from a miss: the 1 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:3
- `Directory.Build.props` 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`. — Directory.Build.props:12
What to do
- Add a SAST step to CI running what this repository's stack ships: `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P6 · Release Hygiene
PF3 · Async & latency hygiene
X5 · Nullable reference types
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 77% | Strong | Solid. |
| Architecture | 100% | Exemplary | Solid. |
| Maturity | 62% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 58% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 70% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 1 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.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 77 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 — no DI registrations detected
- AX2 Stateful singletons — no singleton implementations detected
- AX6 Interface segregation — no public interfaces
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — docker build failed (exit 1) — 8 | -------------------- ERROR: failed to solve: process "/bin/sh -c apt-get update && apt-get install -y --no-install-recommends curl ca-certificates gnupg && curl -fsSL https://packages.microsoft.com/keys/microsoft.asc | gpg --dearmor -o /usr/share/keyrings/microsoft.gpg" did not complete successfully: exit code: 2; 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 — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C2 Access Controls — No access-control surface detected in the analyzed source — no web/app surface to authorize (no HTTP API or web-UI project) and no authorization code at all (no [Authorize]/policies, no imperative guard methods). Access control is therefore N/A here — this is a library/CLI, which is authorized by its CALLER, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- D10 Test Quality — ~16152 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.
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution, but this repository's production source is mostly .fs, which the C#/VB workspace does not load — the projects that loaded are an immaterial minority, so solution shape was not assessed for this repository. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
- D21 Naming Consistency — D21 withholds its case and prefix conventions rows: 9 candidate(s) found and not reported.
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — single shared-core project — no cross-context coupling to assess
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .fs source were not judged.
- D25 ADR Conformance — no ADRs to check
- D26 Project Cohesion — D26 could not read how the parts of this repository's one project reference each other, so its cohesion was not measured. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- 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.
- D4 Code Duplication — Code Duplication not included (time budget)
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- D8 Code Coverage — Coverage not measured — no coverage collector is wired up
- DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 42 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 — IC1 reached only 2% of this repository's production lines — fsharp (43,440 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- M4 Documentation accuracy — Not applicable: the 1 current-state document(s) make no claim of a kind M4 checks. 5 claim(s) of kinds M4 does not check were not checked (path 2, environment variable 3); M4 checks only links and versions and artefact counts.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P2 Observability — This repo is a library, not a deployed service — it has no process to operate, so production observability (structured logging, tracing/metrics, health checks) is N/A. A library may log via an injected ILogger, but the absence of operational telemetry is not a defect here. If it grows a host (web API, worker), the dimension reactivates.
- P7 Outbound HTTP resilience — not applicable — this isn't a service/API/worker
- P8 Schema migrations — no EF Core usage detected
- P9 Domain vs controller coverage — 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 — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- S1 Web-Security Posture — No web surface detected in the analyzed source — no HTTP API or web-UI project (no controllers/minimal-API endpoints, no Razor/Blazor views) and no web middleware (HTTPS redirection, HSTS, security headers, cookies). Transport security, security headers, secure cookies, CSRF/input-validation and middleware-order controls are therefore N/A here — this is a library/CLI/worker, not a web app. Crypto hygiene was still checked and found nothing to flag. If this codebase becomes web-facing, the dimension reactivates automatically.
- X1 Async correctness — X1 reached only 2% of this repository's production lines — fsharp (43,440 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — X12 reached only 2% of this repository's production lines — fsharp (43,440 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X16 Unfloored truncation loop — X16 reached only 2% of this repository's production lines — fsharp (43,440 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — X18 reached only 2% of this repository's production lines — fsharp (43,440 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — X2 reached only 2% of this repository's production lines — fsharp (43,440 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X21 Side-effecting pattern guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X27 Collection changed while being enumerated — X27 reached only 2% of this repository's production lines — fsharp (43,440 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X3 Exception handling — X3 reached only 2% of this repository's production lines — fsharp (43,440 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X4 Structured logging — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 13 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- EmptyCatchBlock src/Facil.Runtime.CSharp/GeneratedCodeUtils.cs:65
- EmptyCatchBlock src/Facil.Runtime.CSharp/GeneratedCodeUtils.cs:82
- REDACTED
- REDACTED
- REDACTED
Serious — 49 finding(s)
- Unfinished stub — throws NotImplementedException src/Facil.Runtime.CSharp/TempTableLoader.cs:46
- Unfinished stub — throws NotImplementedException src/Facil.Runtime.CSharp/TempTableLoader.cs:74
- Unfinished stub — throws NotImplementedException src/Facil.Runtime.CSharp/TempTableLoader.cs:79
- Unfinished stub — throws NotImplementedException src/Facil.Runtime.CSharp/TempTableLoader.cs:84
- Unfinished stub — throws NotImplementedException src/Facil.Runtime.CSharp/TempTableLoader.cs:89
- Unfinished stub — throws NotImplementedException src/Facil.Runtime.CSharp/TempTableLoader.cs:94
- Unfinished stub — throws NotImplementedException src/Facil.Runtime.CSharp/TempTableLoader.cs:99
- Unfinished stub — throws NotImplementedException src/Facil.Runtime.CSharp/TempTableLoader.cs:104
- Unfinished stub — throws NotImplementedException src/Facil.Runtime.CSharp/TempTableLoader.cs:109
- Unfinished stub — throws NotImplementedException src/Facil.Runtime.CSharp/TempTableLoader.cs:114
- Unfinished stub — throws NotImplementedException src/Facil.Runtime.CSharp/TempTableLoader.cs:119
- Unfinished stub — throws NotImplementedException src/Facil.Runtime.CSharp/TempTableLoader.cs:124
- Unfinished stub — throws NotImplementedException src/Facil.Runtime.CSharp/TempTableLoader.cs:129
- Unfinished stub — throws NotImplementedException src/Facil.Runtime.CSharp/TempTableLoader.cs:134
- Unfinished stub — throws NotImplementedException src/Facil.Runtime.CSharp/TempTableLoader.cs:139
- Unfinished stub — throws NotImplementedException src/Facil.Runtime.CSharp/TempTableLoader.cs:144
- Unfinished stub — throws NotImplementedException src/Facil.Runtime.CSharp/TempTableLoader.cs:149
- Unfinished stub — throws NotImplementedException src/Facil.Runtime.CSharp/TempTableLoader.cs:170
- Unfinished stub — throws NotImplementedException src/Facil.Runtime.CSharp/TempTableLoader.cs:175
- FileTooLong: Facil.Generator/Db.fs src/Facil.Generator/Db.fs
- FileTooLong: Facil.Generator/Render.fs src/Facil.Generator/Render.fs
- FileTooLong: Facil.Generator/Config.fs src/Facil.Generator/Config.fs
- BareSuppressMessage src/Facil.Runtime.CSharp/GeneratedCodeUtils.cs:18
- BareSuppressMessage src/Facil.Runtime.CSharp/GeneratedCodeUtils.cs:19
- Db.getEverything (cyclomatic 201) src/Facil.Generator/Db.fs:1339
- Render.renderProcOrScript (cyclomatic 137) src/Facil.Generator/Render.fs:251
- Program.main (cyclomatic 34) src/Facil.Generator/Program.fs:37
- Db.getColumnsFromQuery (cyclomatic 23) src/Facil.Generator/Db.fs:586
- Db.getTableDtosIncludingThoseNeededForTableScriptsWithSkippedColumns (cyclomatic 19) src/Facil.Generator/Db.fs:1098
- Db.getScriptParameters (cyclomatic 18) src/Facil.Generator/Db.fs:281
- Db.getColumnsFromSpDescribeFirstResultSet (cyclomatic 18) src/Facil.Generator/Db.fs:455
- Db.getStoredProceduresWithoutResultSetOrTempTables (cyclomatic 16) src/Facil.Generator/Db.fs:871
- Deprecated: Hedgehog.Experimental src/DbTests/DbTests.fsproj:33
- Prerelease dependency: Glob
- Db.getEverything (cognitive 326) src/Facil.Generator/Db.fs:1339
- Render.renderProcOrScript (cognitive 261) src/Facil.Generator/Render.fs:251
- Program.main (cognitive 65) src/Facil.Generator/Program.fs:37
- Db.getColumnsFromQuery (cognitive 37) src/Facil.Generator/Db.fs:586
- ScriptIncludes.readSource (cognitive 36) src/Facil.Generator/ScriptIncludes.fs:15
- Db.getTableDtosIncludingThoseNeededForTableScriptsWithSkippedColumns (cognitive 33) src/Facil.Generator/Db.fs:1098
- Db.getScriptParameters (cognitive 24) src/Facil.Generator/Db.fs:281
- Db.getColumnsFromSpDescribeFirstResultSet (cognitive 22) src/Facil.Generator/Db.fs:455
- Render.renderTableType (cognitive 16) src/Facil.Generator/Render.fs:137
- REDACTED
- ClassTooLong: GeneratedCodeUtils src/Facil.Runtime.CSharp/GeneratedCodeUtils.cs
- REDACTED
- REDACTED
- REDACTED
- NuGet dependencies are not locked
Minor — 14 finding(s)
- Outdated: Microsoft.Extensions.Configuration.Binder src/DbTests/DbTests.fsproj:36
- Outdated: Microsoft.Extensions.Configuration.EnvironmentVariables src/DbTests/DbTests.fsproj:34
- Outdated: Microsoft.Extensions.Configuration.UserSecrets src/DbTests/DbTests.fsproj:35
- No ADRs found src/Facil.Generator/Facil.Generator.fsproj:4
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No SAST REDACTED:3
- No dependency-update automation Directory.Build.props:12
- No release approval gate
Minor — 12 finding(s)
- Outdated: DotNet.ReproducibleBuilds
- Outdated: FSharp.Core
- Outdated: FSharp.SystemTextJson
- Outdated: Microsoft.Data.SqlClient
- Outdated: Microsoft.SqlServer.TransactSql.ScriptDom
- Outdated: Expecto
- Outdated: FSharp.Control.AsyncSeq
- Outdated: Hedgehog
- Outdated: Hedgehog.Experimental
- Outdated: Microsoft.NET.Test.Sdk
- Outdated: Unquote
- Outdated: YoloDev.Expecto.TestSdk
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-a8785eaf339147f6b588d2baf07eafba/history.json --exit-code 0 --source . | 7 | 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-a8785eaf339147f6b588d2baf07eafba/tree.json --exit-code 0 --source . | 2 | 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 . | 7 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list Facil.slnx package --vulnerable --include-transitive --format json | 0 | artifacts/raw/dotnet-vulnerable.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 5 | 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-77706f6a21b3439b9669242e81e8d760 | 0 | artifacts/raw/osv-scanner.json |