Executive summary
SchlenkR/Trulla falls short of our standard for production because we found no working pipeline that builds or tests changes to the code and no automated security scanning of the code, its secrets or its dependencies. It scores 56 out of 100 and is rated Adequate, and one of its two critical findings is a security problem in the packages it uses.
Production Readiness, at 41, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 9 points. Adding an automated build and test pipeline would lift Production Readiness itself, worth about 7 points. Raising Production Readiness to 70 would lift the score to about 65.
One known security hole in a package the code depends on can be used by attackers. One part of the code is no longer understood by anyone working on it. Having someone learn the forgotten files and updating the vulnerable packages would close both risks.
The product code is 15,401 lines, about €13,000 to rebuild.
If Production Readiness rose from 41 to 70, the lowest score rated Strong, the score would rise from 56 to about 65.
New since the last survey: 5 findings
- Platform End-of-Life · End-of-life runtime: .NET net6.0 REDACTED
- Platform End-of-Life · End-of-life runtime: .NET net6.0 src/NodeCli/Cli/NodeCli.fsproj
- Platform End-of-Life · End-of-life runtime: .NET net6.0 src/SourceGenerator/Tests/Tests.fsproj
- Platform End-of-Life · End-of-life runtime: .NET net6.0 src/TypeProvider/ProviderTests.Nuget/ProviderTests.Nuget.fsproj
- Platform End-of-Life · End-of-life runtime: .NET net6.0 src/TypeProvider/Tests/Tests.fsproj
Fixed since the last survey: 1 finding
- Platform End-of-Life · End-of-life runtime: .NET net6.0 src/TypeProvider/Tests/Tests.fsproj
Rebuild cost: about €13,000 · Estimate
| Cost to rebuild | €4,400 to €22,000, for 74 to 234 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Low, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 56. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 15,401 lines of product code |
| Comment lines | The estimate prices 15,400 lines. Comment lines count towards the size of 15,401 lines but aren't priced as work. |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — bounded-context dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 ProviderImplementation.ProvidedTypes | 2 ProviderImplementation.ProvidedTypes.AssemblyReader | 3 ProviderImplementation.ProvidedTypes.AssemblyReader.Reader | 4 ProviderImplementation.ProvidedTypes.UncheckedQuotations | 5 TheBlunt | 6 Trulla | 7 Trulla.Core.KnownTypes | 8 Trulla.Core.Parsing.Consts | 9 Trulla.Core.Parsing.Internal | 10 Trulla.Core.Parsing.Keywords | 11 Trulla.Core.ReflectionRenderer | 12 Trulla.Core.Text | 13 Trulla.Core.Utils.List | 14 Trulla.Core.Utils.Map | 15 Trulla.Core.Utils.String | 16 Trulla.DesignTime.Consts | 17 Trulla.DesignTime.Internal.ProviderCompiler.Consts | 18 Trulla.DesignTime.Internal.ProviderCompiler.Expr | 19 Trulla.SourceGenerator | 20 Trulla.Tests.TestHelper | 21 Trulla.Tests.TestHelper.Templates | 22 TheBlunt.CursorModule | 23 TheBlunt.DocPosModule | 24 TheBlunt.PError | 25 TheBlunt.POk | 26 TheBlunt.PVal | 27 TheBlunt.RangeModule | 28 Trulla.Core | 29 Trulla.DesignTime | 30 Trulla.Core.AstModule | 31 Trulla.Core.Inference | 32 Trulla.Core.Parsing | 33 Trulla.Core.Parsing.MemberToken | 34 Trulla.Core.Solver | 35 Trulla.DesignTime.Internal.ProviderCompiler | 36 Trulla.NodeCli.Renderer | 37 Trulla.NodeCli.Renderer.MemberExp | 38 Trulla.SourceGenerator.Renderer | 39 Trulla.SourceGenerator.Renderer.MemberExp |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 ProviderImplementation.ProvidedTypes | |||||||||||||||||||||||||||||||||||||||
| 2 ProviderImplementation.ProvidedTypes.AssemblyReader | |||||||||||||||||||||||||||||||||||||||
| 3 ProviderImplementation.ProvidedTypes.AssemblyReader.Reader | |||||||||||||||||||||||||||||||||||||||
| 4 ProviderImplementation.ProvidedTypes.UncheckedQuotations | |||||||||||||||||||||||||||||||||||||||
| 5 TheBlunt | |||||||||||||||||||||||||||||||||||||||
| 6 Trulla | |||||||||||||||||||||||||||||||||||||||
| 7 Trulla.Core.KnownTypes | |||||||||||||||||||||||||||||||||||||||
| 8 Trulla.Core.Parsing.Consts | |||||||||||||||||||||||||||||||||||||||
| 9 Trulla.Core.Parsing.Internal | |||||||||||||||||||||||||||||||||||||||
| 10 Trulla.Core.Parsing.Keywords | |||||||||||||||||||||||||||||||||||||||
| 11 Trulla.Core.ReflectionRenderer | |||||||||||||||||||||||||||||||||||||||
| 12 Trulla.Core.Text | |||||||||||||||||||||||||||||||||||||||
| 13 Trulla.Core.Utils.List | |||||||||||||||||||||||||||||||||||||||
| 14 Trulla.Core.Utils.Map | |||||||||||||||||||||||||||||||||||||||
| 15 Trulla.Core.Utils.String | |||||||||||||||||||||||||||||||||||||||
| 16 Trulla.DesignTime.Consts | |||||||||||||||||||||||||||||||||||||||
| 17 Trulla.DesignTime.Internal.ProviderCompiler.Consts | |||||||||||||||||||||||||||||||||||||||
| 18 Trulla.DesignTime.Internal.ProviderCompiler.Expr | |||||||||||||||||||||||||||||||||||||||
| 19 Trulla.SourceGenerator | |||||||||||||||||||||||||||||||||||||||
| 20 Trulla.Tests.TestHelper | |||||||||||||||||||||||||||||||||||||||
| 21 Trulla.Tests.TestHelper.Templates | |||||||||||||||||||||||||||||||||||||||
| 22 TheBlunt.CursorModule | 2 | ||||||||||||||||||||||||||||||||||||||
| 23 TheBlunt.DocPosModule | 2 | ||||||||||||||||||||||||||||||||||||||
| 24 TheBlunt.PError | 1 | ||||||||||||||||||||||||||||||||||||||
| 25 TheBlunt.POk | 2 | ||||||||||||||||||||||||||||||||||||||
| 26 TheBlunt.PVal | 2 | ||||||||||||||||||||||||||||||||||||||
| 27 TheBlunt.RangeModule | 1 | ||||||||||||||||||||||||||||||||||||||
| 28 Trulla.Core | 4 | ||||||||||||||||||||||||||||||||||||||
| 29 Trulla.DesignTime | 1 | ||||||||||||||||||||||||||||||||||||||
| 30 Trulla.Core.AstModule | 2 | 7 | |||||||||||||||||||||||||||||||||||||
| 31 Trulla.Core.Inference | 7 | ||||||||||||||||||||||||||||||||||||||
| 32 Trulla.Core.Parsing | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 33 Trulla.Core.Parsing.MemberToken | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 34 Trulla.Core.Solver | 2 | 3 | |||||||||||||||||||||||||||||||||||||
| 35 Trulla.DesignTime.Internal.ProviderCompiler | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 36 Trulla.NodeCli.Renderer | 7 | ||||||||||||||||||||||||||||||||||||||
| 37 Trulla.NodeCli.Renderer.MemberExp | 1 | ||||||||||||||||||||||||||||||||||||||
| 38 Trulla.SourceGenerator.Renderer | 6 | ||||||||||||||||||||||||||||||||||||||
| 39 Trulla.SourceGenerator.Renderer.MemberExp | 1 |
22→5 TheBlunt.CursorModule uses TheBlunt✕
- Connections
- 2 pairs of types, where a type in TheBlunt.CursorModule uses a type in TheBlunt.
- The types involved
TheBlunt.CursorModule.CursorModule→TheBlunt.CursorTheBlunt.CursorModule.CursorModule→TheBlunt.ParserResult`1
- Direction
- TheBlunt.CursorModule uses TheBlunt, so a change to TheBlunt can break TheBlunt.CursorModule, while a change to TheBlunt.CursorModule can't break TheBlunt.
- Position
- Below the diagonal: TheBlunt.CursorModule uses a module listed above it, which is the healthy direction.
23→5 TheBlunt.DocPosModule uses TheBlunt✕
- Connections
- 2 pairs of types, where a type in TheBlunt.DocPosModule uses a type in TheBlunt.
- The types involved
TheBlunt.DocPosModule.DocPosModule→TheBlunt.CursorTheBlunt.DocPosModule.DocPosModule→TheBlunt.DocPos
- Direction
- TheBlunt.DocPosModule uses TheBlunt, so a change to TheBlunt can break TheBlunt.DocPosModule, while a change to TheBlunt.DocPosModule can't break TheBlunt.
- Position
- Below the diagonal: TheBlunt.DocPosModule uses a module listed above it, which is the healthy direction.
24→5 TheBlunt.PError uses TheBlunt✕
- Connections
- 1 pair of types, where a type in TheBlunt.PError uses a type in TheBlunt.
- The types involved
TheBlunt.PError.PError→TheBlunt.ParserResult`1
- Direction
- TheBlunt.PError uses TheBlunt, so a change to TheBlunt can break TheBlunt.PError, while a change to TheBlunt.PError can't break TheBlunt.
- Position
- Below the diagonal: TheBlunt.PError uses a module listed above it, which is the healthy direction.
25→5 TheBlunt.POk uses TheBlunt✕
- Connections
- 2 pairs of types, where a type in TheBlunt.POk uses a type in TheBlunt.
- The types involved
TheBlunt.POk.POk→TheBlunt.ParserResult`1TheBlunt.POk.POk→TheBlunt.Range
- Direction
- TheBlunt.POk uses TheBlunt, so a change to TheBlunt can break TheBlunt.POk, while a change to TheBlunt.POk can't break TheBlunt.
- Position
- Below the diagonal: TheBlunt.POk uses a module listed above it, which is the healthy direction.
26→5 TheBlunt.PVal uses TheBlunt✕
- Connections
- 2 pairs of types, where a type in TheBlunt.PVal uses a type in TheBlunt.
- The types involved
TheBlunt.PVal.PVal→TheBlunt.PVal`1TheBlunt.PVal.PVal→TheBlunt.Range
- Direction
- TheBlunt.PVal uses TheBlunt, so a change to TheBlunt can break TheBlunt.PVal, while a change to TheBlunt.PVal can't break TheBlunt.
- Position
- Below the diagonal: TheBlunt.PVal uses a module listed above it, which is the healthy direction.
27→5 TheBlunt.RangeModule uses TheBlunt✕
- Connections
- 1 pair of types, where a type in TheBlunt.RangeModule uses a type in TheBlunt.
- The types involved
TheBlunt.RangeModule.RangeModule→TheBlunt.Range
- Direction
- TheBlunt.RangeModule uses TheBlunt, so a change to TheBlunt can break TheBlunt.RangeModule, while a change to TheBlunt.RangeModule can't break TheBlunt.
- Position
- Below the diagonal: TheBlunt.RangeModule uses a module listed above it, which is the healthy direction.
28→5 Trulla.Core uses TheBlunt✕
- Connections
- 4 pairs of types, where a type in Trulla.Core uses a type in TheBlunt.
- The types involved
Trulla.Core.TExp→TheBlunt.PVal`1Trulla.Core.TVal`1→TheBlunt.RangeTrulla.Core.Token→TheBlunt.PVal`1Trulla.Core.TrullaError→TheBlunt.Range
- Direction
- Trulla.Core uses TheBlunt, so a change to TheBlunt can break Trulla.Core, while a change to Trulla.Core can't break TheBlunt.
- Position
- Below the diagonal: Trulla.Core uses a module listed above it, which is the healthy direction.
29→1 Trulla.DesignTime uses ProviderImplementation.ProvidedTypes✕
- Connections
- 1 pair of types, where a type in Trulla.DesignTime uses a type in ProviderImplementation.ProvidedTypes.
- The types involved
Trulla.DesignTime.TemplateProviderImplementation→ProviderImplementation.ProvidedTypes.TypeProviderForNamespaces
- Direction
- Trulla.DesignTime uses ProviderImplementation.ProvidedTypes, so a change to ProviderImplementation.ProvidedTypes can break Trulla.DesignTime, while a change to Trulla.DesignTime can't break ProviderImplementation.ProvidedTypes.
- Position
- Below the diagonal: Trulla.DesignTime uses a module listed above it, which is the healthy direction.
30→5 Trulla.Core.AstModule uses TheBlunt✕
- Connections
- 2 pairs of types, where a type in Trulla.Core.AstModule uses a type in TheBlunt.
- The types involved
Trulla.Core.AstModule.AstModule→TheBlunt.PVal`1Trulla.Core.AstModule.AstModule→TheBlunt.Range
- Direction
- Trulla.Core.AstModule uses TheBlunt, so a change to TheBlunt can break Trulla.Core.AstModule, while a change to Trulla.Core.AstModule can't break TheBlunt.
- Position
- Below the diagonal: Trulla.Core.AstModule uses a module listed above it, which is the healthy direction.
30→28 Trulla.Core.AstModule uses Trulla.Core✕
- Connections
- 7 pairs of types, where a type in Trulla.Core.AstModule uses a type in Trulla.Core.
- The types involved
Trulla.Core.AstModule.AstModule→Trulla.Core.AstTrulla.Core.AstModule.AstModule→Trulla.Core.TVal`1Trulla.Core.AstModule.AstModule→Trulla.Core.TVarTrulla.Core.AstModule.AstModule→Trulla.Core.TokenTrulla.Core.AstModule.AstModule→Trulla.Core.TrullaErrorTrulla.Core.AstModule.Scope→Trulla.Core.MemberExpTrulla.Core.AstModule.Scope→Trulla.Core.TVal`1
- Direction
- Trulla.Core.AstModule uses Trulla.Core, so a change to Trulla.Core can break Trulla.Core.AstModule, while a change to Trulla.Core.AstModule can't break Trulla.Core.
- Position
- Below the diagonal: Trulla.Core.AstModule uses a module listed above it, which is the healthy direction.
31→28 Trulla.Core.Inference uses Trulla.Core✕
- Connections
- 7 pairs of types, where a type in Trulla.Core.Inference uses a type in Trulla.Core.
- The types involved
Trulla.Core.Inference.Inference→Trulla.Core.MemberExpTrulla.Core.Inference.Inference→Trulla.Core.ProblemTrulla.Core.Inference.Inference→Trulla.Core.TExpTrulla.Core.Inference.Inference→Trulla.Core.TVarTrulla.Core.Inference.Inference→Trulla.Core.TrullaErrorTrulla.Core.Inference.Unification→Trulla.Core.ProblemTrulla.Core.Inference.Unification→Trulla.Core.TrullaError
- Direction
- Trulla.Core.Inference uses Trulla.Core, so a change to Trulla.Core can break Trulla.Core.Inference, while a change to Trulla.Core.Inference can't break Trulla.Core.
- Position
- Below the diagonal: Trulla.Core.Inference uses a module listed above it, which is the healthy direction.
32→5 Trulla.Core.Parsing uses TheBlunt✕
- Connections
- 2 pairs of types, where a type in Trulla.Core.Parsing uses a type in TheBlunt.
- The types involved
Trulla.Core.Parsing.Parsing→TheBlunt.PVal`1Trulla.Core.Parsing.Parsing→TheBlunt.ParserResult`1
- Direction
- Trulla.Core.Parsing uses TheBlunt, so a change to TheBlunt can break Trulla.Core.Parsing, while a change to Trulla.Core.Parsing can't break TheBlunt.
- Position
- Below the diagonal: Trulla.Core.Parsing uses a module listed above it, which is the healthy direction.
32→28 Trulla.Core.Parsing uses Trulla.Core✕
- Connections
- 1 pair of types, where a type in Trulla.Core.Parsing uses a type in Trulla.Core.
- The types involved
Trulla.Core.Parsing.Parsing→Trulla.Core.Token
- Direction
- Trulla.Core.Parsing uses Trulla.Core, so a change to Trulla.Core can break Trulla.Core.Parsing, while a change to Trulla.Core.Parsing can't break Trulla.Core.
- Position
- Below the diagonal: Trulla.Core.Parsing uses a module listed above it, which is the healthy direction.
33→5 Trulla.Core.Parsing.MemberToken uses TheBlunt✕
- Connections
- 1 pair of types, where a type in Trulla.Core.Parsing.MemberToken uses a type in TheBlunt.
- The types involved
Trulla.Core.Parsing.MemberToken.MemberToken→TheBlunt.PVal`1
- Direction
- Trulla.Core.Parsing.MemberToken uses TheBlunt, so a change to TheBlunt can break Trulla.Core.Parsing.MemberToken, while a change to Trulla.Core.Parsing.MemberToken can't break TheBlunt.
- Position
- Below the diagonal: Trulla.Core.Parsing.MemberToken uses a module listed above it, which is the healthy direction.
33→28 Trulla.Core.Parsing.MemberToken uses Trulla.Core✕
- Connections
- 1 pair of types, where a type in Trulla.Core.Parsing.MemberToken uses a type in Trulla.Core.
- The types involved
Trulla.Core.Parsing.MemberToken.MemberToken→Trulla.Core.MemberToken
- Direction
- Trulla.Core.Parsing.MemberToken uses Trulla.Core, so a change to Trulla.Core can break Trulla.Core.Parsing.MemberToken, while a change to Trulla.Core.Parsing.MemberToken can't break Trulla.Core.
- Position
- Below the diagonal: Trulla.Core.Parsing.MemberToken uses a module listed above it, which is the healthy direction.
34→5 Trulla.Core.Solver uses TheBlunt✕
- Connections
- 2 pairs of types, where a type in Trulla.Core.Solver uses a type in TheBlunt.
- The types involved
Trulla.Core.Solver.Solver→TheBlunt.PVal`1Trulla.Core.Solver.Solver→TheBlunt.ParserResult`1
- Direction
- Trulla.Core.Solver uses TheBlunt, so a change to TheBlunt can break Trulla.Core.Solver, while a change to Trulla.Core.Solver can't break TheBlunt.
- Position
- Below the diagonal: Trulla.Core.Solver uses a module listed above it, which is the healthy direction.
34→28 Trulla.Core.Solver uses Trulla.Core✕
- Connections
- 3 pairs of types, where a type in Trulla.Core.Solver uses a type in Trulla.Core.
- The types involved
Trulla.Core.Solver.Solver→Trulla.Core.SolutionTrulla.Core.Solver.Solver→Trulla.Core.TokenTrulla.Core.Solver.Solver→Trulla.Core.TrullaError
- Direction
- Trulla.Core.Solver uses Trulla.Core, so a change to Trulla.Core can break Trulla.Core.Solver, while a change to Trulla.Core.Solver can't break Trulla.Core.
- Position
- Below the diagonal: Trulla.Core.Solver uses a module listed above it, which is the healthy direction.
35→1 Trulla.DesignTime.Internal.ProviderCompiler uses ProviderImplementation.ProvidedTypes✕
- Connections
- 2 pairs of types, where a type in Trulla.DesignTime.Internal.ProviderCompiler uses a type in ProviderImplementation.ProvidedTypes.
- The types involved
Trulla.DesignTime.Internal.ProviderCompiler.ProviderCompiler→ProviderImplementation.ProvidedTypes.ProvidedMethodTrulla.DesignTime.Internal.ProviderCompiler.ProviderCompiler→ProviderImplementation.ProvidedTypes.ProvidedTypeDefinition
- Direction
- Trulla.DesignTime.Internal.ProviderCompiler uses ProviderImplementation.ProvidedTypes, so a change to ProviderImplementation.ProvidedTypes can break Trulla.DesignTime.Internal.ProviderCompiler, while a change to Trulla.DesignTime.Internal.ProviderCompiler can't break ProviderImplementation.ProvidedTypes.
- Position
- Below the diagonal: Trulla.DesignTime.Internal.ProviderCompiler uses a module listed above it, which is the healthy direction.
35→28 Trulla.DesignTime.Internal.ProviderCompiler uses Trulla.Core✕
- Connections
- 1 pair of types, where a type in Trulla.DesignTime.Internal.ProviderCompiler uses a type in Trulla.Core.
- The types involved
Trulla.DesignTime.Internal.ProviderCompiler.ProviderCompiler→Trulla.Core.RecordDef
- Direction
- Trulla.DesignTime.Internal.ProviderCompiler uses Trulla.Core, so a change to Trulla.Core can break Trulla.DesignTime.Internal.ProviderCompiler, while a change to Trulla.DesignTime.Internal.ProviderCompiler can't break Trulla.Core.
- Position
- Below the diagonal: Trulla.DesignTime.Internal.ProviderCompiler uses a module listed above it, which is the healthy direction.
36→28 Trulla.NodeCli.Renderer uses Trulla.Core✕
- Connections
- 7 pairs of types, where a type in Trulla.NodeCli.Renderer uses a type in Trulla.Core.
- The types involved
Trulla.NodeCli.Renderer.Renderer→Trulla.Core.MemberExpTrulla.NodeCli.Renderer.Renderer→Trulla.Core.RecordDefTrulla.NodeCli.Renderer.Renderer→Trulla.Core.SolutionTrulla.NodeCli.Renderer.Renderer→Trulla.Core.TVal`1Trulla.NodeCli.Renderer.Renderer→Trulla.Core.TVarTrulla.NodeCli.Renderer.Renderer→Trulla.Core.TrullaErrorTrulla.NodeCli.Renderer.Renderer→Trulla.Core.Typ
- Direction
- Trulla.NodeCli.Renderer uses Trulla.Core, so a change to Trulla.Core can break Trulla.NodeCli.Renderer, while a change to Trulla.NodeCli.Renderer can't break Trulla.Core.
- Position
- Below the diagonal: Trulla.NodeCli.Renderer uses a module listed above it, which is the healthy direction.
37→28 Trulla.NodeCli.Renderer.MemberExp uses Trulla.Core✕
- Connections
- 1 pair of types, where a type in Trulla.NodeCli.Renderer.MemberExp uses a type in Trulla.Core.
- The types involved
Trulla.NodeCli.Renderer.MemberExp.MemberExp→Trulla.Core.MemberExp
- Direction
- Trulla.NodeCli.Renderer.MemberExp uses Trulla.Core, so a change to Trulla.Core can break Trulla.NodeCli.Renderer.MemberExp, while a change to Trulla.NodeCli.Renderer.MemberExp can't break Trulla.Core.
- Position
- Below the diagonal: Trulla.NodeCli.Renderer.MemberExp uses a module listed above it, which is the healthy direction.
38→28 Trulla.SourceGenerator.Renderer uses Trulla.Core✕
- Connections
- 6 pairs of types, where a type in Trulla.SourceGenerator.Renderer uses a type in Trulla.Core.
- The types involved
Trulla.SourceGenerator.Renderer.Renderer→Trulla.Core.MemberExpTrulla.SourceGenerator.Renderer.Renderer→Trulla.Core.RecordDefTrulla.SourceGenerator.Renderer.Renderer→Trulla.Core.SolutionTrulla.SourceGenerator.Renderer.Renderer→Trulla.Core.TVal`1Trulla.SourceGenerator.Renderer.Renderer→Trulla.Core.TVarTrulla.SourceGenerator.Renderer.Renderer→Trulla.Core.Typ
- Direction
- Trulla.SourceGenerator.Renderer uses Trulla.Core, so a change to Trulla.Core can break Trulla.SourceGenerator.Renderer, while a change to Trulla.SourceGenerator.Renderer can't break Trulla.Core.
- Position
- Below the diagonal: Trulla.SourceGenerator.Renderer uses a module listed above it, which is the healthy direction.
39→28 Trulla.SourceGenerator.Renderer.MemberExp uses Trulla.Core✕
- Connections
- 1 pair of types, where a type in Trulla.SourceGenerator.Renderer.MemberExp uses a type in Trulla.Core.
- The types involved
Trulla.SourceGenerator.Renderer.MemberExp.MemberExp→Trulla.Core.MemberExp
- Direction
- Trulla.SourceGenerator.Renderer.MemberExp uses Trulla.Core, so a change to Trulla.Core can break Trulla.SourceGenerator.Renderer.MemberExp, while a change to Trulla.SourceGenerator.Renderer.MemberExp can't break Trulla.Core.
- Position
- Below the diagonal: Trulla.SourceGenerator.Renderer.MemberExp uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 1 | High / Critical |
| A02:2025 — Security Misconfiguration | 1 | Medium |
Roadmap
Top priorities: Resolve the 1 No ADRs found finding(s) in ADR Quality — start with GeneratorTests.Nuget.csproj; Resolve the 10 Orphaned file finding(s) in Knowledge Freshness — start with Renderer.fs (2), TheBlunt.fs, Inference.fs; Add a CI workflow that builds and runs the test suite on every push/PR.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with GeneratorTests.Nuget.csproj. | +9.4 pts | Low | ADR Quality |
| Resolve the 10 Orphaned file finding(s) in Knowledge Freshness — start with Renderer.fs (2), TheBlunt.fs, Inference.fs. | +8.9 pts | Medium | Knowledge Freshness |
| Add a CI workflow that builds and runs the test suite on every push/PR. | +6.6 pts | Medium | CI/CD gates |
| Resolve the 1 Orphaned knowledge finding(s) in Knowledge Freshness — start with ProvidedTypes.fs. | +2.5 pts | Low | Knowledge Freshness |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +4.6 pts | Medium | Architecture documentation |
| Resolve the 3 Outdated finding(s) in Dependency Hygiene — start with REDACTED (2), Trulla.SourceGenerator.csproj. | +2.1 pts | Low | Dependency Hygiene |
| 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.7 pts | Medium | Deployment & Rollback |
| Resolve the 6 End-of-life runtime finding(s) in Platform End-of-Life — start with REDACTED (3), NodeCli.fsproj, ProviderTests.Nuget.fsproj. | +1.4 pts | Low | Platform End-of-Life |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 4.4 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| src/TypeProvider/Trulla.DesignTime/TpSdk/ProvidedTypes.fs | 5.7 | Mixed | Cyclomatic Complexity: UncheckedQuotations.|ShapeCombinationUnchecked|ShapeVarUnchecked|ShapeLambdaUnchecked| (cyclomatic 42) |
| src/SourceGenerator/GeneratorTests.Nuget/GeneratorTests.Nuget.csproj | 7.4 | Mixed | Platform End-of-Life: End-of-life runtime: .NET net7.0 |
| src/Common/CoreFiles/Inference.fs | 7.8 | Mixed | Cyclomatic Complexity: Inference.solveProblems (cyclomatic 27) |
| src/Common/CoreFiles/Ast.fs | 7.8 | Mixed | Cyclomatic Complexity: AstModule.buildTree (cyclomatic 25) |
| src/Common/CoreFiles/ReflectionRenderer.fs | 7.8 | Mixed | Cyclomatic Complexity: ReflectionRenderer.renderTemplate (cyclomatic 16) |
| src/NodeCli/Cli/NodeCli.fsproj | 7.9 | Mixed | Platform End-of-Life: End-of-life runtime: .NET net6.0 |
| src/SourceGenerator/Tests/Tests.fsproj | 7.9 | Mixed | Platform End-of-Life: End-of-life runtime: .NET net6.0 |
| src/TypeProvider/ProviderTests.Nuget/ProviderTests.Nuget.fsproj | 7.9 | Mixed | Platform End-of-Life: End-of-life runtime: .NET net6.0 |
| src/TypeProvider/Tests/Tests.fsproj | 7.9 | Mixed | Platform End-of-Life: End-of-life runtime: .NET net6.0 |
| src/SourceGenerator/Trulla.SourceGenerator/TrullaSourceGenerator.cs | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/Common/CoreFiles/Solver.fs | 8.5 | Near-clean | Cognitive Complexity: Solver.solveParseResult (cognitive 28) |
| src/Common/CoreFiles/TheBlunt.fs | 8.5 | Near-clean | God Classes: TooManyFunctions: TheBlunt |
| REDACTED | 9.3 | Near-clean | IaC & Container Security: Low IaC: REDACTED |
| src/SourceGenerator/Trulla.SourceGenerator/Trulla.SourceGenerator.csproj | 9.5 | Near-clean | Dependency Hygiene: Outdated: FSharp.Core |
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 39 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 39 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, 40 of 53 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 6-minute budget on a solution this large — not included in this run.
- D8 Code Coverage — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Coverage NOT MEASURED: this repository's test suite BUILT and its tests PASSED in this run — so neither the build nor our analyzer environment is in question — but the run produced no coverage data, and it captured no message saying why. The usual cause is that the test projects wire up no coverage collector (`--collect:"XPlat Code Coverage"` needs a `coverlet.collector` PackageReference); on a very large suite the instrumented run can also exceed its per-target budget before writing anything. Add a `coverlet.collector` PackageReference, or commit the Cobertura/OpenCover/lcov report your CI already produces, and real coverage is 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).
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT MEASURED: the test run produced no results for any test tier, so no test ever ran and flakiness could not be exercised. The cause could not be attributed, so it is excluded from the score rather than read as an absence of tests.
- D12 Dependency Hygiene — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares npm dependencies as well as NuGet ones — manifest: src/NodeCli/Cli/package.json — and the counts on this row cover the NuGet side ONLY. This dimension reads dependency currency from `<PackageReference>` elements via `dotnet list package`; it does not read it, so the npm packages declared there were not checked for newer, deprecated or unmaintained releases. Their absence from the counts above is a gap in this analyzer's ecosystem coverage — not a finding that those dependencies are current.
- 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. All 11 significant source file(s) were last meaningfully changed so long ago that no living knowledge remains — nothing since has been substantial enough to re-establish ownership (a broad, mechanical sweep that touches many files shallowly does not count, and neither does no activity at all). There is no concentration to measure, so the bus factor is not scored. This is not a clean bill: nobody currently holds working knowledge of this code (see D34 Knowledge Freshness). Counted over 10 of the 21 production source files in this repository: 10 are under the ~2,400-byte size floor this dimension measures over, and the remaining 1 have no attributable history left to measure.
- 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/SourceGenerator/Trulla.SourceGenerator.Core/Trulla.SourceGenerator.Core.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 1 deducted marker(s) and the 0.0/KLoC density on this row were taken over this repository's .NET projects ALONE: .fs (15,273 lines, 99% 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.
- AXB2 Runtime readiness — 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. `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. (rule: no-root-manifest). The renderer reported: the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
- 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 DevServer (dev). the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
- 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.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
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.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- 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.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
4 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was UncheckedQuotations.|ShapeCombinationUnchecked|ShapeVarUnchecked|ShapeLambdaUnchecked| at 42.
What to do
- Bring the 4 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with UncheckedQuotations.|ShapeCombinationUnchecked|ShapeVarUnchecked|ShapeLambdaUnchecked| (cyclomatic 42), Inference.solveProblems (cyclomatic 27), AstModule.buildTree (cyclomatic 25). — 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 4 together lifts Cyclomatic Complexity from 8.6 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
6 method(s) exceeded the cognitive complexity threshold of 15; the worst was UncheckedQuotations.|ShapeCombinationUnchecked|ShapeVarUnchecked|ShapeLambdaUnchecked| at 59.
What to do
- Bring the 2 bodies over 30 down to 30 or less in Cognitive Complexity — start with UncheckedQuotations.|ShapeCombinationUnchecked|ShapeVarUnchecked|ShapeLambdaUnchecked| (cognitive 59), AstModule.buildTree (cognitive 32). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 8.0 to about 8.8/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
D3 · God Classes
2 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 1 FileTooLong finding(s) in God Classes — start with ProvidedTypes.fs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 TooManyFunctions finding(s) in God Classes — start with TheBlunt.fs. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
2 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D6 · Cohesion (LCOM4)
1 of 3 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with ProvidedTypes.fs. — One of this dimension's main actionable groups (1 warning-level).
D12 · Dependency Hygiene
9 outdated, 0 vulnerable, 0 deprecated packages. NuGet only — this repository also declares npm dependencies, which are not read for currency here.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 182 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 11 direct `PackageReference`(s), and 158 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
1 deducted debt markers + unmeasured dead symbols across 61 LoC in the .NET projects (0.0/KLoC) → score 9.9. Dead code not measured: the solution did not load cleanly, so the reference search was skipped. Measured on the .NET source only: .fs (99% of production source) was not read, and carries at least 0 uncounted task marker(s) in 0 file(s).
What to do
- Resolve the 1 TodoComment finding(s) in Explicit Debt — start with TrullaSourceGenerator.cs. — One of this dimension's main actionable groups (1 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 6 document(s) read across 3 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 GeneratorTests.Nuget.csproj. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
0 of 2 projects flagged as possibly oversized/incoherent.
D27 · Navigability
82 % of calls cross a namespace and 3 % go through an interface, but 31 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
What to do
- Resolve the 1 Scattered collaborators finding(s) in Navigability. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
semgrep found no security issues.
D30 · Dependency Vulnerabilities
1 finding(s): 0 critical, 1 high, 0 medium, 0 low.
What to do
- Resolve the 1 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D31 · IaC & Container Security
1 finding(s): 0 critical, 0 high, 0 medium, 1 low.
D34 · Knowledge Freshness
11 of 11 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/TypeProvider/Trulla.DesignTime/TpSdk/ProvidedTypes.fs. Counted over 11 of the 21 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 10 Orphaned file finding(s) in Knowledge Freshness — start with Renderer.fs (2), TheBlunt.fs, Inference.fs. — One of this dimension's main actionable groups (10 recommendation-level).
- Resolve the 1 Orphaned knowledge finding(s) in Knowledge Freshness — start with ProvidedTypes.fs. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
2 end-of-life runtime(s) and 0 end-of-life framework(s), read from 10 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.
What to do
- Resolve the 6 End-of-life runtime finding(s) in Platform End-of-Life — start with REDACTED (3), NodeCli.fsproj, ProviderTests.Nuget.fsproj. — One of this dimension's main actionable groups (6 warning-level).
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX5 · Architecture & structure
AX8 · Test isolation
GD1 · Unfinished & placeholder code
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
- src/NodeCli/Cli/README.md links to `./src/docs/NodeCli.md`, but `src/NodeCli/Cli/src/docs/NodeCli.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/NodeCli/Cli/README.md:30
- src/NodeCli/Cli/README.md links to `./src/docs/SourceGenerator.md`, but `src/NodeCli/Cli/src/docs/SourceGenerator.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/NodeCli/Cli/README.md:34
What to do
- Reconcile the README with reality: src/NodeCli/Cli/README.md links to `./src/docs/NodeCli.md`, but `src/NodeCli/Cli/src/docs/NodeCli.md` does not exist; src/NodeCli/Cli/README.md links to `./src/docs/SourceGenerator.md`, but `src/NodeCli/Cli/src/docs/SourceGenerator.md` does not exist.
P1 · CI/CD gates
- No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
What to do
- Add a CI workflow that builds and runs the test suite on every push/PR.
P10 · Library API & versioning
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) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
- `REDACTED` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — REDACTED:25
What to do
- Run 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) — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
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
- ~3.0 `!` suppressions per 1k syntax nodes — 1 suppression(s) across the 334 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
What to do
- Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 85% | Strong | Solid. |
| Architecture | 95% | Exemplary | Solid. |
| Maturity | 50% | Weak — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 41% | Weak — gated by P1, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 80% | Adequate — gated by D44 | 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 — the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered. 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 — ~178 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.
- D11 Test Reliability — Test reliability not measured — no test run produced results
- D16 Bus Factor — dormant codebase — no living knowledge left to concentrate
- D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution, but this repository's production source is mostly .fs, .ts, 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: 2 candidate(s) found and not reported.
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — small single-context codebase (15,399 production LoC in the .NET projects) — bounded contexts are not needed at this size No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .fs source were not judged.
- D25 ADR Conformance — no ADRs to check
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- 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 — the suite ran but produced no coverage data
- DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 56 value object(s); 5 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- IC1 Incompleteness & stubs — IC1 reached only 0% of this repository's production lines — fsharp (15,273 lines), typescript (65 lines), javascript (2 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- P12 CI test-gate honesty — no CI workflow found
- P2 Observability — This repo is a library, not a deployed service — it has no process to operate, so production observability (structured logging, tracing/metrics, health checks) is N/A. A library may log via an injected ILogger, but the absence of operational telemetry is not a defect here. If it grows a host (web API, worker), the dimension reactivates.
- P7 Outbound HTTP resilience — not applicable — this isn't a service/API/worker
- P8 Schema migrations — no EF Core usage detected
- P9 Domain vs controller coverage — 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 — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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 — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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 — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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 — no async method does work a token could cancel
- 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 — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — 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 — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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 — 2 finding(s)
- REDACTED
- Orphaned knowledge src/TypeProvider/Trulla.DesignTime/TpSdk/ProvidedTypes.fs:1
Serious — 22 finding(s)
- End-of-life runtime: .NET net6.0 REDACTED:4
- End-of-life runtime: .NET net6.0 src/NodeCli/Cli/NodeCli.fsproj:5
- End-of-life runtime: .NET net6.0 src/SourceGenerator/Tests/Tests.fsproj:4
- End-of-life runtime: .NET net6.0 src/TypeProvider/ProviderTests.Nuget/ProviderTests.Nuget.fsproj:4
- End-of-life runtime: .NET net6.0 src/TypeProvider/Tests/Tests.fsproj:4
- End-of-life runtime: .NET net7.0 src/SourceGenerator/GeneratorTests.Nuget/GeneratorTests.Nuget.csproj:5
- UncheckedQuotations.|ShapeCombinationUnchecked|ShapeVarUnchecked|ShapeLambdaUnchecked| (cyclomatic 42) src/TypeProvider/Trulla.DesignTime/TpSdk/ProvidedTypes.fs:515
- Inference.solveProblems (cyclomatic 27) src/Common/CoreFiles/Inference.fs:95
- AstModule.buildTree (cyclomatic 25) src/Common/CoreFiles/Ast.fs:55
- ReflectionRenderer.renderTemplate (cyclomatic 16) src/Common/CoreFiles/ReflectionRenderer.fs:21
- TodoComment src/SourceGenerator/Trulla.SourceGenerator/TrullaSourceGenerator.cs:24
- UncheckedQuotations.|ShapeCombinationUnchecked|ShapeVarUnchecked|ShapeLambdaUnchecked| (cognitive 59) src/TypeProvider/Trulla.DesignTime/TpSdk/ProvidedTypes.fs:515
- AstModule.buildTree (cognitive 32) src/Common/CoreFiles/Ast.fs:55
- Solver.solveParseResult (cognitive 28) src/Common/CoreFiles/Solver.fs:24
- ReflectionRenderer.renderTemplate (cognitive 19) src/Common/CoreFiles/ReflectionRenderer.fs:21
- Inference.solveProblems (cognitive 19) src/Common/CoreFiles/Inference.fs:95
- ProvidedTypeDefinition.AddAssemblyTypesAsNestedTypesDelayed (cognitive 17) src/TypeProvider/Trulla.DesignTime/TpSdk/ProvidedTypes.fs:1790
- FileTooLong: TpSdk/ProvidedTypes.fs src/TypeProvider/Trulla.DesignTime/TpSdk/ProvidedTypes.fs
- TooManyFunctions: TheBlunt src/Common/CoreFiles/TheBlunt.fs:1
- Low cohesion: TypeProviderForNamespaces (LCOM4 4) src/TypeProvider/Trulla.DesignTime/TpSdk/ProvidedTypes.fs:15861
- No CI pipeline
- NuGet dependencies are not locked
Minor — 23 finding(s)
- Orphaned file src/Common/CoreFiles/TheBlunt.fs:1
- Orphaned file src/Common/CoreFiles/Inference.fs:1
- Orphaned file src/Common/CoreFiles/Ast.fs:1
- Orphaned file src/TypeProvider/Trulla.DesignTime/ProviderCompiler.fs:1
- Orphaned file src/SourceGenerator/Trulla.SourceGenerator.Core/CodeGen/Renderer.fs:1
- Orphaned file src/NodeCli/Cli/CodeGen/Renderer.fs:1
- Orphaned file src/Common/CoreFiles/Parsing.fs:1
- Orphaned file src/Common/CoreFiles/Solver.fs:1
- Orphaned file src/Common/CoreFiles/ReflectionRenderer.fs:1
- Orphaned file src/TypeProvider/ProviderTests.Nuget/Program.fs:1
- Outdated: FSharp.Core src/SourceGenerator/Trulla.SourceGenerator/Trulla.SourceGenerator.csproj:41
- Outdated: coverlet.collector REDACTED:29
- Outdated: FsUnit REDACTED:25
- README/code drift src/NodeCli/Cli/README.md:30
- README/code drift src/NodeCli/Cli/README.md:34
- No ADRs found src/SourceGenerator/GeneratorTests.Nuget/GeneratorTests.Nuget.csproj:4
- Scattered collaborators
- REDACTED
- Further orphaned files (smaller)
- No ADRs
- No SAST
- No dependency-update automation REDACTED:25
- Null-forgiving operator (`!`) suppressions override nullable warnings
Minor — 6 finding(s)
- Outdated: Microsoft.CodeAnalysis
- Outdated: Microsoft.NET.Test.Sdk
- Outdated: NUnit
- Outdated: NUnit3TestAdapter
- Outdated: Fable.Core
- Outdated: Fable.Node
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-8fe7c456de554050aed82bcf0dfef676/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-8fe7c456de554050aed82bcf0dfef676/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 0 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list src/Trulla..sln package --vulnerable --include-transitive --format json | 1 | artifacts/raw/dotnet-vulnerable.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 1 | 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 | — |
| D36 · Supply-chain Provenance & Signing | provenance | — | provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for. | 0 | — |
| D37 · Vulnerability-disclosure 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 | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |