Executive summary
si-informational-systems/Rosetta falls short of our standard for production, in part because we found no automated security scanning of the code, its secrets or its dependencies. It scores 64 out of 100 and is rated Adequate, and all seven of its critical findings are security problems in the build pipeline.
Production Readiness, at 35, is the weakest lens and counts most in the score. The best first step for the work it takes is recording design decisions, worth about 5 points. Planning backups and recovery would lift Production Readiness itself, worth about 8 points. Raising Production Readiness to 70 would lift the score to about 80.
Seven pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Pinning each tool to an exact version would close this risk.
The product code is 7,885 lines, about €14,000 to rebuild.
If Production Readiness rose from 35 to 70, the lowest score rated Strong, the score would rise from 64 to about 80.
New since the last survey: 29 findings
- Code Coverage · Low coverage: SI.Rosetta.Projections/SkipUnknownEventsAttribute.fs SI.Rosetta.Projections/SkipUnknownEventsAttribute.fs
- Code Coverage · Low coverage: SI.Rosetta.Projections/RebuildWithoutClearingAttribute.fs SI.Rosetta.Projections/RebuildWithoutClearingAttribute.fs
- Code Coverage · Low coverage: SI.Rosetta.Projections/CustomProjectionStreamAttribute.fs SI.Rosetta.Projections/CustomProjectionStreamAttribute.fs
- Code Coverage · Low coverage: SI.Rosetta.Projections.KurrentDB/KurrentDBProjectionsHttpApi.fs SI.Rosetta.Projections.KurrentDB/KurrentDBProjectionsHttpApi.fs
- Code Coverage · Low coverage: SI.Rosetta.Projections.KurrentDB/KurrentDBCustomJSProjectionsFactory.fs SI.Rosetta.Projections.KurrentDB/KurrentDBCustomJSProjectionsFactory.fs
- Code Coverage · Low coverage: SI.Rosetta.Projections.KurrentDB/KurrentDBSubscription.fs SI.Rosetta.Projections.KurrentDB/KurrentDBSubscription.fs
- Code Coverage · Low coverage: SI.Rosetta.Projections.KurrentDB/KurrentDBSubscriptionFactory.fs SI.Rosetta.Projections.KurrentDB/KurrentDBSubscriptionFactory.fs
- Code Coverage · Low coverage: SI.Rosetta.Projections.KurrentDB/CustomProjectionDiscovery.fs SI.Rosetta.Projections.KurrentDB/CustomProjectionDiscovery.fs
- Code Coverage · Low coverage: SI.Rosetta.Projections.HostBuilder/ProjectionStores/ProjectionStores.fs SI.Rosetta.Projections.HostBuilder/ProjectionStores/ProjectionStores.fs
- Code Coverage · Low coverage: SI.Rosetta.Projections.HostBuilder/EventRepositories/EventRepositories.fs SI.Rosetta.Projections.HostBuilder/EventRepositories/EventRepositories.fs
- Code Coverage · Low coverage: SI.Rosetta.Projections.RavenDB/RavenDbProjectionsUnitOfWork.fs SI.Rosetta.Projections.RavenDB/RavenDbProjectionsUnitOfWork.fs
- Code Coverage · Low coverage: SI.Rosetta.Projections.RavenDB/RavenDbProjectionsStore.fs SI.Rosetta.Projections.RavenDB/RavenDbProjectionsStore.fs
- Code Coverage · Low coverage: SI.Rosetta.Projections.RavenDB/RavenDbCheckpointStore.fs SI.Rosetta.Projections.RavenDB/RavenDbCheckpointStore.fs
- Code Coverage · Low coverage: SI.Rosetta.Projections.RavenDB/RavenDbRetries.fs SI.Rosetta.Projections.RavenDB/RavenDbRetries.fs
- Code Coverage · Low coverage: SI.Rosetta.Projections.MongoDB/MongoDbCheckpointStore.fs SI.Rosetta.Projections.MongoDB/MongoDbCheckpointStore.fs
- Code Coverage · Low coverage: SI.Rosetta.Projections.PostgreSQL/PostgreSqlCheckpoints.fs SI.Rosetta.Projections.PostgreSQL/PostgreSqlCheckpoints.fs
- Code Coverage · Low coverage: SI.Rosetta.Aggregates.HostBuilder/AggregateRepositories/AggregateRepositories.fs SI.Rosetta.Aggregates.HostBuilder/AggregateRepositories/AggregateRepositories.fs
- Code Coverage · Low coverage: SI.Rosetta.Aggregates.KurrentDB/KurrentDBAggregateRepository.fs SI.Rosetta.Aggregates.KurrentDB/KurrentDBAggregateRepository.fs
- Code Coverage · No test project references Test.Aggregates Test.Aggregates/Test.Aggregates.fsproj
- Code Coverage · No test project references Test.Projections Test.Projections/Test.Projections.fsproj
- Code Coverage · No test project references SI.Rosetta.Aggregates.Template SI.Rosetta.Aggregates.Template/SI.Rosetta.Aggregates.Template.fsproj
- Code Coverage · No test project references Test.PL Test.PL/Test.PL.fsproj
- Code Coverage · No test project references Test.DTOs Test.DTOs/Test.DTOs.csproj
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Supply-chain Provenance & Signing · REDACTED
Fixed since the last survey: 26 findings
- Cognitive Complexity · KurrentDBSubscription`1.HandleEvent (cognitive 18) SI.Rosetta.Projections.KurrentDB/KurrentDBSubscription.fs
- Cognitive Complexity · KurrentDBSubscription`1.SI.Rosetta.Projections.ISubscription<'TEvent>.StartAsync (cognitive 17) SI.Rosetta.Projections.KurrentDB/KurrentDBSubscription.fs
- Cognitive Complexity · AggregateHandler`2.Handle (cognitive 16) SI.Rosetta.Aggregates/AggregateHandler.fs
- Code Duplication · Duplicated block (11 lines × 2) SI.Rosetta.Projections.MongoDB/MongoDbCheckpointStore.fs
- Code Duplication · Duplicated block (11 lines × 2) SI.Rosetta.Projections.MongoDB/MongoDbCheckpointStore.fs
- Code Duplication · Duplicated block (11 lines × 2) SI.Rosetta.Projections.MongoDB/MongoDbProjectionsStore.fs
- Code Duplication · Duplicated block (10 lines × 2) SI.Rosetta.Projections.MongoDB/MongoDbProjectionsStore.fs
- Code Duplication · Duplicated block (10 lines × 2) SI.Rosetta.Projections.MongoDB/MongoDbProjectionsStore.fs
- Code Duplication · Duplicated block (9 lines × 2) SI.Rosetta.Aggregates.HostBuilder/HostBuilderExtensions.fs
- Code Duplication · Duplicated block (9 lines × 2) SI.Rosetta.Projections.HostBuilder/HostBuilderExtensions.fs
- Code Duplication · Duplicated block (8 lines × 2) SI.Rosetta.Projections.MongoDB/MongoDbProjectionsStore.fs
- Code Duplication · Duplicated block (7 lines × 2) SI.Rosetta.Projections.MongoDB/MongoDbProjectionsStore.fs
- Code Duplication · Duplicated block (5 lines × 3) SI.Rosetta.Aggregates.HostBuilder/HostBuilderExtensions.fs
- Code Duplication · Duplicated block (5 lines × 3) SI.Rosetta.Projections.HostBuilder/HostBuilderExtensions.fs
- Code Duplication · Duplicated block (5 lines × 2) SI.Rosetta.Aggregates.HostBuilder/HostBuilderExtensions.fs
- Code Duplication · Duplicated block (5 lines × 2) SI.Rosetta.Projections.HostBuilder/HostBuilderExtensions.fs
- Code Duplication · Duplicated block (5 lines × 2) SI.Rosetta.Projections.MongoDB/MongoDbCheckpointStore.fs
- Code Duplication · Duplicated block (8 lines × 2) SI.Rosetta.Projections/CustomProjectionStreamAttribute.fs
- Code Duplication · Duplicated block (10 lines × 2) Test.Projections/Projections/TotalPeopleCustomProjection.fs
- Supply-chain Provenance & Signing · Workflow token permissions not restricted REDACTED
- Encapsulated state · Mutable entity: Aggregate`2 SI.Rosetta.Aggregates/Aggregate.fs
- Domain ↔ infrastructure boundary · Domain uses infrastructure in a method body: HostBuilderMongoDBExtensionCommmon SI.Rosetta.Aggregates.HostBuilder/HostBuilderExtensions.fs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: MongoDBAggregateRepository SI.Rosetta.Aggregates.MongoDB/MongoDBAggregateRepository.fs
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: MongoDBOutbox SI.Rosetta.Aggregates.MongoDB/MongoDBOutbox.fs
- Ambient inputs in the domain · Domain type reads the wall clock: AggregateHandler`2 SI.Rosetta.Aggregates/AggregateHandler.fs
- Ambient inputs in the domain · Domain type reads the wall clock: OutboxEvents SI.Rosetta.Aggregates/Outbox.fs
Rebuild cost: about €14,000 · Estimate
| Cost to rebuild | €4,500 to €23,000, for 75 to 238 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.9 at a score of 64. 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: 7,885 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 7 | High / Critical |
| A02:2025 — Security Misconfiguration | 2 | Medium |
Roadmap
Top priorities: Resolve the 1 finding(s) in DR & Backup; Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Test.Aggregates.fsproj; Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Test.Aggregates.fsproj. | +5.5 pts | Low | ADR Quality |
| Resolve the 1 finding(s) in DR & Backup. | +8.0 pts | Medium | DR & Backup |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +3.8 pts | Medium | Architecture documentation |
| Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding. | +2.8 pts | Medium | Deployment & Rollback |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +2.8 pts | Medium | Release Hygiene |
| Resolve the 18 Low coverage finding(s) in Code Coverage — start with SkipUnknownEventsAttribute.fs, RebuildWithoutClearingAttribute.fs, CustomProjectionStreamAttribute.fs. | +1.2 pts | Medium | Code Coverage |
| Resolve the 1 No test project references Test.Aggregates finding(s) in Code Coverage — start with Test.Aggregates.fsproj. | +0.1 pts | Low | Code Coverage |
| Resolve the 1 No test project references Test.Projections finding(s) in Code Coverage — start with Test.Projections.fsproj. | +0.1 pts | Low | Code Coverage |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.6 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 6.9 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| Test.Aggregates/Test.Aggregates.fsproj | 8.0 | Near-clean | Code Coverage: No test project references Test.Aggregates |
| SI.Rosetta.Projections/SkipUnknownEventsAttribute.fs | 8.5 | Near-clean | Code Coverage: Low coverage: SI.Rosetta.Projections/SkipUnknownEventsAttribute.fs |
| SI.Rosetta.Projections/RebuildWithoutClearingAttribute.fs | 8.5 | Near-clean | Code Coverage: Low coverage: SI.Rosetta.Projections/RebuildWithoutClearingAttribute.fs |
| SI.Rosetta.Projections/CustomProjectionStreamAttribute.fs | 8.5 | Near-clean | Code Coverage: Low coverage: SI.Rosetta.Projections/CustomProjectionStreamAttribute.fs |
| SI.Rosetta.Projections.KurrentDB/KurrentDBProjectionsHttpApi.fs | 8.5 | Near-clean | Code Coverage: Low coverage: SI.Rosetta.Projections.KurrentDB/KurrentDBProjectionsHttpApi.fs |
| SI.Rosetta.Projections.KurrentDB/KurrentDBCustomJSProjectionsFactory.fs | 8.5 | Near-clean | Code Coverage: Low coverage: SI.Rosetta.Projections.KurrentDB/KurrentDBCustomJSProjectionsFactory.fs |
| SI.Rosetta.Projections.KurrentDB/KurrentDBSubscription.fs | 8.5 | Near-clean | Code Coverage: Low coverage: SI.Rosetta.Projections.KurrentDB/KurrentDBSubscription.fs |
| SI.Rosetta.Projections.KurrentDB/KurrentDBSubscriptionFactory.fs | 8.5 | Near-clean | Code Coverage: Low coverage: SI.Rosetta.Projections.KurrentDB/KurrentDBSubscriptionFactory.fs |
| SI.Rosetta.Projections.KurrentDB/CustomProjectionDiscovery.fs | 8.5 | Near-clean | Code Coverage: Low coverage: SI.Rosetta.Projections.KurrentDB/CustomProjectionDiscovery.fs |
| SI.Rosetta.Projections.HostBuilder/ProjectionStores/ProjectionStores.fs | 8.5 | Near-clean | Code Coverage: Low coverage: SI.Rosetta.Projections.HostBuilder/ProjectionStores/ProjectionStores.fs |
| SI.Rosetta.Projections.HostBuilder/EventRepositories/EventRepositories.fs | 8.5 | Near-clean | Code Coverage: Low coverage: SI.Rosetta.Projections.HostBuilder/EventRepositories/EventRepositories.fs |
| SI.Rosetta.Projections.RavenDB/RavenDbProjectionsUnitOfWork.fs | 8.5 | Near-clean | Code Coverage: Low coverage: SI.Rosetta.Projections.RavenDB/RavenDbProjectionsUnitOfWork.fs |
| SI.Rosetta.Projections.RavenDB/RavenDbProjectionsStore.fs | 8.5 | Near-clean | Code Coverage: Low coverage: SI.Rosetta.Projections.RavenDB/RavenDbProjectionsStore.fs |
| SI.Rosetta.Projections.RavenDB/RavenDbCheckpointStore.fs | 8.5 | Near-clean | Code Coverage: Low coverage: SI.Rosetta.Projections.RavenDB/RavenDbCheckpointStore.fs |
| SI.Rosetta.Projections.RavenDB/RavenDbRetries.fs | 8.5 | Near-clean | Code Coverage: Low coverage: SI.Rosetta.Projections.RavenDB/RavenDbRetries.fs |
| SI.Rosetta.Projections.MongoDB/MongoDbCheckpointStore.fs | 8.5 | Near-clean | Code Coverage: Low coverage: SI.Rosetta.Projections.MongoDB/MongoDbCheckpointStore.fs |
| SI.Rosetta.Projections.PostgreSQL/PostgreSqlCheckpoints.fs | 8.5 | Near-clean | Code Coverage: Low coverage: SI.Rosetta.Projections.PostgreSQL/PostgreSqlCheckpoints.fs |
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 30 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 — 30 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, 36 of 42 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
- D1 Cyclomatic Complexity — 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. Most of this repository's production source (.fs) had no cyclomatic complexity computed for it: no method bodies were exposed for those file kinds by any language model this pass could load.
- D2 Cognitive Complexity — 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. Most of this repository's production source (.fs) had no cognitive complexity computed for it: no method bodies were exposed for those file kinds by any language model this pass could load.
- 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. Most of this repository's production source (.fs) was not read by duplication detection: no source of those file kinds was exposed to the token comparison by any language model this pass could load.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT MEASURED: the test run produced no results for any test tier, so no test ever ran and flakiness could not be exercised. The cause could not be attributed, so it is excluded from the score rather than read as an absence of tests.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: `dotnet list package` exited 1 with no output.
- D15 Churn × Complexity Hotspots — 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. A hotspot is churn × complexity. Churn was measured (25212 line(s) across the 90-day window), but no complexity could be computed for .fs, which is most of this repository's production code — so every churned file would score as complexity 0 and the hotspot list would be empty no matter how tangled the code is. Not scored — this is a gap in the analysis run, not a finding about this repository.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-contributor repository — bus factor is not applicable (1 contributor(s) across 102 commit(s) sampled, automation and bot accounts excluded). Concentration needs a team to concentrate: with one contributor there is nobody to spread the knowledge to, so there is nothing here for the owner to act on.
- D17 Explicit Debt — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Cannot open project 'SI.Rosetta.Aggregates/SI.Rosetta.Aggregates.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 0 deducted marker(s) and the 0.0/KLoC density on this row were taken over this repository's .NET projects ALONE: .fs (7,871 lines, 100% 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.
- 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.
- 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.
- Production source was not modelled — run is Degraded — No code model read .fs, so the complexity, duplication and architecture dimensions were scored over a minority of this repository rather than its product, and dimensions that abstained did so for want of a model rather than for want of findings. The grade is NOT representative of this repository; diagnostics.md records the exact cause. The F# sidecar did not produce a code model, so the F# code model degraded to null; the engine recorded no reason.
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
- 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.
- 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.
- 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.
- 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").
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- 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".
- P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D5 · Coupling
1 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D8 · Code Coverage
Line coverage 70.2% — 18 file(s) below 50%.
What to do
- Resolve the 18 Low coverage finding(s) in Code Coverage — start with SkipUnknownEventsAttribute.fs, RebuildWithoutClearingAttribute.fs, CustomProjectionStreamAttribute.fs. — One of this dimension's main actionable groups (18 warning-level).
- Resolve the 1 No test project references Test.Aggregates finding(s) in Code Coverage — start with Test.Aggregates.fsproj. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 No test project references Test.Projections finding(s) in Code Coverage — start with Test.Projections.fsproj. — One of this dimension's main actionable groups (1 warning-level).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 211 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 25 direct `PackageReference`(s), and 186 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.
D17 · Explicit Debt
0 deducted debt markers + unmeasured dead symbols across 14 LoC in the .NET projects (0.0/KLoC) → score 10.0. Dead code not measured: the solution did not load cleanly, so the reference search was skipped. Measured on the .NET source only: .fs (100% of production source) was not read, and carries at least 0 uncounted task marker(s) in 0 file(s).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 29 document(s) read across 1 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 Test.Aggregates.fsproj. — 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)
7 finding(s): 0 critical, 7 high, 0 medium, 0 low. 7 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens.
What to do
- No action in Static Analysis (SAST) — all 7 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (7 issue-level, 0 of them charged here).
D31 · IaC & Container Security
2 finding(s): 0 critical, 0 high, 2 medium, 0 low.
What to do
- Resolve the 2 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 54 of the 124 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
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 30 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX5 · Architecture & structure
AX8 · Test isolation
GD1 · Unfinished & placeholder code
M1 · Documentation (README)
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) as a CI step. What was searched, so you can tell an absence from a miss: the 2 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:6
- `SI.Rosetta.Aggregates.KurrentDB/SI.Rosetta.Aggregates.KurrentDB.fsproj` 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`. — SI.Rosetta.Aggregates.KurrentDB/SI.Rosetta.Aggregates.KurrentDB.fsproj:13
What to do
- Add a SAST step to CI running what this repository's stack ships: `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
What to do
- Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding.
P5 · DR & Backup
- A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
X5 · Nullable reference types
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 100% | Checked 2 of 5 | Strongest area. |
| Architecture | 100% | Exemplary | Solid. |
| Maturity | 79% | Strong | Solid. |
| Readiness | 35% | Weak — gated by P3, P5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 100% | Exemplary | Solid. |
Unscored — 2 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Not included — 83 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
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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.
- D1 Cyclomatic Complexity — cyclomatic complexity not measured — .fs exposed no member bodies
- D10 Test Quality — ~6025 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
- D12 Dependency Hygiene — Dependency hygiene not measured
- D15 Churn × Complexity Hotspots — complexity unreadable for .fs — churn × complexity hotspots could not be measured
- D16 Bus Factor — single-contributor repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution, but this repository's production source is mostly .fs, which the C#/VB workspace does not load — the projects that loaded are an immaterial minority, so solution shape was not assessed for this repository. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
- D2 Cognitive Complexity — cognitive complexity not measured — .fs exposed no member bodies
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (7 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — small single-context codebase (14 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
- D26 Project Cohesion — This repository is one project, `Test.DTOs` (14 LoC, 2 public types across 1 namespaces), within the size bounds. Not scored: a single unit of this size gives project cohesion nothing to grade.
- D27 Navigability — No calls could be sampled, so navigability was not assessed — tracing effort is measured over resolved call sites and this target exposed none. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
- D3 God Classes — Most of this repository's production source (.fs) was not read by god-class detection, so class size was not assessed for the languages that are the product — whatever else this pass did read is not this repository's class size. Not scored — this is a gap in the analyzer, not a verdict about this repository.
- D30 Dependency Vulnerabilities — nuget: `dotnet list package --vulnerable` could not read this solution's dependency graph — it reported an error for at least one project and returned no package data at all (typically a packages.config / non-PackageReference project, which the command cannot read). An unreadable dependency graph is not a clean one; migrate the project(s) to PackageReference to enable this 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.
- 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 — Duplication not measured — .fs not exposed to the token comparison
- 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 2 type(s) found, none both holds instance state and has two or more methods whose shared use of it could be read (2 with fewer than two methods), 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 none of the 3 signals this lens looks for
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- IC1 Incompleteness & stubs — reported, not scored — this repository's C# declares no analysable method bodies (a constants, record or DTO assembly), and this score is a density of unfinished work per method, which has no denominator here. The file-level signals below were still collected and are shown in full
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- 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 data present for 82 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
- 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.
- PF3 Async & latency hygiene — 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.
- 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
- 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 — 7 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 28 finding(s)
- Low coverage: SI.Rosetta.Projections/SkipUnknownEventsAttribute.fs SI.Rosetta.Projections/SkipUnknownEventsAttribute.fs:1
- Low coverage: SI.Rosetta.Projections/RebuildWithoutClearingAttribute.fs SI.Rosetta.Projections/RebuildWithoutClearingAttribute.fs:1
- Low coverage: SI.Rosetta.Projections/CustomProjectionStreamAttribute.fs SI.Rosetta.Projections/CustomProjectionStreamAttribute.fs:1
- Low coverage: SI.Rosetta.Projections.KurrentDB/KurrentDBProjectionsHttpApi.fs SI.Rosetta.Projections.KurrentDB/KurrentDBProjectionsHttpApi.fs:1
- Low coverage: SI.Rosetta.Projections.KurrentDB/KurrentDBCustomJSProjectionsFactory.fs SI.Rosetta.Projections.KurrentDB/KurrentDBCustomJSProjectionsFactory.fs:1
- Low coverage: SI.Rosetta.Projections.KurrentDB/KurrentDBSubscription.fs SI.Rosetta.Projections.KurrentDB/KurrentDBSubscription.fs:1
- Low coverage: SI.Rosetta.Projections.KurrentDB/KurrentDBSubscriptionFactory.fs SI.Rosetta.Projections.KurrentDB/KurrentDBSubscriptionFactory.fs:1
- Low coverage: SI.Rosetta.Projections.KurrentDB/CustomProjectionDiscovery.fs SI.Rosetta.Projections.KurrentDB/CustomProjectionDiscovery.fs:1
- Low coverage: SI.Rosetta.Projections.HostBuilder/ProjectionStores/ProjectionStores.fs SI.Rosetta.Projections.HostBuilder/ProjectionStores/ProjectionStores.fs:1
- Low coverage: SI.Rosetta.Projections.HostBuilder/EventRepositories/EventRepositories.fs SI.Rosetta.Projections.HostBuilder/EventRepositories/EventRepositories.fs:1
- Low coverage: SI.Rosetta.Projections.RavenDB/RavenDbProjectionsUnitOfWork.fs SI.Rosetta.Projections.RavenDB/RavenDbProjectionsUnitOfWork.fs:1
- Low coverage: SI.Rosetta.Projections.RavenDB/RavenDbProjectionsStore.fs SI.Rosetta.Projections.RavenDB/RavenDbProjectionsStore.fs:1
- Low coverage: SI.Rosetta.Projections.RavenDB/RavenDbCheckpointStore.fs SI.Rosetta.Projections.RavenDB/RavenDbCheckpointStore.fs:1
- Low coverage: SI.Rosetta.Projections.RavenDB/RavenDbRetries.fs SI.Rosetta.Projections.RavenDB/RavenDbRetries.fs:1
- Low coverage: SI.Rosetta.Projections.MongoDB/MongoDbCheckpointStore.fs SI.Rosetta.Projections.MongoDB/MongoDbCheckpointStore.fs:1
- Low coverage: SI.Rosetta.Projections.PostgreSQL/PostgreSqlCheckpoints.fs SI.Rosetta.Projections.PostgreSQL/PostgreSqlCheckpoints.fs:1
- Low coverage: SI.Rosetta.Aggregates.HostBuilder/AggregateRepositories/AggregateRepositories.fs SI.Rosetta.Aggregates.HostBuilder/AggregateRepositories/AggregateRepositories.fs:1
- Low coverage: SI.Rosetta.Aggregates.KurrentDB/KurrentDBAggregateRepository.fs SI.Rosetta.Aggregates.KurrentDB/KurrentDBAggregateRepository.fs:1
- REDACTED
- REDACTED
- REDACTED
- No test project references Test.Aggregates Test.Aggregates/Test.Aggregates.fsproj
- No test project references Test.Projections Test.Projections/Test.Projections.fsproj
- No test project references SI.Rosetta.Aggregates.Template SI.Rosetta.Aggregates.Template/SI.Rosetta.Aggregates.Template.fsproj
- No test project references Test.PL Test.PL/Test.PL.fsproj
- No test project references Test.DTOs Test.DTOs/Test.DTOs.csproj
- No DR/backup evidence
- NuGet dependencies are not locked
Minor — 7 finding(s)
- No ADRs found Test.Aggregates/Test.Aggregates.fsproj:4
- REDACTED
- No ADRs
- No SAST REDACTED:6
- No dependency-update automation SI.Rosetta.Aggregates.KurrentDB/SI.Rosetta.Aggregates.KurrentDB.fsproj:13
- No rollback/health safety
- No changelog
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-71c66580cc4f44859f9b9158cff57b45/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-71c66580cc4f44859f9b9158cff57b45/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 . | 7 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | nuget | — | nuget: not applicable — nuget: `dotnet list package --vulnerable` could not read this solution's dependency graph — it reported an error for at least one project and returned no package data at all (typically a packages.config / non-PackageReference project, which the command cannot read). An unreadable dependency graph is not a clean one; migrate the project(s) to PackageReference to enable this scan | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 2 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-32c3485c88e34311ba1c073d03451110 | 0 | artifacts/raw/osv-scanner.json |