Executive summary
context-and-oss/XrmContext falls short of our standard for production because the project has no automated tests and we found no logging, tracing or health checks in the code. It scores 45 out of 100 and is rated Weak, and one of its two critical findings is a security problem in the packages it uses.
Production Readiness, at 30, is the weakest lens and counts most in the score. The best first step for the work it takes is recording design decisions, worth about 10 points. Adding automated tests would lift Production Readiness itself, worth about 15 points. Raising Production Readiness to 70 would lift the score to about 56.
One known security hole in a package the code depends on can be used by attackers. The project has no automated tests, so a change can break it without warning. Adding automated tests and updating the vulnerable packages would close both risks.
The product code is 2,618 lines, about €2,500 to rebuild.
If Production Readiness rose from 30 to 70, the lowest score rated Strong, the score would rise from 45 to about 56.
Rebuild cost: about €2,500 · Estimate
| Cost to rebuild | €830 to €4,200, for 14 to 44 hours of work, under 0.1 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.7 at a score of 45. 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: 2,618 lines of product code |
| Comment lines | The estimate prices 2,608 lines. Comment lines count towards the size of 2,618 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: which parts of the code depend on which
| uses → | 1 DG.XrmContext | 2 DG.XrmContext.CrmAuth | 3 DG.XrmContext.CrmNameHelper | 4 DG.XrmContext.IntermediateRepresentation | 5 DG.XrmContext.Utility | 6 System.AssemblyVersionInformation | 7 docs.files.res | 8 docs.tools.templates.res | 9 DG.XrmContext.CodeDomHelper | 10 DG.XrmContext.CommandLineHelper | 11 DG.XrmContext.CrmBaseHelper | 12 DG.XrmContext.DataRetrieval | 13 DG.XrmContext.FileGeneration | 14 DG.XrmContext.GenerationMain | 15 DG.XrmContext.InterpretEntityMetadata | 16 DG.XrmContext.InterpretOptionSetMetadata | 17 DG.XrmContext.Setup | 18 DG.XrmContext.XrmCodeDom | 19 Program |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 DG.XrmContext | |||||||||||||||||||
| 2 DG.XrmContext.CrmAuth | |||||||||||||||||||
| 3 DG.XrmContext.CrmNameHelper | |||||||||||||||||||
| 4 DG.XrmContext.IntermediateRepresentation | |||||||||||||||||||
| 5 DG.XrmContext.Utility | |||||||||||||||||||
| 6 System.AssemblyVersionInformation | |||||||||||||||||||
| 7 docs.files.res | |||||||||||||||||||
| 8 docs.tools.templates.res | |||||||||||||||||||
| 9 DG.XrmContext.CodeDomHelper | 1 | ||||||||||||||||||
| 10 DG.XrmContext.CommandLineHelper | 1 | ||||||||||||||||||
| 11 DG.XrmContext.CrmBaseHelper | 1 | ||||||||||||||||||
| 12 DG.XrmContext.DataRetrieval | 2 | ||||||||||||||||||
| 13 DG.XrmContext.FileGeneration | 1 | ||||||||||||||||||
| 14 DG.XrmContext.GenerationMain | 4 | ||||||||||||||||||
| 15 DG.XrmContext.InterpretEntityMetadata | 4 | ||||||||||||||||||
| 16 DG.XrmContext.InterpretOptionSetMetadata | 4 | ||||||||||||||||||
| 17 DG.XrmContext.Setup | 2 | 3 | |||||||||||||||||
| 18 DG.XrmContext.XrmCodeDom | 5 | ||||||||||||||||||
| 19 Program | 3 |
9→4 DG.XrmContext.CodeDomHelper uses DG.XrmContext.IntermediateRepresentation✕
- Connections
- 1 pair of types, where a type in DG.XrmContext.CodeDomHelper uses a type in DG.XrmContext.IntermediateRepresentation.
- The types involved
DG.XrmContext.CodeDomHelper.CodeDomHelper→DG.XrmContext.IntermediateRepresentation.XrmAttributeType
- Direction
- DG.XrmContext.CodeDomHelper uses DG.XrmContext.IntermediateRepresentation, so a change to DG.XrmContext.IntermediateRepresentation can break DG.XrmContext.CodeDomHelper, while a change to DG.XrmContext.CodeDomHelper can't break DG.XrmContext.IntermediateRepresentation.
- Position
- Below the diagonal: DG.XrmContext.CodeDomHelper uses a module listed above it, which is the healthy direction.
10→1 DG.XrmContext.CommandLineHelper uses DG.XrmContext✕
- Connections
- 1 pair of types, where a type in DG.XrmContext.CommandLineHelper uses a type in DG.XrmContext.
- The types involved
DG.XrmContext.CommandLineHelper.CommandLineHelper→DG.XrmContext.ArgInfo
- Direction
- DG.XrmContext.CommandLineHelper uses DG.XrmContext, so a change to DG.XrmContext can break DG.XrmContext.CommandLineHelper, while a change to DG.XrmContext.CommandLineHelper can't break DG.XrmContext.
- Position
- Below the diagonal: DG.XrmContext.CommandLineHelper uses a module listed above it, which is the healthy direction.
11→1 DG.XrmContext.CrmBaseHelper uses DG.XrmContext✕
- Connections
- 1 pair of types, where a type in DG.XrmContext.CrmBaseHelper uses a type in DG.XrmContext.
- The types involved
DG.XrmContext.CrmBaseHelper.CrmBaseHelper→DG.XrmContext.XrmAuthentication
- Direction
- DG.XrmContext.CrmBaseHelper uses DG.XrmContext, so a change to DG.XrmContext can break DG.XrmContext.CrmBaseHelper, while a change to DG.XrmContext.CrmBaseHelper can't break DG.XrmContext.
- Position
- Below the diagonal: DG.XrmContext.CrmBaseHelper uses a module listed above it, which is the healthy direction.
12→1 DG.XrmContext.DataRetrieval uses DG.XrmContext✕
- Connections
- 2 pairs of types, where a type in DG.XrmContext.DataRetrieval uses a type in DG.XrmContext.
- The types involved
DG.XrmContext.DataRetrieval.DataRetrieval→DG.XrmContext.RawStateDG.XrmContext.DataRetrieval.DataRetrieval→DG.XrmContext.XrmAuthentication
- Direction
- DG.XrmContext.DataRetrieval uses DG.XrmContext, so a change to DG.XrmContext can break DG.XrmContext.DataRetrieval, while a change to DG.XrmContext.DataRetrieval can't break DG.XrmContext.
- Position
- Below the diagonal: DG.XrmContext.DataRetrieval uses a module listed above it, which is the healthy direction.
13→4 DG.XrmContext.FileGeneration uses DG.XrmContext.IntermediateRepresentation✕
- Connections
- 1 pair of types, where a type in DG.XrmContext.FileGeneration uses a type in DG.XrmContext.IntermediateRepresentation.
- The types involved
DG.XrmContext.FileGeneration.FileGeneration→DG.XrmContext.IntermediateRepresentation.InterpretedState
- Direction
- DG.XrmContext.FileGeneration uses DG.XrmContext.IntermediateRepresentation, so a change to DG.XrmContext.IntermediateRepresentation can break DG.XrmContext.FileGeneration, while a change to DG.XrmContext.FileGeneration can't break DG.XrmContext.IntermediateRepresentation.
- Position
- Below the diagonal: DG.XrmContext.FileGeneration uses a module listed above it, which is the healthy direction.
14→1 DG.XrmContext.GenerationMain uses DG.XrmContext✕
- Connections
- 4 pairs of types, where a type in DG.XrmContext.GenerationMain uses a type in DG.XrmContext.
- The types involved
DG.XrmContext.GenerationMain.GenerationMain→DG.XrmContext.RawStateDG.XrmContext.GenerationMain.GenerationMain→DG.XrmContext.XcGenerationSettingsDG.XrmContext.GenerationMain.GenerationMain→DG.XrmContext.XcRetrievalSettingsDG.XrmContext.GenerationMain.GenerationMain→DG.XrmContext.XrmAuthentication
- Direction
- DG.XrmContext.GenerationMain uses DG.XrmContext, so a change to DG.XrmContext can break DG.XrmContext.GenerationMain, while a change to DG.XrmContext.GenerationMain can't break DG.XrmContext.
- Position
- Below the diagonal: DG.XrmContext.GenerationMain uses a module listed above it, which is the healthy direction.
15→4 DG.XrmContext.InterpretEntityMetadata uses DG.XrmContext.IntermediateRepresentation✕
- Connections
- 4 pairs of types, where a type in DG.XrmContext.InterpretEntityMetadata uses a type in DG.XrmContext.IntermediateRepresentation.
- The types involved
DG.XrmContext.InterpretEntityMetadata.InterpretEntityMetadata→DG.XrmContext.IntermediateRepresentation.XrmAlternateKeyDG.XrmContext.InterpretEntityMetadata.InterpretEntityMetadata→DG.XrmContext.IntermediateRepresentation.XrmAttributeTypeDG.XrmContext.InterpretEntityMetadata.InterpretEntityMetadata→DG.XrmContext.IntermediateRepresentation.XrmEntityDG.XrmContext.InterpretEntityMetadata.InterpretEntityMetadata→DG.XrmContext.IntermediateRepresentation.XrmOptionSet
- Direction
- DG.XrmContext.InterpretEntityMetadata uses DG.XrmContext.IntermediateRepresentation, so a change to DG.XrmContext.IntermediateRepresentation can break DG.XrmContext.InterpretEntityMetadata, while a change to DG.XrmContext.InterpretEntityMetadata can't break DG.XrmContext.IntermediateRepresentation.
- Position
- Below the diagonal: DG.XrmContext.InterpretEntityMetadata uses a module listed above it, which is the healthy direction.
16→4 DG.XrmContext.InterpretOptionSetMetadata uses DG.XrmContext.IntermediateRepresentation✕
- Connections
- 4 pairs of types, where a type in DG.XrmContext.InterpretOptionSetMetadata uses a type in DG.XrmContext.IntermediateRepresentation.
- The types involved
DG.XrmContext.InterpretOptionSetMetadata.InterpretOptionSetMetadata→DG.XrmContext.IntermediateRepresentation.XrmOptionDG.XrmContext.InterpretOptionSetMetadata.InterpretOptionSetMetadata→DG.XrmContext.IntermediateRepresentation.XrmOptionLocalizedDG.XrmContext.InterpretOptionSetMetadata.InterpretOptionSetMetadata→DG.XrmContext.IntermediateRepresentation.XrmOptionSetDG.XrmContext.InterpretOptionSetMetadata.InterpretOptionSetMetadata→DG.XrmContext.IntermediateRepresentation.XrmOptionSetType
- Direction
- DG.XrmContext.InterpretOptionSetMetadata uses DG.XrmContext.IntermediateRepresentation, so a change to DG.XrmContext.IntermediateRepresentation can break DG.XrmContext.InterpretOptionSetMetadata, while a change to DG.XrmContext.InterpretOptionSetMetadata can't break DG.XrmContext.IntermediateRepresentation.
- Position
- Below the diagonal: DG.XrmContext.InterpretOptionSetMetadata uses a module listed above it, which is the healthy direction.
17→1 DG.XrmContext.Setup uses DG.XrmContext✕
- Connections
- 2 pairs of types, where a type in DG.XrmContext.Setup uses a type in DG.XrmContext.
- The types involved
DG.XrmContext.Setup.Setup→DG.XrmContext.RawStateDG.XrmContext.Setup.Setup→DG.XrmContext.XcGenerationSettings
- Direction
- DG.XrmContext.Setup uses DG.XrmContext, so a change to DG.XrmContext can break DG.XrmContext.Setup, while a change to DG.XrmContext.Setup can't break DG.XrmContext.
- Position
- Below the diagonal: DG.XrmContext.Setup uses a module listed above it, which is the healthy direction.
17→4 DG.XrmContext.Setup uses DG.XrmContext.IntermediateRepresentation✕
- Connections
- 3 pairs of types, where a type in DG.XrmContext.Setup uses a type in DG.XrmContext.IntermediateRepresentation.
- The types involved
DG.XrmContext.Setup.Setup→DG.XrmContext.IntermediateRepresentation.InterpretedStateDG.XrmContext.Setup.Setup→DG.XrmContext.IntermediateRepresentation.XrmAttributeDG.XrmContext.Setup.Setup→DG.XrmContext.IntermediateRepresentation.XrmEntity
- Direction
- DG.XrmContext.Setup uses DG.XrmContext.IntermediateRepresentation, so a change to DG.XrmContext.IntermediateRepresentation can break DG.XrmContext.Setup, while a change to DG.XrmContext.Setup can't break DG.XrmContext.IntermediateRepresentation.
- Position
- Below the diagonal: DG.XrmContext.Setup uses a module listed above it, which is the healthy direction.
18→4 DG.XrmContext.XrmCodeDom uses DG.XrmContext.IntermediateRepresentation✕
- Connections
- 5 pairs of types, where a type in DG.XrmContext.XrmCodeDom uses a type in DG.XrmContext.IntermediateRepresentation.
- The types involved
DG.XrmContext.XrmCodeDom.XrmCodeDom→DG.XrmContext.IntermediateRepresentation.XrmAlternateKeyDG.XrmContext.XrmCodeDom.XrmCodeDom→DG.XrmContext.IntermediateRepresentation.XrmAttributeDG.XrmContext.XrmCodeDom.XrmCodeDom→DG.XrmContext.IntermediateRepresentation.XrmEntityDG.XrmContext.XrmCodeDom.XrmCodeDom→DG.XrmContext.IntermediateRepresentation.XrmOptionSetDG.XrmContext.XrmCodeDom.XrmCodeDom→DG.XrmContext.IntermediateRepresentation.XrmRelationship
- Direction
- DG.XrmContext.XrmCodeDom uses DG.XrmContext.IntermediateRepresentation, so a change to DG.XrmContext.IntermediateRepresentation can break DG.XrmContext.XrmCodeDom, while a change to DG.XrmContext.XrmCodeDom can't break DG.XrmContext.IntermediateRepresentation.
- Position
- Below the diagonal: DG.XrmContext.XrmCodeDom uses a module listed above it, which is the healthy direction.
19→1 Program uses DG.XrmContext✕
- Connections
- 3 pairs of types, where a type in Program uses a type in DG.XrmContext.
- The types involved
Program.Program→DG.XrmContext.XcGenerationSettingsProgram.Program→DG.XrmContext.XcRetrievalSettingsProgram.Program→DG.XrmContext.XrmAuthentication
- Direction
- Program uses DG.XrmContext, so a change to DG.XrmContext can break Program, while a change to Program can't break DG.XrmContext.
- Position
- Below the diagonal: Program 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 | 2 | High / Critical |
Roadmap
Top priorities: Resolve the 1 No automated tests finding(s) in Code Coverage; Resolve the 1 No ADRs found finding(s) in ADR Quality — start with REDACTED; Resolve the 14 Orphaned file finding(s) in Knowledge Freshness — start with XrmCodeDom.fs, XrmExtensions.cs, InterpretEntityMetadata.fs.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with REDACTED. | +9.9 pts | Low | ADR Quality |
| Resolve the 14 Orphaned file finding(s) in Knowledge Freshness — start with XrmCodeDom.fs, XrmExtensions.cs, InterpretEntityMetadata.fs. | +8.0 pts | Medium | Knowledge Freshness |
| Resolve the 1 No automated tests finding(s) in Code Coverage. | +14.6 pts | High | Code Coverage |
| Where a method uses `?.` on a symbol and then dereferences it directly, settle the question once: test it before the first use and handle null, or drop the `?.`. | +6.3 pts | Medium | Nullable reference types |
| Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce. | +6.0 pts | Medium | Observability |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +5.5 pts | Medium | Architecture documentation |
| Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. | +0.8 pts | Low | Knowledge Freshness |
| Run the test suite in CI via an explicit runner step for your stack, and gate merges on it. | +1.7 pts | Medium | CI/CD gates |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 4.1 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| src/XrmContext/Interpretation/InterpretEntityMetadata.fs | 8.5 | Near-clean | Cognitive Complexity: InterpretEntityMetadata.interpretAttribute (cognitive 22) |
| src/XrmContext/CodeDom/CodeDomHelper.fs | 8.5 | Near-clean | God Classes: TooManyFunctions: CodeDomHelper |
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 32 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 — 32 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, 23 of 34 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- 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 14 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 12 of the 20 production source files in this repository: 6 are under the ~2,400-byte size floor this dimension measures over, and the remaining 2 have no attributable history left to measure.
- D22 Internal API 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. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository DOES commit C#/VB source and a project or solution file, so the conventions are there to read and the load still produced nothing. That is OUR side and it is an ENVIRONMENT fault, not a missing collector: the collector exists and runs on C# constantly, and the remedy is to inspect the restore, the SDK band and the target resolution — not to build anything.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check'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.
- 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.
- 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.
- P8 Schema migrations — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads EF Core usage in C# and the schema tooling its file scan recognises only, and no .NET project was loaded, and this repository's language is not one the scan models, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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.
- 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 repository's C# was parsed (it ships no .sln or .csproj, so it was read as syntax-only projects), but this check proves its findings from resolved symbols and a reference-free parse resolves none. It abstained rather than report a clean bill it could not earn. That is a gap in this analyzer's reach into build-less repositories — not a finding that the repository is free of what this check looks for.
- X28 Index access outside its own emptiness guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check'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.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- 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.
- 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.
- 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.
- 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
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
1 method(s) exceeded the cognitive complexity threshold of 15; the worst was InterpretEntityMetadata.interpretAttribute at 22.
What to do
- Bring the 1 body over 15 down to 15 or less in Cognitive Complexity — start with InterpretEntityMetadata.interpretAttribute (cognitive 22). — Refactoring it lifts Cognitive Complexity from 9.5 to about 10.0/10.
D3 · God Classes
1 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 1 TooManyFunctions finding(s) in God Classes — start with CodeDomHelper.fs. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
0 duplicated block group(s) detected. 0.0 % of the production lines (0 of 2,540) are in a reported copy.
D5 · Coupling
1 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D8 · Code Coverage
No automated tests — no test code was found in this repository.
What to do
- Resolve the 1 No automated tests finding(s) in Code Coverage. — One of this dimension's main actionable groups (1 issue-level).
D12 · Dependency Hygiene
2 outdated, 0 vulnerable, 0 deprecated packages.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 83 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 1 direct `PackageReference`(s), and 82 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.
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
92 % of calls cross a namespace and 1 % go through an interface, but 94 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
semgrep found no security issues.
D30 · Dependency Vulnerabilities
2 finding(s): 0 critical, 1 high, 1 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).
- Resolve the 1 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D34 · Knowledge Freshness
14 of 14 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/XrmContext/CodeDom/XrmCodeDom.fs. Counted over 14 of the 20 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 14 Orphaned file finding(s) in Knowledge Freshness — start with XrmCodeDom.fs, XrmExtensions.cs, InterpretEntityMetadata.fs. — One of this dimension's main actionable groups (14 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge 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
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
GD1 · Unfinished & placeholder code
M1 · Documentation (README)
What to do
- 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.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
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.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
P1 · CI/CD gates
- A CI pipeline exists but no test-runner invocation (your stack's test command, or a test job) was found — changes may merge without the suite running.
What to do
- Run the test suite in CI via an explicit runner step for your stack, and gate merges on it.
P2 · Observability
- No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
What to do
- Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) as a CI step. What was searched, so you can tell an absence from a miss: the 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` 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:81
What to do
- Add a SAST step to CI running what this repository's stack ships: `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
PF3 · Async & latency hygiene
X5 · Nullable reference types
- This method contradicts itself about `resp`: line 319 assigns it with `as UpsertResponse`, which hands back null rather than throwing when the value is not a `UpsertResponse`, but line 320 then dereferences it directly as `resp.Target` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `resp` once before the first use and handle the null case, or cast with `(UpsertResponse)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/XrmContext/Resources/XrmExtensions.cs:320
- This method contradicts itself about `resp`: line 360 assigns it with `as ExecuteMultipleResponse`, which hands back null rather than throwing when the value is not a `ExecuteMultipleResponse`, but line 361 then dereferences it directly as `resp.Responses` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `resp` once before the first use and handle the null case, or cast with `(ExecuteMultipleResponse)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/XrmContext/Resources/XrmExtensions.cs:361
- 0/1 C# file(s) are in a nullable-enabled context. This repository commits no project file, so nothing sets <Nullable>enable</Nullable> for it: a file is enabled only by its own `#nullable enable`, by a Unity `csc.rsp` with `-nullable:enable` for its assembly, or as a file-based app (`#:` directives) whose `#:property Nullable` does not turn it off. NRTs catch a whole class of null-deref bugs at compile time.
What to do
- Where a method uses `?.` on a symbol and then dereferences it directly, settle the question once: test it before the first use and handle null, or drop the `?.`.
- Put every file in a nullable-enabled context — `#nullable enable` at its top, or commit a project file with <Nullable>enable</Nullable> — and resolve warnings rather than suppressing with `!`.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 53% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 100% | Exemplary | Solid. |
| Maturity | 40% | Weak — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 30% | Weak — gated by D8, P2, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 100% | Exemplary | Strongest area. |
| Performance | 100% | Exemplary | Solid. |
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 — 2 control(s) we could not find positive evidence for
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 81 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
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — AX6 reached only 17% of this repository's production lines — fsharp (2,176 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- C1 Data Protection — 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 — No tests were found in the analyzed repository to assess for quality.
- D11 Test Reliability — No test suite was found to re-run, so reliability couldn't be assessed. Two searches produced that zero and both came back empty: the classifier that reads the loaded workspace recognised no suite it could run, and a walk of the source on disk — which covers the JS/TS `*.test.*` and `*.spec.*` conventions and probes for a Pester suite — found no test source in any other ecosystem either. Neither search reaches a suite that is missing from the loaded workspace and carries no name either walk recognises, so this is 'no suite found by those two searches', not a verdict that the repository has none.
- D16 Bus Factor — dormant codebase — no living knowledge left to concentrate
- D17 Explicit Debt — the C# workspace loaded 0 projects, so explicit-debt density could not be measured
- D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution; this repository's .NET projects are all F# (.fsproj), which the C#/VB workspace does not load, so the dimension does not apply.
- D19 Documentation Quality — No runnable or published unit to look for an example in, and no multi-project root README to look for a map in; the other documentation kinds are withheld (see the gaps), so documentation quality is not applicable here.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (654 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .fs source were not judged.
- D25 ADR Conformance — no ADRs to check
- D26 Project Cohesion — Project cohesion is assessed over the .NET project set; this target exposed no projects, so project size and spread could not be assessed. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D36 Supply-chain Provenance & Signing — The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D6 Cohesion (LCOM4) — Cohesion (LCOM4) was not measured: of the 6 type(s) found, none both holds instance state and has two or more methods whose shared use of it could be read (1 with fewer than two methods, 4 stateless, 1 holding only inherited state), so LCOM4 is undefined for every type in this repository. Not scored — the metric does not apply here, and this is not a finding about this repository.
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (13 value object(s))
- 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 (this repository commits no MSBuild project, so its C# was read as syntax-only projects — a handler marked ONLY by an interface from a package is not visible without a build)
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- IC1 Incompleteness & stubs — IC1 reached only 14% of this repository's production lines — fsharp (2,176 lines), javascript (78 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 4 current-state document(s) make no claim of a kind M4 checks.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not measured — the application kind could not be determined for this repo
- P8 Schema migrations — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — 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 — X12 reached only 14% of this repository's production lines — fsharp (2,176 lines), javascript (78 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 — 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 — This check needs a compiled C# program and this repository commits no project file to compile, so only its syntax could be read. That is a limit of the analyzer, not a finding about your code.
- X28 Index access outside its own emptiness guard — X28 reached only 14% of this repository's production lines — fsharp (2,176 lines), javascript (78 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- 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 14% of this repository's production lines — fsharp (2,176 lines), javascript (78 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 — 2 finding(s)
- REDACTED
- No automated tests
Serious — 7 finding(s)
- Symbol treated as nullable, then dereferenced unguarded src/XrmContext/Resources/XrmExtensions.cs:320
- Symbol treated as nullable, then dereferenced unguarded src/XrmContext/Resources/XrmExtensions.cs:361
- InterpretEntityMetadata.interpretAttribute (cognitive 22) src/XrmContext/Interpretation/InterpretEntityMetadata.fs:70
- TooManyFunctions: CodeDomHelper src/XrmContext/CodeDom/CodeDomHelper.fs:1
- REDACTED
- No structured logging
- NuGet dependencies are not locked
Minor — 24 finding(s)
- Orphaned file src/XrmContext/CodeDom/XrmCodeDom.fs:1
- Orphaned file src/XrmContext/Resources/XrmExtensions.cs:1
- Orphaned file src/XrmContext/Interpretation/InterpretEntityMetadata.fs:1
- Orphaned file src/XrmContext/Crm/CrmBaseHelper.fs:1
- Orphaned file src/XrmContext/CommandLine/Arguments.fs:1
- Orphaned file src/XrmContext/CodeDom/CodeDomHelper.fs:1
- Orphaned file src/XrmContext/Program.fs:1
- Orphaned file src/XrmContext/Utility.fs:1
- Orphaned file src/XrmContext/Interpretation/InterpretOptionSetMetadata.fs:1
- Orphaned file src/XrmContext/Generation/FileGeneration.fs:1
- Orphaned file src/XrmContext/Crm/CrmAuth.fs:1
- Orphaned file src/XrmContext/XrmContext.fs:1
- Orphaned file src/XrmContext/CommandLine/CommandLineHelper.fs:1
- Orphaned file src/XrmContext/Generation/Setup.fs:1
- Outdated: FSharp.Core REDACTED:82
- No ADRs found REDACTED:18
- Orphaned files with no living knowledge
- REDACTED
- No ADRs
- No architecture diagram/doc
- CI test execution not evidenced
- No SAST
- No dependency-update automation REDACTED:81
- Nullable reference types not enabled everywhere
Minor — 1 finding(s)
- Outdated: Microsoft.CrmSdk.XrmTooling.CoreAssembly
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-68b6acf69cd049b6a4e0f8318e02791c/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-68b6acf69cd049b6a4e0f8318e02791c/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 XrmContext.sln package --vulnerable --include-transitive --format json | 2 | artifacts/raw/dotnet-vulnerable.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | 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-d789108aff224746afefeb0e1f3b37dd | 0 | artifacts/raw/osv-scanner.json |